Translations Editor only working for files named "strings.xml"? - Android Studio

I'm trying to use the Translations Editor on Android Studio 1.5.1 running on Mac OSx 10.8.5. My projects string resources are divided up into several XML files to make it easier to find the strings. But it seems that I can only get the right click menu option "Open in Translations Editor" when I right click on files named "strings.xml", not for example "translate_preferences.xml". Is there any other way I can open the translations editor for those files?

Related

[HOW-TO] MIUI MiLocker Themeing / Customization

Good Afternoon XDA Family and Friends - Modders and such...
Today, I would like to bring you something of a how to that would possibly get Sticky-d as I think that this app is growing in popularity and customization requests. Due to some demand on our Youtube Partner Channel, we are working on a Video on how to modify and deploy these new themes for this app to your non-rooted phone / device.
Many of you may or may not know about this software: MiLocker - App to allow you to get the MIUI type Themes that are seen on their ROMS on Non-Rooted and Rooted Phones. This app will let you customize your Lockscreen and have that MIUI type theme.
Please note that this tutorial - How To involves basic knowledge of XML and modifications of types of variables that are used in the theme.
I have enclosed 2 Samples that you can use as a basis, I have converted them from Japanese / Chinese language so that you can understand them better.
Some of the basic steps are outlined below.
1. First get the theme downloaded that you wish to modify using the Machine of your choosing: Mac or PC.
a. Upon getting the theme from the provider of the application to the device, you will then need to get it on the PC.
b. Connect your device to your machine as normal, and use “Disk Drive” to access the data storage on the device. (this could be internal or SD depending on device)
c. Once you have accessed the data on the device, look for the folder “MIUI” and under will be the “Theme” folder. In this folder will be all your downloaded themes. (MTZ Format)
2. After you have the MTZ files copied to your machine, (always best to create copies as this ensures you don’t break the mtz file you have already as source)
3. You can then (if you don’t already get 7zip for PC or The Unarchiver for Mac both free utilities) to then open the MTZ file and extract it’s contents to your desktop or destination of choosing.
4. Upon extraction you will usually find a few folders and files in there. Most notably: “Preview Folder”, “Wallpaper Folder” “Fonts folder”, lockscreen file, icons file, description.xml.
5. These are usually the basics for the theming. Most of them are self-explanatory.
a. For modifying or making your own wallpaper or preview, this is quite simple, just modify the wallpaper you find in the folders and create new ones using Paint, Photoshop or GIMP (utility of your choice)
b. Create a new wallpaper of the same dimensions used and name it the same as the original file found in the folder. Just delete the original when done. (Best cases for this I have tested are : 480x954, 480x860 and a few others) at about 72DPI or better.
6. Once you have created the wallpaper and it’s preview that you wish to show in the chooser, place those files in the respective folders.
7. To first start the modification and in this the main reason for the XML is to change the Chinese Characters displayed to English or US. Most people will just change the Wallpaper and repack, and that is ok. This is for those who seek to have English displayed.
8. In the first XML : description.xml - This file allows you to customize fields of Title of the Theme , Author, Version and such. These are the only three I recommend changing. ONLY CHANGE DATA between the <Title> THIS IS TO BE CHANGED</Title>
a. (changing only the data between the start and stop tags which are the <Field></Field> items)
9. Please note that changing the information in-between the start tags and end tags for XML is how the data is read by the application. So those values are how this is displayed.
10. The second XML is called the manifest.xml file, and it’s in the lockscreen file.
11. To modify this file, you need to rename the lockscreen file to lockscreen.zip and then extract the contents and open the folder under and look for the manifest.xml file.
a. Renaming method for Windows: Start > Run > cmd | in the command prompt, CD to the correct location of the lockscreen file and then issue the command with out quotes: “rename lockscreen lockscreen.zip”
b. Renaming method for MAC: Terminal – cd to the location of the lockscreen file issue the following command : “sudo mv lockscreen lockscreen.zip” It will ask for password, input your user password.
12. If the renaming happened correctly you should now see the file as a zip file.
13. You can now extract this file using 7zip or Archive utility or other to extract to a destination of your choice.
14. After you have done this, find the “manifest.xml” file in the folder from extraction.
15. You can edit this file in any great number of free XML utilities out there: PC : Notepad++ and MAC : TextWrangler. Editing this will allow you to find all the characters, which are not English and then copy them, open a browser and go to translate.google.com and translate them and insert the correct words as necessary.
16. When you have completed editing all the Japanese and Chinese out of the document, save it and then back out of the directory that you extracted and then ZIP the lockscreen file back up using Winzip, 7zip or Arhcive Utility in Mac or whatnot.
17. Once you have compressed and ZIP’d the lockscreen folder back up, you will see a new lockscreen.zip file with your modified files in it.
18. Now it’s time for you to Reverse Rename the file and removes the .zip file making it a file plain object. (Hint – Do the reverse of step 11 above, going from lockscreen.zip to lockscreen)
19. Once you have completed this phase, you will need to compress it to a MTZ to put back on the phone. 7Zip has this built in and you can just compress using 7zip and select MTZ as the file format. As for MAC I recommend using this Automator, which will do it for you. (MAC USERS WILL NEED TO TO one extra step)
a. Mac users will need to after creating the MTZ file, make the file Unix Executable – Terminal (open this app) and then go to the MTZ file and issue the following command: “sudo chmod a+x yourfile.mtz” , it will ask for password, do as above. Then the system will make it a UNIZ Executable just like the other MTZ’ files
20. Now transfer the MTZ file you have created back to your device and launch the app and choose your new theme.
MAC TOOLS for MTZ:
PLEASE EMAIL ME for TOOLS (don't have enough posts)
IF you have any questions, please feel free to email us at [email protected]
Or check our Youtube Channel as we will be posting a tutorial on this soon!
Please EMAIL for YouTube Channel (not enough posts)
Thanks.
FluxboxMedia and GeekTekneek
*****UPDATE******
Upon more and more research , our team has discovered that simple repackaging of the theme once modified does not always work as listed above. If you are using the PC and wish to use the 7zip method, the tip we found on DroidForums was to Open the MTZ file in 7zip and leave it open. Then 'Drag' From the file manager of 7zip the contents to your machine which will allow you to modify a copy of the theme. Make your changes , wallpapers and such, and then copy 'drag' them back into the open Archive of MTZ theme you did from above in this update. Once done, close the archive by closing 7zip. If you make any changes to the 'advance' folder under the lockscreen file (note you can just 2x click on the lockscreen file while in the 7zip archive and it will open), you will need to copy the changed files into this folder, and then click the "up one folder icon " it will annouce "There are changes to the original packing files, would you like to update the file and repack?" CHOOSE YES. Then you can close the entire 7zip app and deploy to your device. If you have questions, please feel free to email us. Video YTube tutorials will be online shortly.
Great idea. I really like this application. I also see it becoming a hit.
Yup, this app is awesome! I didn't know about 7zip's ability to compress to mtz, thanks for sharing that. What we really need is a tutorial on converting themes to mdpi
Great tut tho. Excellent and clear.
Tapatalkin it from my IHO CM7.1'd, ICS Themed Optimus V
Thanks for the support so far. We at our studio have done lots over the last 2 years with customizations and installations and testing, and just feel that now is the perfect time on a brand new app.
We are going to be doing a tutorial Video which will show the basics on it.
Some of them however are not happy with configuring the XML in the manifest file. (meaning as soon as you modify any part of it, the repack and then put on device) The theme comes out as just the default.
We are still working on some of the buggy themes.
Thanks
Examples of our work thus far
Examples of the Customization Completed
Converted from Japanese/Chinese to English Format
Attached as Inline image posting is restricted to people more posts than 8
???
Nice, I'm also working a TUT, nice locker/screenlocker to have! Easy to theme!
Pitty it doesn't run the ICS'ed ones
Hello
if i want to modify a theme for my SGA what resolution and DPI should i choose?thnks
kcls said:
Yup, this app is awesome! I didn't know about 7zip's ability to compress to mtz, thanks for sharing that. What we really need is a tutorial on converting themes to mdpi
Great tut tho. Excellent and clear.
Tapatalkin it from my IHO CM7.1'd, ICS Themed Optimus V
Click to expand...
Click to collapse
From HDPI to M/LDPI just resize images, and change dimension values in manifest.xml (be aware of how MIUI roms/apps sees y value), although you don't need to do that, if you're using newest MiLocker version (1.4.2 I guess?). But as for M/LDPI Miui rom port you have to do it.
Sent from my GT-I5800 using Tapatalk 2 Beta-5
Nice Info for people who are Novice about MIUI Themes and Lockscreens.
Thanks for the great tut :good: You deserve more thanks.

[Q] translations setings apk

can someone may help
i want to translate mising thing in cynomobile rewo a in setings to my language [polish] i need step by step instruction
i was trying but after translation and replacing whit orginal setings apk and reeboot setings gone .
i need list tools and step by step procedure
use apk tool
search for apk tool and a tutorial to use it.
when you now how to basically use it,
install systemui.apk with this string
Code:
apktool if systemui.apk
(the same as framework)
then unpack the settings.apk (apktool d settings.apk etc etc...)
then you can translate the settings.apk in this way:
Change into the /res folder
Code:
Check to see if a values-xx folder exists, where xx is the two letter code of the target language to be translated into.
For example, if you are aiming to translate into German, check for a values-de folder. If it does not exist
(and chances are that if you are translating into a new language, that it will not exist), you need to create it.
Then, copy the arrays.xml and strings.xml files from the /values folder into the folder you just created.
Open these two files (in Notepad ++) and alter the strings (the text in BLACK ONLY).
Look out for things that look like %d and %s /’ - Don’t edit these, as they are variables. Also, if you see &, it represents the ‘&’ sign, so feel free to change it.
Finally, you MUST be sure to place a backslash ‘\’ before an apostrophe, for example Proxy\’s would be the equivalent of Proxy’s.
Once you have translated and edited your arrays.xml and strings.xml files, save them, and return to the root directory of APKTool
then repack the apk as you have learn from using apktool (search for tutorials) and the the work is done!
(press thanks if this post was useful!)
is there posible to flash strings after translation via cwm
and can sombody may help me
i thinking about strings from setings apk and cmparts apk in squadzone rom

[TOOL]Colors.xml Changer

Hello everyone!
I would like to share my simple-but useful,script!
What's that script?
This script is taking a colors.xml file which you select , and changes all the colors to the one you need.
How can that script be "useful"?
Sometimes when themers want to find out which color (i.e) affects the color of toolbar of an app,are searching in the colors.xml
Instead of searching all the colors.xml,i created that script which changes all the color values to one color of your choise.
This will make all the colors (i.e.) green.So compiling the theme will make you understand what is affected by colors.xml or styles.xml or or or...
Yes but...malware?
Source code
Also its compiled with AutohotKey.that means ,if u open the .exe as text file,there is all the source code there.
How to use it:
Download the zip and extract it.
Run the .exe
The script will do nothing until you press the 'F2' button.
Select the colors.xml you want.
Type the color you want.
Pressing ok ,will create a new modified xml at your desktop
Profit.
Pressing ESC in the operation will exit the script and will remove the produced folder at desktop
Give me some feedback,if that app is running on your computer because i use x64 windows 7

Building Your Own LG Themes

Introduction
This is going to be a long post! A few weeks ago I started thinking about making my own themes for my LG G5. I had installed some custom roms previously and used substratum a bit but I have always ended up going back to xpirt's Fulmics rom, which doesn't allow this. I started to think how I could do this and have today got to the first stage of being able to change the colours of my phone to precisely what I want, not only for the settings but in some of the stock apps. I thought I would share this with the community and provide some step by step instructions so you can try it yourself. This should work on LG G6, V10, V20 & V30 if you use an app made for these phones but I have no way of testing this so don't hold me to it. This has taken me about 5 full days to work this out and there is still more that I need to do.
I am not in anyway a developer or coder and have very little knowledge of Java so if anything goes wrong here it is likely that I will not be able to help you. I absolutely am a noob at this and do this only for a hobby, using just my common sense and our friend Google to overcome the problems I have come across. Saying that, I will try to offer assistance if I can.
I managed to make my theme from reverse engineering a free LG theme app that was readily available. If you do this method though please consider getting approval from the app developer first. There is a template on here posted by Raafat here. While this was helpful it was only basic and I could not work out exactly what to do. Reverse engineering an app was much easier. Here is how I did it with step by step instructions:
******DISCLAIMER******
I am in not responsible for what you do to your phone. If you decide to try and theme your phone make a backup first or be prepared to do a full reset if anything goes wrong. You do this at your own risk.
1. Programmes
The programmes/software needed for theming are:
• Notepad++
• Apktool
• Android Studio (I used version 2.3 as I was getting an error on re-signing with 3.0)
2. Installing Frameworks Using Apktool:
• Firstly, delete the files in your local temp directory. To do this open ‘Search’ and type in %temp% and delete all files in this folder. You may not be able to delete some of the files. This does not matter
• Next, extract the framework files from your rom/custom rom. For Fulmics 5.5 this was:
Frameworks-res.apk
lge-res.apk
• At a guess I would say that any rom will have these files named exactly as they are above, but I am not sure if these have been altered by xpirt for his rom so you may not be able to use them across other roms.
• Open a command prompt and navigate to the folder where the framework files are kept. This is easiest in a folder called C:/apktool so create a folder in your C:/ drive and place them there. You can of course name the folder or locate it where you want though.
• Use apktool to install the frameworks using this command in the command prompt in C:\apktool
apktool if framework-res.apk
apktool if lge-res.apk
• Once this is done you should find the following files Installed here: C:\Users\[your username]\AppData\Local\apktool\Framework
1.apk
2.apk
• If, like me, you get an error with apktool that says it cannot write to C:\Users\[your username]\AppData\Local\apktool\Framework and instead has placed them in the temp folder then go into the Local folder using the pathway above and create a folder called 'apktool' and then a subfolder called 'framework'. Try the commands again and it should then work.
• You should also find the following files in the C:\apktool folder (if that is the folder you are using). If they are not here you may have to copy and paste them from the apktool github download.
apktool.jar
apktool.bat
• If you have found these files then you are set to go with decoding the theme/app you have chosen as a basis to amend.
3. Decoding APKs Using Apktool
• Download the apk/app you want to use. I used Backup and Restore app from Play to get the app I wanted to use onto my PC. Once you have this on your PC place the main APK/app in the same folder as the apktool.bat and the apktool.jar (for me this this was C:\apktool)
• Point the command prompt at this place and type the following:
apktool d [app name]
• A folder with the name of the app you just decoded will appear in the directory that you use (in this case C:\apktool)
• In this folder you should find another folder called assets. There may be more sub APKs here in subfolders. This subfolder will likely be assets>overlays
• All the sub APKs in here will have to be decoded otherwise you will have different signing keys and the app, once compiled again, will not work. Decode all the sub APKs in this same folder. You will have to copy the following files to the folder you are decoding the sub APKs in. These are:
apktool.jar
apktool.bat
• Decode every sub apk using the command apktool d [sub_apkname]
• You should now have the same number of folders in the drive as the number of sub APKs, if you decoded them all.
4. Changing the Colours and other Themes from the Decoded APKs Using Notepad++
• Many theme APKs will have internal APKs, such as common, settings, phone, systemui, calendar etc, etc. This is what I have worked out so far:
Common: Changes the switches, brightness bar and the text headings in settings, changes swipe left panels in apps such as gallery, changes background, message icon & phone icon colour in contact/phone app, statusbar background, separating lines in settings (some themes do not have these), background bar of setting title (i.e. wireless network, device etc), settings text colour, secondary text (i.e. the text you see under Wifi and Bluetooth which shows you what you are connected to), the headings in apps such as clock where it shows 'Alarm' 'World Clock' 'Timer' etc
System UI: Changes the quick settings tiles & text and the non-heading text in settings
• To change the colour of these you have to amend the colors.xml located in one of the folders in the assets>overlays and then the folder of the overlay you want to change. I used Notepad++ to do this. Navigate to 'res' folder and then usually something like 'values-xxxhdpi-v4'. There is sometimes more than one color.xml file so you may need to look in more than one folder and amend all the color.xml files. The colours are at the end of the lines of text and will be standard Android colour coding, such as ffffffff (white) or 00000000 (black) or any other colours.
5. Building APKs & Signing with Android Studio
• If you are building the sub APKs from an app (these are the ones inside an APK such as common, systemui, phone etc) I found it best to use a different folder. For this I used C:\apktool builder
• Copy and paste the folder from the decoded APK (e.g. the [appname].LGE.common folder) that is in the asset>overlays folder to the apktool builder folder above
• Once you have made the colour amendments it is time to build the amended themes. To do this you will need Android Studio
• Open the splash screen of Android Studio and instead of the 'Open' command use the 'Import Project' command and navigate to the folder you want to import
• When opening Android Studio you have to configure the frameworks otherwise you will not be able to sign the app. This warning should come up automatically. THIS MUST BE DONE FOR IT TO WORK
• Navigate and find your APK in apktool builder and import it. If you do this more than once you will be prompted to overwrite the settings a few times.
• Go to ‘Build’ along the top and choose ‘Generate Signed APK’. If this is the first time it will ask for the Key Store Path. You will need to choose ‘Create New’. Select a place to store this key (I chose C:\apktool Builder) and input the passwords and the other data in the boxes. You must put a two-digit country code in the last box, for example US, UK etc). For ease I kept most of these very simple. For example, password was 'asdfgh'
• Once this has been completed and if there are no errors (warnings are ok) then it will generate a signed sub APK and save it to the location you are in (in this case C:\apktool builder). Copy and paste that sub APK over the one in the C:\apktool folder where the original sub APK was kept.
• Once you have done this then you need to sign the main app APK. Do the same as above and build in Android Studio. If there are no errors it will save it to your directory (in my case C:\apktool\[app name].
• Copy and paste this APK into your phone, apply the theme and it should work.
Everytime you amend a sub apk you will have to re-sign it through Android studio and then re-sign the main app apk. Once you get the hang of it though it is fairly straight forward.
6. Other Things
Nothing else in the app will change at this point. The name, wallpaper jpegs, screenshots and icons will all be the same. I am working on this at the moment but they don't actually need changing that much. The difficult thing for me is how to change the 9.png icon files and still get them to work. Once I have worked this out I will be able to finish it off.
7. Screenshots
Attached are some screenshots of how my phone now looks. I have made a few different apk's with different colours so I can now change this daily if I want a change (see post 2 for updated screenshots).
8. Thanks/Credits
@xpirt - Made it easy to get the framework files I needed for apktool and for a great custom rom!
@Raafat - for giving me the idea and the initial information
@iBotPeaches - for developing apktool.
.
Building Your Own LG Theme
I've been able to fine tune the themes over the past few weeks and have been able to colour the settings icons on the main settings page as well as putting a background behind it. I've also been able to theme the switches initially getting over a problem of the 'off' switch not showing. Here is some updated screenshots of a green/grey&blue theme.
I've also attached the updated blue & red theme from the initial post. I've not fully completed this yet though as I started to concentrate on the green/grey&blue theme as I preferred that.
Could someone make a stock theme just dark? I found one on play store but is not the best thing (it changes system sounds and other things that i don't like) I'd like a full stock theme but dark. Thanks in advance
Help
Can you help me? I tried changing package names in .json file and added new icons in the theme. I don't understand why it is failing on apply. It was running properly with only color change before doing this.
[email protected] said:
Can you help me? I tried changing package names in .json file and added new icons in the theme. I don't understand why it is failing on apply. It was running properly with only color change before doing this.
Click to expand...
Click to collapse
Here is the apk.
I probably won't be able to get round to this until the weekend due to work commitments but will have a look and let you know.
strikerman10 said:
I probably won't be able to get round to this until the weekend due to work commitments but will have a look and let you know.
Click to expand...
Click to collapse
Take your time, and thanks. ?
[email protected] said:
Take your time, and thanks. ?
Click to expand...
Click to collapse
In case you haven't checked the apk I provided earlier, I have found and fixed some package name errors but the result is still same. It get stuck at 90% and then fails. I have changed icons too, is there anything needed to do in public.xml ? New apk is attached below.
strikerman10 said:
I probably won't be able to get round to this until the weekend due to work commitments but will have a look and let you know.
Click to expand...
Click to collapse
Did you took a look at it?

[Newbies][Documentation]What's an apk and how does it work

Quick Intro :
Let me answer that question, an apk, first of all, is the format of Android apps, as .exe would be for Windows, apk means Android Package by the way.
But what’s the big deal?
Well an apk contain a lot of things into it.
When you open it as an archive, you might get those files:
AndroidManifest.xml
assets
res
META-INF
resources.arsc
classes.dex
AndroidManifest.xml is the file that contains the information about the app itself: the list of all activities, all permissions, the name of the app’s package, and the software/hardware requirements. To be able to read it, you’ll need to decompile the apk file.
Assets and res folders are meant for resources. Most often, you won’t see the assets folder because its usage is limited, (explanations here). We’ll focus on res since asset isn’t used so often.
META-INF contains CERT.RSA and CERT.SF (certificate) as well as MANIFEST.MF (a manifest)
Those files are the app signature, and META-INF is the folder that contains signature.
The resources.arsc file is the file holding most of the resources that were originally in the res folder. After compiling the code, Android Studio (or others software) compile resources into this file. You won’t be able to open it with an archive explorer. We’ll need to decompile the apk to get the resources back into the res folder.
And, finally, the classes.dex file contains the every smali files of the app. A smali file contains the java code for a specific part of the app. To be able to have the smali files (into the smali folder), you’ll have to baksmali your app.
Hopefully, apktool (a reverse engineering tool) does it for you.
Let’s decompile the apk using apktool (a popular tool used to decompile apps):
Once apktool is installed (see the apktool web page to know how to install), you’ll need to use the command prompt to decompile the apk:
Code:
java -jar apktool.jar d [name of the apk].apk
(I advise to create a folder and to put every file needed in it: the apk, the apktool.jar file, and the apktool script).
You’ll have an out folder, and when you browse it, you’ll have most of the time:
AndroidManifest.xml
original (a folder)
res (a folder)
smali (a folder)
The AndroidManifest.xml that you see here is the translated one.
In the “original” folder rest the META-INF folder and the original AndroidManifest.xml file (untranslated). As you can guess by its name, this folder contains unchanged original files.
The res folder is now full, because every resource from the resources.arsc file are now back into the res folder
Same for the smali folder, this folder contains every piece of code contained into the classes.dex file.
We will now focus on the res folder. Now that it’s complete, we can see those folders (it depends on your apk, but here is the list of the most common ones):
anim (other animation stuff, see the links at the end of the thread)
animator (animation properties)
color (color state list: in which condition this color is used for a particular element)
drawable (can be pictures or xml files, it contains a lot of things)
layout (contains the files that define the layouts of the app)
mipmap (icons for different screen densities)
values (xml files that contains values, that will be referenced in other xml files in other folders)
xml (every other unclassified xml files)
Those folders contain files that will be named following their resource ID.
So how does all of this work together?
Well, the java code written in the smali files will call resources with their IDs. This way, the app will show you the write thing at the right moment, following the code. The layouts are already described in the layout folder. What the code really do is analyzing the action of the end user and calling other resources in consequence.
For example, I’m using the XDA Labs app on my phone. I’m in my phone’s section, and I’m about to click on a thread to open it.
I clicked on the thread, so the code loaded the thread layout with every post in it, and other resources such as the little arrows at the top to jump to the end/beginning of the thread, the reply button, its color, … That’s how to work if I want to keep it simple.
I tried, in this guide, to simplify android app basic for beginners. Feel free to ask any question, I’ll be glad to answer.
If you want to go further into it, you can read a very complete guide about app basics by google (it’s a bit complicated to read, assuming you’re just starting to understand).
Here are the links:
https://developer.android.com/guide
If you have any question about that guide, you can also ask me (with the quote you didn’t understood).
Keep at mind that mastering app basics is really important if you ever want to theme/create an app. So, this guide and the google one is a good place to start.
Have fun reading
Hello Raiz,
I decompiled the apk of an androind app from playstore using dex jar and apktool however I can't find the scripts anywhere in the resulting files. Where should I look? Or is there something more that I have to do? I'm trying to edit something for personal use to make the game more enjoyable. I saw a .unity3D file in there so I presume it was made in unity if this helps.
Good tutorial about concepts of APK file. The details you share are so educational. Thanks for sharing

Categories

Resources