Database Info

Scheduled Scripting App - Scheduled Reboots, etc... Phone Prioritizer App

This is the phone prioritizer app for the people that are looking for it.
As title states this allows you to schedule scripts to run at specific times and time intervals.
Place scripts you want to run into the following files in the folder /sdcard/phonePrioritizer:
reboot.txt - Runs one time nightly at scheduled time (placing reboot in this file will reboot your phone on cupcake but not on hero)
script.txt - Runs at scheduled intervals (5 minutes to 24 hours)
afterboot.txt - Runs one time after each reboot
Open the phonePrioritizer app and set options by pressing menu. (Buttons on main page of app only control the script.txt script, rest of the scripts are controlled in preferences.)
!Don't put the word reboot into script.txt or afterboot.txt for obvious reasons!

Great job. I'll play with this when I have more time.

Mike, Thanks for the script.
Hope I didn't spoil your surprise on your awesome script. I figured I would still release this in case someone has a need for it.
It is working well for me so far.

jinx10000 said:
Mike, Thanks for the script.
Hope I didn't spoil your surprise on your awesome script. I figured I would still release this in case someone has a need for it.
It is working well for me so far.
Click to expand...
Click to collapse
I think we both got spoiled by that damn BFS working. It makes my stuff useless if the ROM has it. There are a few ROMs that don't have it yet so it has a little life left in it.

LOL. I hadn't heard that. That is too bad.
I had heard that your scripts were working great in xrom and Jacxheroski 1.8. I thought both of those had your script and bfs in them. Of course I haven't looked much today since I have been working on this program.
I guess people can still use my program that want an automated reboot.

Before, it would take at least 3 rings on the caller before I see a notification and my phone rings. When i installed this, my screen showed an incoming call on the first ring on the caller. My phone started ringing on the second ring on the caller though. I'm wondering what adjustment I should make to make my phone ring as soon as I see a notification? I used the default script.txt. thanks

cx92001 said:
Before, it would take at least 3 rings on the caller before I see a notification and my phone rings. When i installed this, my screen showed an incoming call on the first ring on the caller. My phone started ringing on the second ring on the caller though. I'm wondering what adjustment I should make to make my phone ring as soon as I see a notification? I used the default script.txt. thanks
Click to expand...
Click to collapse
Turn off your vibrate on ring. That delays the ringtone. Also the second call usually comes in faster.

miketaylor00 said:
Turn off your vibrate on ring. That delays the ringtone. Also the second call usually comes in faster.
Click to expand...
Click to collapse
Cool that helped. Thanks to your awesome script miketaylor00 and your scheduler jinx10000.

Updated.
1.7 had a problem where unchecking the Enable Scheduled Reboot would disable the wrong script.
Sorry for those that downloaded it. It is fixed in the newest version.

I believe this is the final update. Got it the way I like it.
Cleaned up the code a little.
Now runs completely in the background. No toast when script runs.

I really think this is the final version. lol
I had left some unnecessary timers in 2.0. --- Run script wait a few seconds then kill service. Was not sure if this was necessary when I first started making this program. I doubt for those with earlier versions that it will make any difference. --- Doesn't seem necessary so removed. I thought I had removed them in 2.0.
I have a question for Java/android programmers. The code that I found to call the services is :
mAlarmSender = PendingIntent.getService(AlarmService.this, 1394, new Intent(AlarmService.this, AlarmService_Service.class), 0);
timeSet = calendar.getTimeInMillis();
AlarmManager am = (AlarmManager)getSystemService(ALARM_SERVICE);
am.setRepeating(AlarmManager.RTC_WAKEUP, timeSet, whateverTime, mAlarmSender);
In order to setup multiple schedules I have created multiple services and called them in mAlarmSender variable. For ex, AlarmService_Service, AlarmReboot_Service, etc... However, these do almost the same thing. How can I combine them into the same service and distinguish the exact purpose for which it is being called?

Do all the scripts run as su? or only the reboot one?

all scripts run as su.
Process process = Runtime.getRuntime().exec("su");
DataOutputStream os = new DataOutputStream(process.getOutputStream());
...
os.writeBytes("exit\n");
os.flush();

Uploaded source if anyone is interested.
The program appears to be fully functional.

Thanks so much for this.
afterboot.txt is exactly what I was looking for a few days back. Now I can finally have an IM app launch at boot, might actually use the thing now lol.
Nice work, appreciate the app.

Great job with the app
If anyone needs a command to kill a certain task on startup (AK Notepad was starting up for me all the time), do the following:
Type in Terminal
Code:
ps
This will display all of the processes that are currently running.
Find out the PID of your process you want to kill; mine was 491.
Plug it in to where x is:
Code:
kill -9 x
So in my case, I typed:
Code:
kill -9 491
And it killed AK Notepad from processes. So if you want to auto-kill a process, that's what you could do - put kill -9 [your PID here] into the autostart script after every reboot.
Hope this helps.

