I have a schedule which I created with nothing fancy html. I have it in a custom html screen and the issue I am having is it has links in different places? you can see the screen right here: http://www.buzztouch.com/applications012012/EAF35B2049348D3487A37EA36/customHTML-8D21F938C00DB21872BC563.html But in my Droid-X and emulators it has about 5 links when clicked they go no where and the the spinner just hangs..... any ideas? Thanks

Not sure. The HTML output in the screenshot looks nice but there isn't anyway to know exactly what Android is trying to load when you tap one of the HTML links. Have a look at the BT_screen_webView.java file and find the method named shouldOverrideUrlLoading on about line 128. Use the console to track down what's happening? Not sure what could be happening but Android is picky about allowing or not allowing the page to load and this is all controlled in this shouldOverrideUrlLoading method.

LOL I know why it is called Buzztouch, more bugs than beetle juice. this I say is the problem what it means who knows: 02-17 08:14:23.926: I/TelephonyRegistry(1318): notifyDataConnection: state=1 isDataConnectivityPossible=true reason=null interfaceName=null networkType=6 02-17 08:14:23.989: W/ConnectivityService(1318): DISCONNECT for unknown interface null 02-17 08:14:24.059: E/NetStatUtils(14372): The report APN is not in local map, un-match case, fatal error!! here is log from beginning of issue: 02-17 08:12:33.911: I/ActivityManager(1318): Displayed com.idragracenews/.BT_screen_customHTML: +1s680ms 02-17 08:12:35.223: W/ZZ(14665): BT_screen_customHTML:onPageFinished finished Loading: http://www.buzztouch.com/applications012012/EAF35B2049348D3487A37EA36/customHTML-8D21F938C00DB21872BC563.html 02-17 08:12:48.661: W/ZZ(14665): BT_act_controller:canLoadDocumentInWebView geo:0,0?q=27-29 02-17 08:12:48.661: W/ZZ(14665): 02-17 08:12:48.661: W/ZZ(14665): 02-17 08:12:48.661: W/ZZ(14665): 02-17 08:12:48.661: W/ZZ(14665): O'Reilly Auto Parts NHRA Spring Nationals 02-17 08:12:48.661: W/ZZ(14665): Houston%2C TX 02-17 08:14:23.887: I/TelephonyRegistry(1318): notifyDataConnection: state=0 isDataConnectivityPossible=false reason=null interfaceName=null networkType=6 02-17 08:14:23.926: I/TelephonyRegistry(1318): notifyDataConnection: state=1 isDataConnectivityPossible=true reason=null interfaceName=null networkType=6 02-17 08:14:23.989: W/ConnectivityService(1318): DISCONNECT for unknown interface null 02-17 08:14:24.059: E/NetStatUtils(14372): The report APN is not in local map, un-match case, fatal error!! 02-17 08:14:24.059: E/NetStatUtils(14372): The report APN is not in local map, un-match case, fatal error!!

What is the URL you are trying to load when you tap the link? Maybe a map (guessing here). I don't see any links in the page when I load it in Safari. 'more bugs than bettle juice' If you're referring to BT having bugs you're not understanding the idea. This is not a bug, it's an issue of how Android's built in browser, the one developers (like you and us) can program. It's not the same as the Android built in browser application. The built in browser application is an actual full blown application, not just a way to display HTML. The built in browser that you're dealing with here is totally different and very complicated. It's purpose is to allow developers to have total control over what's happening (or not happening) when HTTP requests are made for internet data. Images, documents, maps, style sheets, everything in the HTML file is a seperate request and as such requires special handling sometimes. The build in browser widget that you can program with changes it's behavior based on lots and lots of factors. Example: Most folks don't realize that it makes many many requests to load 'one page' (images, style sheets, links tapped, forms submitted, etc). In each case, for each request, it runs the shouldOverrideUrlLoading method to determine if it should load. It looks to me like it's having trouble understanding what you're trying to load when you click a link. There isn't anyway for us to cover all the possible scenarios using the built in browser. The idea is that each canned screen type is a place to get started. Many times these canned screens are 'good enough' and work well for the situation. In many other cases the source code needs to be adjusted to solve the problem. In this case, I think it's a matter of seeing what Android is trying to load when the link is tapped, loading that page in a regular browser then seeing why the built in browser 'doesn't like it'

Well then, it ended up being the buggy browser, it does not like dashes and a certain amount of numbers in a table row. What is tries to do is call a number with the phone. Example went from Jul 2-4 to Jul 2,3,4 Thanks for the help.