Stacey5150
Lost but trying
Profile
Posts: 54
Reg: Feb 17, 2013
West Middlesex,...
8,490
11/04/13 01:23 PM (10 years ago)

Error in imported project

When I imported my project it showed the following error 3 times. I tried to clean the project as well as fix the project properties with no success. Not sure what is creating these errors in my project. I downloaded my project with Buzztouch v3. Thank you! Error Mon Nov 04 14:52:04 EST 2013 Exception occurred while saving project preferences: /letsgo/.settings/org.eclipse.jdt.core.prefs. org.eclipse.core.internal.resources.ResourceException: A resource already exists on disk 'C:UsersOwnerDownloadsletsgo_Android.settings'. at org.eclipse.core.internal.resources.Folder.assertCreateRequirements(Folder.java:47) at org.eclipse.core.internal.resources.Folder.create(Folder.java:95) at org.eclipse.core.internal.resources.ProjectPreferences$1.run(ProjectPreferences.java:566) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.core.internal.resources.ProjectPreferences.save(ProjectPreferences.java:590) at org.eclipse.core.internal.preferences.EclipsePreferences.internalFlush(EclipsePreferences.java:465) at org.eclipse.core.internal.resources.ProjectPreferences.flush(ProjectPreferences.java:350) at org.eclipse.jdt.internal.core.JavaProject.setOption(JavaProject.java:2953) at com.android.ide.eclipse.adt.internal.project.ProjectHelper.checkAndFixCompilerCompliance(ProjectHelper.java:515) at com.android.ide.eclipse.adt.internal.project.ProjectHelper.fixProjectClasspathEntries(ProjectHelper.java:420) at com.android.ide.eclipse.adt.internal.project.ProjectHelper.fixProject(ProjectHelper.java:294) at com.android.ide.eclipse.adt.internal.wizards.newproject.NewProjectCreator.createEclipseProject(NewProjectCreator.java:837) at com.android.ide.eclipse.adt.internal.wizards.newproject.NewProjectCreator.createProjectAsync(NewProjectCreator.java:660) at com.android.ide.eclipse.adt.internal.wizards.newproject.NewProjectCreator.access$0(NewProjectCreator.java:590) at com.android.ide.eclipse.adt.internal.wizards.newproject.NewProjectCreator$3.execute(NewProjectCreator.java:400) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
11/04/13 01:48 PM (10 years ago)
I'd try deleting the project from the workspace, closing Eclipse, and then start again from scratch. Maybe it'll clear out some cache that has stale data in it? Mark
 
MadRod
Aspiring developer
Profile
Posts: 1853
Reg: Apr 12, 2012
Lisbon
27,930
like
11/04/13 03:50 PM (10 years ago)
Mark is the man to follow on these kind of problems.
 
tb
buzztouch Evangelist
Profile
Posts: 2050
Reg: Nov 03, 2011
Oxford
32,300
like
11/04/13 04:33 PM (10 years ago)
Yep, I think I can echo Mark. Maybe try using just the default Android 2.0 Core.
 
Stacey5150
Lost but trying
Profile
Posts: 54
Reg: Feb 17, 2013
West Middlesex,...
8,490
like
11/04/13 05:52 PM (10 years ago)
I deleted the workspace and started from scratch in v3 and did the same in v2 with the same results. )-:
 
