[APP] MyDroid - Progress Report - G1 Android Development

I am working on an application, akin to Droid Explorer, with my own tweaks and such.
Based on the idea of Droid Explorer, My Droid allows you to update your ROM, install/uninstall applications (APKs), take screen shots, view/interact with a screencast, input commands directly into the android command line, edit the file systems, browse files, etc.
UPDATE: It seems that AndoridSpin has changed their website layout for everything, which has caused me to need to rewrite the way I am parsing their page to be able to get the Download links for the ROMs. I will be working on getting this updated within the next few days.
Currently Working:
Install Single APK
Install Multiple APKs (Batch)
Backup (nandroid/nandroid+ext/bart (including backup name for bart)
Rebooting Phone (into recovery, or plain reboot)
Powering off phone
Partially Working/In Progress:
File and Directory Explorer
AndroidSpin Integration
Currently reads the ROM Database RSS Feed. Working on implementingthat data into the application.
Needed to be done:
Uninstalling APKs
Backing Up APKs (might remove due to 'theft' of paid apps)
Installing custom ROMs
The installation of Custom ROMs is going to be the big hurdle. Not because of the steps involved in the process though, thats fairly easy. But, I am going to include updating from the AndroidSpin ROM Database (as you can see in the menus). That will parse the RSS and Summary feeds of the ROM Datbase, and you can pick/choose the ROM of your liking. It will download it, and do the installation for you, including wiping the appropriate partitions and such.
As I progress further into development, I will also include things such as "screencast", to control your phone completely from the computer, as well as screenshots, debugging, etc.
I am hoping for an initial 'pre-pre-alpha' release shortly
Download: Not Yet Available
Any questions/comments/ideas/etc would be greatly appreciated!

Pre-requisites for installing?
Will there need to be anything installed prior to this package? Will this be a seamless process from download to altering system files? I have had issues with Droid Explorer and Windows Vista, and i could never get adb to work right.
It would be very nice to have an app like this while keeping it simple. For the people who cant figure out multiple installations/drivers and such.

This would (does) require that ADB be installed (with the correct drivers) for your system. ADB should also be in your %PATH% so that the application can utilize it. I will also add an option to specify the path for ADB so that you do not have to put it into your %PATH%

Looks great! If you'd like any help testing, I'd be glad to help.
Also, keep the ability to backup. If some users choose to use it for the wrong reasons, then that's a problem with their own morality. For the rest of us, constantly cooking roms and playing with new builds, being able to easily backup and restore all of our apps is a god-send.
It's nice to have a tool that does everything you need, not just some
Again, looks great so far

Hopefully yours will work with Vista 64bit. I have adb installed and working but Droid Explorer still doesnt work currently.

Joe333x said:
Hopefully yours will work with Vista 64bit. I have adb installed and working but Droid Explorer still doesnt work currently.
Click to expand...
Click to collapse
I do not have a 64 bit machine to test this on, but seeing as it is being written strictly in .Net, and not using any 3rd party libraries, I do not see why it should be an issue.
If anyone knows of any complications that the .Net framework has with any certain functions on a 64 bit system, let me know, so I can attempt to program in appropriate work-arounds for the 64 bit crowd.

[email protected] said:
I have had issues with Droid Explorer and Windows Vista, and i could never get adb to work right.
Click to expand...
Click to collapse
I had these issues as well. My ADB was working just fine in Vista, then I installed Droid Explorer and ADB stopped working, it stopped recognizing that my device was there. Yet, ADB works just fine in my laptop.

It looks interesting I'm waiting for download link

jmhecker said:
I am working on an application, akin to Droid Explorer, with my own tweaks and such.
Features:
snip snip
Backing Up APKs (might remove due to 'theft' of paid apps)
Click to expand...
Click to collapse
if you disable this feature...people will just find another way to steal paid apps(its not the hardest task).... just sayin
i say you keep it

PanPiotr said:
It looks interesting I'm waiting for download link
Click to expand...
Click to collapse
That might be a while. I have a long way to go to even consider an alpha release, heh.
jamezelle said:
if you disable this feature...people will just find another way to steal paid apps(its not the hardest task).... just sayin
i say you keep it
Click to expand...
Click to collapse
Okay, y'all twisted my arm, I'll add that feature

Hmmm looks pretty promising, wouldnt mind tryin it, n am I the only 1 who thinks this is the wrong section? This should be in the Apps section

i also thought creating such app, i wanted to start working at it these days but it seems someone else already doing it, keep the good works, cheers

AsaSpades said:
Hmmm looks pretty promising, wouldnt mind tryin it, n am I the only 1 who thinks this is the wrong section? This should be in the Apps section
Click to expand...
Click to collapse
No you're not only one, I'm also think this is wrong section.

Just a quick update:
Progress is coming along nicely. A lot of features are implemented as of now, but not enough to constitute an alpha or beta release.
What I am currently working on is the parsing of the AndroidSpin database (using their RSS feed). That progress is coming along great, just a few hiccups.
Any other feature requests besides what I have listed in the OP?
And for those complaining that this is in the wrong section, please clarify as to where you think it should be, so I can be sure that future posts go to there.

Okay, time is coming close for a Beta.
I have finished the AndroidSpin RSS portion. I have successfully used my application to browse the ROMs (categorized by phone) from the AndroidSpin RSS feed, selected a rom, downloaded it, copied it to the SD card, rebooted into recovery, performed a nandroid and bart backup, wiped all 3 items(system/dalvik/ext), installed the new ROM, and rebooted, without ever having to touch my phone.
I need to do some code cleanup in that area to streamline the process, but at least I know it works
After I streamline the ROM upgrade process, I am going to work on getting things like screenshots, screencasting, etc, working as they should. Nothing really difficult with any of that, but just time consuming to get it all pieced together properly.
I am hoping for a beta release sometime soon.

any progress?

looks good.. now will this be open source?

Related

[How To] Install AmazonMP3 on Haykuro, Dude's, and JF's Firmware

Hi everyone, as many of you guys have noticed, the newer firmwares do not come with the Amazon MP3 application. For those of you who want this, here is a tutorial on installing.
First, download the com.amazon.mp3.zip file uploaded, and place it on your desktop. DO NOT OPEN IT OR EXTRACT IT. Change .zip extension to .apk. For those of you who do not know how to do that, hit Start> My Computer> Organization> Folder and Search Options> and Uncheck "Hide Extentions for Known File Types". Then, delete the .zip extension and type in .apk. Have your G1 ready and plugged in, as you will be using ADB to install this program.
Open up command prompt and type:
cd desktop
adb install com.amazon.mp3.apk
exit
It should now be installed!
For those of you who do not have ADB installed for whatever reason, place the com.amazon.mp3.apk onto your SDcard. Then, using a file manager on your G1 (I use OIfilemanager) navigate to the location where the file is placed and install.
Also, the com.amazon.mp3.apk can also be extracted directly from RC and JF 1.4x builds.
NOTE TO MODS: I understand that Amazon MP3 is not an open source application. Therefore, if for any reason if you guys do not feel that uploading this apk is allowed, feel free to remove this post.
Paying $1 per mp3 can add up over time
With RC 33 i wanted to removed this program, now that JF 1.50 removed automatically, do you believe that i will tried this? But thanks anyway...
PS- People DL music MP3's on theirs PC' for free, Amazon Sucks!
Sometimes I find Amazon MP3 useful for previewing a CD while I am at the library.
By the way, there is no need to distribute the apk here when anyone can just extract it themselves legally from an official update.zip
jashsu said:
Sometimes I find Amazon MP3 useful for previewing a CD while I am at the library.
By the way, there is no need to distribute the apk here when anyone can just extract it themselves legally from an official update.zip
Click to expand...
Click to collapse
Yeah I understand that, I'm just saving them the trouble of having to do it themselves. However, when you say "legally" do you mean distributing this apk is illegal? If so I will remove it.
SolemnWishing said:
However, when you say "legally" do you mean distributing this apk is illegal? If so I will remove it.
Click to expand...
Click to collapse
It's not expressly forbidden. The general stance on xda is as long as the software in question isn't payware, then it is okay (of course a mod is free to make a judgement otherwise). However, everyone should have a RC33 or somesuch build lying around that they can extract the file from themselves anyway.
Seems that most folks don't appreciate the usefulness of Amazon MP3 as a source of track preview. I just wish that it still integrated into ShopSaavy and CompareEverywhere. Used to be you could scan a barcode of a CD and it would pull up the CD on Amazon MP3. If anyone knows how to make this work with current software versions, let me know.
Thank you for the explicit directions. This worked great on my G1 and my friend's using a mac.
Well, I guess that means we will wait for a mod to say something... next in line.. PDFviewer.
Okay, PDFviewer will not work on my JF1.50 build. Just for fun I also tried to push the H build camera and the H build dialer. The pushed camera resulted in the camera app disappearing all together along with the camcorder, gallery and picture frame widget. The H build dialer caused the phone to be completely unresponsive.
Remember, always use a Nandroid backup when attempting risky procedures
SolemnWishing said:
Well, I guess that means we will wait for a mod to say something... next in line.. PDFviewer.
Okay, PDFviewer will not work on my JF1.50 build. Just for fun I also tried to push the H build camera and the H build dialer. The pushed camera resulted in the camera app disappearing all together along with the camcorder, gallery and picture frame widget. The H build dialer caused the phone to be completely unresponsive.
Remember, always use a Nandroid backup when attempting risky procedures
Click to expand...
Click to collapse
If you want to extract features from Haykuro's H build for 1.50 installation, I suggest you hook up ddms so you can get realtime debugging and see what libraries/functions are being called that are causing problems. It should work in the emulator too.
By the way PDFViewer's dependencies have been well established, but the program checks some unknown properties of the build and will refuse to run for non-HTC builds. Decompiling the dex might lead to clues as to what it is and how to workaround it or patch the apk. I'm actually hoping it will just run unmodified on the official T-Mo 1.5 rom expected any day now.
jashsu said:
If you want to extract features from Haykuro's H build for 1.50 installation, I suggest you hook up ddms so you can get realtime debugging and see what libraries/functions are being called that are causing problems. It should work in the emulator too.
By the way PDFViewer's dependencies have been well established, but the program checks some unknown properties of the build and will refuse to run for non-HTC builds. Decompiling the dex might lead to clues as to what it is and how to workaround it or patch the apk. I'm actually hoping it will just run unmodified on the official T-Mo 1.5 rom expected any day now.
Click to expand...
Click to collapse
hehehhe! We can always dream can't we...
lol HTC dream.. well, I do not know how to work apps, or port them or anything, so that is pretty much out of the question. Ill just stick with the obvious ones.
Much thanks!! I wanted Amazon back.
thanks
works on JF flawless. no issue yet. Thanks.
I installed the Amazon MP3 apk night before last and found that the search function wouldn't open its search box. I uninstalled and then pushed it to /system/app via adb and now it works just fine. FWIW, I have apps on SD (the symlink version).
That is good, and does anyone know if the Teeter game from the original Haykuro H build requires some sort of special resource or something? As the game installs, but force closes on startup.
thank you very much for this... anybody got a fix for myfaves???
jashsu said:
If you want to extract features from Haykuro's H build for 1.50 installation, I suggest you hook up ddms so you can get realtime debugging and see what libraries/functions are being called that are causing problems. It should work in the emulator too.
By the way PDFViewer's dependencies have been well established, but the program checks some unknown properties of the build and will refuse to run for non-HTC builds. Decompiling the dex might lead to clues as to what it is and how to workaround it or patch the apk. I'm actually hoping it will just run unmodified on the official T-Mo 1.5 rom expected any day now.
Click to expand...
Click to collapse
hehehe. the properties aren't unknown. It's a library, and 2 framework files.
TheDudeOfLife said:
hehehe. the properties aren't unknown. It's a library, and 2 framework files.
Click to expand...
Click to collapse
So you have PDFViewer working without the "Only for HTC devices" nag screen?
Haha mind enlightening us??
someone run some diffs on thedudes libs and framework files =P!

Rooted my EVO and now I'm lost....

I don't know anything about this programming. I am a complete idiot when it comes to this stuff. I rooted the phone because I wanted to be have full control over it's capabilities going forward, but I didn't realize I'd need to use these programs on my computer to do it. I thought things would be available through simple downloads.
Anyway, I've spent the last several hours attempting to become at least functional so that I could install another OS on my phone. I have no idea what rebooting in recovery or clearing caches or any of this is. I know it's probably simple, remedial stuff to practically everyone reading this but I am clueless.
I'm sure I could learn and was willing to do so. I downloaded SDK and Java update and Eclipse and painstakingly followed installation instructions several times from several sources. And I can't get the adb to function. My computer won't recognize the path. I'm pretty certain that I've installed everything completely and updated the path accurately, etc. I go through cmd, type in adb and it says it's not recognized as an internal or external command, operable program or batch file.
I've gotten to the point where I just want to set my phone back to the way it was when I bought it 2 days ago. I want to go back to being a simple lemming and just oblivious to this whole world. I don't belong over here. I'm out of my league and I know it.
Now the problem I have is that it's supposedly easy to "unroot" the phone. You just have to download 3 things and "flash" them. I don't even know what the **** that means though. And if it invloves using adb (or abd...I don't even know that), then I'm screwed.
I'm really frustrated guys. I'm tired. I should have never attempted this, but it all sounded so easy and awesome. Now I just want my normal, restricted phone back. Can anyone help me?
OK. I got the phone back to it's original state. I know some of you are probably shaking your heads at the decision, but it makes me feel a lot more comfortable.
Maybe if I could figure out how to access adb, it would be different but I just felt handcuffed without it. Well there eventually be ROMs that are more easily installed like re-installing the original was? Will there be ways to just steam it through HTC Sync?
i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.
SupremeBeaver said:
i think one reason why u didnt manage to get adb working is because u didnt set up the environmental variables for java. Go into command prompt and type java. See what that returns.
Click to expand...
Click to collapse
Thank you for the response. That command produced a long string of information. Is there something in that I should be looking for, or was this just a test to see if it would be recognized?
it was a test to see if java was working fine. By string of commands do u mean like this:
http://img682.imageshack.us/img682/8440/48798806.jpg
Otherwise the problem may be that you havent specified the environmental variables for the android sdk.
Right click on My Computer and go to properties, under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Now what u need to do is add the location of ur sdk to the end of the "Variable Value".
So if u put the adroid sdk folder in the root of ur C drive, then u would add this line
;C:\Android\tools
to the end of the Variable Value line. This depends on where u put the skd folder though. Whats important here is u dont replace whats already there! Just add the line to the end, even the ";" symbol.
Hope this helps. let me know how it goes
Thank you again for the response. Yes, that looks to be the same screen information that appears when I run java in command.
I have the SDK in a folder named AndroidSDK on the root of my C drive. I have added the line ";C:\AndroidSDK\tools" to the end of the path. One thing I just realized is that when I double click the AndroidSDK folder, the next screen contains a single folder named "android-sdk-windows". When I double click that folder I see subfolders for add-ons, platforms, tools, SDK readme, and SDK setup. I'm wondering now if I need to include that "android-sdk-windows" in the path line in order for it to find adb in the tools.
I would really like to solve this adb issue. I still want to learn enough about this stuff to root the phone again and feel comfortable working with it. I'm completely obsessed with this right now. It's driving me mad.
in that case the line you should add would be
;C:\AndroidSDK\android-sdk-windows\tools
I can't believe it was that simple!
Actually I can believe it. Thank you so much for your help. Sorry if I came off as a bit of a drama queen in the OP, but I have just spent about 6 hours messing with this if you include the rooting.
Ok. I think I'm going to give it all another shot. Thanks again. I may be back to this thread again if I end up running into another dead end though.
Glad it worked
Dont worry about it, i can understand ur frustration because this is by no means straight forward.
Hope u enjoy playing with ur soon to be rooted EVO
If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?
Im not too sure with that actually. I dont have an EVO (or any android phone for that matter). But yeah i think the superuser app should appear without flashing a custom rom.
I think you might want to create a thread in the EVO section where im sure many EVO owners will help u out with this. Or maybe a mod could move this thread?
JelloB said:
If you have time to answer another question, I went through the OTA Simple Root process again and everything appears to have worked. But I don't think that finishes the phone in root. I don't have a Superuser app, for instance.
Isn't there something else I need to do? (Install a custom rom maybe?)
If so, how do I accomplish it in the least technical way possible?
Click to expand...
Click to collapse
Disclaimer - I have not used the simple root method.
That being said I have helped a few people with this and it seems that the last img file that it flashes does not have super user access. You need to flash a custom ROM in order to fix that. I will post a link to the thread that I was helping in and that should answer some of your questions on how to do that.
Hope that helps
http://forum.xda-developers.com/showthread.php?t=722194
Sent via the Sprint HTC EVO
Just wanted to update this. I finally was able to put it all together. I was previously unaware of the "extras" tab on the OTASimpleRoot program. Just didn't read the instructions in post well enough, which is the story of my life....but I digress.
Anyway, I was able to root the phone again, flash recovery and now I have even gotten to the point where I understand a little bit how to install custom roms. In fact, I just installed my first using Baked Snacks latest update. I've also downloaded ROM manager so in the future I should I have no trouble at all (even though I'm pretty comfortable doing it the "long" way now).
Thanks again to both of the guys above who took the time to read and respond to a complete newbies questions.
I now that I have successfully loaded a custom ROM onto my EVO that it is full root and I don't have to worry about that anymore. I don't have a "superuser" app that I can tell, but I do have a "dev tools" app and folders which I don't think were on the phone before.
Alright, I do have a superuser permissions app. When I click it nothing happens though. I don't know if that's normal or not.
The issue I'm having now is that when the phone was rooted it took it back to the 1.17.651.1 software version. I went through the steps in the "How to start over: Fully rooted stock 1.47..." thread but the phone doesn't appear to be reading the PC36IMG.zip file. It doesn't ask if I want to update it. I tried it a couple times and then skipped to the second file in that thread (su-2.1-e-unsecure-signed.zip) and got a message about ....something "build". Went ahead with the install but I don't see anything different. Still says I'm on software 1.17.....
Wireless tethering app doesn't work for me, which was the impetus to dig further into this....deeper down the rabbit hole.
Ok. This will be my last update but I'm pretty excited because something has happened to correct issues I was having.
I thought I would go through the root process from start to see if I could get the 1.47 software. Once I got to the second step and did the factory reset, upon reboot it took me to the recovery screen which was different and made me a little nervous. I found the cue to install BakedSnack again from the sdcard and chose that function.
This time things were different than before. For instance, upon booting the phone I got a cool screen saver with streaming, trippy colors instead of the 4G and Sprint crystaline logos. I don't remember this happening the first time I installed this ROM. Once I got into the phone I noticed some minor changes I didn't notice the first time. The music widget wasn't on the second page, nor the nascar or football crap either. I think they were there before. Then I went into apps and saw ROM manager installed and superuser and Wifi tethering. Went straight to wifi tethering and low and behold it works like a charm.
Last but least, I went to check the software and I am now running 1.47. I don't know why it's on their now. This is all still a little mysterious to me. I could swear this Baked ROM is a little different than the first time I had it on the phone. Maybe that's my imigination. Maybe the factory wipe did something. I don't know but I'm very happy now.
Congrats
SupremeBeaver said:
Congrats
Click to expand...
Click to collapse
Thanks again man!
What a difference 24 hours can make. At this point last night I was ready to pull my hair out in frustration. By noon today I had unrooted the phone and re-installed the most recent OTA software update and was ready to just stick with that. Now I have re-rooted, somehow managed to get the updated software back on the phone, and have installed and am running an incredibly awesome custom ROM.
I love my new phone. Thanks again to both of you guys who offered help. I think I'm going to be good from here on.

[Q] Roms and patches - is it this easy?

When I first got my G-tab I was baffled by all the instructions and the literally thousands of posts in the forum. Even now, I haven't been able to find exactly how (or why) I should update my kernel. That said, I have TNT Lite running and I love my g-tab. Exploring the possible uses and utilities on it provides hours of fun. Now - here is my question. I stumbled on some instructions for installing the ROM and I have used those same instructions to install several patches to the Rom. I see all this commentary on Clockwork, side loading, etc. and I wonder if I am missing something. Today I just installed the .25 patch for TNT-Lite. I downloaded the rar file, unzipped it on my PC to get the Recovery folder and the update.zip file. I plugged the g-tab into the pc and switched it to usb mode. Then I moved the old recover folder and update.zip to a folder (cautious me) and put the new ones in the root. I disconnected the usb and started the g-tab in recovery mode (holding the power and volume+ key. It rebooted, applied the patch and I was done. That seems simple enough. It would seem that this would work for switching roms, applying patches and probably even upgrading the kernel (If I knew where it was and why I should do it). Am I missing something? Everything seems to work.
Sounds like you got the basics ok.
The real main reason to update the kernal as i see it is to add things like driver support for devices like gps and g3, so on, also minor fixs. If your not using your gtab for anything like this you maybe happy to stay stock. But if you like myself like to use your gtab to surf with g3 or as a sweet gps, then thats what the kernal updates allow. Im sure others can correct me if ive got anything wrong or add to what ive said.
You got the basic steps right, but installing ClockWorkMod Recovery has a lot of benefits.
First, built in backup and recovery will save your skin if the gTab get "cranky".
Second, installing ROMs and/or updates saves you a few steps. From "tar" files (TnT-lite), extract the update.zip file to a folder (I created a folder named "xda", just an example) and name it after the version of ROM/update.
CWM will flash "*.zip" file. This way you can keep multiple ROMs/updates on the card and switch between them.
CWM lets you clear cache, wipe Data partition, clear Dalvik-cache (use caution there), fix permissions and so much more! It is a great tool.
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
So now we peel back another layer
OK so now the question of multiple roms comes up. I am not clear about the role of the rom - can I switch roms and keep all of my apps and data intact? I'm thinking like changing style sheets on a web page - presentation is different but the underlying data is still the same? Is it that easy?
And... if I am doing that perhaps I need to "clear cache" or "wipe data partition" but although I like to investigate new things I'm not willing to just walk up and push the big red button without knowing what it is for. So why would I "clear" or "wipe" things?
I get the impression that I could switch between ROMs just like switching between browsers on a pc - today Chrome, tomorrow, Firefox and never Internet Exploder... Is that correct? It took me quite a while to get the market working and it still doesn't work optimally but I'd hate to undo all the work I've done getting the g-tab humming along by switching roms. Can I?
So - anyone care to expound on the structure and how it all hooks together? What parts can be swapped out and what parts form the foundation? I'd hate to brick the little guy in my ignorance.
One final note if you know and you answer - where did YOU learn about this. Is there a book somewhere to read?
Thanks again for sharing your knowledge.
The Need for A Wiki
I'm in the same boat as enigma. I'm not even sure what ROM is an acronym for, though I think it means operating system. A wiki would be a big help for many people. I bet people would be glad to contribute.
Well, I don't know about Android book, especially about "hacking android book" , but this (and others) forum has plenty of reading material and guides. Not to mention people (a lot more knowledgeable and experienced than me) who will offer advice and lend a hand. And Google search comes in handy too.
Switching ROMs is almost like switching the OS, or a flavor of. Very much like switching between Linux distributions; the base OS is the same, but the overlay changes the user experience. Some things do change deep down inside, that's why is advisable to clear data.
Android, like Linux which it is based on, uses separate partitions for different parts of the OS, like boot, recovery, data, cache and user data. Plenty of write ups and discussions on the web on that.
So when flashing a ROM, you'll rewrite boot and system. Your user apps and data/preferences pertaining to those apps are stored in data partition, and since you are changing the 'OS', the apps need to be recompiled for it. Backup apps, like Titanium Backup, come extremely handy here: backup and restore apps AND appdata with a few clicks.
Backups are stored on sdcard, which is a lot like Linux /home directory, and do not get wiped during flash. Also the CWM (sometimes called Nandroid) backups are also stored there. A backup-of-the-backup is always a good habit (copy of /sdcard to your PC for safekeep).
This is just a quick rundown, hopefully that answered some of the questions.
There is a world of information available out there in "ether-world", Google is your friend.
[EDIT]:
Some links:
http://android-dls.com/wiki/index.php?title=Main_Page
http://lifehacker.com/#!5596108/how-to-choose-the-right-android-rom-for-you
and of course:
http://forum.xda-developers.com/forumdisplay.php?f=841
(use the search on top of the screen)
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
TeamSpeed said:
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
Click to expand...
Click to collapse
Yes, your Sticky is as clear as Florida sky.
I just installed Thumb Keyboard on my gTab last night and I guess I got carried away getting used to it!
Yes, I have found some very good step by steps (reflashed to vegan after reading that one). Step by steps are great but I 'd like to understand why I'm doing it. The market fix...I can follow the steps and it works but why? I wish I had time to research all these things but there are so many forums,so many posts to read! The explanation that did surface in this thread was great though. Thanks. I'll keep asking questions. There are a lot of smart people out there!

App removal - bloat (Depreciated thread - See OP for update links)

UPDATE/EDIT: September 12th, 2011 -
I am depreciating this thread and will no longer check on or support it. For more information on this topic:
See MT4GS Stock App Encyclopedia for information about the apps themselves.
See Bloater to make stock app removal easier then you could ever imagine it being.
UPDATE/EDIT: August 21st, 2011 -
Posts 19 through 25 are a summary and how-to of what we have learned about removing apps from the stock rooted rom so far. Skip ahead if you want, otherwise the thread is a good read all the way through.
Now that we have a working S-OFF/Root procedure, a lot of us want to kill some of the stuff that came pre-loaded on our phones.
Root is required, and performing a backup through Clockworkmod is a necessity as well. Both backup and restore actions have been tested and working in CWM 4.0.0.9.
I am not responsible for what happens to your device after removing these files, so make sure you make a CWM backup BEFORE you start mucking around with this.
Some other threads that have been dealing with this for this device are Here, Here and Here. I would like to thank the people who have contributed, and continue to do so in those threads. I made this one in "themes and apps", as I think that people in the future coming in will look here first and this may cut down future confusion and questions.
There are a couple of ways you can accomplish this, but i'll start with the (almost) longest way. See the bottom of the post for other options.
We will be using a file manager to accomplish this task, "File Expert", free from the Google market. (I recommend "Root Explorer", a paid app, but if you've come this far you should get it at some point).
You will need to hit options, choose more, then Mount. Select "Mount as Read Write" to be able to delete the files/folders.
Listed below are the apps and what you have to delete to remove them.
Archived to code tags to make the post smaller. The summaries I wrote out are full page further in the thread, so it's easier to see the whole process.
Themes:
Code:
Aubergine
/system/app/aubergine.apk
/data/data/com.tmobile.theme.aubergine
Brooklyn
/system/app/Brooklyn.apk
/data/data/com.tmobile.theme.brooklyn
Jazz
/system/app/Jazz.apk
/data/data/com.tmobile.theme.jazz
Retro
/system/app/Retro.apk
/data/data/com.tmobile.theme.retro
Spring
/system/app/Spring.apk
/data/data/com.tmobile.theme.spring
Live Wallpapers
/system/app/LiveWallpapers.apk
/system/app/LiveWallpapers.odex
/data/data/com.android.wallpaper
Magic Smoke Wallpapers
/system/app/MagicSmokeWallpapers.apk
/system/app/MagicSmokeWallpapers.odex
/data/data/com.android.magicsmoke
Music Visualization Wallpapers
/system/app/VisualizationWallpapers.apk
/system/app/VisualizationWallpapers.odex
/data/data/com.android.musicvis
Sense Live Wallpaper
/system/app/Mode10Wallpapers.apk
/system/app/Mode10Wallpapers.odex
/data/data/com.htc.android.wallpaper
Streak Live Wallpaper
/system/app/HTCLivewallpaperStreak.apk
/system/app/HTCLivewallpaperStreak.odex
/data/data/com.htc.livewallpaper.streak
Weather Live Wallpaper
/system/app/HtcWeatherWallpaper.apk
/system/app/HtcWeatherWallpaper.odex
/data/data/com.htc.WeatherWallpaper
Widgets:
Code:
HTC Widget Download Manager
/system/app/WidgetDownloadManager.apk
/system/app/WidgetDownloadManager.odex
/data/data/com.htc.wdm
Bookmark Widget
/system/app/htcbookmarkwidget3d.apk
/system/app/htcbookmarkwidget3d.odex
/data/data/com.htc.fusion.htcbookmarkwidget
Calculator Widget
/system/app/htcCalculatorWidget.apk
/system/app/htcCalculatorWidget.odex
/data/data/com.htc.android.fusion.calculator
Calendar Widget
/system/app/htccalendarwidgets3d.apk
/system/app/htccalendarwidgets3d.odex
/data/data/com.htc.htccalendarwidgets
Clock Widget
/system/app/htcclock3dwidget.apk
/system/app/htcclock3dwidget.odex
/data/data/com.htc.clock3dwidget
FM Radio Widget
/system/app/com.htc.FMRadioWidget.apk
/system/app/com.htc.FMRadioWidget.odex
/data/data/com.htc.FMRadioWidget
Friend Stream Widget
/system/app/com.htc.FriendStream3DWidget.apk
/system/app/com.htc.FriendStream3DWidget.odex
/data/data/com.htc.FriendStream3DWidget
Mail Widget
/system/app/htcmailwidgets3d.apk
/system/app/htcmailwidgets3d.odex
/data/data/com.htc.htcmailwidgets
Messages Widget
/system/app/com.htc.htcmsgwidgets3d.apk
/system/app/com.htc.htcmsgwidgets3d.odex
/data/data/com.htc.htcmsgwidgets3d
Music Widget
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.MusicWidget.odex
/data/data/com.htc.MusicWidget3D
Photo Widget
/system/app/HtcPhotoWidget.apk
/system/app/HtcPhotoWidget.odex
/data/data/com.htc.photowidget3d
Setup Widget
/system/app/HtcSetupWidget.apk
/system/app/HtcSetupWidget.odex
/data/data/com.htc.setupwidget
Sync Widget
/system/app/com.htc.Sync3Dwidget.apk
/system/app/com.htc.Sync3Dwidget.odex
/data/data/com.htc.Sync3DWidget
Tips for Home Widget
/system/app/HtcTipWidget.apk
/system/app/HtcTipWidget.odex
/data/data/com.htc.rosiewidgets.tip
Trends Widget
/system/app/com.htc.TrendsWidget.apk
/system/app/com.htc.TrendsWidget.odex
/data/data/com.htc.Trends3DWidget
Twitter Widget
/system/app/com.htc.Twitter3DWidget.apk
/system/app/com.htc.Twitter3DWidget.odex
/data/data/com.htc.Twitter3DWidget
Weather Widget
/system/app/HtcWeather3DWidget.apk
/system/app/HtcWeather3DWidget.odex
/data/data/com.htc.widget3d.weather
System-Type Apps:
Code:
App Sharing
/system/app/appsharing.apk
/system/app/appsharing.odex
/data/data/com.htc.appsharing
AppPack
/system/app/MallLite-4.0.92.apk
/data/data/com.tmobile.appack
Backup
/system/app/MobileBackup.apk
/data/data/com.voxmobile.sync.mobilebackup2
Calculator
/system/app/calculator.apk
/system/app/calculator.odex
/data/data/com.android.calculator2
Home Screen Tips
/system/app/Protips.apk
/system/app/Protips.odex
/data/data/com.android.protips
Setup
/system/app/HTCSetupWizard.apk
/system/app/HTCSetupWizard.odex
/data/data/com.htc.android.htcsetupwizard
Swype
/system/app/Swype.apk
/data/data/com.swype.android.inputmethod
T Mobile Device Carbon
/system/app/TmobileAndroidDeviceCarbon-c42-n123.apk
/data/data/com.zipwhip.devicecarbon.tmobile
T Mobile TV
/system/app/com.mobitv.client.tmobiletvhd
/data/data/com.mobitv.client.tmobiletvhd
Video Chat
/system/app/qik.apk
/data/data/com.qiktmobile.android
Apps:
Code:
Adobe Reader
/system/app/AdobeReader.apk
/data/data/com.adobe.reader
Bejeweled 2
/system/app/Bejeweled2_trust5.apk
/data/data/com.eamobile.bejeweled2_small
DT-Sync
/system/app/desktopPointer-signed-v6.apk
/data/data/com.doubletwist.desktopPointer
Facebook
/system/app/HtcFacebook.apk
/system/app/HtcFacebook.odex
/data/data/com.htc.socialnetwork.facebook
Flickr
/system/app/flickr.apk
/system/app/flickr.odex
/data/data/com.htc.socialnetwork.flickr
Friend Stream
/system/app/FriendStream.apk
/system/app/FriendStream.odex
/data/data/com.htc.friendstream
Media Room
/system/app/MediaRoom.apk
/system/app/MediaRoom.odex
/data/data/com.htc.MediaLauncher
Netflix
/system/app/netflix-17-release-android-marketplace-upgrade.apk
/data/data/com.netflix.mediaclient
Peep
/system/app/HtcTwitter.apk
/system/app/HtcTwitter.odex
/data/data/com.htc.htctwitter
PhotoGrid
/system/app/HtcPhotoGridWidget3D.apk
/system/app/HtcPhotoGridWidget3D.odex
/data/data/com.htc.rosiewidgets.photogridwidget3d
Polaris Office
/system/app/PolarisOffice.apk
/data/data/com.infraware.docmaster
Slacker Radio
/system/app/slackerradio.apk
/data/data/com.slacker.radio
Telenav GPS Navigator
/system/app/TMOUS_Navigator.apk
/data/data/com.telenav.app.android.telenav
Zinio Reader
/system/app/ZinioReader.v2.03.3312.Regular.apk
/data/data/com.zinio.mobile.android
ZS Provider
/system/app/ZinioSettingsProvider.v2.03.3198.TMobile.Smartphone.apk
/data/data/com.zinio.android.settings
I have removed all of these apps from my system, and it still runs fine. No problems.
You may get a crash report to send to HTC while removing some of these things (I denied it), but you can ignore it. You will get them it when removing themes for sure.
I don't see why using an app to remove these (like Absolute System) would be an issue - just make sure to go back and manually delete the .odex files, as such apps probably won't get them.
And, of course, you could always use a terminal emulator to (rm) remove the files/folders manually.
Also, for the more adventurous: (but it wasn't a problem)
Internet
/system/app/Browser.apk
/system/app/Browser.odex
/data/data/com.android.browser
(I replaced with "Opera Mobile" by Opera Software ASA - Free app)
Mail
/system/app/mail.apk
/system/app/mail.odex
/data/data/com.htc.android.mail
(Removing mail does not prevent GMAIL from working correctly)
Music
/system/app/HtcMusic.apk
/system/app/HtcMusic.odex
/data/data/com.htc.music
Music Enhancer
/system/app/HtcMusicEnhancer.apk
/system/app/HtcMusicEnhancer.odex
/data/data/com.htc.musicenhancer
(I replaced with "Android Music" by JRTStudio - Free app)
If anyone else finds things they can safely remove, please post it for others to play with.
Have fun!
deleted most of those and got
'uids on the system are inconsistent' every time on boot
careful...
Can you list which ones you removed to cause that?
Also, were you using a theme that you deleted?
CWM backup is vital when starting to mess with this - I haven't had to restore due to system issues.
I'd love to try to duplicate your problem on my phone to find a fix. Thanks!
I prefer not to actually delete apps in case I ever want to unroot (though this probably isn't that likely but still) and I understand that by doing so, those apps need to be present. if any of you are interested, there is a free app on the market that I discovered. just search "antek" in the market and it freezes whatever bloatware you have so that it no longer runs in the background and should you want to recover it, all you do is just "defrost" it and it runs exactly as it did before. I've saved loads of battery by using this.
I'm using a custom theme that wasn't deleted. I understand that I could get the cyanogenmod fix_permissions script to fix this, but haven't located it yet.
I stuck to your list before this happened except for swype and a few others.
Wasn't looking for help with the issue, just wanted to let you know it happened. Ofcourse I made a backup before and after.
fix_permissions didn't solve. Gonna restore and try again. Btw I didn't freeze first, I just deleted. Doubt that's the reason though.
Protricity said:
fix_permissions didn't solve. Gonna restore and try again. Btw I didn't freeze first, I just deleted. Doubt that's the reason though.
Click to expand...
Click to collapse
I'm sorry to hear that it's not working out so great for you. Glad to hear you did a backup first though.
It might be good to note, and I should have said it at the beginning, I did a fresh factory reset on my phone just before the S-OFF/Root procedure, and hadn't used any of the things I got rid of.
They were basically just deleted right off the phone before it got used.
Keep us updated on how it's going, and as info comes in i'll add what I can to help. Knowing what apps you got rid of specifically could narrow it down some, and what ones you used first might help as well.
Of course, restoring a backup eliminates the problem, and you may or may not be able to reproduce after - please let us know either way, and thanks for the input!
For our next trick, we're gonna dump HTC Sense.
Blue6IX said:
okay - sorry to post after myself but I got rid of kidzone.
First, I restored a CWM backup I made right after root/busybox installation.
So, my phone state is fresh S-OFF/Root with SU & busybox installed.
It may be important to note that I did a factory reset to my phone just before S-OFF/Root & had a freshly formatted MicroSD card.
I then installed ADW Launcher from the Market, and hit my "home" key. Selected "Use Default" and chose ADW Launcher.
Now my phone defaults to ADW as it's launcher.
I then installed "Absolute System" from the Market, and used it to remove "HTC Sense"
Closed out Absolute System, then scrolled between all 5 ADW desktop screens, powered down the phone, then powered up again. (*NOTE fastboot = off)
Booted fine, was able to ditch sense without issue, and KIDZONE IS GONE!
As always, make sure to do a fresh system backup before messing with anything like this, but Kidzone is linked to sense, and replacing sense with another launcher will remove it.
HTC Sense was the only app removed from the phone, and I haven't checked everything to make sure it works yet, but no HTC crash report to send, and no force close issues. (yet - to be determined)
I've been itching to ditch sense since I got the phone, and this was my first quick test at it. Works good so far.
Edit to add:
Checked the "personalize" option at the top of the "settings" list. This just brings you back to the main desktop, doesn't throw an error.
I knew this one thing would be messed up somehow after ditching sense, but the fact that it doesn't make a problem and just closes the menu is fine by me.
I'll spend the rest of the day testing out my phone without sense to see how it runs. I'll post back how it went tomorrow.
Click to expand...
Click to collapse
Quoted myself from the kidzone thread, I want to put the info for slimming down my phones apps here.
I'm going to see how the phone runs on just the free version of ADW for a day, then see about coming up with a procedure to remove apps and keep it all stable in the process.
Happy modding!
Protricity said:
fix_permissions didn't solve. Gonna restore and try again. Btw I didn't freeze first, I just deleted. Doubt that's the reason though.
Click to expand...
Click to collapse
Also, a thought. Boot to CWM and clear the dalvik cache.
I looked up some info on this since rooting the other day, and after uninstalling apps it's good to do to clear out the old app data. Something to consider - it might solve your problem.
Blue6IX said:
For our next trick, we're gonna dump HTC Sense
Click to expand...
Click to collapse
Does the camera app still work after you deleted sense? I wouldn't want to lose that..
I froze "T-mobile Name ID" and everything seems to be working fine.
You might also want to mention that you can temp-root your device, then freeze these apps, and they will stay frozen after reboot. Just, for anyone that doesn't want to perma-root their device right now (like me). It's not very stable to perma-root your device right now. Just read that if your MT4GS dies and your perma-rooted, you will either have to buy a new battery or find a way to charge your battery without your phone... some issue with the HBoot... So till thats fixed, and till i'm sure things are stable. I'll stick with my Temp-Root
nldroid said:
Does the camera app still work after you deleted sense? I wouldn't want to lose that..
Click to expand...
Click to collapse
The camera app still works, but I haven't used all the features.
I would assume this still does work completely, though, because this is only getting rid of the sense launcher, and not the underlying frameworks that power it. (which I hear the camera is dependent upon.)
A solid day of running ADW instead of sense as my launcher has been fine, i'll go play with the camera for a little while and get back to you with a more complete answer to this.
dansl said:
I froze "T-mobile Name ID" and everything seems to be working fine.
You might also want to mention that you can temp-root your device, then freeze these apps, and they will stay frozen after reboot. Just, for anyone that doesn't want to perma-root their device right now (like me). It's not very stable to perma-root your device right now. Just read that if your MT4GS dies and your perma-rooted, you will either have to buy a new battery or find a way to charge your battery without your phone... some issue with the HBoot... So till thats fixed, and till i'm sure things are stable. I'll stick with my Temp-Root
Click to expand...
Click to collapse
This had to do with a charging issue using Clockworkmod 4.0.0.8 which is fixed with Clockworkmod 4.0.0.9.
I have personally run my battery to completely dead using CWM 4.0.0.9 and it charged up and booted fine.
Good to know that freezing apps stays after reboot on temp-root, that's an awesome find!
Also, just found this.
http://forum.xda-developers.com/showthread.php?t=1150805
Post by rmk40, talking about freezing bloatware apps on the HTC Sensation. There are some apps ppl have frozen on there that are also on the MT4GS. I'm going to look through it now and will check back later.
The Notes app from:
/system/app/androidnotes.apk
Is that it, or is there more in the /data folder?
I think it may be /data/data/com.marigold.android.notes
and /data/data/com.marigold.android.notes/databases/notes
But I don't want to delete it without being fully sure, can someone verify this for me?
nldroid said:
Does the camera app still work after you deleted sense? I wouldn't want to lose that..
Click to expand...
Click to collapse
Yep, the camera app works completely. I tested all the modes, and used all the different manual settings in the last option. Nothing was broken, it was all fine.
Removing just the sense launcher and replacing it with something else has no impact on the camera, and I would imagine anything else that requires sense frameworks. We should test anything before making that blanket statement, though, but consider camera.apk to be tested and working without the sense launcher.
dansl said:
Also, just found this.
http://forum.xda-developers.com/showthread.php?t=1150805
Post by rmk40, talking about freezing bloatware apps on the HTC Sensation. There are some apps ppl have frozen on there that are also on the MT4GS. I'm going to look through it now and will check back later.
Click to expand...
Click to collapse
That's awesome - while i'm busy re-inventing the wheel, way to pick up where someone else left off. I glanced through there quickly, but i'm kinda having fun figuring this out. I definitely look forward to hearing what you've learned browsing through, and i'll get there at some point.
Thanks clicked on that helpful post!
Sinfamy said:
The Notes app from:
/system/app/androidnotes.apk
Is that it, or is there more in the /data folder?
I think it may be /data/data/com.marigold.android.notes
and /data/data/com.marigold.android.notes/databases/notes
But I don't want to delete it without being fully sure, can someone verify this for me?
Click to expand...
Click to collapse
Yep, you were right on. Delete the .apk in bold, then go delete the folder in bold. Once you delete the folder in /data/data, then your second line about the database in notes becomes moot, since it will have already been deleted.
Updated my list of stuff too (http://forum.xda-developers.com/showthread.php?p=16683780).
One thing i found that I couldn't quite figure out what is was for, is the Com.Redbend.SWM-C app. I've read that it might be used for tracking/analytics or DRM content... i dont know, but I froze it, and everything seems to be working fine still! I read someone had issues with Youtube, but youtube has been working fine for me.
thank you for this thread and thanks to dansl too. I was able to remove sense and a lot of the htc bloatware, making the phone a lot better.
I don't know what doubleshotandroidzipgroup was that was running in the background, but i froze it and it seems fine...
So it seems like this thread has been helping people, in conjunction with the other threads on the different aspects of this subject. I don't deal with freezing apps, it always seemed cleaner to me to just get rid of them.
I know in some cases that's not possible, maybe for us maybe not. I've sure learned a lot from this project, and from what people have discovered by freezing apps.
I want to take a moment to thank everyone who has contributed towards what we've learned here.
I took the time to really work out what has to be done to remove the various things we discovered, and the next few posts reflect the contributions everyone has made to this project.
Also, i'm hoping that this road map we are making will cut the time down it takes for developers to introduce roms for our device. Having the locations, and user test data of what you can dump should take some of their headache away. This is one of the motivations behind my trying to lay this all out like this, making it easier not only for us to use now, but for developers to refer to later.
Enjoy, i've had fun with it so far!
There was an initial surge of testing what could or could not be removed from the phone right after we got root, which has mostly passed now. Most of the obvious "I can get rid of this" stuff has been figured out, and the rest of the things we can safely get rid of will take a closer look and involve a bit of head scratching to figure out.
Meantime, I felt like it was a good idea to summarize what we know a bit, and come up with a good procedure for removing stuff that was both simple and stable. You could (and I, as well as others, have) delete(d) this stuff all at once without issue, but i'm more comfortable with a more cautious approach - and I know others will be too.
To that end, i've taken the time to test this method a few times, re-engineer it, tweak things, change the order up a bit, and finally lay it out here. We all pretty much want to get the most out of our phones, and for almost all of us here the "extras" pre-installed on our phones get in the way of this.
This'll be fun, and pretty painless - so - ready to remove some bloat?
Setup 1: We're going to go backwards in time a few steps. The ideal situation here is:
00 - Backup all phone data to somewhere off the phone itself.
01 - Factory reset phone, power down.
02 - Remove microsd card, format in computer.
03 - re-insert microsd card in phone, power on.
04 - Set up your Gmail account, enable the Market on your phone.
05 - S-OFF (if necessary), installing CWM 4.0.0.9 and Rooting your phone.
06 - Installing Busybox and Root Checker, verifying that both root and busybox are obtained/available on your phone.
07 - Uninstalling Busybox installer, checking Busybox installation in Root Checker again, then uninstalling Root Checker.
08 - Power down your phone, and boot into recovery mode.
09 - Make a CWM backup of your system in recovery, then rebooting your phone.
10 - (optional, but recommended) Making a copy of the CWM backup to another place, like your computer.
If you did/do it this way then you can always restore to a clean CWM backup from right after you got Root & Busybox on your phone, in the cleanest ready state it can be.
Otherwise, do a CWM backup of your system now, before following the instructions laid out below to be able to restore your phone if something goes wrong.
I'll try and help anyone who needs it if something doesn't go right, but please understand you do this at your own risk and backups are your best friend!
Setup 2: Tools.
01 - Install Root Explorer.
+ Other file managers may work with varying degrees of success, and there are some free alternatives, but nothing that will do the job like Root Explorer. I highly recommend this app, and if you're going to be doing this kind of stuff on your phone you should probably pick it up. You at least need a file manager capable of read/write access to your system folders, and that can copy and delete.
02 - Install Absolute System Root Tools.
+ Again, there are probably free alternatives out there, but this program is pretty awesome and I recommend it. You should have an app that lets you uninstall system apps, and lets you clear their data before uninstalling. One thing to note, is that it won't delete the .odex files of installed apps, so you'll have to go back and get them manually with Root Explorer.
03 - Before performing any steps listed below, you should make backups of all the files you will delete. I list the locations of everything so you can navigate to it with Root Explorer and copy the files somewhere else, like your sdcard. I would also go so far as to say you should make a CWM backup before attempting each of the steps below, but i'm overly cautious when it comes to backups - that's up to you.
(You could end up making changes in files you aren't working in, without realizing it. A Nandroid backup is the only way to ensure you can restore those files if that should happen)
** - Use Absolute System to uninstall .apk files listed below, and it will also get the /data/data location as well. You will have to go back and get the .odex files manually. If you choose not to use an app to uninstall the .apk files listed below, I wrote out their full path location so you can use Root Explorer to delete them manually.
** - Changes made to /system/etc are mirrored in /etc as soon as you make them. All changes made in /system/ are mirrored in the main directory in any corresponding folders or files in real-time as you make them.
** - I recommend removing all widgets and shortcuts/folders or any other items that may be on your desktop before starting this process. You can always put back anything that survives later when you are done.
** - It might be a good idea to turn off GPS, Mobile Networks, Bluetooth and Wi-Fi before proceeding. Optional, but recommended.
Feel free to skip any apps you want to keep along the way, and you don't necessarily have to go in order, but it'll be cleaner that way. Part of the organization behind it is to make it easy for the user to remember what they are doing, and break it down into smaller blocks so you'll lose less progress if something goes wrong.
Now that we're past all that, lets get down to business.
Part 1: Stock themes and wallpapers.
00 - Make sure your phone is set to the "System" theme before continuing (default theme). Then take a picture with your camera, or get a picture you like on your phone. Set this as your background wallpaper.
01 - Using Absolute System, uninstall the stock themes:
-com.tmobile.theme.Aubergine
+ /system/app/Aubergine.apk
+ /data/data/com.tmobile.theme.Aubergine
-com.tmobile.theme.Brooklyn
+ /system/app/Brooklyn.apk
+ /data/data/com.tmobile.theme.Brooklyn
-com.tmobile.theme.Jazz
+ /system/app/Jazz.apk
+ /data/data/com.tmobile.theme.Jazz
-com.tmobile.theme.Retro
+ /system/app/Retro.apk
+ /data/data/com.tmobile.theme.Retro
-com.tmobile.theme.Spring
+ /system/app/Spring.apk
+ /data/data/com.tmobile.theme.Spring
02 - Using Absolute System, uninstall the stock live wallpapers:
-com.android.wallpaper (Android Live Wallpapers)
+ /system/app/LiveWallpapers.apk
+ /data/data/com.android.wallpaper
-com.htc.android.wallpaper (HTC Sense Live Wallpaper)
+ /system/app/Mode10Wallpapers.apk
+ /data/data/com.htc.android.wallpaper
-com.htc.android.image_wallpaper (HTC Slide Show Wallpaper)
+ /system/app/HtcImageWallpaper.apk
+ /data/data/com.htc.android.image_wallpaper
-com.android.magicsmoke (Magic Smoke Wallpapers)
+ /system/app/MagicSmokeWallpapers.apk
+ /data/data/com.android.magicsmoke
-com.android.musicvis (Music Visualization Wallpapers)
+ /system/app/VisualizationWallpapers.apk
+ /data/data/com.android.musicvis
-com.htc.livewallpaper.streak (Streak Live Wallpaper)
+ /system/app/HTCLivewallpaperStreak.apk
+ /data/data/com.htc.livewallpaper.streak
Okay, we are done with Absolute System for the moment.
Fire up Root Explorer, and go to:
03 - /system/app/ (delete the files: )
-HtcImageWallpaper.odex
-HTCLivewallpaperStreak.odex
-LiveWallpapers.odex
-MagicSmokeWallpapers.odex
-Mode10Wallpapers.odex
-VisualizationWallpapers.odex
Still in Root Explorer, now go to:
04 - /system/customize/resource/ (delete the files: )
-htc_wallpaper_01.jpg
-htc_wallpaper_01_lockscreen.jpg
-htc_wallpaper_02.jpg
-htc_wallpaper_03.jpg
-htc_wallpaper_04.jpg
-htc_wallpaper_05.jpg
-htc_wallpaper_06.jpg
-tmo_wallpaper_01.png
-tmo_wallpaper_02.png
-tmo_wallpaper_03.png
-tmo_wallpaper_04.png
-tmo_wallpaper_05.png
-tmo_wallpaper_06.png
-tmo_wallpaper_grid_preview_01.png
-tmo_wallpaper_grid_preview_02.png
-tmo_wallpaper_grid_preview_03.png
-tmo_wallpaper_grid_preview_04.png
-tmo_wallpaper_grid_preview_05.png
-tmo_wallpaper_grid_preview_06.png
-tmo_wallpaper_preview_01.png
-tmo_wallpaper_preview_01_land.png
-tmo_wallpaper_preview_02.png
-tmo_wallpaper_preview_02_land.png
-tmo_wallpaper_preview_03.png
-tmo_wallpaper_preview_03_land.png
-tmo_wallpaper_preview_04.png
-tmo_wallpaper_preview_04_land.png
-tmo_wallpaper_preview_05.png
-tmo_wallpaper_preview_05_land.png
-tmo_wallpaper_preview_06.png
-tmo_wallpaper_preview_06_land.png
-wallpaper.jpg
-wallpaper.png
Still in Root Explorer, last place to go is:
05 - /system/etc/ (delete folder: )
-slideshow
(These are all the sample images for the HTC slideshow live wallpaper.)
06 - Exit Root Explorer, Reboot your phone to recovery. In CWM choose advanced and then "Wipe Dalvik Cache". Hit back and then "Wipe Cache Partition". Reboot your phone. (It will take a little while longer to boot since you wiped your cache, but not much)
After booting back up and making sure everything still works:
07 - Reboot into recovery, make a CWM Nandroid backup of your system. Make sure to back this up somewhere off the phone too.
Congratulations! You now have a recovery image of your phone with all of the stock themes and wallpapers removed.

[TOOL] ApkSpy v1.8 - Resurrected (APK: view manifest on PC and/or Install APK via PC)

APKSPY - RESURRECTED​
First:
I want to thank @ido for the original application -- It was his idea (and his code I've hacked :cyclops and modified.
Second:
Since Ido seems not to be active anymore I'll re-publish the application here.
Unless for some reason Ido will specifically ask me to remove it.
The original post
ido said:
ApkSpy is a simple tool I hacked up tonight which allows you to easily view the manifest of an APK (screenshots attached - not up to date though) just by double clicking it. (It can even associate with the .apk filetype, yay!)
ApkSpy relies on the aapt.exe tool from the android SDK, so you must have that installed (or just copy aapt.exe from somewhere, that's the only file needed to run ApkSpy).
Click to expand...
Click to collapse
Third:
Requires Microsoft©® .Net Framework v4
(Kind of since I've done it some time ago and waited for Ido [the orignal developer] to respond and allow or disallow me to re-publish... So, I don't remember all the changes I've already done...)
v1.8.19 CHANGELOG:
Fixed some Date parsing function (zipped file with no time stamp) in ZipStorer (by @Jaime Olivares) maybe causing some of the error reported here...
v1.8 CHANGELOG:
Changed Icon - CONTRIBUTED BY @Jarmezrocks
Removed unneeded tabs (System, Batch Rename, Log)
Minimize / Maximized restored back
v1.7 CHANGELOG:
(Actually 4.1.7.870, but the first and the last parts are internally used :fingers-crossed:)
Try to automatically find adb.exe and aapt.exe in ApkSPY directory or in PATH variable: If failed finding any of the executables, the user is asked to manually locate them
(★ Currently the location is not saved... ★).
Check if the ADB server is running and Start or ask if to Restart ADB server
Tidy up the code
Refining the original libraries written by Ido related to ADB and AAPT
Some more minor code updates
Revised most of the "General" tab (other tabs ware not touched) of the UI:
Grouped and ordered controls on form
Added DropDown of devices attached (★ Not automatically updating upon plugging... ★)
Added some control over ADB actions
Added status bar that some other details are shown, e.g. device type (Nexus, I9100...), OS version (4.1.2, 4.4.2...) and OS build (KOT49H, KVT49L...)
Added (nice looking) information panel with clickable links (for actions on the form) and coloring
Other changes (I can't recall right now, since I've done it some time ago and waited for a response from Ido for permission to republish)
(★ Maybe I'll add an option for this later, depending on my -- not to much -- free time and requested by users .... ★)
Known bugs:
Sometimes ADB fails to return build.prop property for the status bar (however it has not caused any critical problem, so (I think) it can be safely ignored) -- haven't been able (yet) to find the exact state it is happening
Please take the time to look at the application ABOUT tab
Any Other ideas are welcome!
If you like it, Don't forget to Thank me
If you enjoy using this application as much as I have enjoyed re-writing it
please donate to show your appreciation​
RESERVED
Nice
Sent from my SM-N900T using Tapatalk
Good news
Bug report, every time I open this program, this dialog pops up, after click OK, this program works well.
PS, aapt.exe is in the same dir with ApkSpy
I got this errors:
1:
2:
Error in property: [email protected]@usrdata
cmlx said:
Good news
Bug report, every time I open this program, this dialog pops up, after click OK, this program works well.
PS, aapt.exe is in the same dir with ApkSpy
Click to expand...
Click to collapse
Hey dude,
I am not sure what you are doing wrong on your PC but it's certainly not the app as it works perfectly fine on my computer? Out of interest and for the sake or helping the new dev I thought I would raise a few points just to eliminate any finger pointing. There's a wishy-washy area when it comes to building/hacking things that were originally someone elses work...so yeah one can easily make great improvements yet open the door to bugs at the same time too. Anyway...thought I'd ask this:
Does aapt sit on your path? I know you said it is in the same directory, however just like a batch script in Windows it needs to "CD" or change directories to the %~dp0 if it is to understand what an executable is that happens to be sitting in the same directory as it's self. So this is is kinda directed at the new dev now. What I think is happening is that aapt is assumed to be in the system path when quite often it is not (i.e. those on XDA who have not yet played with the Android SDK properly). Put simply unless the application knows it is in the same directory as your executable it won't at all understand what aapt is. Does that make sense?
@dmagician , I would make sure that the apkspy app can do a check (even if it is a string search for the first few lines returned from aapt.exe), a simple if statement before throwing that error ....actually it would likely be an 'if not' statement. I don't have any of the code in front of me atm but I can help you out if you like? I was hacking this app myself sometime ago when ido first released it just using reshacker.
Note: If you are stuck and don't have source code you technically could write a full AutoIT wrapper for this app that could do all the checks and more and then bundle everything up into the one exe still. Check out the newer WinAPI stuff for AutoIT and in particular "Run binary" (yes that's correct you can just about run anything repackaged now and not need to deploy the original exe's or even libraries....they can all be stream fed to AutoIT @Compile time and need not be typically "installed" like you used to have to do. Anyway...I am waffling on shoot me a PM man.
@cmlx, to overcome your ApkSpy woes, and until dmagician can put his finger on what the cause is or what ido did when building it ages ago.....then you will firstly need to be patient (props to dmagician to figuring sh!t out so far) but till then where ever you have dumped the ApkSpy and aapt.exe on your system; just copy the address and put it on your system path. To do this 1) right click on My Computer or Computer if you are on Win 7 or 8. 2) Choose properties. 3) Advanced System settings and then at the bottom of tab you will see 'Environment Variables', click it and you will see some "User" and "System" options. Depending on your User access rights on the system you are running on (hopefully you are running as Admin surely?) then you can choose to edit your main system path or create a new variable in your user settings called 'path' Note User variables are always postfix to system variables but should always work anyhow.
Disclaimer: cmlx, if however you have already got an aapt.exe already existing on your system path but it is dodgy then you have to ensure that the good aapt.exe in your app directory is placed on path BEFORE the dodgy one....just sayin. Cause your system searches till it finds what it wants and then doesn't search anymore. Simple but can stuff people up quite often....and likely your case. Nowdays we tend to work from the known application location and not from a "Global environment path" when we know that there are going to be conflicts...and I can assure you that aapt is possibly the worst and most modified binary out there LOL. Hence this is also a note to the dev to ensure that ApkSpy reads from the current directory.....or like I am suggesting, wrap aapt up in the main application as well and that way there is no confusion EVER.
And I am done.....
Oh wait no I am not....sorry bug reports LOL :good: you thought I was all praise eh? Got another thing coming man
OK....so um the red boxes should explain everything. A picture says a thousand words (and yeah I needed at least 1 picture for this god damned long arsed post - sry). Um why in gods name would you remove the minimise and expand buttons? WTF? Anyway...it works but errrm yeah it doesn't wrap the text anymore? and it cuts the words off lol.
Other than that....I only really have one suggestion and it isn't even really a suggestion as I have kind of already made it so I can just give it to you if you want it? And that is that most people (well I can't say most as I am not speaking for everyone) tend not to like how apps take over their system. This isn't your fault at all in anyway as the first dev thought it was a good idea back then.....and back then hardly anything in Windows knew what a freakin apk was so it was a GOOD thing.....However now, every man and his dog wants to steel .apk extension for himself. I myself tend to be all over the shop with apks so I tend not to want to have any particular Windows app take it away from my control. I use WinZip as the main app for simple double click open as I want to see the contents of apks without needing to decompile them (great for theming) however I have apk shell extensions displaying the apks main icon to explorer, so if I set WinZip as default I get a nice lumping hunk of gold turd/box running rampet all over my Windoze bro ......so if you like I can show you my code that allows me to have default apps for specific tasks without interfering with anyones existing sh!t It looks neat too as you can right click any apk and just choose from a dropdown list what particular app you want at the time. If one has the need to use more apps then they need only put those apps in a list. There is nothing worse than double clicking an apk to find that Bluestacks or some other rubbish Windoze crApp has taken offf with your apk.
Lastly I thought I'd ask, Why no config file? Why store everything in memory? I know it's only small....but seeking for things everytime it is executed is a pain in the arse and not good practice. At the very least if you have no idea how to make an exe totally portable then you could reference a config file in the same directory....Or do as most do and write entries to the registry all neat and tucked away. If we get paranoid about "portable-ness" then we write to temporary space in the registry and make sure we clean up upon closing and/or inspect at runtime. simple!
I have plenty of AutoIT scripts that do exactly that too, so if you are stuck for ideas let me know. Anyway I have rambled enough, good luck and I will keep reporting bugs haha
Edit: That's waaaay too many emoticons. Oooops someone is a little high aren't they?
PS: I have attached my PNG of the icon I used for this bugger waaaaaay back....it's less generic and feel free to take it and abuse it and do as you please.
cmlx said:
Good news
Bug report, every time I open this program, this dialog pops up, after click OK, this program works well.
PS, aapt.exe is in the same dir with ApkSpy
Click to expand...
Click to collapse
Yes, I know of this one (and I've specifically wrote about it in the OP), it is NOT related to AAPT executable but to the way ADB is acting (sorry, out of my hands... :angel:
Explanation
The error comes from the application when trying to query the "ro.build.id" property via adb ('ADB shell getprop "ro.build.id" ') command.
I've came across this one but cannot determine the exact situation it is happening (as it can occur when first launching of the app, but after the app is loaded, clicking on refresh does not show this error)...
[ I've tried it on with the (only) two devices I own (1st dev. is stock (only the kernel is changed) 4.4.2 Nexus 4, 2nd dev. is S2-i9100 with customized RR ROM)and it seems to happen ONLY on the S2...]
It looks that in times, the getprop is being executed before the whole "build.prop" is being processed by ADB (This one I cannot control since it is happening on the ADB shell side [running on the device] -- unless MAYBE doing some [UGLY] delay after first initialization of ADB, which is, by far NOT best practice of process handling according to the literature)...
CyberianIce said:
I got this errors:
1:
2:
Error in property: [email protected]@usrdata
Click to expand...
Click to collapse
Which came first, the "SpkSpy spy stopped working" or the "Error in property" (if anyways related)?
Was it on the same run or two different runs?
As of the 1st one:
I do not have enough information from your post to check it up...
I'll post a new version which shows the exception details
As of the 2nd one:
Can you send me a copy of your /system/build.prop (so i'll be able to dig trough it and check it)?
It looks like my name-value splitter character exist as part of a given value in your build.prop .
Wooow, Long one! But it is nice to know people are using (trying) it!
Jarmezrocks said:
Hey dude,
I am not sure what you are doing wrong on your PC but it's certainly not the app as it works perfectly fine on my computer? Out of interest and for the sake or helping the new dev I thought I would raise a few points just to eliminate any finger pointing. There's a wishy-washy area when it comes to building/hacking things that were originally someone elses work...so yeah one can easily make great improvements yet open the door to bugs at the same time too. Anyway...thought I'd ask this:
Does aapt sit on your path? I know you said it is in the same directory, however just like a batch script in Windows it needs to "CD" or change directories to the %~dp0 if it is to understand what an executable is that happens to be sitting in the same directory as it's self. So this is is kinda directed at the new dev now. What I think is happening is that aapt is assumed to be in the system path when quite often it is not (i.e. those on XDA who have not yet played with the Android SDK properly). Put simply unless the application knows it is in the same directory as your executable it won't at all understand what aapt is. Does that make sense?
Click to expand...
Click to collapse
Hi
As I've replied to @clmx, This error is not related to AAPT (either executable [location or whatever] or results), but to the ADB command being used...
Jarmezrocks said:
@dmagician , I would make sure that the apkspy app can do a check (even if it is a string search for the first few lines returned from aapt.exe), a simple if statement before throwing that error ....actually it would likely be an 'if not' statement. I don't have any of the code in front of me atm but I can help you out if you like? I was hacking this app myself sometime ago when ido first released it just using reshacker.
Click to expand...
Click to collapse
Sorry I did not understand... Check for what?
Jarmezrocks said:
Note: If you are stuck and don't have source code you technically could write a full AutoIT wrapper for this app that could do all the checks and more and then bundle everything up into the one exe still. Check out the newer WinAPI stuff for AutoIT and in particular "Run binary" (yes that's correct you can just about run anything repackaged now and not need to deploy the original exe's or even libraries....they can all be stream fed to AutoIT @Compile time and need not be typically "installed" like you used to have to do. Anyway...I am waffling on shoot me a PM man.
Click to expand...
Click to collapse
I do not need the Auto-IT to wrap these files (although I am using it for other automation in windows), as I can do it right in the C# code (on one of my early versions these files was embedded...)
BTW, I know there are some antiviruses out in the wild that do not like the embedded executables -- but it can be done -- and probably will save some time to anyone using this app...
If it will be required / asked, I'll embed the 4 binaries (AAPT.EXE, ADB.EXE, and two DLL's AdbWinApi.dll and AdbWinUsbApi.dll [I'm not sure both are required]) needed by the application.
Jarmezrocks said:
@cmlx, to overcome your ApkSpy woes, and until dmagician can put his finger on what the cause is or what ido did when building it ages ago.....then you will firstly need to be patient (props to dmagician to figuring sh!t out so far) but till then where ever you have dumped the ApkSpy and aapt.exe on your system; just copy the address and put it on your system path. To do this 1) right click on My Computer or Computer if you are on Win 7 or 8. 2) Choose properties. 3) Advanced System settings and then at the bottom of tab you will see 'Environment Variables', click it and you will see some "User" and "System" options. Depending on your User access rights on the system you are running on (hopefully you are running as Admin surely?) then you can choose to edit your main system path or create a new variable in your user settings called 'path' Note User variables are always postfix to system variables but should always work anyhow.
Disclaimer: cmlx, if however you have already got an aapt.exe already existing on your system path but it is dodgy then you have to ensure that the good aapt.exe in your app directory is placed on path BEFORE the dodgy one....just sayin. Cause your system searches till it finds what it wants and then doesn't search anymore. Simple but can stuff people up quite often....and likely your case. Nowdays we tend to work from the known application location and not from a "Global environment path" when we know that there are going to be conflicts...and I can assure you that aapt is possibly the worst and most modified binary out there LOL. Hence this is also a note to the dev to ensure that ApkSpy reads from the current directory.....or like I am suggesting, wrap aapt up in the main application as well and that way there is no confusion EVER.
Click to expand...
Click to collapse
The application IS searching for AAPT and ADB executables; The order is
Application directory (where ApkSpy.exe resides)
PATH environment variable
Jarmezrocks said:
OK....so um the red boxes should explain everything. A picture says a thousand words (and yeah I needed at least 1 picture for this god damned long arsed post - sry). Um why in gods name would you remove the minimise and expand buttons? WTF?
Click to expand...
Click to collapse
Mostly I like it this way, otherwise - No specific reason...
It will be back in the next version...
Jarmezrocks said:
Anyway... it works but errrm yeah it doesn't wrap the text anymore? and it cuts the words off lol.
Click to expand...
Click to collapse
This Tab was NOT changed by me in any way... To be honest, I've thought of removing it completely -- But -- out of respect to Ido's work -- I've left it in.
I assume it is not wrapping due to Font size changed by me globally...
I'm seriously giving it second thoughts -- if it should stay at all (It was originally meant for batch rename of multiple APK's... I haven't used it even once...)...
I'm Really, REALLY, think of removing it completely (unless someone is / will be using it -- then I'll fix it all)...
Jarmezrocks said:
Other than that....I only really have one suggestion and it isn't even really a suggestion as I have kind of already made it so I can just give it to you if you want it? And that is that most people (well I can't say most as I am not speaking for everyone) tend not to like how apps take over their system. This isn't your fault at all in anyway as the first dev thought it was a good idea back then.....and back then hardly anything in Windows knew what a freakin apk was so it was a GOOD thing.....However now, every man and his dog wants to steel .apk extension for himself. I myself tend to be all over the shop with apks so I tend not to want to have any particular Windows app take it away from my control. I use WinZip as the main app for simple double click open as I want to see the contents of apks without needing to decompile them (great for theming) however I have apk shell extensions displaying the apks main icon to explorer, so if I set WinZip as default I get a nice lumping hunk of gold turd/box running rampet all over my Windoze bro ......so if you like I can show you my code that allows me to have default apps for specific tasks without interfering with anyones existing sh!t It looks neat too as you can right click any apk and just choose from a dropdown list what particular app you want at the time. If one has the need to use more apps then they need only put those apps in a list. There is nothing worse than double clicking an apk to find that Bluestacks or some other rubbish Windoze crApp has taken offf with your apk.
Click to expand...
Click to collapse
The application is NOT taking over anything, Unless you've clicked the asterisk ("*") button on the System Tab...
Was it registered for you without clicking this button?
If so, I'll recheck the code (may be it's some residue from the original code).
BTW
As the previous part of the answer I've wrote -- this one was left in as of respect to @ido's work...
2nd BTW
I'd like to see that explorer extension (and [preferable] the code of it - if you are willing to share it) you ware writing about...
Jarmezrocks said:
Lastly I thought I'd ask, Why no config file? Why store everything in memory? I know it's only small....but seeking for things everytime it is executed is a pain in the arse and not good practice. At the very least if you have no idea how to make an exe totally portable then you could reference a config file in the same directory....Or do as most do and write entries to the registry all neat and tucked away. If we get paranoid about "portable-ness" then we write to temporary space in the registry and make sure we clean up upon closing and/or inspect at runtime. simple!
Click to expand...
Click to collapse
Yep, I've thought of it... But... I was thinking, that (at least) everyone is as geeky as me dauuh , and the most are setting the path correctly...
It'll be added in next version (I hope... TIME, TIME!!!! :cyclops...
Jarmezrocks said:
I have plenty of AutoIT scripts that do exactly that too, so if you are stuck for ideas let me know. Anyway I have rambled enough, good luck and I will keep reporting bugs haha
Click to expand...
Click to collapse
I prefer writing my own code (sorry, I'm a developer in heart and soul...) then using automation like Auto-IT...
Jarmezrocks said:
Edit: That's waaaay too many emoticons. Oooops someone is a little high aren't they?
Click to expand...
Click to collapse
Jarmezrocks said:
PS: I have attached my PNG of the icon I used for this bugger waaaaaay back....it's less generic and feel free to take it and abuse it and do as you please.
Click to expand...
Click to collapse
(@Jarmezrocks please see my PM to you.)
PHEW...
Long Answer, BUT HEY, I'm not the only one writing longies... :angel: (and i like referencing each and every part separately)...
dmagician said:
PHEW...
Long Answer, BUT HEY, I'm not the only one writing longies... :angel: (and i like referencing each and every part separately)...
Click to expand...
Click to collapse
Ahh yes. I write long messages sometimes when my medication has kicked in and I am high....not my fault I kinda need to get all the info out of my head in one go while I am awake.....or else there would just be zeds on the response zzzzzzzzzzzzzzzzzzzzzz lol :laugh: (ref narcolepsy).
I commend you on your efforts at responding to such gibberish and making good sense of it! :highfive:
I have responded to your PM accordingly, and hopefully covered all you need? I have attached all info and sources etc.....well most of it...actually a fair bit of it you will have to workout your self but that is part the fun. Shoot me any questions if you need to...although I have a feeling that you will have mostly all of it covered as you are streets ahead of my knowledge already. I may have misjudged a little in my previous post (although hopefully not to make you feel any less than you actually are? please excuse me if I had said anything that may offended - being naive or what ever....you ARE definitely on the right track). As for the middle menu....I think you could easily remove it and not offend the original dev. It wasn't being used as you mention...and I think it could make way for more/better functionality don't you think? (discuss). However I would ensure all the things I mentioned in my PM first before going too deep and releasing on here.
Good move on bringing the buttons back. They were functional. But I DO like the single button close GUI myself on just about everything else....It looks clean. We have similar taste in that regard. It just isn't functional for me to pressing the task notification desktop link everytime I want to minimise the app LOL.
The rest I we can discuss via PM, this is pretty much only posted here as an open area for other forum members to provide input and opinion (or complaint....like how often it usually is, eh?).
CyberianIce said:
I got this errors:
1:
2:
Error in property: [email protected]@usrdata
Click to expand...
Click to collapse
I'd got the same error!
For me it helped to copy two files to the install dir
"adb.exe" and "AdbWinApi.dll"
Both are installed with the well known MyPhoneExplorer into "Program Files\MyPhoneExplorer\DLL"
Hope it helps!
Feature Request
I use this tool for testing new APK builds on a project I am working on it. It allows me to quickly verify the version number and push to the device. However, since I am usually installing another version of an existing installed APK, I must manually uninstall before using APKSPY. Would it be possible to add a check box that would uninstall any previous versions? It would be really helpful.
Nevermind - I didn't fully read the message presented when it fail. It say uninstall/update and it allows the installation. HOWEVER, that brings up a question... Does it uninstall or does it update? There is a difference as you know.
Thanks,
Jonathan
Hi, I try to run this on Mac via Wineskin Winery, but no luck. Do I need something like .Net, or something else to run ApkSpy?
Thank you.
Ja_som said:
Hi, I try to run this on Mac via Wineskin Winery, but no luck. Do I need something like .Net, or something else to run ApkSpy?
Thank you.
Click to expand...
Click to collapse
The only requirement is the Microsoft .Net 4.
(I'll add this to OP)
jmo said:
I use this tool for testing new APK builds on a project I am working on it. It allows me to quickly verify the version number and push to the device. However, since I am usually installing another version of an existing installed APK, I must manually uninstall before using APKSPY. Would it be possible to add a check box that would uninstall any previous versions? It would be really helpful.
Nevermind - I didn't fully read the message presented when it fail. It say uninstall/update and it allows the installation. HOWEVER, that brings up a question... Does it uninstall or does it update? There is a difference as you know.
Thanks,
Jonathan
Click to expand...
Click to collapse
Yes I know there is difference between the two (update vs uninstall and install again).
It is updating the application (like using "adb install -r apk_file_name.apk"), not doing remove and install
Removed unneeded tabs (System, Batch Rename, Log)
Click to expand...
Click to collapse
The unneeded Batch Rename tab was the only tab I needed really. :laugh: Luckily I found Ido's original version. It's ideal for renaming all those apk's I downloaded and still have the package name when I back them up to my PC.
I have an Asus Memo Pad 10 and an Asus Memo Pad 7 and neither are recognised by APKSpy. Not that it's a problem as I have no problem copying to and from them with Windows Exploder or Total Commander.
Other than that, it's been a handy little app for this tablet/smartphone virgin newbie.
Martin.
wolrik said:
The unneeded Batch Rename tab was the only tab I needed really. :laugh: Luckily I found Ido's original version. It's ideal for renaming all those apk's I downloaded and still have the package name when I back them up to my PC.
I have an Asus Memo Pad 10 and an Asus Memo Pad 7 and neither are recognised by APKSpy. Not that it's a problem as I have no problem copying to and from them with Windows Exploder or Total Commander.
Other than that, it's been a handy little app for this tablet/smartphone virgin newbie.
Martin.
Click to expand...
Click to collapse
Hello.
1st:
I can -- if requested - re-add the Batch rename.
2nd:
I don't know why these two devices are not being recognized -- unless not being recognized by ADB itself -- since I'm spawning devices by parsing the resulting text of "ADB devices" command, So unless being unrecognized by ADB, there should be NO PROBLEM detecting ANY android device with ADB on...
if you have any exception messages thrown by the application, please post them here.
dmagician said:
Hello.
1st:
I can -- if requested - re-add the Batch rename.
2nd:
I don't know why these two devices are not being recognized -- unless not being recognized by ADB itself -- since I'm spawning devices by parsing the resulting text of "ADB devices" command, So unless being unrecognized by ADB, there should be NO PROBLEM detecting ANY android device with ADB on...
if you have any exception messages thrown by the application, please post them here.
Click to expand...
Click to collapse
No need to re-add the tab just for me, but thanks for the offer. As I get to know my way around Android I'll probably need such things less and less.
Sorry, but I know nothing about ADB other than APKSpy needing it. As you can see from the attached pic, the Asus is recognised by Total Commander
Martin.
Hi dmagician,
Nice work, and a shout-out to Ido who originally created it.
I have a feature request:
Could you add the option to remove certain permission(s) and save the modified APK file?
There are many apps which I feel allow themselves way too much permissions, and this option could be very useful to tame them apps.
One more thing:
I noticed that APKSpy v1.8.2 doesn't work with the latest version of AAPT.exe (1432KB), from the Android SDK r24.
So I had to use a previous version of AAPT.exe (833KB), which worked.
Thanks,
Eric
Hey does anybody know where the name of the apk is in the XML files inside the apk?

Categories

Resources