Android BT 1.5 In the HTML doc I have <img src=mycoolimage.png/> and the image are in the BT_images folder but only placehoulder are visable. However, placing the image in BT_Docs result in the image visable in the screen/HTML doc. But thats wrong is´t?

Hi @Lars1, Yeah, that's not the way it's supposed to work. Any image you reference in your local HTML file should go into BT_Images folder. When you put the image there, did you add it to your Xcode/Eclipse project? You need to do that as well. Here's a doc that explains how : http://www.buzztouch.com/resources/Adding_Files_To_A_Project_v1.0.pdf I may have to check out the way you got it to work...seems like a bug (or a feature, depending on how you look at it!). Mark

Yes, I added it to the Eclipse project. The same way both to BT_docs and BT_images. Also tried with one imagefile already in the BT_images folder, it didn´t work either.

HTML images go in the Docs file. Read the Buzztouch Method to understand. http://wp.me/p1ZRa7-4O Fred

Well, that's weird! As long as there are no spaces or special characters in the image filename, and I think it has to be all lowercase for Android, then it should work. If you've met those requirements, could you remove the image from your BT_Docs folder, keep it in the BT_Images folder, and show us the console output from when you load that page? That way we can see why it's not showing the image. Here's a doc on debugging in case you need it : http://www.buzztouch.com/resources/Problem_Reporting_and_Basic_Debug_v1.0.pdf Mark

@Fred is probably correct. I haven't done an Android app with HTML yet, so I'm not entirely sure! Mark

I'm just doing it the Buzztouch way, figured I didn't need to reinvent the wheel. Fred

Sorry GoNorthWest. What do You mean with console output?? I guess it´s in Eclipse but where?

This doc shows you how to provide debug info for both Eclipse and Xcode : http://www.buzztouch.com/resources/Problem_Reporting_and_Basic_Debug_v1.0.pdf Mark

Don't say much to me. In console [2012-02-03 21:27:13 - bohus1] Android Launch! [2012-02-03 21:27:13 - bohus1] adb is running normally. [2012-02-03 21:27:13 - bohus1] Performing com.bohuskust.BT_activity_root activity launch [2012-02-03 21:27:17 - bohus1] Uploading bohus1.apk onto device 'S583068f348bf' [2012-02-03 21:27:21 - bohus1] Installing bohus1.apk... [2012-02-03 21:27:29 - bohus1] Success! [2012-02-03 21:27:29 - bohus1] Starting activity com.bohuskust.BT_activity_root on device S583068f348bf [2012-02-03 21:27:30 - bohus1] ActivityManager: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.bohuskust/.BT_activity_root } Log cat 02-03 21:35:56.109: D/BatteryService(160): update start 02-03 21:35:56.129: D/BatteryService(160): update start 02-03 21:35:59.889: D/StatusBarPolicy(208): updateSignalStrength: numeric=24008, curOperator=SWEDEN 02-03 21:36:01.769: W/PowerManagerService(160): Timer 0x3->0x1|0x0 02-03 21:36:01.769: I/PowerManagerService(160): Ulight 3->1|0 02-03 21:36:01.889: D/StatusBarPolicy(208): updateSignalStrength: numeric=24008, curOperator=SWEDEN 02-03 21:36:02.099: I/PowerManagerService(160): Light Animator Finished curIntValue=20 02-03 21:36:02.889: D/StatusBarPolicy(208): updateSignalStrength: numeric=24008, curOperator=SWEDEN 02-03 21:36:03.889: D/StatusBarPolicy(208): updateSignalStrength: numeric=24008, curOperator=SWEDEN 02-03 21:36:05.889: D/StatusBarPolicy(208): updateSignalStrength: numeric=24008, curOperator=SWEDEN 02-03 21:36:06.129: D/BatteryService(160): update start 02-03 21:36:06.139: D/BatteryService(160): update start 02-03 21:36:06.149: D/BatteryService(160): update start 02-03 21:36:06.889: D/StatusBarPolicy(208): updateSignalStrength: numeric=24008, curOperator=SWEDEN 02-03 21:36:08.779: W/PowerManagerService(160): Timer 0x1->0x0|0x0 02-03 21:36:08.779: I/PowerManagerService(160): Ulight 1->0|0 02-03 21:36:08.799: E/power(160): *** set_screen_state 0 02-03 21:36:08.799: I/PowerManagerService(160): Light Animator Finished curIntValue=0 02-03 21:36:08.799: W/PowerManagerService(160): CurLockF mPS:0 mUS=0 02-03 21:36:08.799: W/PowerManagerService(160): mPokeLocks.size=0: 02-03 21:36:08.809: D/KeyguardViewMediator(160): onScreenTurnedOff(3) 02-03 21:36:08.809: D/KeyguardViewMediator(160): setting alarm to turn off keyguard, seq = 205 02-03 21:36:08.809: I/OrientationDebug(160): [pwm] in updateOrientationListenerLp() 02-03 21:36:08.809: V/OrientationDebug(160): in updateOrientationListenerLp(), Screen status=false, current orientation=-1, SensorEnabled=true 02-03 21:36:08.809: I/OrientationDebug(160): [pwm] in updateOrientationListenerLp(), now call mOrientationListener.disable(), and mOrientationSensorEnabled = false #2 02-03 21:36:08.809: I/OrientationDebug(160): [WindowOrientationListener] in disable(), now call SensorManager.unregisterListener() 02-03 21:36:08.809: E/SensorManager(160): unregisterListener:: all sensors, listener = android.view.WindowOrientationListener$SensorEventListenerImpl@40b269c0 02-03 21:36:08.809: E/SensorHAL(160): +__poll_activate: handle=0 enabled=0 02-03 21:36:08.809: E/SensorHAL(160): > Accelerometer Write /sys/class/input/input3/enable 0