Proxin said:
Great job with the app
If anyone needs a command to kill a certain task on startup (AK Notepad was starting up for me all the time), do the following:
Type in Terminal
Code:
ps
This will display all of the processes that are currently running.
Find out the PID of your process you want to kill; mine was 491.
Plug it in to where x is:
Code:
kill -9 x
So in my case, I typed:
Code:
kill -9 491
And it killed AK Notepad from processes. So if you want to auto-kill a process, that's what you could do - put kill -9 [your PID here] into the autostart script after every reboot.
Hope this helps.
Click to expand...
Click to collapse
Correct me if I'm wrong but I don't believe the PID is a constant, i.e. it changes.

AndroidAppCritic said:
Correct me if I'm wrong but I don't believe the PID is a constant, i.e. it changes.
Click to expand...
Click to collapse
Yes, just realized that too
Haha oh well. Maybe someone someday will find use in this instead of buying/downloading a task manager app

Proxin said:
Yes, just realized that too
Haha oh well. Maybe someone someday will find use in this instead of buying/downloading a task manager app
Click to expand...
Click to collapse
I use GScript for a lot of various scripts that are apps. For example, instead of Clear Me for $1 (which I already bought) I just use GScript to clear my necessary caches. But I found that for task managing purposes I used Advanced Task Manager which pretty much allows you to do just about anything. Sometimes you just need to bite the bullet and pay for an app. I'd love to see this thread become huge because I LOVE GScript.

Proxin said:
Great job with the app
If anyone needs a command to kill a certain task on startup (AK Notepad was starting up for me all the time), do the following:
Type in Terminal
Code:
ps
This will display all of the processes that are currently running.
Find out the PID of your process you want to kill; mine was 491.
Plug it in to where x is:
Code:
kill -9 x
So in my case, I typed:
Code:
kill -9 491
And it killed AK Notepad from processes. So if you want to auto-kill a process, that's what you could do - put kill -9 [your PID here] into the autostart script after every reboot.
Hope this helps.
Click to expand...
Click to collapse
if you need a dynamic PID try the below:
Code:
pidof com.akproduction.notepad
so you could create a small script
to store it then run the kill on the variable as i cant seem to get the kill to run it in single quote i get a bad pid message

[TUT] Tasker – Create an Auto-killing Task Manager with Widget!

Not using Tasker? Shame on you… Download your free trial here
The debate about whether or not to use an automatic task killer in Android is for another thread. The general consensus seems to be ‘don’t’, but regardless, we all have them in case of troublesome processes (even if you can long-press the back button) and therefore I’ve produced this tutorial to show you how to use Tasker to create one that you can configure how you wish, should you wish!
If nothing else, there’s a few good Tasker tips in here, that I’m sure will come in handy for your other profiles.
Let’s get on with it!
Preparation
For best practice, testing and understanding, you’ll need:
1) A Terminal Emulator
2) A Task Killer (!)
3) The Locale Execute Plug-in for Tasker (make sure this is installed prior to importing the profile)
4) A speech engine – Pico TTS for example.
The Short Winded Tutorial
It kills sh*t loads of processes.
Proceed to the download!
The Long Winded Tutorial
Import the profile and ‘un-tick’ it to make sure it is not active until you have edited it to suit your needs.
The trigger for this profile is time based and set up as standard to run every 30 minutes between the times you are likely to be using your phone. Be sure that the activation time does not match that of your AutoSync Profile that you may/should/could be using from here, or otherwise how often your standard email and widgets sync with their individual settings – you don’t want those processes being killed mid-sync.
In this profile, Tasker will use Linux commands via the Locale Execute Plug-in to kill processes you have specified. Let’s get familiar with them.
Open up the Terminal Emulator and type:
Code:
su
then:
Code:
ps
The current running processes will be listed. You’ll note that all applications you would want to kill are assigned a process ID (PID) and an application number app_** (listed under 'User'). The application process (process name) is listed at the end, such as com.android.google.browser.
A process can be killed using its corresponding PID. Try it with an application you see in the list (NOT A SYSTEM PROCESS!):
Code:
pkill 3456
Unfortunately, the PID changes and therefore is not a constant we can use to terminate applications. We therefore have to focus on the process name – bbc.iplayer.android for example.
Try killing an application by name (open it first, list the processes again to make sure it’s there and then see if it has gone afterwards by listing processes again):
Code:
pkill com.google.android.youtube
Sometimes a process is persistent and needs further encouragement (execution) to die:
Code:
pkill -9 com.facebook.katana
Sometimes a process refuses to die – this can be because there are other processes associated with it that are not killed by the above.
Code:
Killall -9 com.levelup.beautifulwidgets
That’s the process killing commands lesson complete and only leaves us with one small issue = What if you are using the process at the time? Obviously we don’t want the browser killed if you are in the middle of surfing, so we have to use a variable to make certain of this. The chosen built in variable is %LAPP, which is the last foreground application used. By making sure this isn’t killed, it’ll stop your current program being terminated in the middle of a message to someone! Therefore, each separate action to kill a process has an IF statement included to prevent the termination if that application is currently being used.
There are plenty of examples in the profile for you to use, but of course you’ll want to add your own entries in the KillProcesses task by:
+
Plugin
Execute
Edit
And then type (or even better paste):
@! pkill -9 and then the process name* (@! Stops the commands appearing on the screen)
Press the back button to save
Click IF
%LAPP
Click ‘~’ select ‘doesn’t match’
Enter the application name**.
Done
* The process name can be found and noted in the Terminal Emulator. Alternatively, often the process names are listed in the Task Manager you are already using.
** In the profile, there is a speech task, popup notification and a STOP task, these are there to discover the correct application name. Open the application you want to add to the list, long hold the home button and select Tasker and then press ‘test’. Tasker will say the name of the application and show how it is spelt on the screen. If the speech says ‘Launcher’, you may need to navigate back to Tasker (after opening the desired app) via the notification bar.
Copying all of the process names and completing the IF statements can be a little tedious, but when it’s done, it’s done… Test each new action to ensure the application is actually killed – just drag it above the STOP action. The Super User application may request permission first time (for each application command). Go to your current Task Manager, refresh it and check the application was terminated! If it wasn’t, try the ‘killall -9’ command detailed above. I have to use this for Beautiful Widgets and Titanium Backup as they are stubborn (and return again soon).
When you've completed your list, delete the pop-up, speech and stop actions and you're good to go.
Finally, it couldn’t be easier to create a widget for the home-screen to activate KillProcesses whenever you like. Hold down somewhere on the home-screen, select widgets. Select Tasker. Select Task. Select KillProcesses. Select your icon and hit ‘make widget’! Done!
There you have it! Your very own self created task murderer at the touch of a button!
Enjoy!
Shortfalls
You are unable to kill a troublesome process if it’s not in your task list!
Future Inclusions?
When setting this up, I had Locale write the process list to a text file. In theory it is possible to get Tasker to read this file, dissect it and therefore discover by the constant app_** which tasks are running and place the process name in a variable which then could be exported to Locale to kill (I think). This is waaay too much effort, but have a go if you want!
In addition, Tasker could compare the before and after (kill) process list and work out approximately how many applications it killed, displaying the number in a popup notification. Again, effort – go for your life!
At present a notification is displayed showing the last time it murdered something.
Please let me know if you have any sensible requests and your feedback is always welcome!

Installation Instructions
In menu options/profile data 'Import One Profile':
Task_Manager
The thanks meter lets me know I'm appreciated!

Feedback?!
There have been a few downloads of this now... but no comments!
Do I assume that it works absolutely fine? No errors or anything? If so, I'll stick it on the Tasker Wiki for educational purposes.

Wow! But how about use Locale AutoKill Plug-in ? It works for me with 2.2 Froyo. So much easier )

memberfive said:
Wow! But how about use Locale AutoKill Plug-in ? It works for me with 2.2 Froyo. So much easier )
Click to expand...
Click to collapse
For education purposes
Sent from my HTC Desire using XDA Premium App

brandall said:
For education purposes
Click to expand...
Click to collapse
Well. In this case, suggest another simple solution, without the use of additional fee applications.
1) Connect your phone via USB.
2) Do adb shell and then ps to remember the last lines.
3) On your phone start the unnecessary application, again execute ps
and see the process name (like android.process.media) after the last lines.
4) Add it to the killing list (say kill_list.txt): echo android.process.media>>/sdcard/kill_list.txt.
5) Repeat for all the unnecessary applications.
6) In the Locale Execute Plug-in is only one line: @! /system/xbin/cat /sdcard/kill_list.txt | /system/xbin/xargs -n1 /system/xbin/killall

memberfive said:
Well. In this case, suggest another simple solution, without the use of additional fee applications.
1) Connect your phone via USB.
2) Do adb shell and then ps to remember the last lines.
3) On your phone start the unnecessary application, again execute ps
and see the process name (like android.process.media) after the last lines.
4) Add it to the killing list (say kill_list.txt): echo android.process.media>>/sdcard/kill_list.txt.
5) Repeat for all the unnecessary applications.
6) In the Locale Execute Plug-in is only one line: @! /system/xbin/cat /sdcard/kill_list.txt | /system/xbin/xargs -n1 /system/xbin/killall
Click to expand...
Click to collapse
Do you mean 'fee' applications? It only uses locale which is free??
I originally messed with the idea of using a list like this, but the problem is, you can't pass the %LAPP variable in this way. I had Tasker/locale writing the original .txt file from ps output and getting Tasker to try and 'read line/find' the associated %LAPP process in order to exclude it from the list prior to the xargs command being executed... but it became more complicated than just listing IF actions individually as I was going to have to list them anyway!
Hope that made sense? If you can think of a betterway to exclude the foreground process and then use a single command in this way, please do let me know!
Sent from my HTC Desire using XDA Premium App

