03-28-2011 04:10 PM
48 12
tools
  1. Dunbar's Avatar
    What started out as a minor annoyance has now morphed into a major problem. Having to go through the about:debug process every time the browser closes is a major annoyance. Especially since the stock browser crashes on a fairly frequent basis. Even with about:debug bookmarked, it is still an eight touch process.

    I don't know how they could have released the xoom without fixing this, much less not patched it on the latest update. Do we have any idea when a fix is going to be implimented?
    03-26-2011 08:33 AM
  2. tntdroid's Avatar
    May never change. Remember its a mobile device and will have a mobile browser. The about debug can be done on a phone to so it will have a full browser. I'd like a permanent option to keep it a full browser on the xoom. Just not sure if that's what they plan on doing.

    Sent from my DROIDX using Tapatalk
    03-26-2011 08:42 AM
  3. kennycrudup's Avatar
    ?! ... have you yet found a site that doesn't have a "Full Version" link? Once you do that 90% of the time they set a cookie so you don't have to do that any longer.

    Far less annoying than having to set your UserAgent a couple of times a day.
    bworley50 likes this.
    03-26-2011 08:59 AM
  4. jcstarr's Avatar
    I have had very few problems with mobile sites popping up. I've only had to do the about:debug once. As far as the browser crashing, I've only had it happen once... *knocks on wood*
    03-26-2011 09:23 AM
  5. 2CupsWithString's Avatar
    What started out as a minor annoyance has now morphed into a major problem. Having to go through the about:debug process every time the browser closes is a major annoyance. Especially since the stock browser crashes on a fairly frequent basis. Even with about:debug bookmarked, it is still an eight touch process.

    I don't know how they could have released the xoom without fixing this, much less not patched it on the latest update. Do we have any idea when a fix is going to be implimented?
    Have you tried Dolphin HD? You can set your user agent during install and it stays like that.
    03-26-2011 09:28 AM
  6. Holsum's Avatar
    What started out as a minor annoyance has now morphed into a major problem. Having to go through the about:debug process every time the browser closes is a major annoyance. Especially since the stock browser crashes on a fairly frequent basis. Even with about:debug bookmarked, it is still an eight touch process.

    I don't know how they could have released the xoom without fixing this, much less not patched it on the latest update. Do we have any idea when a fix is going to be implimented?
    why are you having to change this sovoften. I browse for hours without issues. i use stock and ipad uastring. And It isn't a bug. Please refrain from using that terminalogy when addressing this issue which is lack of user knowledge. The zoom requires different dimensions from other browsers/devices. Because of this websites aren't optimized to recogognize the difference android mobile and android tablet. Hence why all websites come up as mobile. Until web developers start designing their CSS to adjust to the different platforms, like they did with iPhone and Ipad you are going to experience this. Your best bet is to set it to Ipad for now. Flash will load where html5 doesn't.
    03-26-2011 10:26 AM
  7. Drew2u's Avatar
    ?! ... have you yet found a site that doesn't have a "Full Version" link? Once you do that 90% of the time they set a cookie so you don't have to do that any longer.

    Far less annoying than having to set your UserAgent a couple of times a day.
    mobile.Newsday.com ... no link to the full site.

    mobile.engadget.com ... has a link to desktop mode, but... if you were referred to a specific article at mobile.engadget.com, from Twitter for example, when you click the "desktop" link it takes you to the engadget home page - not the current article you are browsing.

    That being said, I've decided I'd rather have the browser default to mobile mode simply because if I'm using 3G, it conserves bandwidth, loads faster and takes up less of my limited monthly data quota.

    However, what I do want is the ability to quickly switch one tab (or window) to desktop mode while keeping everything else in mobile, plus the ability to set a desktop or mobile mode with the bookmark. This would let me choose
    which sites to open in mobile mode and which in desktop mode.
    03-26-2011 10:39 AM
  8. Rigelian's Avatar
    I believe that this problem exists because website developers don't distinguish between the Android user string and the Android Mobile user string. The easy solution to this problem would be for the website developers to modify their code to make this distinction and default Android to the desktop version of the site. This is what is done to distinguish ipad from iphone.

    The other option would be to have the browser simply report itself as a desktop browser. The problem with this approach is that it reduces the incentive of website developers from developing code that can take advantage of functionality that might be in desktop Android browsers. I suggest that Honeycomb users send the website and persuasive email complaining that their site does not properly recognize the Android browser for Honeycomb. Or, at the very least, that they provide some mechanism to permanently recognize that you want to use the desktop version of their site when you visit there.

    Sent from my Xoom using Tapatalk
    03-26-2011 10:44 AM
  9. Dunbar's Avatar
    And It isn't a bug. Please refrain from using that terminalogy when addressing this issue which is lack of user knowledge. The zoom requires different dimensions from other browsers/devices. Because of this websites aren't optimized to recogognize the difference android mobile and android tablet. Hence why all websites come up as mobile. Until web developers start designing their CSS to adjust to the different platforms, like they did with iPhone and Ipad you are going to experience this. Your best bet is to set it to Ipad for now. Flash will load where html5 doesn't.
    First off, this "wait for developers" excuse is ridiculous. It's the same thing I pad users say to defend against their device not having flash. I wanrt a device that will let me view the web as it is now, not in the device maker's ideal view of how it should be.

    Secondly, this is a bug. If you change the setting to desktop mode through about:debug and restart the browser, mobile sites show up even though the desktop setting is still checked in the about:debug menu. You have to unselect it and then reselect it to turn desktop mode back on. Pretty sure that is not how it is intended to work.

    Honestly I cannot understand how people are defending this. It is a pain in the a** that is easily fixed (just have a menu setting where you can permanently switch to desktop mode) . I shouldn't have to switch to a different browser or wait for developers to catch up or search for a link to the desktop version of a webpage. I paid for this device, I shouldn't have to compromise on something this stupid.
    03-26-2011 10:49 PM
  10. Rigelian's Avatar
    First off, this "wait for developers" excuse is ridiculous. It's the same thing I pad users say to defend against their device not having flash. I wanrt a device that will let me view the web as it is now, not in the device maker's ideal view of how it should be.

    Secondly, this is a bug. If you change the setting to desktop mode through about:debug and restart the browser, mobile sites show up even though the desktop setting is still checked in the about:debug menu. You have to unselect it and then reselect it to turn desktop mode back on. Pretty sure that is not how it is intended to work.

    Honestly I cannot understand how people are defending this. It is a pain in the a** that is easily fixed (just have a menu setting where you can permanently switch to desktop mode) . I shouldn't have to switch to a different browser or wait for developers to catch up or search for a link to the desktop version of a webpage. I paid for this device, I shouldn't have to compromise on something this stupid.
    Actually I do want the developers to fix it. I Google modifies the standard them the hope of having websites that take advantage of honeycomb's unique atributes goes out the window. I believe that android should be entitled to the same distinctions that the opacity and the iPhone are entitled to. Why do you feel differently?

    Sent from my Xoom using Tapatalk
    03-27-2011 01:29 AM
  11. moosc's Avatar
    my 9inch net book and my 17inch aliemware laptop have no issues with screen size.maybe if Google didn't make the browser a mobile version and ran full Chrome11 on it we wouldn't have this issue. I was hoping that honeycomb would be more pc like then phone like but I guess they still like there phone OS
    why are you having to change this sovoften. I browse for hours without issues. i use stock and ipad uastring. And It isn't a bug. Please refrain from using that terminalogy when addressing this issue which is lack of user knowledge. The zoom requires different dimensions from other browsers/devices. Because of this websites aren't optimized to recogognize the difference android mobile and android tablet. Hence why all websites come up as mobile. Until web developers start designing their CSS to adjust to the different platforms, like they did with iPhone and Ipad you are going to experience this. Your best bet is to set it to Ipad for now. Flash will load where html5 doesn't.


    Sent from my DROIDX using Tapatalk
    03-27-2011 01:56 AM
  12. moosc's Avatar
    there are thousands, millions, billions of websight on this planet you can not expect them to cater to or redesign there sight for a phone or tablet viewing.
    Actually I do want the developers to fix it. I Google modifies the standard them the hope of having websites that take advantage of honeycomb's unique atributes goes out the window. I believe that android should be entitled to the same distinctions that the opacity and the iPhone are entitled to. Why do you feel differently?

    Sent from my Xoom using Tapatalk


    Sent from my DROIDX using Tapatalk
    03-27-2011 02:00 AM
  13. brandonx1000's Avatar
    ive had mine since feb 24 and still no browser crashes
    03-27-2011 08:38 AM
  14. Dunbar's Avatar
    Actually I do want the developers to fix it. I Google modifies the standard them the hope of having websites that take advantage of honeycomb's unique atributes goes out the window. I believe that android should be entitled to the same distinctions that the opacity and the iPhone are entitled to. Why do you feel differently?

    Sent from my Xoom using Tapatalk

    Because all I care about is being able to view webpages in full now. Regular web pages look fine for me on the xoom. We are already having to wait to get many features on the zoom, and why wait for this? The android tablet market is in its infancy. we will be waiting a long time for developers to institute a unique honeycomb design.

    Why do you feel you need to have a special design for android? Again there is a very easy fix for this. Just get it done.
    03-27-2011 09:46 AM
  15. Rigelian's Avatar
    I care about the standard being supported. If these thousands and thousands of developers are capable of recognizing the distinction between the iPhone and the ipad it is not unreasonable to expect them to make the same distinction between android and android mobile. The pressure should be put on the developer where it belongs.

    Why should Android users get less than adequate support from developers? You think that Apple users just sit back and complain to Apple about this problem? I am sure they demanded that websites correct their deficiency. And guess what it worked.
    03-27-2011 10:05 AM
  16. Dunbar's Avatar
    I care about the standard being supported. If these thousands and thousands of developers are capable of recognizing the distinction between the iPhone and the ipad it is not unreasonable to expect them to make the same distinction between android and android mobile. The pressure should be put on the developer where it belongs.

    Why should Android users get less than adequate support from developers? You think that Apple users just sit back and complain to Apple about this problem? I am sure they demanded that websites correct their deficiency. And guess what it worked.
    Yes, we could start the always effective email campaign asking tens of thousands of web developers to make unique versions of their pages for a device that makes up about 1 percent of the market. We would also have to lobby the companies who pay for the pages to be made so they would fund the work of the web developers.

    OR Google could spend an hour adding a menu setting and solve the issue entirely.

    What sounds more practical to you?
    03-27-2011 10:41 AM
  17. Rigelian's Avatar
    Whatever happened the ipad seemed to have worked. I suspect it will work on the honeycomb side as well. Changing that piece of code from Google's eliminates the incentive to fix the real error.

    Sent from my Xoom using Tapatalk
    03-27-2011 10:58 AM
  18. harold42483's Avatar
    ?! ... have you yet found a site that doesn't have a "Full Version" link? Once you do that 90% of the time they set a cookie so you don't have to do that any longer.

    Far less annoying than having to set your UserAgent a couple of times a day.
    Actually i thinmk it is either gizmodo or boygeniusreport that doesnt have that button. and it really is annoying. the need to fix this asap. if my evo can do full web browser then my xoom should as well
    03-27-2011 11:27 AM
  19. Rigelian's Avatar
    It's Gizmodo,and it's very annoying.

    Sent from my Xoom using Tapatalk
    03-27-2011 01:41 PM
  20. Dunbar's Avatar
    Whatever happened the ipad seemed to have worked. I suspect it will work on the honeycomb side as well. Changing that piece of code from Google's eliminates the incentive to fix the real error.
    Correction: changing that piece of code will solve the problem entirely.

    We will just have to agree to disagree. But for the life of me I cannot understand your position. Google could solve this on its own in probably less time than it's taken us to write these posts. But instead you want literally the entire internet to change to accommodate the xoom. Just baffling.
    03-27-2011 03:12 PM
  21. anon(167668)'s Avatar
    Correction: changing that piece of code will solve the problem entirely.

    We will just have to agree to disagree. But for the life of me I cannot understand your position. Google could solve this on its own in probably less time than it's taken us to write these posts. But instead you want literally the entire internet to change to accommodate the xoom. Just baffling.
    I don't think you understand how HTML headers work. It identifies the type of device you're running on. The "fix" would be to fabricate the device you're using. For example, the 'desktop' UAstring option in the debug menu makes the xoom pretend it's a Mac. The issue is that sites are just scanning for "Android", not if it's a cell phone or not. This issue will get fixed when Honeycomb becomes more popular with other devices released.
    TPadden likes this.
    03-27-2011 05:38 PM
  22. slinky317's Avatar
    why are you having to change this sovoften. I browse for hours without issues. i use stock and ipad uastring. And It isn't a bug. Please refrain from using that terminalogy when addressing this issue which is lack of user knowledge. The zoom requires different dimensions from other browsers/devices. Because of this websites aren't optimized to recogognize the difference android mobile and android tablet. Hence why all websites come up as mobile. Until web developers start designing their CSS to adjust to the different platforms, like they did with iPhone and Ipad you are going to experience this. Your best bet is to set it to Ipad for now. Flash will load where html5 doesn't.
    Um, it definitely is a bug. When the browser crashes or shuts down and you load the debug menu, it says that the UA String is still set to Desktop even though it's rendering mobile sites. Bug.

    If you haven't crashed yet then you must be really lucky, as I tried to reply to this post three times (trying both Android and Desktop UA Strings) and it crashed each time until now.

    The XOOM has issues, and there's really no reason why it should default to the Android UA String when it has the power to display the full site without a problem.
    03-27-2011 06:46 PM
  23. anon(167668)'s Avatar
    If the browser needs to be loaded again the debug mode must be re-engaged before any of the debug settings take hold. It's not a bug, it's just how it's set up.
    03-27-2011 06:48 PM
  24. Dunbar's Avatar
    I don't think you understand how HTML headers work. It identifies the type of device you're running on. The "fix" would be to fabricate the device you're using. For example, the 'desktop' UAstring option in the debug menu makes the xoom pretend it's a Mac. The issue is that sites are just scanning for "Android", not if it's a cell phone or not. This issue will get fixed when Honeycomb becomes more popular with other devices released.
    Everything you say may be true. This does not change the fact that a simple menu setting would solve this without having to wait for honeycomb to get more popular.

    Generally I am the type of person who likes to know the details of a problem. But in circumstances like this, I don't care. There is an easy fix that does not involve waiting. Google needs to get this done fast. Otherwise they are simply reinforcing the negative stereotypes sourrounding android tablets.
    03-27-2011 09:47 PM
  25. anon(167668)'s Avatar
    There is an easy fix. Set about:debug as your home page and just push Enter when you have to load up the browser.
    03-27-2011 09:53 PM
48 12
LINK TO POST COPIED TO CLIPBOARD