Stacey5150
Lost but trying
Profile
Posts: 54
Reg: Feb 17, 2013
West Middlesex,...
8,490
like
11/05/13 08:41 AM (10 years ago)
Ok, I figured out this problem. For some reason I have to import my projects under General-->Existing projects into workspace and NOT Android-->Existing Android code into workspace in order to avoid getting errors...hey as long as it works. Next order of business is back to the emulator. I'm using The Nexus 7 with a API 13-4.0. I dropped the memory down to 700 of RAM because it crashed using the default 1024 of RAM, but still the apk fails to load in the emulator. Any suggestions? The following is what I get in the console: [2013-11-05 10:12:57 - SDK Manager] Updated AVD 'buzztouch_v3' based on Android 4.0, ARM (armeabi-v7a) processor, [2013-11-05 10:12:57 - SDK Manager] with the following hardware config: [2013-11-05 10:12:57 - SDK Manager] hw.sdCard=no [2013-11-05 10:12:57 - SDK Manager] hw.device.manufacturer=Google [2013-11-05 10:12:57 - SDK Manager] hw.mainKeys=no [2013-11-05 10:12:57 - SDK Manager] hw.lcd.density=213 [2013-11-05 10:12:57 - SDK Manager] hw.accelerometer=yes [2013-11-05 10:12:57 - SDK Manager] hw.dPad=no [2013-11-05 10:12:57 - SDK Manager] hw.device.hash=-2113695447 [2013-11-05 10:12:57 - SDK Manager] hw.trackBall=no [2013-11-05 10:12:57 - SDK Manager] hw.device.name=Nexus 7 [2013-11-05 10:12:57 - SDK Manager] hw.sensors.proximity=no [2013-11-05 10:12:57 - SDK Manager] hw.battery=yes [2013-11-05 10:12:57 - SDK Manager] disk.dataPartition.size=200M [2013-11-05 10:12:57 - SDK Manager] hw.audioInput=yes [2013-11-05 10:12:57 - SDK Manager] hw.sensors.orientation=yes [2013-11-05 10:12:57 - SDK Manager] hw.camera.front=none [2013-11-05 10:12:57 - SDK Manager] hw.gps=yes [2013-11-05 10:12:57 - SDK Manager] skin.dynamic=yes [2013-11-05 10:12:57 - SDK Manager] hw.keyboard=yes [2013-11-05 10:12:57 - SDK Manager] vm.heapSize=32 [2013-11-05 10:12:57 - SDK Manager] hw.ramSize=700 [2013-11-05 10:13:17 - letsgo] ------------------------------ [2013-11-05 10:13:17 - letsgo] Android Launch! [2013-11-05 10:13:17 - letsgo] adb is running normally. [2013-11-05 10:13:17 - letsgo] Performing com.letsgo.BT_activity_start activity launch [2013-11-05 10:13:17 - letsgo] Automatic Target Mode: launching new emulator with compatible AVD 'buzztouch_v3' [2013-11-05 10:13:17 - letsgo] Launching a new emulator with Virtual Device 'buzztouch_v3' [2013-11-05 10:13:21 - Emulator] emulator: emulator window was out of view and was recentered [2013-11-05 10:13:21 - Emulator] [2013-11-05 10:13:21 - letsgo] New emulator found: emulator-5554 [2013-11-05 10:13:21 - letsgo] Waiting for HOME ('android.process.acore') to be launched... [2013-11-05 10:25:12 - letsgo] HOME is up on device 'emulator-5554' [2013-11-05 10:25:12 - letsgo] Uploading letsgo.apk onto device 'emulator-5554' [2013-11-05 10:25:48 - letsgo] Failed to install letsgo.apk on device 'emulator-5554': timeout [2013-11-05 10:25:48 - letsgo] Launch canceled! I appreciate all the help!
 
Stacey5150
Lost but trying
Profile
Posts: 54
Reg: Feb 17, 2013
West Middlesex,...
8,490
like
11/05/13 08:42 AM (10 years ago)
Correction, I meant API 14 for the emulator.
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
11/05/13 09:08 AM (10 years ago)
Glad you got the first problem worked out. Eclipse is strange for sure. For the emulator, it appears that it's timing out during its attempt to load the program. You could try launching the emulator and making sure it's up and running before you try running your app. Or, you could try running it on a real device instead (which is actually preferable). I've also dropped the memory down to 512 and gotten some good results that way. Mark
 
