Related
...let you decompile and apk and edit the layout in the xmls, and then display the results in a device emulator without having to recompile and sign the apk and push it to your device? I have all the tools (SDK, Eclipse, apk manager, etc etc etc) but as I am new to Android tweaking I may be missing some simple knowledge that will save a lot of trial and error!
I am looking initially to edit the HtcQuickLaunchWidget.apk (the non-m10 version) and was wondering if there was a way of loading the apk or decompiled apk back into Eclipse or something similar to then be able to tweak the layout of the widget and view the result on the PC rather than spending hours of making single changes and pushing to my phone each time to see the result.
The answer might be a simple 'no other way' or as I say I might be missing something obvious and all I need to do is 'this, this and this'... Any advice would be greatly appreciated. And before you mock, remember we all have to start (or in my case start again) somewhere
Thanks.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to Q&A
UPDATE: Tickle My Android is now in the main Android Themes forum!
http://forum.xda-developers.com/showthread.php?t=1633333
Head on over there and pick up version 2.0...
I use apktool and ADB a lot to tweak my phone, my tablet and the phones of my colleagues at work (4 Androids to 1 iPhone at work...take that, Apple!).
After a while, it got a bit tedious typing the same set of commands over and over again so I wrote some batch files.
Then I got a bit carried away..
Presenting Tickle My Android, a command-line tool for Windows (XP/Vista/7). This is designed to make the process of theming your phone and modifying it to your exact requirements so much easier and faster.
What's needed:
a rooted phone with ClockworkMod Recovery
a Windows PC with Java and phone/tablet drivers installed
a brain
a coffee or some nice cookies
Download the tool from the link at the bottom of this post and run it. It's a self-extracting archive that will set itself up on your computer. It doesn't install anything or do anything unpleasant to your machine.
Once set up, there will be seven folders. Ignore the tool_files folder, that's full of things to run the tool with. The BOOTANIMATIONS and FONTS folder are to store boot animatons and fonts in, about which more later. The BACKUP folder will hold your backups.
When you start using this to modify your apps, you'll be using the "in", "out" and "working" folders.
apps pulled from the phone go into "in"
decompiled apps go into "working" and
recomplied apps go into "out"
What does this decompile/recompile nonsense mean? Have a look at shivenjuneja's post here: http://forum.xda-developers.com/showthread.php?t=849223 to find out more!
Run TickleMyAndroid.bat and you'll see this:
{
"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"
}
Connect your phone to the PC, make sure USB Debugging is set to on, and away you go!
You can use this tool to pull, decompile, recompile and push files to and from your phone but you can also:
change the battery icons
add Ice-Cream Sandwich-style transitions
change the status bar to transparent, semi-transparent, black or white
sign and zipalign your own applications
compress recompiled system apps correctly so they actually work and don't cause a boot-loop
backup your texts, picture messages and contacts
transfer your texts, picture messages and contacts to another phone or a new rom
change the boot animation
change the font
install an ad-blocker (this is up to you, ads pay for apps!)
add sounds from other devices and
anything else I can think of that I'll add later
This is designed to work on any Android device running any rom, and on pretty much any PC. I do most of my modifying at work where there are two Samsung phones, one ZTE and my beloved Sony Ericsson so it needs to be flexible and get past my IT department..
Try it out, have a play, and let me know what you think!
Download Tickle My Android -v1_2_2 here: http://db.tt/fdq0725r
Changelog
1_2_2: Bug-Fixes. Adding Battery Icons Should Now Work For All Roms
Changing Battery Icons
To use Tickle My Android to change the battery icons on your phone is very simple and very quick.
************BACKUP YOUR PHONE FIRST!!!!***************Start the tool and select Option 2 to open the Theming Menu.
Select Option 2 again to open the Pull Menu.
This will let you pull what I call 'The Big Four' apps from your phone. These are the apps that seem to be modified most often so you can pull those with just a button press. Want to pull a different file? That's what Options 5, 6 and 7 are for!
First, select Option 1 to pull "framework-res.apk" from your phone. Say yes to backing it up, decompiling it and installing it. Installing "framework-res.apk" to your PC doesn't actually install it as such, it just makes the resources in the app available to others. Which can be essential for modifying a lot of system applications. Don't worry, there is an Option to uninstall it back in the Theming Menu.
Back at the Pull Menu, use Option 4 to pull, backup and decompile "SystemUI.apk" as well. If you're running Android 2.3 (Gingerbread) or anything later, you'll have this on your phone. Any Android version earlier than that and you won't, so you can skip this step.
On your PC, in the TickeMyAndroid folder, there will be seven sub-folders. In the "in" folder will be the apps you've pulled from your phone and now, in the "working" folder", there will be the decompiled apps as well.
Go back to the Theming Menu and select Option 5 to go into the Battery Menu:
This gives you the option to install a selection of different battery icons that I've found around the internet. I've credited people where I could but if you came up with these and I haven't, then let me know.
The various options you can install are:
Multi-Tone Circular
New Sense
Bolt
ICS Circle by nbeebe
Full Circle by Pendo
Digital Numbers by Zaphod Beeblebrox
Circles by Hoolm
Stock Gingerbread With Percentage
Blue Circle With White Text
Purple Android by UOT
Meter by UOT
Pick the icon you want to go with and a new window will open...then close again. Your battery icons will have now been changed, along with appropriate charging animations. It doesn't matter what resolution your phone is, this is designed to work with ldpi, mdpi, hdpi and even xhdpi.
Go back to the Theming Menu and select Option 8. Recompile "framework-res.apk" and "SystemUI.apk" (if you decompiled them earlier). This can take a little while so now's a good time to sip that coffee or munch those cookies.
Once this is done, you'll have two apps in the "out" folder on your PC. Do NOT push these to your phone unless you want to soft-brick it! They won't be signed correctly and the compression will be all wrong.
So go back to the Theming Menu and select Option 9. Prepare both files. This will open another window..and then close it again.
With both files prepared, you need to push them to your phone. Do NOT push them while the phone is running. Seriously.
Pushing system apps to the phone while it's still running can cause all sorts of problems. You could lose signal, develop random force closes, all kinds of things.
Reboot your phone and go into the recovery menu. Once there, mount the /system partition. This gives your PC access to the partition without the phone actually running its operating system.
Now go back to Tickle My Android, go to the Theming Menu, select Option 12 and push "framework-res.apk" and "SystemUI.apk" back to your phone.
Go to your phone, unmount the /system partition and reboot. It will take longer than normal but that's nothing to worry about. Once it has, you will have a shiny new battery icon!
Don't like it? Well, either go back to the battery menu, try another, compile, prepare and push or you can push your original apps back to the phone by selecting Option 13. Backups are timecoded so just pick the one that applies to you.
When you're done, either use Options 14 and 15 on the Theming Menu to clear all the folders or go back to the Main Menu and select Option 6. Resetting will wipe your backups, mind you!
And that's it. More battery icons will follow in time. If you spot anything you'd like me to include, let me know!
Other Fun Stuff
How To Change Boot Animations & Fonts
In the Tickle My Android folder, there will be seven folders. The "BOOTANIMATIONS" folder and the "FONTS" folder are for your boot animations and your fonts...as you might have guessed.
If you've found a boot animation or a font you'd like to try, put it into the appropriate folder and start up Tickle My Android.
Select Option 3 to go into the Modifying Menu and then pick either Option 4 or Option 5.
First use Option 1 to pull your phone's current animation or font and back it up.
Then use Option 2 and choose which animation or font you want to install. I've added some for you already.
If you're choosing a font, another window will open showing you what the font actually looks like.
Make sure you reboot your phone and go into the recovery menu before confirming your selection. Once there, mount your /system partition.
Pushing files to the internal memory while the phone's running can cause all kinds of nasty bugs. Fonts and boot animations should be fine but it's good practice to get into. Plus, the font won't install until you reboot anyway..
Once you're ready, push the font or animation to your phone, unmount the partition and reboot.
Don't like the results? Either try another font or animation, or use Option 3 to restore your original.
And that's it! Simple, no?
How To Transfer Personal Data To A New Phone Or Rom
To transfer your SMS's, MMS's and your contacts, go to the Modifying Menu and select Option 1 - Backup, Restore Or Transfer Personal Data
Here you can backup the data, restore a backup (backups are timecoded) or install the data onto a new device or rom.
Use Option 1 to backup your details first. The tool does its thing and...you'll get an error. Two, hopefully.
Why? Well, Android used to store this information in /data/data/ in the internal memory but, more recently, it's stored in /dbdata/databases/. Currently I don't know how to make a batch file automatically find out which option your phone uses (sorry! ) so it tries both and makes a note of which works.
Option 2 will restore your backup and will put it in the same place it came from.
Option 3 will push to either /data/data/ or /dbdata/databases/, depending on which one already has the right files.
Which basically means Option 3 will put your messages and your contacts onto any phone or rom. Very handy if you're changing device or trying out a new setup.
Please note, this will replace any existing messages or contacts, it doesn't merge the two together.
I plan to expand this section to include any sort of user detail (appointments, user dictionary, etc) just as soon as I can find out where that information is stored..
Will try it later tonight, sounds like an excellent tool.
Reserved will check it.....
Love x10 mini pro
Accidentally typed with my x10 mini pro u20i using my fingers
Hey where can i find apktool.......
Accidentally typed with my x10 mini pro u20i using my fingers
kkkhattak said:
Hey where can i find apktool.......
Accidentally typed with my x10 mini pro u20i using my fingers
Click to expand...
Click to collapse
It's already included with the tool.
Ticklefish said:
It's already included with the tool.
Click to expand...
Click to collapse
Downloaded it into the phone will try it tonight on computer......SO EXCITED
Accidentally typed with my x10 mini pro u20i using my fingers
Well, this is a good start.. Part of the code didn't quite work correctly. A new, corrected version has been uploaded and the download link has been changed in the original post.
Great!
Also think on HTC phones , not all the mods are compatible with both Samsung and htc. Thinking in the status bar mods you are thinking in adding for future releases, for example. (I had to mod them again for then to compiled orrectly).
jaggyjags said:
Great!
Also think on HTC phones , not all the mods are compatible with both Samsung and htc. Thinking in the status bar mods you are thinking in adding for future releases, for example. (I had to mod them again for then to compiled orrectly).
Click to expand...
Click to collapse
Really? Well, that's annoying. I may have to add a Sense and TouchWiz section in version 2 in that case. How did you mod the mods to get them to work?
Tickle My Android
By Ticklefish
**ALWAYS Backup Your Device Before Fiddling With It!**
Now Pulling "/system/framework/framework-res.apk"
From Android Device Into "in" Folder
--This Will Overwrite Any Existing File--
enter 'x' To Cancel Or Any Other Key To Continue: 1
error: device not found
Error! Something Has Gone Wrong! Please Try Again!
Do you have USB Debugging enabled on your phone? If yes, is it recognised by SEUS or PC Companion?
This error is caused by ADB not finding any Android device attached to the computer..
Ticklefish said:
Do you have USB Debugging enabled on your phone? If yes, is it recognised by SEUS or PC Companion?
This error is caused by ADB not finding any Android device attached to the computer..
Click to expand...
Click to collapse
usb debugging - on
seus defines my mobile and advises to upgrade my rom.
minicm7 nAa.
I seems a really good job! I'm going also to try it and give my opinion, I'm not an android expert yet. But I think it could have great development prospectives.
I tried it but it didn't work it didn't build the framework-res.apk
It said cant find sources.
Though the files in the 'in' and 'working' folders are present.
So I aborted and it was fine it didn't soft brick my phone.
can you add ICS battery and signal bar..
i think it will be a BRAVO
XGr7078 said:
I tried it but it didn't work it didn't build the framework-res.apk
It said cant find sources.
Though the files in the 'in' and 'working' folders are present.
So I aborted and it was fine it didn't soft brick my phone.
Click to expand...
Click to collapse
:-( Can you post a screenshot?
This won't soft-brick your phone unless you push a framework-res that hasn't been prepared properly so there's no worries there at least.
Sent from my U20i using xda premium
CruzEmpire said:
can you add ICS battery and signal bar..
i think it will be a BRAVO
Click to expand...
Click to collapse
Oh, I should think so. Can you provide a link and I'll take a look?
Sent from my U20i using xda premium
Moratko said:
usb debugging - on
seus defines my mobile and advises to upgrade my rom.
minicm7 nAa.
Click to expand...
Click to collapse
That's odd.
Try using the command prompt, going to the directory you put the tool into and typing in the following:
tool_files\adb shell ls
Click to expand...
Click to collapse
As long as your phone is attached to the PC and running, this will bring up a list of the files and directories in the system partition on your phone. If it says it can't find the device, then something's not right. It may be worth checking your version of java.
Sent from my U20i using xda premium
I'm trying to activate the on screen navigation bar that exists in ICS.
However... I am having difficulties with the whole process of decompiling framework-res.apk and then compiling it so I can't use that method.
I can vaguely remember I managed to do it with simply adding / changing something in build.prop, but for the life of me I can't remember what and can't find anything on searches.
I did find someone saying to try ro.build.characteristics=tablet but that changed nothing.
Anyone has an idea?
Since there's now an Xposed Framework Module available to do this same thing, that is the much better way to go than modifying your framework-res.apk directly.
Check that out here http://repo.xposed.info/module/de.makuser.nexussms
-Original post follows-
I got tired of seeing several threads about this topic so I figured I would post a "How to", which should work on all ROMs and versions around.
This procedure is actually fairly simple, and if you have basic Android and computer knowledge you can do this.
What Does This Do?
On mobile-enabled tablets like the N7 3G and the N7 LTE, the device itself is capable of sending & receiving MMS and SMS messages. Maybe you've read about how Google Hangouts got the ability to do this not too long ago. However, if you excitedly downloaded and installed the new version, you may be like "What the hell is this?!?" because by default you cannot see any SMS-related options. In Jellybean and KitKat, a device has to be "a phone" before the system thinks the device is able to send SMS and MMS messages. However, its fairly easy to change this particular property on your device so that it self-identifies as a "phone" and you get access to SMS.
Important: You actually have to have SMS service to use SMS service. Even though it boggles my mind, people have actually sometimes been confused by this particular mod, and have asked me if it somehow gives you SMS service. It does not, it only gives you access to the software functionality to send and receive SMS messages.
Even More Bolded Text!: there is one exception to this. If you are using CyanogenMod 10.2 (or 11 if they have ported Voice+ to it, not sure at this time), you can use this mod in conjunction with Google Voice and the Voice Plus app. Voice+ allows you to send & receive messgaes via the Google Voice service behind the scenes, but on the front end you can use the stock MMS.apk, or the Google Hangouts app to do this. This does not involve modifying Google Hangouts, its just sort of "bridging" Google Voice and the native SMS handling so that your Google Voice texts act like regular SMS messages. Voice+ is part of the CyanogenMod project and you can read more about it here. It's honestly pretty nice if you're a Google Voice user, since the regular Google Voice app kindof sucks.
This procedure involves modifying a boolean setting in your device's framework-res.apk file. That may sound like gibberish to you, but its still not hard to get this done.
What You'll Need
This guide is written for people who use Windows. All the utilities I'll talk about in this guide are for Windows. I'm sure its possible to do this on Mac & Linux, but the main utility I use to make this easy (FrameWork Flasher) is for Windows.
-An archive manager. I recommend 7-Zip, since it is free, open source, and can handle basically every archive format known to man.
-FrameWork Flasher. I updated this application to work with KitKat, but am not the original creator. You can download the updated version from MediaFire. FrameWork Flasher was created by XDA's own Wes Foster, and you can see his original post here.
-Some kind of text editor. I use NotePad++
-An Android device with a custom recovery installed on it. "Custom Recovery" means like ClockWork Mod, or TWRP. You need this to flash your modded file back onto your device.
Got all your stuff together? OK, on with the How Tos.
How To Do This
The first thing you'll need to do is get a copy of your current ROM's framework-res.apk file. There are a variety of ways to do this. If you're running a custom flashable ROM, like CyanogenMod, the simplest way to go is to just download your ROM's flashable ZIP file onto your computer and then open it up in 7-Zip. The file should be located inside the ZIP in the system\framework folder. Just extract that to your Desktop, or wherever you're going to keep the files you're working on.
If you're running a "stock" firmware, probably the easiest way to get your current framework-res.apk is to copy it from your current tablet. Note: this method should always work regardless what ROM you are running, I just find it easier to pull the files out of the downloaded ZIPs on a computer. You'll need an Android file manager that allows you access to the entire file system, not just the "sdcard" type area. I use SolidExplorer, but Root Explorer would work just as well. Your goal is to get the file /system/framework/framework-res.apk on your Android device onto your computer. There are probably a dozen ways to accomplish this. Super noob method: just copy this file from its original location to your "Downloads" folder, then plug your device into your computer via USB and copy the file out of the Downloads folder and onto your computer using MTP. Another method would be to send it to yourself as an attachment on an email. Hell, Solid Explorer has a SMB/SAMBA client built into it, so if you know how to use that you can just push the file directly from its original location to a shared folder on your computer. If you need a step-by-step on how to accomplish this particular step, IMO you're not tech savvy enough to be doing this stuff.
Anyways, so you should now have the framework-res.apk file from your current ROM on your computer.
Download and unzip my FrameworkFlasher-MOD file. Inside the folder, you'll see several folders and files. You need to put the original framework-res.apk file in the "place-framework-res-here" folder (how inscrutible!). Then you can run RunMe.bat.
You should get a pop-up window with a simple text-based menu. You'll want to run Option 1. The program will process for a while, and then should end up at a "The APK has been decompiled successfully" message. You can press any key to continue. At this point its not a bad idea to just leave FrameWork Flasher running.
FrameWork Flasher should have unpacked all the resources from the APK into the folder "files-to-edit". You'll need to go into files-to-edit\framework-res.apk\res\values. Inside of their, you'll find a bunch of XML files. You need to open bools.xml in the text editor of your choice. You're looking for the line that says
<bool name="config_voice_capable">false</bool>
All you need to do is change false to true, so you should end up with
<bool name="config_voice_capable">true</bool>
Then, save the file and close your text editor and go back to FrameWork Flasher.
You'll now want to run through options 2, 3 and 4. After doing this, you'll have a file called "update.zip" in the "final-zip-file" folder. You'll need to put this onto your device and flash it.
If you've flashed ROMs before, I'd hope you know how to do this. As with the "get your framework file" step, there are many different possible ways to get the update.zip file onto your device. You could transfer via USB, over the network, via email, whatever.
Once you've got the file on your device, you flash it like you do any other flashable ZIP using CWM or TWRP. This ZIP should work with either recovery, and you do NOT need to clear cache or anything like that. Simply flash and then reboot your device.
NOTE FOR T-MOBILE USERS: Some T-Mobile customers, including me, get a "New Voicemail" notification on their device(s) with voice capable turned on. This is specifically a problem with the way your T-Mobile account was initially set up and/or provisioned. The device is correctly reporting the voicemail status it gets from your account. The problem is that T-Mobile sometimes puts the "Welcome to your new voice mailbox!" message into your inbox even if your voicemail is not turned on. As far as I know there's no way to fix this issue short of working with a T-Mobile tech to get them to fix it, which I haven't bothered trying to do given the weird nature of what I'm doing. In CM10.2 you can just swipe this message away. It occurs once and only once each time the device is rebooted. On the current builds of CM11, the voicemail notfication cannot be swiped away. This is a known bug in AOSP and was fixed in 4.4.2, so the fix should come to CM11 soon enough.
Forgot to mention, since this makes your device think its a "phone", if you install Dialer.apk, you can have access to the normal "Phone" app in your Apps drawer, and mess with SIP goodness
Also, for CyanogenMod users, your ROM probably did not come with some APKs that will make this more useful.
You CAN just use Google Hangouts as your SMS/MMS app, but some people may prefer to use the native CM app instead (it has those nice pop-up messages!). For that you need MMS.apk.
If you want to mess with the "Phone" functionality, you'll need Dialer.apk.
And finally, if you want to receive emergency notifications from the government (for like natural disasters and Independence Day-style alien invasions and stuff ) you'll need CellBroadcastReceiver.apk. Please note that none of these are needed for SMS functionality and all these APKs are from CyanogenMod and will not work on stock or other ROMs.
For CM10 Stable, I grabbed these APKs out of the Nexus 4 (mako) ROM, stuck them in a zip and uploaded them here.
On CM11-M1. same deal but I used the Nexus 5 (hammerhead) ROM as my source. Those are here.
These files just need to be placed into the appropriate folder(s) on your device and then you'll need to set the file ownership & permissions the same as the rest of the the stuff in there (owned by root:root, -rw-r--r-).
They all go in /system/app, except for MMS and Dialer on CM11. On KitKat they have introduce the new /system/priv-app folder. My ZIPs contain those directories to remind you where to put the stuff.
I'm not a Windows user and I'd love to modify my own (stock) framework-res.apk to re-enable SMS support. Do you know what tools FrameWork Flasher uses "behind the scenes" to decompile and recompile the apk?
I don't like the idea of tampering with framework-res.apk using apktool unless somebody can confirm that this is the right direction.
sbiriguda said:
I'm not a Windows user and I'd love to modify my own (stock) framework-res.apk to re-enable SMS support. Do you know what tools FrameWork Flasher uses "behind the scenes" to decompile and recompile the apk?
I don't like the idea of tampering with framework-res.apk using apktool unless somebody can confirm that this is the right direction.
Click to expand...
Click to collapse
APK Tool is indeed the right direction to take.
I actually had to update the binary of APK tool that Framework Flasher uses, since the one included in the original isn't new enough to know what JellyBean and KitKat are Since FrameWork Flasher is a Windows Batch Script, I'm certain its just automatically doing stuff in the command line you could be doing by hand.
Looking at the source, I think the deompilation is done with this command:
java -Xmx%heapn%m -jar apktool.jar d "../place-framework-res-here/framework-res.apk" "../files-to-edit/framework-res.apk"
"%heapn%" is a variable, which appears to default to the value of 64.
So the command
"java -Xmx64m -jar apktool.jar d "/path/toframework-res.apk" "/path/to/extract/to"
should work on Linux or Mac, provided you've got Java installed and the jar in the current working directory. Obviously change the paths to match your local stuff. Post how it works if you'd like, I'love to update the guide to include Mac / Linux instructions, and Framework Flasher is the only "Windows" part about it.
DivinityCycle said:
Post how it works if you'd like, I'love to update the guide to include Mac / Linux instructions, and Framework Flasher is the only "Windows" part about it.
Click to expand...
Click to collapse
Obviously I messed up the resulting framework-res.apk because it got stuck in a Zygote startup loop. It's worth noting that I built apktool from the latest git sources, so there might be some bugs lurking in the shadows.
Oh well, I'll just wait for somebody else to do the dirty work
sbiriguda said:
Obviously I messed up the resulting framework-res.apk because it got stuck in a Zygote startup loop. It's worth noting that I built apktool from the latest git sources, so there might be some bugs lurking in the shadows.
Oh well, I'll just wait for somebody else to do the dirty work
Click to expand...
Click to collapse
Well, if you send me your framework-res.apk I can mod it for you. Takes like 2 seconds
The Framework Flasher source code shows the following for the actual "do the work" steps:
To decompile the original APK-
java -Xmx%heapn%m -jar apktool.jar d "../place-framework-res-here/framework-res.apk" "../files-to-edit/framework-res.apk"
To compile the new APK-
java -Xmx%heapn%m -jar apktool.jar b %~dp0files-to-edit\framework-res.apk %~dp0place-framework-res-here\unsignedframework-res.apk
To sign the APK-
java -Xmx%heapn%m -jar signapk.jar -w testkey.x509.pem testkey.pk8 ../place-framework-res-here/unsignedframework-res.apk ../place-framework-res-here/signedframework-res.apk
To build the unsigned ZIP-
7za a -tzip %~dp0place-framework-res-here\unsignedframework-res.apk %~dp0temp-files\* -mx%usrc% -r
And finally, to sign the ZIP-
java -Xmx%heapn%m -jar signapk.jar -w testkey.x509.pem testkey.pk8 ../final-zip-file/update_unsigned.zip ../final-zip-file/update.zip
note: you do not actually need to sign the ZIP. You CAN flash a zip without a signature on it, its just that with signature you get verification that the file is intact, which isn't a bad idea.
In Batch's screwy syntax, %heapn% is the variable that contains the heap size, and it looks like the default heap size the script uses is 64 unless otherwise specified by the end-user.
Also, %~dp0 is just a path expansion expression used to give the full path to the target files where its used.
I'm pretty sure you can make use of the jar and key files inside the FrameWork Flasher zip file I attached to this thread. You can find them in the resources folder. Both apktool.ar and signapk.jar are necessary, and I'm pretty sure the testkey files are needed to do the digital signatures and make this stuff work. Hope that stuff helps
Your mediafire link is just another link to download 7zip, could you update it. Thanks.
deyanimay said:
Your mediafire link is just another link to download 7zip, could you update it. Thanks.
Click to expand...
Click to collapse
Damn you multi-tasking!!! sorry about that. Fixing it nao.
The link should be http://www.mediafire.com/download/jozlg1xy4vxiegb/FrameworkFlasher-MOD.zip
when I tried to use framework flasher option 1 it said
Framework Flasher 1.1.4 - by Wes Foster (wesf90)
Please read the "Help" section before using this script
--------------------------------------------------------------------------------
----
Compression: 9 Heap Size: 64mb
````````````````````````````````````````````````````````````````````````````````
````
Main Options (in order)
-----------------------------------
(1) Decompile APK
(2) Compile APK
(3) Sign APK
(4) Create and Sign update.zip
(5) Great News! (when your finished creating the zip)
Other Options
-----------
(10) Set Compression Level for APK's
(11) Set Max Memory Size (if you get stuck when decompiling/compiling)
(12) Read Logs
(13) About / How-to / Help
(99) Exit
--------------------------------------------------------------------------------
Choose the number corresponding to the option:1
(removing old files...)
(removing old files-to-edit...)
===============++ Decompiling the APK. Please, please be patient ++==========
=====
ECHO is off.
An error has occurred. Check the log for more info.
ECHO is off.
Press any key to continue . . .
Click to expand...
Click to collapse
I attached the log. I'm trying to do this with CM 11 M1 on my deb, windows 8. Any ideas?
edit: framework-res.apk i'm trying to decompile: https://www.dropbox.com/s/iqc3eniv0u51ytg/framework-res.apk
seems like this is a common problem (googled it echo off) but I havent found a solution that works
edit 2: just tried it on my windows 7 laptop with the same result
edit 3: tried doing this with the cm 10.2 framework-res.apk with the same result.
About the voice mail message. Have you tried to install T-mobile Visual Voicemail to see if it could download then delete the message? I don't know how this app works, it's just the first thing I thought of when I read your post.
Thanks for creating this quide. I tried the single steps of the guide two weeks ago (I described it here: http://forum.xda-developers.com/showpost.php?p=47928887&postcount=167), but always got a bootloop. (De-)compiling the framework succeeded without errors and I tried it with and without changing the build.prop. By now I have no clue what went wrong. Mabye you need a special version of apktool fitting the rom you want to patch ?
Paten said:
About the voice mail message. Have you tried to install T-mobile Visual Voicemail to see if it could download then delete the message? I don't know how this app works, it's just the first thing I thought of when I read your post.
Click to expand...
Click to collapse
I've tried this and it doesn't work. I guess the app can't properly add the visual voicemail service to that line. I've also asked T-mobile about it and they said that I don't even have a voicemail box to store messages so there is nothing they can do about it.
nsmart said:
Thanks for creating this quide. I tried the single steps of the guide two weeks ago (I described it here: http://forum.xda-developers.com/showpost.php?p=47928887&postcount=167), but always got a bootloop. (De-)compiling the framework succeeded without errors and I tried it with and without changing the build.prop. By now I have no clue what went wrong. Mabye you need a special version of apktool fitting the rom you want to patch ?
Click to expand...
Click to collapse
Same here, it appears that setting config_voice_capable to true triggers an NPE inside the Keyguard class (i.e. the system PIN entry dialog) which then in turn causes SystemUI to restart over and over.
Perhaps the answer lies somewhere in the changes between 4.4 and 4.4.2 inside the AOSP device tree for deb, but I don't have the time to do an extensive diff of everything that has changed between those two releases.
Has anybody succeded in modding the stock KOT49H build without side effects?
---EDIT---
Apparently @GuyAdams managed to do it. Question is, how
cheers mate, nice post etc, been trying to get this going the last few days (and trying the other posts I've seen you talking on) but so far no luck. I'm getting the same log error as the previous poster too.
cheers
running nexus 7 with cm11 latest nightly.
burpitt said:
cheers mate, nice post etc, been trying to get this going the last few days (and trying the other posts I've seen you talking on) but so far no luck. I'm getting the same log error as the previous poster too.
cheers
running nexus 7 with cm11 latest nightly.
Click to expand...
Click to collapse
Well that sucks! It looks like APKtool doesn't work on anything newer than 4.4. I was able to reproduce the errors by trying to decompile / recompile the framework-res.apk from stock 4.4.2. The current release of APKtool from Slimbean I found here on XDA Devs appears to not be new enough. The main attraction of FrameWork Flasher over other solutions was the extremely easy & rapid download & use (as opposed to the end user having to like go download and install the entire Android dev kit), and Virtuous Ten Studio can definitely do this job, but again it looks to be an order of magnitude more complex for the average user to use. I'm going to be a little busy today doing actual work, but I should be able to find the time to work on this other stuff as well. Frustrating!
Is this working for the rom here: http://forum.xda-developers.com/showthread.php?t=2545628
And what about the carrier dont they see you now making calls and texts on a line that is set to be a tablet?
curtdragon said:
Is this working for the rom here: http://forum.xda-developers.com/showthread.php?t=2545628
And what about the carrier dont they see you now making calls and texts on a line that is set to be a tablet?
Click to expand...
Click to collapse
Did you even read my post? At no point did I say anything about "making calls", and as stated in the OP, this simply turns on the software on the tablet that allows you to send & receive SMS/MMS messages. You have to have to actually have SMS service to send / received SMS messages.
Also as carefully stated in OP, using CM10 or CM11 means you can use Voice+ to make Google Voice messages act like regular SMS.
Last but not least, the most recent builds of Bruce's CM11 ROM (the one you linked to) already have this modification applied (as he explained in the most recent few posts).
DivinityCycle said:
Did you even read my post? At no point did I say anything about "making calls", and as stated in the OP, this simply turns on the software on the tablet that allows you to send & receive SMS/MMS messages. You have to have to actually have SMS service to send / received SMS messages.
Also as carefully stated in OP, using CM10 or CM11 means you can use Voice+ to make Google Voice messages act like regular SMS.
Last but not least, the most recent builds of Bruce's CM11 ROM (the one you linked to) already have this modification applied (as he explained in the most recent few posts).
Click to expand...
Click to collapse
Hey thanks for coming off as a douchbag. Do I even read? No, perhaps you've edited your post several times since i did. Not to mention the fact that your title reads "Enable SMS on any ROM" then you go on to say that it will also enable the voice portion of the phone. Finally I asked a legitimate question it he texts why? because with ATT i have a share plan. While the plan says it's unlimited talk and text then the data is shared each device is different on the account and priced differently as well.
Also if I wanted to use Google Voice to send text messages i would just do that. Voice+ sends
But as you said this is enabled in the ROm i am using so I will exit this thread now.
You really need work on your people skills.
I do not run framework flasher is not possible to have a zip ready to be flash? I have a nexus 7 2013 LTE with cm 11 kot49h.... Thanks
Inviato dal mio Nexus 7 utilizzando Tapatalk
Does anyone with experience on the subject know whether it is possible (or im-possible) to install LG's OE Alarm/Clock app on a Samsung phone? The donor phone is an LG Optimus Fuel LGL34C on KitKat 4.4.2. The recipient phone is a Samsung Galaxy Core Prime S820L (Tracphone) on KitKat 4.4.4 and I am loathe to leave behind the stopwatch/timer function (Alarm/Clock) on my old LG. I want to transfer it over but I'm finding that's that's easier said than done.
I have found a number of websites offering a pre-packaged version that's supposed to be that app (LGAlarmClock.apk, or something close to it) sourced from a package of OE LGE apps. Unfortunately, I can't find one that will install. When I tried to install them, most of them failed from the get-go saying there was a problem parsing the file. One of them attempted to run, appeared to run normally but ended with "App not installed," existing package yadda yadda yadda. But I note that they were all of substantially different file sizes and I can't be sure any of them were for KitKat (but I know at least one was sourced from Lollipop).
So when these all failed, next I tried the App Transfer app, which is supposed to compile an installable apk from the files currently on the source phone. But when I tried to install it on the target phone, it did the "App not installed" thing again.
Then I tried a couple of PC-based data and application transference applications. One of them transferred everything except the proprietary LGE stuff, which it ignored, to include Alarm/Clock.
After than I decided to take a shot at installing it manually, so I searched the source phone for all instances of what appeared to be related files. This is what I arrived at:
/system/cust/overlay/app/com.lge.clock.apk
/system/lib/liblgomx_clock.so
/system/priv-app/LGAlarmClock.apk
/system/priv-app/LGAlarmClock.odex
/system/priv-app/LGClockWidget.apk
/system/priv-app/LGClockWidget.odex
/data/data/com.sika524.android.quickshortcut/cache/thumbnails/com.lge.clock:2130837606.0
/data/data/com.sika524.android.quickshortcut/cache/thumbnails/com.lge.appwidget.clock:2130837534.0
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@[email protected]
/data/resource-cache/[email protected]@[email protected]@[email protected]
The first file on the list was a problem because the Samsung doesn't have a '/system/cust' directory, much less '/system/cust/overlay/app.' However, it does have a '/system/app,' which is chockablock with apk files, so I stuck the file 'com.lge.clock.apk' in there.
All the others had a matching directory structure, except the shortcut thumbnail caches, which I gather were the result of the shortcuts I made on the LG phone and not required for the Samsung anyway. So I moved them to a corresponding location on the Samsung and gave them all 644 permissions, same as they were on the source phone, and same as all the other files in the same directories on the target phone.
After copying the files over and rebooting, the new app shows up in the App Drawer, and in the installed apps. Some of the functions work. The Stopwatch works. The Timer function runs but when it counts down to zero, the alarm doesn't sound and it displays the error, "Unfortunately, Alarm/Clock has stopped." If I access the Timer settings and try to change the volume, I get "Unfortunately, Alarm/Clock has stopped." If I try to change the time setting in Alarms, I get that same error. Also the same error if I try to add a city under World Clock. It's like it lacks the ability to activate the alarm tone, or to manage whichever file that stores its configuration settings.
Since the only real "wild card" in my set-up was the lack of the proper directory structure for the 'com.lge.clock.apk' file, I created a matching structure (where none existed before) with a symlink in '/system/cust/overlay/app' pointing back to /system/app/com.lge.clock.apk. That didn't work either so I deleted the link and replaced it with a copy of the file.
Still nothing changed so I gave all the new files 777 permissions, just in case there was a permissions thing I was overlooking. Zip, zilch, nada, bupkis.
So I'm outta bullets. Anybody got a spare magazine? Is it even possible?
did you ever figure this out?
DrWu said:
Does anyone with experience on the subject know whether it is possible (or im-possible) to install LG's OE Alarm/Clock app on a Samsung phone? The donor phone is an LG Optimus Fuel LGL34C on KitKat 4.4.2. The recipient phone is a Samsung Galaxy Core Prime S820L (Tracphone) on KitKat 4.4.4 and I am loathe to leave behind the stopwatch/timer function (Alarm/Clock) on my old LG. I want to transfer it over but I'm finding that's that's easier said than done.
I have found a number of websites offering a pre-packaged version that's supposed to be that app (LGAlarmClock.apk, or something close to it) sourced from a package of OE LGE apps. Unfortunately, I can't find one that will install. When I tried to install them, most of them failed from the get-go saying there was a problem parsing the file. One of them attempted to run, appeared to run normally but ended with "App not installed," existing package yadda yadda yadda. But I note that they were all of substantially different file sizes and I can't be sure any of them were for KitKat (but I know at least one was sourced from Lollipop).
So when these all failed, next I tried the App Transfer app, which is supposed to compile an installable apk from the files currently on the source phone. But when I tried to install it on the target phone, it did the "App not installed" thing again.
Then I tried a couple of PC-based data and application transference applications. One of them transferred everything except the proprietary LGE stuff, which it ignored, to include Alarm/Clock.
After than I decided to take a shot at installing it manually, so I searched the source phone for all instances of what appeared to be related files. This is what I arrived at:
/system/cust/overlay/app/com.lge.clock.apk
/system/lib/liblgomx_clock.so
/system/priv-app/LGAlarmClock.apk
/system/priv-app/LGAlarmClock.odex
/system/priv-app/LGClockWidget.apk
/system/priv-app/LGClockWidget.odex
/data/data/com.sika524.android.quickshortcut/cache/thumbnails/com.lge.clock:2130837606.0
/data/data/com.sika524.android.quickshortcut/cache/thumbnails/com.lge.appwidget.clock:2130837534.0
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@[email protected]
/data/resource-cache/[email protected]@[email protected]@[email protected]
The first file on the list was a problem because the Samsung doesn't have a '/system/cust' directory, much less '/system/cust/overlay/app.' However, it does have a '/system/app,' which is chockablock with apk files, so I stuck the file 'com.lge.clock.apk' in there.
All the others had a matching directory structure, except the shortcut thumbnail caches, which I gather were the result of the shortcuts I made on the LG phone and not required for the Samsung anyway. So I moved them to a corresponding location on the Samsung and gave them all 644 permissions, same as they were on the source phone, and same as all the other files in the same directories on the target phone.
After copying the files over and rebooting, the new app shows up in the App Drawer, and in the installed apps. Some of the functions work. The Stopwatch works. The Timer function runs but when it counts down to zero, the alarm doesn't sound and it displays the error, "Unfortunately, Alarm/Clock has stopped." If I access the Timer settings and try to change the volume, I get "Unfortunately, Alarm/Clock has stopped." If I try to change the time setting in Alarms, I get that same error. Also the same error if I try to add a city under World Clock. It's like it lacks the ability to activate the alarm tone, or to manage whichever file that stores its configuration settings.
Since the only real "wild card" in my set-up was the lack of the proper directory structure for the 'com.lge.clock.apk' file, I created a matching structure (where none existed before) with a symlink in '/system/cust/overlay/app' pointing back to /system/app/com.lge.clock.apk. That didn't work either so I deleted the link and replaced it with a copy of the file.
Still nothing changed so I gave all the new files 777 permissions, just in case there was a permissions thing I was overlooking. Zip, zilch, nada, bupkis.
So I'm outta bullets. Anybody got a spare magazine? Is it even possible?
Click to expand...
Click to collapse
probably not supposed to say this out loud but yolo i wanna give a Beretta a blow job
>>be rooted
>>have latest Lucky Patcher
>rebuild apk componants ,permissions, and resighn
>>have xposed installed
>>get module APP SETTINGS
>>edit build.prop for debug_true flag and others like test-keys making all apps debugable*dont quote me
>>>force install or side load or dont
>>>debug app changing all resorces names to your host device
>>>build an entire rom around this one clock app to make it work for some reason..
whats up with this app anyways? whys it imperative you use it?
₥ike_grips said:
probably not supposed to say this out loud but yolo i wanna give a Beretta a blow job
>>be rooted
>>have latest Lucky Patcher
>rebuild apk componants ,permissions, and resighn
>>have xposed installed
>>get module APP SETTINGS
>>edit build.prop for debug_true flag and others like test-keys making all apps debugable*dont quote me
>>>force install or side load or dont
>>>debug app changing all resorces names to your host device
>>>build an entire rom around this one clock app to make it work for some reason..
whats up with this app anyways? whys it imperative you use it?
Click to expand...
Click to collapse
This is a very very important App to this day.
Here it is 2021 it's very imperitive. For one reason.
It has a PUZZLE option for the Alarm that forces you to complete in order to turn off the Alarm
So that I will ACTUALLY wake up on time and not be late for work.
And I wanna know if this has been solved or if the above mentioned is the only pain in the ass way to do it.
.I wanna put it on my Motorola
YOLO !