brandall said:
Do you mean 'fee' applications? It only uses locale which is free??
I originally messed with the idea of using a list like this, but the problem is, you can't pass the %LAPP variable in this way. I had Tasker/locale writing the original .txt file from ps output and getting Tasker to try and 'read line/find' the associated %LAPP process in order to exclude it from the list prior to the xargs command being executed... but it became more complicated than just listing IF actions individually as I was going to have to list them anyway!
Hope that made sense? If you can think of a betterway to exclude the foreground process and then use a single command in this way, please do let me know!
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
I mean, this solution is just for the Tasker with free Locale Execute Plug-in !
I think that any attempt to pass variables in Tasker and process them would increase the CPU load and reduce performance. It seems to me that there is no difference as to kill the process. And everything works (killed) fine with a single command.

memberfive said:
I mean, this solution is just for the Tasker with free Locale Execute Plug-in !
Click to expand...
Click to collapse
Thought so!
I think that any attempt to pass variables in Tasker and process them would increase the CPU load and reduce performance.
Click to expand...
Click to collapse
Agreed - It was becoming more complicated than an actual Task Killer!
It seems to me that there is no difference as to kill the process. And everything works (killed) fine with a single command.
Click to expand...
Click to collapse
Only problem is with it killing the current application you are using....... Need a solution to prevent that....

Ok, been browsing the web and found these nice profiles, which can trigger an app (Fast Reboot - which acts like a virtual reboot, closing all apps). What do you think about it Brandall? Could it be tweaked even more to get a nice profile using this app? Thanks.
Published by James.
Display- Battery Saver
The initial idea came from some members on the LG2X MoDaCo Forum. The problem at the time was various applications were misbehaving and not stopping when the phone should have been going into its sleep mode. One member suggested using Fast Reboot to ‘reset’ the phone into a state where it can enter sleep mode.
The context:
Event: Display Off
The task:
Wait [ Seconds:11 ]
Stop If [ %SCREEN ~ ON ]
Load App [ App:Fast Reboot Data: Exclude From Recent Apps:On]
The wait is to allow my phone to lock (10 seconds after screen off) then if the phone has been used again the second part should cancel the task #this has limited success if you know a better way to about a task please get in touch!#. Fast reboot unlike many task managers closes and restarts your tasks so your alarms and other app keep working.
Further Improvements
I have added two more complimentary profiles to control when the above profile can run.
Profile: Display- Phone Idle
Event: Phone Idle
Task: Profile Status [ Nameisplay- Battery Saver Set:On]
and
Profile: Display- Phone Offhook
Event: Phone Offhook
Task: Profile Status [ Nameisplay- Battery Saver Set:Off]
These stop the Display- Battery Saver profile from running when the phone is in use. Again, they may not been the most effective solution but they work.
Click to expand...
Click to collapse

mi3x said:
Ok, been browsing the web and found these nice profiles, which can trigger an app (Fast Reboot - which acts like a virtual reboot, closing all apps). What do you think about it Brandall? Could it be tweaked even more to get a nice profile using this app? Thanks.
Published by James.
Click to expand...
Click to collapse
I'd say this is a little excessive... Using a hot/fast reboot as it is known is not addressing the actually issue of misbehaving applications...
For Tasker users, this can be done using Deep Sleep Detective - for other users, this can be done with Better Battery Stats.
Hot/Fast reboot resets the system without rebooting the kernel and is only really necessary when system changes such as remapping hardware keys need to be applied without the need for a full and time-consuming reboot...
Best to track down a problem and resolve it rather and kill everything which this solution does... If a rouge application or process starts at screen-off, then this will happen eventually/immediately after a reboot, so again, a little drastic for short term 'relief'.
The hot reboot is used in my Tasker media mapping profiles though!

I want to kill the backup service that saves data from apps in the cloud and start the service later (when charging) again.
I think it is android alarms: act=android.app.backup.intent.RUN isn't it?
How can I do that?
Thanks in advance!

MaluNoPeleke said:
I want to kill the backup service that saves data from apps in the cloud and start the service later (when charging) again.
I think it is android alarms: act=android.app.backup.intent.RUN isn't it?
How can I do that?
Thanks in advance!
Click to expand...
Click to collapse
This is entirely possible in theory, however killing the service once does not guarantee that it will not start again and again when it feels like it... There is no monitor within Tasker to alert you when it starts...
If there was....
Sent from my Sensation using xda premium

So could you help me with that for the backup service? Or enable/disable toggle?
Thanks.

