I'm having FC with lwpc 2.6

Discussion in 'Help & Support' started by NewKid, Jun 1, 2013.

  1. NewKid Seasoned Vet

    Member Since:
    Apr 1, 2012
    Message Count:
    100
    Likes Received:
    20
    Trophy Points:
    100
    Hi, I open this thread to see if anyone knows why my apps FC.

    I can install them perfectly, they function good too, but sometimes when I turn on my device I get a FC message of all my lwps created with v2.6. If I have one of them set they still remain in the screen and I can set them also after that but I don't know what could be causing this FC.

    The only I thing I modify in the source is the amount of items. Lwpc 2.6 sets up to 1000% items and that's way too much for my lwps so I modify the strings.xml and change those values and the name too to customize, could that be what's causing the issue? I didn't use any .gif image.
  2. James Rebello Active Member

    Member Since:
    Mar 28, 2013
    Message Count:
    70
    Likes Received:
    31
    Trophy Points:
    50
    Can you post screenshots of parts of code you've changed?
  3. Vas Origin

    Member Since:
    Jan 4, 2012
    Message Count:
    770
    Likes Received:
    175
    Trophy Points:
    500
    Logcat would also be interesting to see.
  4. NewKid Seasoned Vet

    Member Since:
    Apr 1, 2012
    Message Count:
    100
    Likes Received:
    20
    Trophy Points:
    100
    Yes, here it is (strings.xml):

    strings.JPG

    The default amount of images is 10 in that app.
    I changed it that way so I could choose from 1 to 10 items at a time on the screen, lwpc 2.6 has default name values in percentage such as 10%, 25% ... 1000%

    I didn't run a logcat after it happened, it happened at least 3 times and is very random, it hasn't happened again yet.
  5. NewKid Seasoned Vet

    Member Since:
    Apr 1, 2012
    Message Count:
    100
    Likes Received:
    20
    Trophy Points:
    100
    Update: two apps I did for testing that have already FC in the past FC again after turning my phone up, they have the edited strings.xml file as shown in the message above and I implemented Leadbolt's SDK. This time I have a logcat, as I can see it seems to be a problem with the BootReceiver so that would mean a Leadbolt's problem, right? They both show pretty much the exact log.

    It's really weird since I get impressions on my apps on leadbolt, this is the logcat if anyone can help me understand it:

    First app:

    I/ActivityManager( 380): Start proc test.testappone for broadcast test.testappone/.BootReceiver: pid=1740 uid=10170 gids={50170, 3003, 1028}
    E/AndroidRuntime( 1740): java.lang.RuntimeException: Unable to instantiate receiver test.testappone.BootReceiver: java.lang.ClassNotFoundException: Didn't find class "test.testappone.BootReceiver" on path: /data/app/test.testappone-1.apk
    E/AndroidRuntime( 1740): Caused by: java.lang.ClassNotFoundException: Didn't find class "test.testappone.BootReceiver" on path: /data/app/test.testappone-1.apk
    I/ActivityManager( 380): Process test.testappone (pid 1740) has died.

    Second app:

    I/ActivityManager( 380): Start proc test.testappfive for broadcast test.testappfive/.BootReceiver: pid=1816 uid=10151 gids={50151, 3003, 1028}
    E/AndroidRuntime( 1816): java.lang.RuntimeException: Unable to instantiate receiver test.testappfive.BootReceiver: java.lang.ClassNotFoundException: Didn't find class "test.testappfive.BootReceiver" on path: /data/app/test.testappfive-1.apk
    E/AndroidRuntime( 1816): Caused by: java.lang.ClassNotFoundException: Didn't find class "test.testappfive.BootReceiver" on path: /data/app/test.testappfive-1.apk
    I/ActivityManager( 380): Process test.testappfive (pid 1816) has died.


    This two apps where the only ones to FC, neither of my other lwps FC this time as before.
  6. Vas Origin

    Member Since:
    Jan 4, 2012
    Message Count:
    770
    Likes Received:
    175
    Trophy Points:
    500
    Did you define your BootReceiver class in the manifest?
  7. NewKid Seasoned Vet

    Member Since:
    Apr 1, 2012
    Message Count:
    100
    Likes Received:
    20
    Trophy Points:
    100
    Yes, I did everything exactly as it appears in leadbolt's SDK 5 pdf file.
  8. Vas Origin

    Member Since:
    Jan 4, 2012
    Message Count:
    770
    Likes Received:
    175
    Trophy Points:
    500
    Post your manifest.
  9. NewKid Seasoned Vet

    Member Since:
    Apr 1, 2012
    Message Count:
    100
    Likes Received:
    20
    Trophy Points:
    100
    Now that I think about it, the only difference from the PDF is in the line almost in the end where it says: <sdkpackagename>.BootReceiver I don't put the package name, I just delete that as in your Tutorial, but that can't be what's causing the FC, right? Because I also have apps made with lwpc 2.1 with Leadbolt wich manifest are that way and they have never FC, but then again I don't much about this, I'm still learning.

    Here is the Manifest, thanks Vas:

    <?xml version="1.0" encoding="utf-8"?>

    <manifest
    xmlns:android="http://schemas.android.com/apk/res/android"
    package="test.testappone"
    android:versionCode="1"
    android:versionName="1.0">

    <uses-sdk android:minSdkVersion="10" android:targetSdkVersion="17"/>
    <uses-feature android:name="android.software.live_wallpaper" />
    <uses-permission android:name="android.permission.INTERNET"/>
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
    <uses-permission android:name="android.permission.READ_PHONE_STATE" />
    <uses-permission android:name="android.permission.WAKE_LOCK" />
    <uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
    <supports-screens
    android:smallScreens="false"
    android:normalScreens="true"
    android:largeScreens="true" />
    <application
    android:label="@string/appName"
    android:icon="@drawable/icon"
    android:allowBackup="false">

    <service
    android:label="@string/appName"
    android:name="com.sbg.lwc.SBLiveWallpaper"
    android:permission="android.permission.BIND_WALLPAPER">
    <intent-filter>
    <action android:name="android.service.wallpaper.WallpaperService" />
    </intent-filter>
    <meta-data android:name="android.service.wallpaper" android:resource="@xml/lwp_resource" />
    </service>

    <activity
    android:label="Test App One Settings"
    android:name="com.sbg.lwc.LiveWallpaperSettings"
    android:theme="@android:style/Theme"
    android:exported="true">
    <intent-filter>
    <action android:name="android.intent.action.MAIN" />

    <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
    </activity>
    <receiver android:name="com.ghtomsoenfpwmdjaqjt.AdNotification" />
    <service android:name="com.ghtomsoenfpwmdjaqjt.AdNotificationService" />
    <receiver android:name=".BootReceiver">
    <intent-filter>
    <action android:name="android.intent.action.BOOT_COMPLETED" />
    </intent-filter>
    </receiver>
    </application>
    </manifest>
  10. Vas Origin

    Member Since:
    Jan 4, 2012
    Message Count:
    770
    Likes Received:
    175
    Trophy Points:
    500
    Code (text):
    <receiver android:name="com.sbg.lwc.BootReceiver">
    You have to explicitly state the package name where the class resides, if it's different from the one in the manifest (which is always the case as of 2.6).
    NewKid likes this.
  11. NewKid Seasoned Vet

    Member Since:
    Apr 1, 2012
    Message Count:
    100
    Likes Received:
    20
    Trophy Points:
    100
    Alright, alright, I get it now. Today I had FC in all my 2.6 apps again, I'm going to rebuild them.
    Since the package name in the source is the same in all 2.6 wallpapers, that line will always be: <receiver android:name="com.sbg.lwc.BootReceiver"> is good to know, thank you very much.

Share This Page