Got completely lost so have gone right back to the start and following GoNorth West's guide I have installed JDK Then installed the Android SDK but my install screen looks nothing like the guide I only have Tools - Android SDK Tools & Platform Tools & nothing below as in the screen shot on the guide Can't find that I've done anything wrong up to this point Any ideas anyone?

Hey Chris, I just finished watching the Oxford Buzztouch meetup videos, and saw your intro! I feel like I know you now! That guide is just a bit dated. I've done some videos that show how to install things on multiple platforms. You can find them here: https://www.youtube.com/user/GoNorthWest/videos The best approach these days is to download and install the Eclipse ADT bundle. That's what the videos are based on. Let me know if you run into any problems! Mark

Thanks I will have a look

I installed the bundle, but I think we still need to create a virtual device and also install some package (2.2?) in the Android SDK manager. I tried to follow https://www.buzztouch.com/files/howtos/Setting_Up_Your_Android_Development_Environment_v1.3.pdf but it does not have up to date URL's and doesn't reference the new integrated IDE+SDK bundle, so I am trying to figure out what still to do. Maybe this pdf should be removed from the how-tos if the video above is more up to date? -Peter

Hi Peter, I'll be working on a new document over the holidays. In the meantime, the videos should get you going. It's only two download locations you need to worry about - Java and the Eclipse ADT bundle. Everything else is contained in the software itself. Let me know if you're still stuck! Mark

Ok I will get back at it. Had some errors already but maybe it's because the SDK wasn't installed/activated. I'll review your videos. Thanks!

Hi Mark - your video really helped and I feel I now have the Eclipse bundle correctly installed. I added the Android 2.2 Api (8) and made a tiny app (with just a splash screen) to see if I can move forward, but am still getting some errors so can't even run the app. The device manager works ok and I got Android running on the emulator. I think there is a step missing somewhere as I don't see why such a basic app with just 1 homescreen w/ menu to splashscreen should give these errors from BT_item.java Description Resource Path Location Type GeoPoint cannot be resolved to a type BT_item.java /tester123/src/com/tester123 line 54 Java Problem Description Resource Path Location Type The import com.google.android.maps cannot be resolved BT_item.java /tester123/src/com/tester123 line 37 Java Problem Is there a demo app somewhere I can try, in case I made my own test app incorrectly?

Pls disregard my last post - I discovered that I had the wrong API setting in properties for the App in eclipse. This is explained in the video Mark did here, at about the 7min mark: https://www.youtube.com/watch?v=NV3Ofi2602I No errors now but I hope to make lots more.. it means progress :) -Peter