brandall, I need some help here, please help me out.
I want the following thing:
Everytime I turn internet (easy) some apps services would be launched, like viber/whatsapp/facebook/gmail runing in background as they already do, and when I turn off the internet, I want to kill those process and services...
how can I do that?
pkill -9 and kill-9 arent killing com.whatsapp for example.

MaluNoPeleke said:
So could you help me with that for the backup service? Or enable/disable toggle?
Thanks.
Click to expand...
Click to collapse
Sorry, I didn't see your reply. It's not possible unless the process is obvious when you type 'ps' in the terminal - you can try manually killing it then and see if it comes back. Let me know if you find it and I'll talk you through how to kick off the intent with Tasker.
Sent from my HTC Sensation XE with Beats Audio using xda premium

brunoshady said:
brandall, I need some help here, please help me out.
I want the following thing:
Everytime I turn internet (easy) some apps services would be launched, like viber/whatsapp/facebook/gmail runing in background as they already do, and when I turn off the internet, I want to kill those process and services...
how can I do that?
pkill -9 and kill-9 arent killing com.whatsapp for example.
Click to expand...
Click to collapse
Hi, don't forget that Android is supposed to handle these processes so they don't use any cpu and remain dormant, however, I understand that sometimes it just feels better if they are not there... (although others would tell you that killing apps may make your device under-perform!)
Anyway, killall -9 com.whatsapp will kill the process, but testing it on my device, it restarted almost instantly.
I have the application system tuner pro by 3c an amazing app and under the apps tab there is a 'startup' option for applications which I assumed referred to at boot - I just unticked whatsapp in there, killed the process and then it didn't restart... Maybe a coincidence, but worth a try...
I've no idea what different events in Android cause these apps to decide to come to life...
Hope that helped!?
Sent from my HTC Sensation XE with Beats Audio using xda premium

brandall said:
Hi, don't forget that Android is supposed to handle these processes so they don't use any cpu and remain dormant, however, I understand that sometimes it just feels better if they are not there... (although others would tell you that killing apps may make your device under-perform!)
Anyway, killall -9 com.whatsapp will kill the process, but testing it on my device, it restarted almost instantly.
I have the application system tuner pro by 3c an amazing app and under the apps tab there is a 'startup' option for applications which I assumed referred to at boot - I just unticked whatsapp in there, killed the process and then it didn't restart... Maybe a coincidence, but worth a try...
I've no idea what different events in Android cause these apps to decide to come to life...
Hope that helped!?
Sent from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
they may not use cpu but for sure they use battery =/

brunoshady said:
they may not use cpu but for sure they use battery =/
Click to expand...
Click to collapse
It's not my understanding, but I have been wrong before
Did what I suggested stop it restarting??

kill service
I would like to kill a service using this method
I can find the service I want in android service list, it's called "RTService"
How can I find the text to put before "pkill" ?
In terminal emulator and "ps", I didn't find anything related to this and of course "pkill RTService" does nothing ^^
Thanks!

Memory Management (LowMemKiller) Options

