Skip to main content

Which Android tablets are usable for testing Javascript heavy web applications


I need to develop a client heavy web application that works on Android tablets. It must work with the default browser and maybe as PhoneGap application. So I need a tablet for testing.



Previously I have had really bad experiences with Android browsers . My HTC Desire Z does not show JavaScript exceptions in Android LogCat. If an exception occurs it just dies silently and there is no way to tell what raised the exception.



So what Android tablets are known to show the exceptions? Stack traces would be awesome, but my hopes are not very high.



I know that console.log messages can be read using weinre or jsconsole , but those alone does not help with the exceptions.



In short I just want someone to confirm that you can see messages about uncaught Javascript exeptions of the default browser in device X.


Source: Tips4allCCNA FINAL EXAM

Comments

  1. Ok I can now confirm this on two devices. Asus Transformer TF101 (Andoid 3.2.1) and Samsung Galaxy Tab 10" P7500XXKG7 (Android 3.1) does log Javascript expections in adb logcat!

    The log entry is following

    E/browser ( 1245): Console: Uncaught Error: mn virhe http://jsbin.com/ihirut:23


    Great!

    But when it comes to being usable for Javascript heavy web apps these both tablets suck a big time! Both seem to have a huge performance regression in HTML5 Canvas drawing performance. My phone, HTC Desire Z, which has a much slower processor and has an older version of webkit in the browser is much faster than these tablets!

    It appears that Google or the manufacturers has screwed up with the hardware accecelaration. More information here:

    http://code.google.com/p/android/issues/detail?id=17458

    http://forum.xda-developers.com/showthread.php?t=1213087

    You can workaround this issue by using Phonegap which does not currently enable the hardware accecelaration.

    ReplyDelete
  2. If I understood your question right, your searching for a tablet which has those exceptions in it.
    I know this of a friend of my which has the same problem on some heavy javascript sits.
    Hes using the Acer Iconia A500.

    I hope it was that what you searched. For debuging i refer to this post:
    Hidden Debuging Tool Android Browser

    Have a nice day

    safari

    ReplyDelete
  3. The Opera Browser said that it has cross-device debug, Maybe it's suitable for you to debug.

    Opera Dragonfly 1.1Opera Dragonfly

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex