• Announcements

    • andrewilley

      Poweramp v3 Project Update   04/24/2017

      As you may be aware, the Poweramp developer has been working hard on an updated material design user interface for Poweramp v3 which required a full ground-up rebuild of the code and is taking some time to get to a beta-test stage. See the forum thread for more details and to discuss.    


Approved Members
  • Content count

  • Joined

  • Last visited

About titanic_fanatic

  • Rank
  • Birthday 04/17/1985

Profile Information

  • Gender
  • Location
    Calgary, Alberta, Canada
  • Interests
    Everything technology related.

Recent Profile Visitors

2,399 profile views
  1. What kind of customization are you looking to achieve? What Android version does it need to support? You can pm me if you like ;-)
  2. I just updated mine last night ;-) Purple Silk, Emerald Desire, Saphire Dream, Ruby Red and Black Onyx. https://play.google.com/store/apps/developer?id=Net+Works+Web+Design
  3. I use Corel (formerly Jasc) Paint Shop Pro, but you can use any graphics editor you want. Many themers just use Gimp (I can't stand gimp though as it's not driven by standards and can be confusing if you have any experience with a professional graphics editing program). Be very careful with .9.png's they MUST have a 1px border with markers in pitch black #000000 marking the stretchable areas (left and top border) and the content areas (right and bottom border). If your border has a color other than transparent or pure black you will get many errors while compiling. If this happens, fix the first graphic that's listed and recompile to get the next error ;-) If your opening any png's from decompiled apk's, then you will run into an issue where they have been optimized for the platform, and most graphic editors make them look blotchy. If this is an issue for you, I have a tool on xda-developers that I designed to fix that problem... You can check out the thread here: http://forum.xda-developers.com/showthread.php?t=2216403 Good Luck ;-)
  4. Check out the android developer page on creating a keystore. This is where I learned from ;-) http://developer.android.com/tools/publishing/app-signing.html
  5. In your local.properties file, the key.store should point to your keystore file key.keystore or something similar (which I think your ok with) and the key.alias is the alias that you used to setup your keystore (like a username, not a path). this is not a path like I see in your previous post. and in regards to the AndroidManifest.xml file, the following line must be present and unchanged: <meta-data android:name="com.maxmpz.PowerampSkins" android:value="true"/>You can specify your package name in the first directive as such: <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.nwwebdesign.poweramp.skins.PurpleSilk" android:versionCode="4" android:versionName="1.3">Hopefully this will get your first build to run successfully ;-)
  6. said that the assets directory doesn't exist. Add an empty asset dir to /home/pdroid/adt-bundle-linux-x86_64-20130522/eclipse/workspace/purewhite it doesn't need to contain anything. Try recompiling again after adding the directory.
  7. Can you please post your build.xml file.
  8. What error message do you get?
  9. The Poweramp apk has been compiled with "unknown" opcodes which is how Max fights piracy. You need to tell your compiler what to do with the "unknown" opcodes in order to decompile it. I don't think he will allow this as it would defeat the purpose of his efforts to stop piracy ;-)
  10. I don't think you've properly configured your local.properties file with the path to the Poweramp apk. This is required in order for the compiler to reference, for example, the styles that are listed above. Double check and make sure that the path to your Poweramp.apk is correct... I used an absolute path instead of a relative path in my local.properties... Not sure if that makes a difference here.
  11. Poweramp Skin Gallery I will be building a new app called Poweramp Skin Gallery. It will be a very simple play store like app to browse only Poweramp skins. In addition to browsing Poweramp skins from the market, you will be able to see all of your currently installed skins and manage them from my app. If you have any suggestions for features, please email me or post to my G+ or Twitter ;-)
  12. I noticed in your build.xml that the declaration for xml is not included: <?xml version="1.0" encoding="UTF-8"?> This should be the very first line in any xml file... Maybe this is the cause. Also, I don't think it's a cause of your problems, but why did you physically specify the build.xml from the sdk instead of letting the vars take care of that... Change the following: <!-- version-tag: custom --> <import file="D:/Android/AndroidSDK/sdk/tools/ant/build.xml" /> to <!-- version-tag: custom --> <import file="${sdk.dir}/tools/ant/build.xml" /> The var ${sdk.dir} should automatically be replaced with the path to your android sdk if you have correctly set it up on your system. One last thing, you are trying to run this from console right, and not from within eclipse... Eclipse is not supported for building/running Poweramp skins with ant. As stated in the quick start guide, eclipse will point out non-existent errors and won't work. Eclipse in this situation is only a glorified text editor... I suggest Notepad++ as it isn't a resource hog like eclipse and eclipse is kind of overkill for developing Poweramp skins.
  13. you simply use the apk that you download from the market or off of the powerampapp.com website (not the unlocker, but the trial)... Install it with apktool as a framework: apktool if C:\path\to\Poweramp.apk Once you have installed this as a framework, you shoud change the path to Poweramp.apk to point to the apk on your computer. You should then be able to compile without issue :-)
  14. Thanks for the quick response Max :-) I will implement this immediately and will keep checking back for the updated classic skin sources :-)
  15. Hey guys, So my skin has been on the market for a couple of weeks now and is doing well... I did get a crash report from my developer console yesterday though, and am not sure that it relates to my skin java.lang.IllegalStateException: Could not execute method of the activity at android.view.View$1.onClick(View.java:3598) at android.view.View.performClick(View.java:4091) at android.view.View$PerformClick.run(View.java:17036) at android.os.Handler.handleCallback(Handler.java:615) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:4912) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.reflect.InvocationTargetException at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:511) at android.view.View$1.onClick(View.java:3593) ... 11 more Caused by: android.content.ActivityNotFoundException: Unable to find explicit activity class {com.maxmpz.audioplayer/com.maxmpz.audioplayer.SettingsActivity}; have you declared this activity in your AndroidManifest.xml? at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1541) at android.app.Instrumentation.execStartActivity(Instrumentation.java:1416) at android.app.Activity.startActivityForResult(Activity.java:3389) at android.app.Activity.startActivityForResult(Activity.java:3350) at android.app.Activity.startActivity(Activity.java:3562) at android.app.Activity.startActivity(Activity.java:3528) at com.nwwebdesign.Poweramp.skins.InfoActivity.onButton1Click(InfoActivity.java:51) ... 14 more Unfortunately the market report does not tell me the version of android being used when this error occurred. It seems that the activity class com.maxmpz.audioplayer.SettingsActivity could not be found. Is this maybe due to a user not using the latest version? Are the classes different from version to version? What should be done to rectify this error?