Hey all,
Ive been playing with AutoKiller since it came out, and its a fabulous way to manage memory in Android. However, recently I found a mod that not only tweaked the lowmemkiller (android memory management) but also reorganized the service\app priority for best responsiveness.
I started this thread as a forum to discuss the different settings for the SuperCharger script, AutoKiller, and anything that modifies android's memory management. Ive included the default script along w/ a few mods for the different launcher versions. I am leaving the details scarce, as I want you to look at the original thread of instructions and issues resolution.
I am personally using the "Hard-To-Kill" launcher feature tweaked to recognize ADW EX (u just change the name of the launcher in the beginning of the script to com.adw.launcher, or whatever your launcher package name is) and MegaRAM (512+) option and have had good results for the past few hours.
Install Instructions
Install Script Manager from the Android Market (Market Link)
Select the script for your launcher (Ive attached a few)
Long-press and open as a "script\executable"
Select "open as root"
Click Save
Click Run
Follow Instructions & refer to orig thread for details
Share feedback here for others (Please try a setting for at least 12-14 hours before deciding its good\bad, tweaks like this CAN cause slow down after a number of hours of use, yet be incredibly responsive initially.)
Package name for Popular Launchers
ADW EX - org.adwfreak.launcher (attached, remove txt extension)
ADW Launcher - org.adw.launcher (attached, remove txt extension)
Launcher Pro - com.fede.launcher
Go Launcher EX - com.gau.go.launcherex (Thanx richua!)
Stock Gingerbread Launcher (or CM's pre-installed ADW) - com.android.launcher
Try it out, and see how it works for you. Please visit the original thread as it is VERY informative, much more than I could be, and it contains much better instructions to get this up and running
Link: Original Thread
Help???!!! "I dont get it", "I'm getting some strange error in Scripting Manager", "WTF are you talking about?" aka Issues\Questions
There is a step-by-step walk through located here (thanks ruchua!), but this is still experimental and isnt ready for "mass consumption", hence why I was slim on details in the OP. If you REALLY want to try these tweaks but dont want to wrestle with the script, download AutoKiller, donate a few bucks so you get access to the advanced kernel tweaks, enable it on optimum or aggressive, enable all advanced tweaks, and it should have a similar effect w/o all the scripting action.
Enjoy and have fun!

Nice find.

Can't get the files to download.. via the (XDA Premium) app its saying can't open file - via desktop, download unsuccessful. I was anxious to try the files you've provided cause I noticed ADW EX on the name of the files and its not titled that in the original thread.
Sent from a Nexus X by LG

eViL D: said:
Nice find.
Click to expand...
Click to collapse
I believe I was the one to point this out to zimphismonger over in faux's thread when I seen zimphishmonger asking about a bug in AutoKiller with faux's latest Kernel. No big deal, its just I've been messing with this thing and been unsuccessful with it. At least somebody knows how to tweek it.
Sent from a Nexus X by LG

DJ "suMo* said:
Can't get the files to download.. via the (XDA Premium) app its saying can't open file - via desktop, download unsuccessful. I've been up and down the oringinal thread, the visual walk through, and cannot figure this out for nothing. I was anxious to try the files you've provided cause I noticed ADW on the name of the files and its not titled that on the original thread. I've been messing with this for the past week and can't get it to run, its just too complicated for me.
Sent from a Nexus X by LG
Click to expand...
Click to collapse
This is def an advanced tweak that requires some knowledge of Android and app development. If you can follow the walkthrough on the original page, thats great. If not, I would suggest AutoKiller Donate as it does a lot of the same things w/o the scripts.
Please share your thoughts suggestions, experience etc, as Im interested in how this will affect different "style" of users: Id classify myself as a app-heavy user with ~200 apps, while others are much less. Im interested in a memory management setting that will help both sides.
Ive been playing w/ the HTK launcher setting and the 2 "MegaRAM" settings to see how it affects general responsiveness, UI, refresh, and if any apps get kicked out of ram (especially messaging and launcher).
DJ "suMo* said:
I believe I was the one to point this out to zimphismonger over in faux's thread when I seen zimphismonger asking about a bug in Autokiller with faux's latest Kernel. No big deal, its just I've been messing with this thing and been unsuccessful with it. At least somebody knows how tweek it.
Click to expand...
Click to collapse
The original author of the thread linked in the OP started talking about this (although a little aggressively, if you ask me...but whatever), but I decided to take a peak at the code anyway. This is a cool script, but it is by no means (end)user friendly and could use some more documentation. The possible bug\glitch between AutoKiller and Faux's kernel (if it exists, I think its a generalized bug) is that enabling the advanced tweak setting for IO scheduler which tells it our phone has no spinning hard disk (all flash memory) causes an immediate reboot back to the kernel's "baked-in" LG logo (the purple one). Disabling that feature fixed that issue, but the "SuperCharger" script has a similar option that ill most likely have a similar result.

Tackling a few points at once here...
The process name for GO Launcher is com.gau.go.launcherex in case anyone else uses that.
Inside GO Launcher settings, there's an option for "system persistent" that I unchecked. There's no explanation as to what that setting does but everything is running smoothly so far. Also in GO Launcher settings as well as LauncherPro (maybe others too but those are the two I use) there's a setting to prevent FC when running out of memory. I kept that checked by default.
Per the dev's suggestion in Faux's thread, my setup is MegaRAM 1 and HTK Launcher. For the past 10 minutes I've been trying to make things lag and frankly, things just aren't lagging. This is much better than any setup I tried with Autokiller, which in its own right is also a very good app. I unchecked all settings in Autokiller so it wouldn't interfere; I will probably uninstall it soon.
The V8 beta for this SuperCharger script and Autokiller's advanced tweaks both have a setting for kernel scheduling, which as some of you may know leads to booty loops. Autokiller was updated today with a change that tries to prevent that but I have not tried it since I hate booty loops and don't even want to risk messing up the great setup I have now. The V8 beta has also been rewritten with the scheduler tweaks commented out. Hopefully this issue can get sorted out. I run the scheduler tweak on my N1 and can't say that it's helping a lot, but it certainly doesn't seem to be hurting.
Seriously, the ROI on running this script is immense. Read the linked OP carefully, follow the directions, and you'll have what feels like a new phone in a few minutes.

@zimphishmonger, I don't know if you follow Paul O'Brien of MoDaCo, but he put out a link yesterday on Twitter for an apk BetterBatteryStats for Gingerbread devices. http://www.cri.ch/sven/doku.php/computing/android/betterbatterystats Have you checked it out? I got it installed and I'm not 100% sure what its doing. I figured it was related to this post being it has to do with utilizing..
Sent from a Nexus X by LG

I got no idea what to do... the more I read the more confused I get. Links lead to other links that lead to other links. I wish someone would make a flashable or something. ;-)
Sent from my LG-P999 using XDA App