So, everything in your LogCat output looks like normal startup stuff. Do you have a snippet from when you launch the HTML page, so we can see what's going on? Mark

02-03 22:40:14.849: W/ZZ(12304): BT_screen_webView:onBackPressed 02-03 22:40:14.849: W/ZZ(12304): BT_screen_webView:REVERSING TRANSITIONS ARE DISABLED 02-03 22:40:14.879: W/ZZ(12304): BT_screen_menuList: start GPS is set to NO in the applications configuration data, not starting GPS 02-03 22:40:16.149: W/ZZ(12304): BT_screen_menuList:handleItemTap loads screen with itemId: 8FDE46BF3E10B4C55FFABB7 02-03 22:40:16.149: W/ZZ(12304): BT_application:getScreenDataByItemId 8FDE46BF3E10B4C55FFABB7 02-03 22:40:16.149: W/ZZ(12304): BT_application:getScreenDataByItemId screenType is BT_screen_webView for screen with nickname: paternoster 02-03 22:40:16.149: W/ZZ(12304): BT_act_controller:loadScreenObject for screen with nickname paternoster and type BT_screen_webView 02-03 22:40:16.149: W/ZZ(12304): BT_act_controller:canLoadDocumentInWebView paternoster.html 02-03 22:40:16.229: W/ZZ(12304): BT_screen_webView:onCreate 02-03 22:40:16.249: W/ZZ(12304): BT_viewUtilities:updateBackgroundColorsForScreen with nickname: paternoster 02-03 22:40:16.249: W/ZZ(12304): BT_viewUtilities:updateBackgroundColorsForScreen: setting background color to: #FFFFFF 02-03 22:40:16.249: W/ZZ(12304): BT_viewUtilities:getNavBarForScreen building nav. bar for screen with nickname: paternoster 02-03 22:40:16.249: W/ZZ(12304): BT_viewUtilities:getNavBarForScreen: setting nav-bar color to: #003399 02-03 22:40:16.259: W/ZZ(12304): BT_screen_webView:backgroundWorkerThread this screen does not use a background image 02-03 22:40:16.269: I/webclipboard(12304): clipservice: android.sec.clipboard.ClipboardExManager@40550050 02-03 22:40:16.279: W/ZZ(12304): BT_fileManager:canCacheDocument paternoster.html 02-03 22:40:16.319: W/ZZ(12304): BT_act_controller:canLoadDocumentInWebView paternoster.html 02-03 22:40:16.319: W/ZZ(12304): BT_screen_webView: loading file from /assets/BT_Docs/paternoster.html 02-03 22:40:16.319: W/ZZ(12304): BT_screen_webView: loadUrl 02-03 22:40:16.319: W/ZZ(12304): BT_screen_webView: start GPS is set to NO in the applications configuration data, not starting GPS 02-03 22:40:16.379: V/webview(12304): OnSizeChanged: Enter 02-03 22:40:16.509: W/ZZ(12304): BT_screen_webView:onPageFinished finished Loading: file:///android_asset/BT_Docs/paternoster.html 02-03 22:40:16.569: V/webview(12304): ZoomScale 3 mPreserveZoom: false

I don't understand why you're trying to fix what's not broken. Fred http://www.buzztouch.com/forum/thread.php?tid=2B9261D871A331586D6F4EF&status=&searchInput=Html&sortColumn=FT.dateStampUTC&sortUpDown=DESC¤tPage=1&doViews=1

Straight from the Readme: /assets/BT_Docs - for documents, javascript and style sheets. Also, any images you use in HTML you include in your project must be in the BT_Docs folder Feels like a Monday...been a super long week. Images go in BT_Docs, and then things will work as expected. Mark