No errors & can launch & got an icon on the emulator screen but it crashes when I open :(

Hi Chris, Are you saying that your app crashes when it launches in the emulator? If it does, there should be some output in the LogCat tab. Can you paste that output here? Give us lines before and after the crash. Thanks! Mark

I presume it's the stuff highlighted in red So here goes: 11-28 19:07:01.770: E/AndroidRuntime(599): FATAL EXCEPTION: main 11-28 19:07:01.770: E/AndroidRuntime(599): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.stafford/com.stafford.WB_screen_menuImage}: java.lang.ClassCastException: android.widget.ImageView 11-28 19:07:01.770: E/AndroidRuntime(599): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2663) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.app.ActivityThread.access$2300(ActivityThread.java:125) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.os.Handler.dispatchMessage(Handler.java:99) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.os.Looper.loop(Looper.java:123) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.app.ActivityThread.main(ActivityThread.java:4627) 11-28 19:07:01.770: E/AndroidRuntime(599): at java.lang.reflect.Method.invokeNative(Native Method) 11-28 19:07:01.770: E/AndroidRuntime(599): at java.lang.reflect.Method.invoke(Method.java:521) 11-28 19:07:01.770: E/AndroidRuntime(599): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868) 11-28 19:07:01.770: E/AndroidRuntime(599): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626) 11-28 19:07:01.770: E/AndroidRuntime(599): at dalvik.system.NativeStart.main(Native Method) 11-28 19:07:01.770: E/AndroidRuntime(599): Caused by: java.lang.ClassCastException: android.widget.ImageView 11-28 19:07:01.770: E/AndroidRuntime(599): at com.stafford.WB_screen_menuImage.onCreate(WB_screen_menuImage.java:207) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047) 11-28 19:07:01.770: E/AndroidRuntime(599): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2627) 11-28 19:07:01.770: E/AndroidRuntime(599): ... 11 more

I think this has got me beat Get an empty screen with no icons on now in the emulator

That's the crash for sure. Can you send me any lines before and after that look like they have to do with Buzztouch?

Ok I will have a look later as I am archiving in Xcode at the moment ready for my first attempt at a submission!

Sounds good. You can also save the log and send the whole thing to me if you'd like. Just send it to MrkFleming at gmail dot com. Mark

11-29 19:14:49.053: W/ZZ(304): stafford_appDelegate: onCreate 11-29 19:14:49.053: W/ZZ(304): stafford_appDelegate:loadAudioPlayer 11-29 19:14:49.063: W/ZZ(304): BT_application: Creating root-app object. 11-29 19:14:49.063: W/ZZ(304): BT_device: Creating root-device object. 11-29 19:14:49.073: W/ZZ(304): BT_device: This device uses an Android display density of: 213dpi (dots per inch) 11-29 19:14:49.073: W/ZZ(304): BT_device: This device can take pictures. 11-29 19:14:49.073: W/ZZ(304): BT_device: This device can take videos. 11-29 19:14:49.083: W/ZZ(304): BT_device: This device can send emails. 11-29 19:14:49.083: W/ZZ(304): BT_device: This device is GPS capable. 11-29 19:14:49.083: W/ZZ(304): BT_user: Creating root-user object. 11-29 19:14:49.133: W/ZZ(304): BT_activity_root:onCreate 11-29 19:14:49.211: W/ZZ(304): BT_activity_root:loadAppData 11-29 19:14:49.293: W/ZZ(304): BT_device:updateDeviceConnectionType: ConnectionType: CELL 11-29 19:14:49.293: W/ZZ(304): BT_device:updateDeviceSize This device has a screen size of: 800 (width) x 1280 (height). 11-29 19:14:49.293: W/ZZ(304): BT_device:updateDeviceSize This application considers this to be a "large device" 11-29 19:14:49.293: W/ZZ(304): BT_device:updateDeviceSize This device is in "portrait" orientation. 11-29 19:14:49.303: W/ZZ(304): BT_activity_root:loadAppData loading BT_config.txt from /assests folder in Eclipse project... 11-29 19:14:49.782: W/ZZ(304): BT_fileManager: readTextFileFromAssets: "/BT_config.txt" 11-29 19:14:49.943: D/dalvikvm(304): GC_FOR_MALLOC freed 1830 objects / 263816 bytes in 75ms 11-29 19:14:50.133: W/ZZ(304): BT_activity_root:loadAppData loaded BT_config.txt from /assets folder successfully... 11-29 19:14:50.133: W/ZZ(304): BT_application: getDataURLFromAppData 11-29 19:14:50.533: W/ZZ(304): BT_activity_root:loadAppData BT_config.txt file does use a dataURL for remote updates... 11-29 19:14:50.543: W/ZZ(304): BT_activity_root:loadAppData cachedAppConfig.txt does not exist in the cache... 11-29 19:14:50.543: W/ZZ(304): BT_application: validateApplicationData 11-29 19:14:50.672: D/dalvikvm(304): GC_FOR_MALLOC freed 9627 objects / 647704 bytes in 56ms 11-29 19:14:50.762: W/ZZ(304): BT_activity_root: application data appears to be valid JSON... 11-29 19:14:50.762: W/ZZ(304): BT_application: parseJSONData 11-29 19:14:50.913: W/ZZ(304): BT_application: parsing core settings... 11-29 19:14:50.913: W/ZZ(304): BT_application: parsing themes... 11-29 19:14:50.913: W/ZZ(304): BT_application: parsing tabs... 11-29 19:14:50.913: W/ZZ(304): BT_application: parsing screens... 11-29 19:14:50.923: W/ZZ(304): BT_application:parseJSONData done parsing application data 11-29 19:14:50.923: W/ZZ(304): BT_activity_root:transitionToAppHomeScreen 11-29 19:14:50.923: W/ZZ(304): BT_activity_root:transitionToAppHomeScreen non-tabbed home screen. 11-29 19:14:50.923: W/ZZ(304): BT_application: getHomeScreen 11-29 19:14:51.003: W/ZZ(304): BT_activity_base:onCreate (BASE CLASS) 11-29 19:14:51.223: W/ZZ(304): WB_screen_menuImage:onCreate 11-29 19:14:51.223: W/ZZ(304): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects 11-29 19:14:51.223: W/ZZ(304): stafford_appDelegate:SoundEffectLoader:doInBackground initSoundEffects DISABLED 11-29 19:14:51.223: W/ZZ(304): BT_viewUtilities:updateBackgroundColorsForScreen with nickname: "Main Menu" 11-29 19:14:51.223: W/ZZ(304): BT_viewUtilities:updateBackgroundColorsForScreen: setting background color to: "#002a5c" 11-29 19:14:51.233: W/ZZ(304): BT_viewUtilities:getNavBarForScreen building nav. bar for screen with nickname: "Main Menu" 11-29 19:14:51.233: W/ZZ(304): WB_screen_menuImage:backgroundWorkerThread this screen does not use a background image 11-29 19:14:51.253: W/ZZ(304): BT_fileManager:deleteFile 990BB9FCC12795F1896A39B_screenData.txt 11-29 19:14:51.263: D/AndroidRuntime(304): Shutting down VM 11-29 19:14:51.273: W/dalvikvm(304): threadid=1: thread exiting with uncaught exception (group=0x4001d800) 11-29 19:14:51.303: E/AndroidRuntime(304): FATAL EXCEPTION: main 11-29 19:14:51.303: E/AndroidRuntime(304): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.stafford/com.stafford.WB_screen_menuImage}: java.lang.ClassCastException: android.widget.ImageView 11-29 19:14:51.303: E/AndroidRuntime(304): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2663) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.app.ActivityThread.access$2300(ActivityThread.java:125) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.os.Handler.dispatchMessage(Handler.java:99) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.os.Looper.loop(Looper.java:123) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.app.ActivityThread.main(ActivityThread.java:4627) 11-29 19:14:51.303: E/AndroidRuntime(304): at java.lang.reflect.Method.invokeNative(Native Method) 11-29 19:14:51.303: E/AndroidRuntime(304): at java.lang.reflect.Method.invoke(Method.java:521) 11-29 19:14:51.303: E/AndroidRuntime(304): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868) 11-29 19:14:51.303: E/AndroidRuntime(304): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626) 11-29 19:14:51.303: E/AndroidRuntime(304): at dalvik.system.NativeStart.main(Native Method) 11-29 19:14:51.303: E/AndroidRuntime(304): Caused by: java.lang.ClassCastException: android.widget.ImageView 11-29 19:14:51.303: E/AndroidRuntime(304): at com.stafford.WB_screen_menuImage.onCreate(WB_screen_menuImage.java:207) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047) 11-29 19:14:51.303: E/AndroidRuntime(304): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2627) 11-29 19:14:51.303: E/AndroidRuntime(304): ... 11 more