siresh said:
I got no idea what to do... the more I read the more confused I get. Links lead to other links that lead to other links. I wish someone would make a flashable or something. ;-)
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
agreed!
FWIW, the OP is crazy confusing for non-techies. Oh, the beauty of a step-by-step laundry list!
(Or a flashable...)

Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.

So do we change anything in the script to match our launcher??

fcisco13 said:
So do we change anything in the script to match our launcher??
Click to expand...
Click to collapse
Check steps 3 and 4 in my post right above yours.

richua said:
Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.
Click to expand...
Click to collapse
This is really good...super clear writing and easy to follow instructions! Thanks for making it so easy for us!!

So does this make a big difference on our devices? I have EB 2.3.5 with faux's kernel and at 1.1 ghz. It's already pretty fast. The before and after benchmark comparison on the OP don't seem to be different. I would like some feedback before I do this let me know! I'll do it in the morning if it's really worth it.

Shaddy-Z. said:
So does this make a big difference on our devices? I have EB 2.3.5 with faux's kernel and at 1.1 ghz. It's already pretty fast. The before and after benchmark comparison on the OP don't seem to be different. I would like some feedback before I do this let me know! I'll do it in the morning if it's really worth it.
Click to expand...
Click to collapse
Overall, it has made performance a bit better. I use the same ROM and settings as you, and I agree it's already very good...but these settings are nice. I'm not sure this process can be undone so easily, so it's a valid point you make. But, fwiw, I followed the instructions above and am noticing a difference in performance.

richua said:
Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.
Click to expand...
Click to collapse
Thanx much easier to understand!!! Will this work on 2.3.3 ota rom rooted.?)
Sent from my LG-P999 using XDA App

richua said:
Here's a list of what I did to get up and running within a few minutes.
Make a nandroid.
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager
If you use ADW or ADW EX as a launcher, download the appropriate file to your SD card from the OP of this thread. Continue to step 6.
If you use LauncherPro/LauncherPro Plus or GO Launcher, download the text file from OP of the linked thread titled "V6_SuperCharger_for_Android-update8.sh.txt" either to your phone (if you have a text editor) or to your computer (if you don't). Here's the link: http://forum.xda-developers.com/attachment.php?attachmentid=661892&d=1311292674
Open the text file. If you have a "find" feature, look for where it says "com.android.launcher". If you're on your phone and/or don't have a "find" feature, scroll down (not too far from the top) to a line that starts with "launcheradj=" and that's where you'll find "com.android.launcher". Replace com.android.launcher with either com.fede.launcher if you're using LP/LPP or com.gau.go.launcherex if you're using GO Launcher. Make sure you don't delete that space between "pidof" and "com.whateverYou'reUsing", and don't delete that tick mark right after it. Save and exit. If you did this on your computer, upload this file to your phone. (Note: if you are using a launcher not described here, you'll have to find the process name yourself and enter it as instructed above)
Open Script Manager and locate where you just stored that file. Long press on it, select "Open As ...", select "Script/Executable." In the box that pops up, check "Run as root" and then hit "Run" in the top left. The script will now be run. The first prompt will be for scrolling speed. Touch the screen to bring up the soft keyboard. Type the number corresponding to which scroll speed you like and hit enter.
You are now inside the script. IF YOU DID NOT READ ANY OF THE LINKED THREAD, type 8 at the main menu prompt and hit enter on the keyboard, wait for it to do some work and automatically return to the main menu prompt, then type 11 and hit enter and wait, then hit 17 and enter and wait. 17 is the exit command so you'll now see on the top left a button that says "Close." Hit that and then back out of Script Manager, then go to step 9.
If you did read the linked thread, you'll know a little bit more about what each option is. Feel free to experiment. To select an option, type the number of the option and hit enter on the keyboard. Current recommendations are both 8 and 11. Once you are done, type 17 followed by an enter, then hit "Close" in the top left and back out of Script Manager.
Provided you followed the instructions and did not encounter any weird errors in any step, the settings you selected are now active. Nothing else is required. Enjoy your snappy new setup.
I rolled back my settings and typed this list up as I started over from scratch so this almost literally is each and every step I took to get things running. If you have download errors, I suggest not using the XDA app and downloading instead from a standard browser. Make sure you are clicking on the right file. If you didn't read the linked thread and are unsure about proceeding, you should read the linked thread. If you read the linked thread and still are unsure, download the Autokiller app and choose the "optimum" setting there.
Click to expand...
Click to collapse
Thanks for the detailed how-to. Please be sure to uninstall and\or disable autokiller to make sure they arent conflicting, as that will def screw with your test results. Also, please run this for at least 24 hours to get a real good idea how it performs after a number of hours. This is a major mod to androids memory management and Im trying to discover if there are any side effects. Thanks for your feedback and testing results. Please keep sharing.
siresh said:
I got no idea what to do... the more I read the more confused I get. Links lead to other links that lead to other links. I wish someone would make a flashable or something. ;-)
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Wanted testing from people who knew what was going on internally, as this is pretty experimental, but this is fine too. Feedback is feedback Try a few different memory settings and see how they work, both MegaRAM and multitasking settings.

