Related
Let's face it, Swype is ugly and there are not many HVGA themes out there, so I made a Gingerbread-inspired HVGA Swype theme for our Arias.
First off, I am greatly indebted to Marurban, who set me on the right path, as well as provided the inspiration in this thread:
http://forum.xda-developers.com/showthread.php?t=930306
But I want to emphasize, all images in this theme are 100% created by me.
Installation is a little complicated and is pretty much the same as for Marurban's theme.
Stuff needed:
apk manager (http://forum.xda-developers.com/showthread.php?t=695701)
ADB pull your Swype from /data/app/
HxD if you want to modify the color of the tracer line (http://mh-nexus.de/en/hxd/)
Swype GB theme files (attached -- download and unzip)
How to:
in apk manager, place Swype apk into folder place-apk-here-for-modding
run Script.bat
choose 19 (-Select compression level for apks-)
choose 0 for compression level
choose 22 (-Set current project-)
choose the number corresponding to your Swype file
choose 9 (-Decompile apk-)
go into apkmanager > projects > [app folder name] > assets > keyboards and overwrite Swype keyboard PNGs with themed files.
go into apkmanager > projects > [app folder name] > res > drawable and overwrite Swype horizontal selection highlight files with themed files. (these are for landscape mode word suggestions -- see screenshot#5)
go into apkmanager > projects > [app folder name] > res > drawable-hdpi and overwrite Swype voice input files with themed files. (see screenshot#4)
if you want to change the color of the Swype trail:
go into apkmanager > projects > [app folder name] > lib > armeabi
open libSwypeCore.so in HxD
CTRL+F (search) for DD A2 5B
find a color you want to use and note it's HEX value. (IIRC, I used #ffba00)
switch values around so that it is B-G-R (mine would be 00 BA FF)
replace values and save
a .bak file will be created in the directory -- delete it
when you are finished with all mods, go back to console window and choose 11 (-Compile apk-)
choose Y (-is this a system apk-)
followed by N (-would you like to copy over any additional files-)
choose 12 to sign your apk
signed apk is in place-apk-here-for-modding folder
uninstall your previous version of Swype before installing this one!
License It:
If you just start using Swype, it will only let you tap type and will say "Swype is not configured for this device," IIRC.
License your modded Swype by running the Swype Installer app. It will guide you through the steps and generate a license.
Enjoy!
Dealing with Swype updates
I'm glad so many people are trying out my theme! Apologies to those that are having problems--I have been busy and not been able to update this thread recently.
So, some people are having problems as of the new Swype Installer (1.1.20186) and Swype version (2.29...)
If you have applied my theme to a previous Swype version, and try to license it via the Swype Installer (after flashing a ROM, for instance), you will run into problems when the installer updates itself, and consequently fails to generate a license for your old version of Swype.
To fix this:
uninstall any versions of Swype you may have, themed or not.
download and install the newest official Swype from the installer (installer may want to update itself first)
ADB pull Swype and apply the theme as above
uninstall the official Swype
install the themed Swype (via sideloading, DropBox, or whatever)
license it, as above
Just to clarify, you won't have to do this every time Swype releases a new beta. But you will have to do this workaround whenever you try to theme the lastest Swype. Seems the Swype Installer only recognizes the latest and greatest, and will fail to license prior versions of Swype.
Here is the Swype beta changelog for the recent update:
http://forum.swype.com/showthread.php?2865-Swype-BETA-for-Android-UPDATE-March-2011
this is pretty cool. good jorb!
Can someone just Make an apk and post please?
Sent from my Liberty using XDA App
Javi97100 said:
Can someone just Make an apk and post please?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Its not allowed.
Sent from my cm7 Aria using XDA App
Yeah, but if someone wanted to help me make a flashable update.zip, that would be cool.
From the screenies it appears the popup word suggestion box also behaves as it does in the regular GB keyboard (across the top of the keys, rather than the vertical box in regular swype). Is this actually the case, and if so, does it behave like this in portrait as well as landscape?
Either way, excellent work - now I have a little project for tonight
Edit: Tried to work through your steps on my linux machine: The APKManager script I am getting (not sure if this is due to linux vs. windows discrepancy, or being a different version for Linux, or both) only 17 options for selection. This means options 19 and 22 (steps 3 and 5) in your instructions are unavailable to me. Could you please post the text related to those options in the script so I can determine the correct options in linux? Unfortunately I don't have a windows box available to play with right now.
Thanks.
Think I'll take a WAG at it in the meantime though...wish me luck.
Edit 2: I think I have it mostly working - can't figure out how to get APKmanager to find java on my linux machine to get it to sign the zipped apk. Not sure what I need to add to the path for it to be found. Out of time screwing around at work now...will be back at it later maybe.
dandrumheller said:
From the screenies it appears the popup word suggestion box also behaves as it does in the regular GB keyboard (across the top of the keys, rather than the vertical box in regular swype). Is this actually the case, and if so, does it behave like this in portrait as well as landscape?
Either way, excellent work - now I have a little project for tonight
Edit: Tried to work through your steps on my linux machine: The APKManager script I am getting (not sure if this is due to linux vs. windows discrepancy, or being a different version for Linux, or both) only 17 options for selection. This means options 19 and 22 (steps 3 and 5) in your instructions are unavailable to me. Could you please post the text related to those options in the script so I can determine the correct options in linux? Unfortunately I don't have a windows box available to play with right now.
Thanks.
Think I'll take a WAG at it in the meantime though...wish me luck.
Edit 2: I think I have it mostly working - can't figure out how to get APKmanager to find java on my linux machine to get it to sign the zipped apk. Not sure what I need to add to the path for it to be found. Out of time screwing around at work now...will be back at it later maybe.
Click to expand...
Click to collapse
Glad you're trying it out.
#19 is set compression level for .zips and you want it to be 0. #22 is choose current project, and you just want to navigate to the Swype file (in case you have a bunch of other APKs you are working on. Later, when I am on my PC, I will transcribe the more detailed text choices and edit first post.
Also, I should have put in a screenshot of the word choice window. Swype functionality is 100% the same as normal. In landscape you get the bar atop the keyboard, and in portrait, you get the squareish pop-up. I made the pop-up grey so it looks good with the theme, but it's still there.
stone_ship said:
Glad you're trying it out.
#19 is set compression level for .zips and you want it to be 0. #22 is choose current project, and you just want to navigate to the Swype file (in case you have a bunch of other APKs you are working on. Later, when I am on my PC, I will transcribe the more detailed text choices and edit first post.
Also, I should have put in a screenshot of the word choice window. Swype functionality is 100% the same as normal. In landscape you get the bar atop the keyboard, and in portrait, you get the squareish pop-up. I made the pop-up grey so it looks good with the theme, but it's still there.
Click to expand...
Click to collapse
Thanks for getting back to me. Neither of those options exist in the linux version of apk manager (or I don't know how to find them if they do). I'm going to guess I'll be ok once I figure out the java/path issue.
Thanks.
Sent from my Liberty using Tapatalk
Thanks
stone_ship said:
Let's face it, Swype is ugly and there are not many HVGA themes out there, so I made a Gingerbread-inspired HVGA Swype theme for our Arias.
First off, I am greatly indebted to Marurban, who set me on the right path, as well as provided the inspiration in this thread:
http://forum.xda-developers.com/showthread.php?t=930306
But I want to emphasize, all images in this theme are 100% created by me.
Installation is a little complicated and is pretty much the same as for Marurban's theme.
Stuff needed:
1. apk manager (http://forum.xda-developers.com/showthread.php?t=695701)
2. ADB pull your Swype from data/app
3. HxD if you want to modify the color of the tracer line (http://mh-nexus.de/en/hxd/)
4. Swype GB theme files (attached -- download and unzip)
How to:
1. in apk manager, place Swype apk into folder place-apk-here-for-modding
2. run Script.bat
3. choose 19
4. choose 0 for compression level
5. choose 22
6. choose your apk for current project
7. choose 9 to decompile
8. go into apkmanager > projects > [app folder name] > assets > keyboards and overwrite Swype keyboard PNGs with themed files.
9. go into apkmanager > projects > [app folder name] > res > drawable and overwrite Swype horizontal selection highlight files with themed files. (these are for landscape mode word suggestions -- see screenshot#4)
10. if you want to change the color of the Swype trail:
a. go into apkmanager > projects > [app folder name] > lib > armeabi
b. open libSwypeCore.so in HxD
c. CTRL+F (search) for DD A2 5B
d. find a color you want to use and note it's HEX value. (IIRC, I used #ffba00)
e. switch values around so that it is B-G-R (mine would be 00 BA FF)
f. replace values and save
g. a .bak file will be created in the directory -- delete it
11. when you are finished with all mods, go back to console window and choose 11 (compile)
12. choose Y, followed by N
13. choose 12 to sign your apk
14. signed apk is in place-apk-here-for-modding folder
15. uninstall your previous version of Swype before installing this one!
License It:
1. If you just start using Swype, it will only let you tap type and will say "Swype is not configured for this device," IIRC.
2. License your modded Swype by running the Swype Installer app. It will guide you through the steps and generate a license.
3. Enjoy!
Click to expand...
Click to collapse
I have never used ANY of these programs, and was able to follow this tut 100%. Thanks
This is gorgeous! Can you build a WVGA version? Would love it for my DInc.
Love swype and now even more so, thanks.....
nerdBrain said:
This is gorgeous! Can you build a WVGA version? Would love it for my DInc.
Click to expand...
Click to collapse
this one by Marurban is pretty similar and has a WVGA. For now, it's just going to be HVGA. You big screened people get all the good themes and such anyway
http://forum.xda-developers.com/showthread.php?t=930306
Thanks. I actually knew about that one...I just think yours looks better . Let me know if you change your mind.
I used Root Explorer to find the name of the Swype app to pull in ADB (com.swype.android.inputmethod-1.apk). However, when I issue the adb pull command, it can't find it.
This is what I get:
C:\android>adb pull data/app/com.swype.android.inputmethod-1.apk c:\android\
remote object 'data/app/com.swype.android.inputmethod-1.apk' does not exist
What am I doing wrong?
I ended up using Root Explorer to copy the APK to the SD card, then followed all the steps from there. However, after compiling the new signed APK, the file size is way off - does that matter? Original file is 2,266KB, New file is 1,911KB. When I try to license the new one it says Registration of Swype failed. Rebooted and tried again with same result.
No help? Anyone...?
911jason said:
No help? Anyone...?
Click to expand...
Click to collapse
I haven't had a chance to get back to troubleshooting my linux issues with getting this done, but wanted to mention there is a new version of swype installer available through the beta program - you might want to give that a shot for licensing if you haven't yet...
Sent from my Liberty using Tapatalk
(then)
i believe it should start out "C:/Android/tools>adb pull. . .after that im confused on where to have it pulled to, since it keeps giving me the "it does not exist crap"
No, I've added adb to my environmental variables so I don't have to be in the tools folder to use the adb command. It works from any location.
I have eclipse and teh android sdk installed, where do I find the draw9patch tool or where can i download it?
For anyone else who might be wondering
Go to where you're android sdk was installed, the file name should be Android SDk by default > go to tools > run draw9patch
I am new to Android Studio.I like the IDE very much,it has got some nice set of features and has a rich look and feel, however I have some issues with the IDE. I recently created a Cordova application in android studio.I created an HTML file called index.html under assests/www folder.I included my jquery-1.11.3.min.js inside index.html file.I have the habit of checking whether the file jquery-1.11.3.min.js has been correctly included inside HTML file.In eclipse I use cntrl +click to check whether the js file path given is right.But when I use the same thing in Android studio,even if the path is right,it is showing like 'Cannot find declaration to go to'.Please help me on this.
So as you may know, Google released their Assistant SDK a couple days back. Naturally, my first instinct was to replace Siri with Google Assistant on my MacBook Pro.
Here we go...
NOTICE: I am not responsible for any loss of data or damage to your computer. I strongly recommend backing up your device before following this tutorial. Proceed at your own risk.
You are installing the Google Assistant SDK on to your device, and there are limitations and differences between it and Google Home.
This is not elegant by any means and doesn't have a fancy GUI like Siri, so be warned. It's a bodge. But hey, it works
1. Firstly, download and extract the zip file attached to the bottom of this post. I chose to do this in the Downloads folder. If you haven't already installed Python 3, go ahead and install it (the pkg file is located in the '1. Python' folder).
2. Go to the Project Page (console.cloud.google.com/project) of Google's Cloud Platform Console, and click 'Create Project'. Name your project "My Google Assistant". After your project has been created, close the page.
3. Enable the Google Assistant API by following this link (console.developers.google.com/apis/api/embeddedassistant.googleapis.com/overview) and clicking 'Enable'. Make sure your project is selected (the project title is displayed at the top of the page). Click "Create Credentials", and select "Other UI (e.g. Windows, CLI tool)" and "User Data" in the following dropdown boxes. Give your OAuth 2.0 Client ID a name, and hit 'Create Client ID'. Call your Product "My Google Assistant". When you are prompted to download credentials, click 'I'll do this later'. You will be brought to a page with a list of OAuth 2.0 Client IDs, and you should see the one you just made. Click the download button to the side, and download it to a folder called "googleassistant" in your Home Directory.
4. Ensure that "Web & App Activity", "Location History", "Device Information" and "Voice & Audio Activity" are all enabled in your Activity Control page (myaccount.google.com/activitycontrols) so that Assistant can be personalised to you.
5. Open a Terminal window (Applications > Utilities > Terminal.app), and install pip if you haven't already installed it, by entering the command:
Code:
sudo easy_install pip
6. Navigate to your googleassistant directory:
Code:
cd ~/googleassistant
7. Install these dependencies:
Code:
python -m pip install google-assistant-sdk[samples]
8. Enter the following command, changing XX to the name of the json file you downloaded earlier:
Code:
python -m googlesamples.assistant.auth_helpers --client-secrets XX.json
9. You will be given a URL. Enter it into your browser and login to your Google Account to authorise the application. You will be given a code. Copy it, and enter it back into the Terminal window - this may take a few minutes.
10. Test that your Google Assistant works with your Mic by entering the following command; it will record 5 seconds of audio and play it back to you.
Code:
python -m googlesamples.assistant.audio_helpers
11. If you can hear yourself, entering the following command to start talking to your new Google Assistant! It can take a couple of minutes to load when you first enter the command, and can take a minute to realise you've finished speaking, so be patient! It does become a lot more responsive after you've ran it for the first time. When you enter the command, wait for it to prompt the command "press Enter to send a new request", and ignore any warnings.
Code:
python -m googlesamples.assistant
Congrats, you just got Google Assistant working on your Mac!
12. Now to replace Siri with Google Assistant, go to the '2. Assistant App' folder from the archive you downloaded and extracted from this post earlier. Copy it, and place it in the ~/googleassistant directory you created earlier.
All this app does is run the Terminal command from step 11 when pressed (if you're worried, all of these apps can be opened in Automator so you can see there's no funny business here).
13. Next, go to System Preferences > Users & Groups > Login Items, and add the Assistant app as a login item, and click the checkbox to Hide the app so it runs in the background.
14. Go to the directory '/System/Library/CoreServices/SystemAppearance.bundle/Contents', and press Cmd-I to bring up the Get Info dialog box. Give yourself Read & Write access by clicking the padlock at the bottom of the window, clicking the '+' Icon, your username, and setting your Privilege to 'Read & Write'.
Next, enter into the 'Resources' folder and do exactly the same thing to the file 'Assets.car', giving yourself Read & Write access.
15. Repeat step 14 at the directory '/System/Library/CoreServices/Siri.bundle/Contents', again with the 'Resources' folder and 'Assets.car' file.
16. IF YOU DO NOT HAVE A TOUCH BAR, SKIP THIS STEP!
Open the '3. Icons' folder from the archive you extracted earlier, and open ThemeEngine.app. Click 'Open Document', go the directory '/System/Library/CoreServices/SystemAppearance.bundle/Contents/Resources',
and click on 'Assets.car'. Go to the "TouchBarControlStripSiriContent" element, and backup the original image by dragging the 'normal' image to your Desktop or location of your choice.
Next, go into the Images > TouchBar folder and drag the 'sharedArt...' image into the 'normal' box to replace it. Click File > Save and exit.
17. If you do not have ThemeEngine open from the last step, open the '3. Icons' folder from the archive you extracted earlier, and open ThemeEngine.app.
Click 'Open Document', but this time go the directory '/System/Library/CoreServices/Siri.bundle/Contents/Resources', and click on 'Assets.car'.
Go through each element, and backup the original images by dragging both of the images in 'StatusMenuDark', 'StatusMenuLight', and the two images in 'ZZZZPackedAsset-1.0' and 'ZZZZPackedAsset-2.0' to your Desktop or another safe location.
Next, go into the Images > StatusMenuDark in the archive you extracted earlier, and ensure the 'StatusMenuDark' element is selected in ThemeEngine. In the folder, there will be two images - one that begins with 'siri-menu-icon-darkmode_', and one that begins with '[email protected]_'.
Look at the image that is selected in Theme Engine, and drag the image with the same name into its place.
Repeat this with the 'StatusMenuLight', 'ZZZZPackedAsset-1.0' and 'ZZZZPackedAsset-2.0' elements + folders in the archive (sidenote: the PackedAsset elements only have one image inside each, unlike the StatusMenu elements). After this, click File > Save and exit.
18. At this point, you have replaced the Siri Icons with Google Assistant Icons, and have Google Assistant set to open in the Terminal when you login. But all those Siri apps still just open Siri! Lets fix that.
It turns out that when you click the Siri Icon on your Touch Bar, in your Status bar, or open Siri in the Applications folder, they're actually all just shortcuts for opening Siri.app in the CoreServices folder.
In System Preferences, click on Siri and make sure it is DISABLED - do not close this window!
Next, open Activity Monitor (Applications > Utilities > Activity Monitor.app) and search for Siri. Kill Siri and its related service if running.
Open a new Finder Window, and navigate to '/System/Library/CoreServices'. Copy Siri.app and back it up somewhere safe. Go the archive, open the folder '4. Siri Shortcut', and copy Siri.app into the CoreServices folder, replacing the Siri app that's already there. Go back to your System Preferences window, and enable Siri. Close out of your windows, restart your mac, and hey presto - Siri has been fully replaced by Google Assistant! You're welcome.
That Siri.app is again an AppleScript made in Automator, and it essentially just enters 'Return' into the Terminal window when pressed. In other words, it's the equivalent of clicking 'return' in that Terminal window when you were talking to Google Assistant earlier. As I said, it's a bodge, but it works!
When the Terminal window launches, don't exit it! Instead, press Cmd-H to hide the window.
If you want to go back to Siri just follow this tutorial again (in the correct order), but replace the Assistant files with the Siri files that you backed up.
I hope you found this useful!
If you did, please follow me on twitter (@_lucasys) and help share this guide around
ZIP FILE: drive.google.com/file/d/0B9n0ZPG3Fgh3emJaanRHT2ZMSWc/view?usp=sharing
Screenshots: imgur.com/s88t7hC, imgur.com/qIi5t9W
Thanks to Alexander S. Zielenski and Mishaal Rahman
Reserved
Reserved Post
Wow keep it up man!
Any tweaks like this for jailbroken iPhones?
Python
Valiante said:
Any tweaks like this for jailbroken iPhones?
Click to expand...
Click to collapse
I don't know if iPhone have the required version of python if yes then there is a way.
hi, nice hack! one of the best!
does this support local commands for the mac?
Would this work with an M1 Macbook Air and that thise post is like 6 years old?
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?