Hi Chris, Thanks for the data. Unfortunately, it's still not 100% obvious what's going on. I have seen issues in the past where putting your images that go into res > drawable into all the res > drawable folders (there's like 4) stops things from crashing. Give that a shot and let me know what happens. Make sure you follow the a_9a_z naming convention, which means no special characters, caps, or spaces. Mark

Sorry not with you there not sure what you mean

re "Make sure you follow the a_9a_z naming convention, which means no special characters, caps, or spaces. " he means the file names for images can't have certain characters. e.g. I had "pic_1.jpg" and had to change it to pic1.jpg. Also images need to go into the res/drawable folder and not the assets/BT_Docs folder.

Yeah, I did a super bad job explaining that...sorry! @pdog is exactly right with respect to the naming of your files. Android doesn't like it when they're not named according to the "rules." With respect to the res > drawable folders, those are where any images that are not associated with HTML files go...like icons and images for menu screens. You'll see those folders as subfolders of the main res folder. The difference in the folders depends on the difference in the screen size of the device the app is running on. Most people just put images in the res > drawable folder, but they appear to need to go into the other drawable folders as well. Does that make a bit more sense? Keep the questions coming! Mark

I think I have found some problems with image names which is where I will start. But first a question - if I change image names in my buzztouch control panel will I have to re compile my app which is published on itunes?