Erislover said:
Overall, it has made performance a bit better. I use the same ROM and settings as you, and I agree it's already very good...but these settings are nice. I'm not sure this process can be undone so easily, so it's a valid point you make. But, fwiw, I followed the instructions above and am noticing a difference in performance.
Click to expand...
Click to collapse
This can easily be undone by running the script again, I think its option 8 to "unsupercharge". Thy options should disable all the tweaks made by the script (you did nandroid before, right??).
FEEDBACK: Tested MEGARAM Option 2 (#9 on the script) and it was too aggressive, imo. We don't need that much free ram anyways, its a waste. Testing MEGARAM 1 + HKL (#8 on script) today, and we'll see how it works.

Im using it now.... this thing is blazing.... feels like overclocking.... whats it doing really?
Sent from my Transformer TF101 using XDA Premium App

KingDavid63 said:
Im using it now.... this thing is blazing.... feels like overclocking.... whats it doing really?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
The SuperCharger script completely re-arranging how Android prioritizes its apps in memory (so which ones get killed and when), and tweaks how aggressive Android's internal memory management. Essentially, it is fending off apps from hogging memory and cpu time unnecessarily, and giving important apps like phone, launcher, sms highest priority. The 98kickasskernel script (if you are using it) is optimizing a lot of kernel settings are set improperly\not optimized (almost identical to Autokillers "advances system tweaks"). Thats a very dumbed down explanation, but it gets the idea across .

Enable flash on your website

I've written a quick script to enable flash on whichever website you prefer.
It only works one at a time
it will force quit iexplorer and attempt to reload it
it requires administrator for silent reg import
Needs work.
save as .bat and put it in its own folder somewhere like the desktop.
enjoy :]
@echo off
color F8
echo !!!NEEDS ADMINISTRATOR PRIVILEGES!!!
echo Windows RT/Metro flash enabler
set /p www=Which website would you like to add to the FLASH WHITELIST?:
echo Windows Registry Editor Version 5.00 > %www%.reg
echo [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Flash] >> %www%.reg
echo "DebugDomain"="%www%" >> %www%.reg
taskkill /f /IM iexplore.exe
regedit /s %www%.reg
del %www%.reg
Click to expand...
Click to collapse

thank but...
simmos said:
I've written a quick script to enable flash on whichever website you prefer.
It only works one at a time
it will force quit iexplorer and attempt to reload it
it requires administrator for silent reg import
Needs work.
save as .bat and put it in its own folder somewhere like the desktop.
enjoy :]
Click to expand...
Click to collapse
Tank you ! it Work !
it important to write correctly the name of the site !!
for exemple:
palmashow.com and not http://palmashow.com/
@+

Good to hear its working for you.
It's a bit rough so you may need to play around to get it to work. i'll note that some sites embed videos from other sites so you will need to add them instead.

Wow, welcome to at least a month ago...
EDIT: over two months ago... but it's been in my signature for a month or so
No offense, but your script is kind of crude. There's absolutely no need to kill off IE (just refresh the page!) and the use of a temp file constantly is wasteful, just use reg.exe
...
Or you could use the script pair that I wrote (and posted on this site) for exactly this purpose over a month back. In addition to a script that does what yours does (less wastefully), it also includes a script that changes the permissions on the registry key in question so that subsequent changing of the relevant registry value can be done without needing admin (the permission-changer script must be run as admin, but only needs to be run once per device).
Seriously, use Search before posting! Your thread even has almost exactly the same subject line.

GoodDayToDie said:
Wow, welcome to at least a month ago...
EDIT: over two months ago... but it's been in my signature for a month or so
No offense, but your script is kind of crude. There's absolutely no need to kill off IE (just refresh the page!) and the use of a temp file constantly is wasteful, just use reg.exe
...
Or you could use the script pair that I wrote (and posted on this site) for exactly this purpose over a month back. In addition to a script that does what yours does (less wastefully), it also includes a script that changes the permissions on the registry key in question so that subsequent changing of the relevant registry value can be done without needing admin (the permission-changer script must be run as admin, but only needs to be run once per device).
Seriously, use Search before posting! Your thread even has almost exactly the same subject line.
Click to expand...
Click to collapse
I'm sorry to hear you spent time on this before. I did not realise.
I'm not trying to steal credit, I just created this for myself last night on my surface and thought it would be worth posting.
I'll make sure to use search next time :] [I did have a quick look on the front page before posting, link to thread?]

It's in my signature... http://forum.xda-developers.com/showthread.php?p=33412065

[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?