Stacey5150
Lost but trying
Profile
Posts: 54
Reg: Feb 17, 2013
West Middlesex,...
8,490
like
11/05/13 12:17 PM (10 years ago)
Ok, getting closer! instead of using the eclipse emulator, I downloaded and installed the Genymotion virtual device....AWESOME and FAST! My next issue (starting to see the light at the end of the tunnel!). The project loads into the emulator for a second then I get the message: unfortunately, letsgo has stopped! I don't know what is stopping it from loading completely.
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
11/05/13 12:22 PM (10 years ago)
Rock on! Getting so close! Assuming that Genymotion is somehow tied to Eclipse, when you run your project, you should see output in the LogCat window. That's all the debug information for the project, and it should give you a clue on what's going on. If you can paste some LogCat output from the time that it tries to load to when it fails, we can help debug. https://www.buzztouch.com/files/howtos/Problem_Reporting_and_Basic_Debug_v1.0.pdf Mark
 
Stacey5150
Lost but trying
Profile
Posts: 54
Reg: Feb 17, 2013
West Middlesex,...
8,490
like
11/05/13 02:01 PM (10 years ago)
Ok, here is the logCat. Saved your .pdf for future reference. Sorry if I haven't always been clear. I will try to do better! 11-05 20:05:11.738: E/Trace(4232): error opening trace file: No such file or directory (2) 11-05 20:05:11.786: W/ZZ(4232): letsgo_appDelegate: onCreate 11-05 20:05:11.786: W/ZZ(4232): letsgo_appDelegate:loadAudioPlayer 11-05 20:05:11.786: W/ZZ(4232): BT_application: Creating root-app object. 11-05 20:05:11.786: W/ZZ(4232): BT_device: Creating root-device object. 11-05 20:05:11.786: W/ZZ(4232): BT_device: This device uses an Android display density of: 213dpi (dots per inch) 11-05 20:05:11.786: W/ZZ(4232): BT_device: This device cannot take pictures. 11-05 20:05:11.786: W/ZZ(4232): BT_device: This device cannot take videos. 11-05 20:05:11.786: W/ZZ(4232): BT_device: This device can send emails. 11-05 20:05:11.786: W/ZZ(4232): BT_device: This device is GPS capable. 11-05 20:05:11.790: W/ZZ(4232): BT_device: This device does not support vibrating. 11-05 20:05:11.790: W/ZZ(4232): letsgo_appDelegate:SoundEffectLoader:doInBackground initSoundEffects 11-05 20:05:11.794: W/ZZ(4232): BT_device: This device has an accelerometer (it can detect shaking). 11-05 20:05:11.794: W/ZZ(4232): letsgo_appDelegate:SoundEffectLoader:doInBackground initSoundEffects DISABLED 11-05 20:05:11.794: W/ZZ(4232): BT_device: This device can record audio. 11-05 20:05:11.798: W/ZZ(4232): BT_user: Creating root-user object. 11-05 20:05:11.814: W/ZZ(4232): BT_activity_start:onCreate 11-05 20:05:11.814: W/ZZ(4232): BT_activity_start:onCreate This device is running Android Build Vers:16 11-05 20:05:11.822: W/ZZ(4232): BT_activity_start:loadAppConfigData 11-05 20:05:11.822: W/ZZ(4232): BT_fragment_load_config_data:onCreate 11-05 20:05:11.822: W/ZZ(4232): BT_fragment_load_config_data:onCreateView 11-05 20:05:11.822: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigDataAfterDelay: Delaying 2000 milliseconds 11-05 20:05:11.906: D/(4232): HostConnection::get() New Host Connection established 0xb986fc68, tid 4232 11-05 20:05:13.882: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigData 11-05 20:05:13.894: W/ZZ(4232): BT_device:updateDeviceConnectionType: ConnectionType: WIFI 11-05 20:05:13.902: W/ZZ(4232): BT_device:updateDeviceSize This device has a screen size of: 1280 (width) x 736 (height). 11-05 20:05:13.902: W/ZZ(4232): BT_device:updateDeviceSize This application considers this to be a "large device" 11-05 20:05:13.902: W/ZZ(4232): BT_device:updateDeviceSize This device is in "landscape" orientation. 11-05 20:05:13.902: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigData loading "BT_config.txt" from /assests folder in project... 11-05 20:05:14.058: W/ZZ(4232): BT_fileManager: readTextFileFromAssets: "/BT_config.txt" 11-05 20:05:14.062: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigData loaded "BT_config.txt" from /assets folder successfully... 11-05 20:05:14.062: W/ZZ(4232): BT_application: getDataURLFromAppData 11-05 20:05:14.098: D/dalvikvm(4232): GC_CONCURRENT freed 215K, 4% free 7392K/7687K, paused 11ms+0ms, total 17ms 11-05 20:05:14.102: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigData "BT_config.txt" file does use a dataURL for remote updates... 11-05 20:05:14.102: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigData cachedAppConfig.txt does not exist in the cache, using the BT_config.txt file included in project... 11-05 20:05:14.106: W/ZZ(4232): BT_application: validateApplicationData 11-05 20:05:14.130: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigData application data appears to be valid JSON... 11-05 20:05:14.130: W/ZZ(4232): BT_application: parseJSONData 11-05 20:05:14.134: W/ZZ(4232): BT_application: parsing core settings... 11-05 20:05:14.134: W/ZZ(4232): BT_application: parsing themes... 11-05 20:05:14.134: W/ZZ(4232): BT_application: parsing tabs... 11-05 20:05:14.134: W/ZZ(4232): BT_application: parsing menus... 11-05 20:05:14.134: W/ZZ(4232): BT_application: parsing screens... 11-05 20:05:14.134: W/ZZ(4232): BT_application:parseJSONData done parsing application data 11-05 20:05:14.134: W/ZZ(4232): BT_fragment_load_config_data:loadAppConfigData:sendMessageToMainThread 0 11-05 20:05:14.198: W/ZZ(4232): BT_activity_start:configureEnvironment 11-05 20:05:14.198: W/ZZ(4232): BT_activity_start:configureEnvironment This app uses a splash screen with JSON itemId: 4C8760D292A19F1DE74B721 11-05 20:05:14.198: W/ZZ(4232): BT_activity_start:configureEnvironment Starting BT_activity_splash 11-05 20:05:14.198: W/ZZ(4232): BT_application:getScreenDataByItemId itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.198: W/ZZ(4232): BT_application:initPluginWithScreenData. Creating plugin with JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.198: W/ZZ(4232): BT_screen_splash:setScreenData JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.198: W/ZZ(4232): BT_activity_start:showFragmentForSplashScreen 11-05 20:05:14.218: W/ZZ(4232): BT_screen_splash:onAttach JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.218: W/ZZ(4232): BT_screen_splash:onCreate JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.218: W/ZZ(4232): BT_screen_splash:onCreateView JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.218: W/ZZ(4232): BT_viewUtilities:updateBackgroundColorsForScreen. Screen with JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.218: W/ZZ(4232): BT_screen_splash:onActivityCreated JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.218: W/ZZ(4232): BT_screen_splash:onStart JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.218: W/ZZ(4232): BT_screen_splash:onResume JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.218: W/ZZ(4232): BT_viewUtilities:updateBackgroundImageForScreen. Screen with JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:14.230: D/dalvikvm(4232): GC_FOR_ALLOC freed 192K, 5% free 7429K/7751K, paused 6ms, total 7ms 11-05 20:05:14.234: I/dalvikvm-heap(4232): Grow heap (frag case) to 9.672MB for 2457612-byte allocation 11-05 20:05:14.250: D/dalvikvm(4232): GC_FOR_ALLOC freed 6K, 4% free 9822K/10183K, paused 14ms, total 14ms 11-05 20:05:14.262: D/dalvikvm(4232): GC_CONCURRENT freed 0K, 4% free 9822K/10183K, paused 12ms+0ms, total 15ms 11-05 20:05:14.402: D/dalvikvm(4232): GC_FOR_ALLOC freed 33K, 4% free 9788K/10183K, paused 9ms, total 9ms 11-05 20:05:14.426: I/dalvikvm-heap(4232): Grow heap (frag case) to 13.787MB for 4355436-byte allocation 11-05 20:05:14.454: D/dalvikvm(4232): GC_CONCURRENT freed 0K, 3% free 14041K/14471K, paused 12ms+14ms, total 29ms 11-05 20:05:14.518: W/ZZ(4232): BT_screen_splash:startEffect. "fallDown" 11-05 20:05:16.566: W/ZZ(4232): BT_screen_splash:animateSplashScreen 11-05 20:05:16.582: D/dalvikvm(4232): GC_FOR_ALLOC freed 2402K, 20% free 11648K/14471K, paused 2ms, total 3ms 11-05 20:05:16.634: I/dalvikvm-heap(4232): Grow heap (frag case) to 15.042MB for 3768332-byte allocation 11-05 20:05:16.670: D/dalvikvm(4232): GC_CONCURRENT freed 2K, 16% free 15325K/18183K, paused 34ms+0ms, total 37ms 11-05 20:05:16.674: D/dalvikvm(4232): GC_FOR_ALLOC freed 0K, 16% free 15325K/18183K, paused 2ms, total 2ms 11-05 20:05:16.678: I/dalvikvm-heap(4232): Grow heap (frag case) to 18.634MB for 3768332-byte allocation 11-05 20:05:16.722: D/dalvikvm(4232): GC_CONCURRENT freed 0K, 14% free 19005K/21895K, paused 39ms+1ms, total 42ms 11-05 20:05:16.722: D/dalvikvm(4232): WAIT_FOR_CONCURRENT_GC blocked 5ms 11-05 20:05:16.726: D/dalvikvm(4232): GC_FOR_ALLOC freed 0K, 14% free 19005K/21895K, paused 3ms, total 3ms 11-05 20:05:16.730: I/dalvikvm-heap(4232): Grow heap (frag case) to 22.228MB for 3768332-byte allocation 11-05 20:05:16.734: D/dalvikvm(4232): GC_FOR_ALLOC freed 0K, 12% free 22685K/25607K, paused 3ms, total 3ms 11-05 20:05:16.774: D/dalvikvm(4232): GC_CONCURRENT freed 0K, 12% free 22686K/25607K, paused 38ms+0ms, total 41ms 11-05 20:05:17.566: W/ZZ(4232): BT_screen_splash:animationFinished 11-05 20:05:17.606: W/ZZ(4232): BT_screen_splash:onPause JSON itemId: "4C8760D292A19F1DE74B721" itemType: "BT_screen_splash" itemNickname: "Splash Screen" 11-05 20:05:17.610: W/ZZ(4232): BT_activity_host:onCreate 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:configureEnvironment 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:configureEnvironment Prompt For Push Notifications is OFF (set to 0) in app's configuration data 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:configureEnvironment start GPS is set to NO (set to 0) in the applications configuration data, not starting GPS 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:setupTabs (0 tabs) 11-05 20:05:17.618: W/ZZ(4232): BT_application: getHomeScreenData 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:setupTabs (no tabs, finding home screen) 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:showAppHomeScreen 11-05 20:05:17.618: W/ZZ(4232): BT_application: getHomeScreenData 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:initPluginWithScreenData. Calling helper method in BT_application 11-05 20:05:17.618: W/ZZ(4232): BT_application:initPluginWithScreenData. Creating plugin with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.618: W/ZZ(4232): WB_screen_menuImage:setScreenData JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:showFragmentForPlugin. Showing plugin with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.618: W/ZZ(4232): BT_activity_host:configureNavBarAndBackgroundForScreen Calling helper methods in BT_viewUtilities... 11-05 20:05:17.626: W/ZZ(4232): BT_viewUtilities:updateBackgroundColorsForScreen. Screen with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.626: W/ZZ(4232): BT_viewUtilities:updateBackgroundImageForScreen. Screen with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.626: W/ZZ(4232): BT_activity_host:configureNavBarAndBackgroundForScreen Calling helper methods in BT_viewUtilities... 11-05 20:05:17.630: W/ZZ(4232): BT_viewUtilities:updateBackgroundColorsForScreen. Screen with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.630: W/ZZ(4232): BT_viewUtilities:updateBackgroundImageForScreen. Screen with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.630: W/ZZ(4232): BT_activity_host:configureNavBarAndBackgroundForScreen Calling helper methods in BT_viewUtilities... 11-05 20:05:17.634: W/ZZ(4232): BT_viewUtilities:updateBackgroundColorsForScreen. Screen with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.634: W/ZZ(4232): BT_viewUtilities:updateBackgroundImageForScreen. Screen with JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.634: W/ZZ(4232): WB_screen_menuImage:onAttach JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.634: W/ZZ(4232): WB_screen_menuImage:onCreate JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.634: W/ZZ(4232): WB_screen_menuImage:onCreateView JSON itemId: "C983707E0F5ADDEAA9F7D33" itemType: "WB_screen_menuImage" itemNickname: "menu" 11-05 20:05:17.638: W/ZZ(4232): BT_fileManager:deleteFile C983707E0F5ADDEAA9F7D33_screenData.txt 11-05 20:05:17.638: W/ZZ(4232): BT_viewUtilities:convertToPixels 11-05 20:05:17.638: W/ZZ(4232): BT_viewUtilities:convertToPixels 11-05 20:05:17.638: W/ZZ(4232): BT_viewUtilities:convertToPixels 11-05 20:05:17.638: D/AndroidRuntime(4232): Shutting down VM 11-05 20:05:17.638: W/dalvikvm(4232): threadid=1: thread exiting with uncaught exception (group=0xa62de288) 11-05 20:05:17.642: E/AndroidRuntime(4232): FATAL EXCEPTION: main 11-05 20:05:17.642: E/AndroidRuntime(4232): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.letsgo/com.letsgo.BT_activity_host}: java.lang.IllegalArgumentException: Unknown color 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2059) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2084) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.ActivityThread.access$600(ActivityThread.java:130) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1195) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.os.Handler.dispatchMessage(Handler.java:99) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.os.Looper.loop(Looper.java:137) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.ActivityThread.main(ActivityThread.java:4745) 11-05 20:05:17.642: E/AndroidRuntime(4232): at java.lang.reflect.Method.invokeNative(Native Method) 11-05 20:05:17.642: E/AndroidRuntime(4232): at java.lang.reflect.Method.invoke(Method.java:511) 11-05 20:05:17.642: E/AndroidRuntime(4232): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786) 11-05 20:05:17.642: E/AndroidRuntime(4232): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) 11-05 20:05:17.642: E/AndroidRuntime(4232): at dalvik.system.NativeStart.main(Native Method) 11-05 20:05:17.642: E/AndroidRuntime(4232): Caused by: java.lang.IllegalArgumentException: Unknown color 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.graphics.Color.parseColor(Color.java:222) 11-05 20:05:17.642: E/AndroidRuntime(4232): at com.letsgo.BT_color.getColorFromHexString(BT_color.java:46) 11-05 20:05:17.642: E/AndroidRuntime(4232): at com.letsgo.WB_screen_menuImage.onCreateView(WB_screen_menuImage.java:174) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:829) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1035) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.BackStackRecord.run(BackStackRecord.java:635) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1397) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.Activity.performStart(Activity.java:5017) 11-05 20:05:17.642: E/AndroidRuntime(4232): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2032) 11-05 20:05:17.642: E/AndroidRuntime(4232): ... 11 more
 
GoNorthWest
buzztouch Evangelist
Profile
Posts: 8197
Reg: Jun 24, 2011
Oro Valley, AZ
1,000,000
like
11/05/13 02:05 PM (10 years ago)
This line sometimes means you've specified an incorrect color somewhere in your control panel: java.lang.IllegalArgumentException: Unknown color 11-05 20:05:17.642: E/AndroidRuntime(4232): at If you've used hex to specify the color, you might have forgotten a digit. Another potential problem we've seen lately is solved by taking all the images you have in res > drawable, and copying them into the other res > drawable folders. Mark
 
Stacey5150
Lost but trying
Profile
Posts: 54
Reg: Feb 17, 2013
West Middlesex,...
8,490
like
11/05/13 02:55 PM (10 years ago)
Thanks Mark! I will check it out. Fingers crossed!
 

Login + Screen Name Required to Post

pointerLogin to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.