Jump to content

titanic_fanatic

Approved Members
  • Posts

    18
  • Joined

  • Last visited

 Content Type 

Profiles

Forums

Blogs

Gallery

Downloads

Poweramp Knowledge Base

База знаний Poweramp

Poweramp知识库

Poweramp Equalizer Knowledge Base

База знаний Poweramp Equalizer

Store

Events

Ideas

Posts posted by titanic_fanatic

  1. Ok, Thanks for your help and your quick answers :)

    Just one little question, what software do you use to create png elements for your themes ?

     

    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 ;-)

  2. That stuffs was already done, but if i change the package name, i get an error.

    I'll try to start build with only manifest, res folder, src folder with my name

    With ant debug it works fine but it's not my signature !

    Do you know how i can create key.store and key.alias ?

    Thanks :)

     

    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

  3. For assets, it works, thx

     

    Now, there is an issue with my keys, i made them by compiling an apk with inteliJ, for alias and store i've only One file wich is ~/keys

    My password had been asked, but after he can't find the file "keys"  :huh:

    I verified, the file "keys" is in "~/" folder with the good typo

    When i input a wrong password, the return is "wrong password" so the keys are readen

    -release-prompt-for-password:    [input] Please enter keystore password (store:../../../../keys):*****************    [input] Please enter password for alias '../../../../keys':*****************-release-nosign:-release-sign:     [echo] Signing final apk...BUILD FAILED/home/pdroid/adt-bundle-linux-x86_64-20130522/sdk/tools/ant/build.xml:1132: The following error occurred while executing this line:/home/pdroid/adt-bundle-linux-x86_64-20130522/sdk/tools/ant/build.xml:1144: Signing key ../../../../keys not found

    Thank you

     

    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 ;-)

  4. I was in the wrong folder, if you watch, i was in "poweramp_api_example" and not in "poweramp_skin_sdk/skin classic"

     

    Now i am ! and i get issues !

    [exec] ERROR: asset directory '/home/pdroid/adt-bundle-linux-x86_64-20130522/eclipse/workspace/purewhite/assets' does not existBUILD FAILED/home/pdroid/adt-bundle-linux-x86_64-20130522/eclipse/workspace/purewhite/build.xml:57: exec returned: 1
    attachicon.gifbuild.xml

     

    Thanks for your answer :)

    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.

  5. Hi, i'am trying just to build the example theme

     

    But it doesn't work

    pdroid@linuxUB-MS-7596:~/adt-bundle-linux-x86_64-20130522/eclipse/workspace/powerampapi/poweramp_api_example$ ant distBuildfile: /home/pdroid/adt-bundle-linux-x86_64-20130522/eclipse/workspace/powerampapi/poweramp_api_example/build.xmlBUILD FAILEDTarget "dist" does not exist in the project "MainActivity". Total time: 0 seconds
     

    When i run ant alone i get this

    pdroid@linuxUB-MS-7596:~/adt-bundle-linux-x86_64-20130522/eclipse/workspace/powerampapi/poweramp_api_example$ ant Buildfile: /home/pdroid/adt-bundle-linux-x86_64-20130522/eclipse/workspace/powerampapi/poweramp_api_example/build.xmlhelp:     [echo] Android Ant Build. Available targets:     [echo]    help:      Displays this help.     [echo]    clean:     Removes output files created by other targets.     [echo]               This calls the same target on all dependent projects.     [echo]               Use 'ant nodeps clean' to only clean the local project     [echo]    debug:     Builds the application and signs it with a debug key.     [echo]               The 'nodeps' target can be used to only build the     [echo]               current project and ignore the libraries using:     [echo]               'ant nodeps debug'     [echo]    release:   Builds the application. The generated apk file must be     [echo]               signed before it is published.     [echo]               The 'nodeps' target can be used to only build the     [echo]               current project and ignore the libraries using:     [echo]               'ant nodeps release'     [echo]    instrument:Builds an instrumented package and signs it with a     [echo]               debug key.     [echo]    test:      Runs the tests. Project must be a test project and     [echo]               must have been built. Typical usage would be:     [echo]                   ant [emma] debug install test     [echo]    emma:      Transiently enables code coverage for subsequent     [echo]               targets.     [echo]    install:   Installs the newly build package. Must either be used     [echo]               in conjunction with a build target (debug/release/     [echo]               instrument) or with the proper suffix indicating     [echo]               which package to install (see below).     [echo]               If the application was previously installed, the     [echo]               application is reinstalled if the signature matches.     [echo]    installd:  Installs (only) the debug package.     [echo]    installr:  Installs (only) the release package.     [echo]    installi:  Installs (only) the instrumented package.     [echo]    installt:  Installs (only) the test and tested packages (unless     [echo]               nodeps is used as well.     [echo]    uninstall: Uninstalls the application from a running emulator or     [echo]               device. Also uninstall tested package if applicable     [echo]               unless 'nodeps' is used as well.BUILD SUCCESSFULTotal time: 0 seconds
    Here is my local.properties file :

    # This file is automatically generated by Android Tools.# Do not modify this file -- YOUR CHANGES WILL BE ERASED!# # This file must *NOT* be checked in Version Control Systems,# as it contains information specific to your local configuration.# location of the SDK. This is only used by Ant# For customization when using a Version Control System, please read the# header note.sdk.dir=../../../../sdk/Poweramp.apk=../Poweramp-2.0.9-build-529.apkkey.store=../../../../../keyskey.alias=../../../../../keys
    Thanks for help ;)

    Can you please post your build.xml file.

  6. Thanks for the help. You are right, i was linking an incorrect Poweramp apk.

     

    Now my problem is i don´t know how to set key.store and key.alias . I generated an android sign from other android project and set the direction to this file in key.store. When i make ant dist eclipse ask for the password but i type it and then i get error.

     

    What error message do you get?

  7. Hi, i've imported into Eclipse an Android aplication project from poweramp_skin_sdk > skin_classic folder.

    I made ​​the changes in manifest package and point sdk.dir and Poweramp.apk locations.

    When i try to run "ant apkpush" i get something like this:

     

    [echo] SKIN: Generating R.java / Manifest.java from the resources...

         [exec] C:\Users\marketing01\workspace\skin_classic\res\values\classic_skin_styles.xml:4: error: Error retrieving parent for item: No resource found that matches the given name '@com.maxmpz.audioplayer:style/ActivityTheme_Default'.

         [exec] C:\Users\marketing01\workspace\skin_classic\res\values\classic_skin_styles.xml:43: error: Error: No resource found that matches the given name: attr 'com.maxmpz.audioplayer:BigRoundButton'.

     

    Can someone help me?

     

    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.

  8. 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 :-)

×
×
  • Create New...