UPDATE: Opera does work as desktop agent. Why not any other? I tried all usual suspects, including the ICS browsers.
I have tried every main browser app and same result. I have tried different agents in different apps (desktop, IE 10, Firefox 9) with same result. The tablet is always seen as a mobile device and not a desktop. I had the same problem with the Droid X 2. Of all the devices had: Gtablet, G1, Incredible, Droid 3, Razr, Thrive, Flyer, View, A500 and Prime, the A510 and the Droid X 2 are the only devices to have the problem.
I already have an iPad that is seen as a mobile device by design, but expect better from Android. I may return the A510 if I can not resolve the issue.
Is this every site you go to or just a few select ones? I have seen a few sites regardless of sitting it to desktop view it stays on mobile with that device. Not sure the full reason why.
I am assuming Chrome beta does it as well?
On a few sites, I have to generally click on the View Full site link of the page to pull it even if the Show Desktop Version is checked in the browser.
I've noticed this with stock Acer ICS ROM's (both official and modded versions) on the A500 too. Opera Mobile will set the UA correctly in this case. Also, CM-based ROM's work perfectly for setting the UA on any browser, including stock (or ICS Browser+ available on the Play Store). I'm assuming the A510 will be the same.
All sites see the A510 as a mobile device, regardless of agent string used. It may seem that some sites are not, but some sites are more generic rather than mobile specific site options. If there is a mobile version, the A510 goes to it, unless the web page has an option of which to go to (this is rare).
This is very annoying. I have no desire to root and use another rom, so might go back to my Thrive and wait for another option.
Bloodflame said:
I've noticed this with stock Acer ICS ROM's (both official and modded versions) on the A500 too. Opera Mobile will set the UA correctly in this case. Also, CM-based ROM's work perfectly for setting the UA on any browser, including stock (or ICS Browser+ available on the Play Store). I'm assuming the A510 will be the same.
Click to expand...
Click to collapse
Good one on Opera, since it does work I never tried it, since figured it was 100% mobile centric. Tried the other eight most common browsers (including stoock). More irony. I saw no thanks button, but THANKS none the less
rushless said:
Good one on Opera, since it does work I never tried it, since figured it was 100% mobile centric. Tried the other eight most common browsers (including stoock). More irony. I saw no thanks button, but THANKS none the less
Click to expand...
Click to collapse
The thanks button should be at the bottom of my post, right before the quote button And you're welcome. I'm almost 100% certain that if you flash CM9, all other browsers will set the UA just fine. There must be something screwy going on in the Acer framework...
Will download opera now! Good find.
Sent from my A510 using xda premium
Something must be real silly for only Opera to work. I prefer Dolphin, so kind of a bummer, but better than nothing.
As far as flashing roms, I just want the device to work and not get into the root and rom cycle. Did that with the G1, GTablet and Incredible because I "had" to, since the stock roms were inadequate.
Besides rooting to freeze some bloat, I have not seen a need on the Razr or Acer 510, since they work fine (sans the desktop issue on the 510). All the major check points appear covered with the 510.
Performance/Speed: Check
Display quality: Check
Sound quality: Check
File management: Check
Full desktop level USB host: Check
Build: Check
Battery life: Check
Stability: Check
Wifi performance/range: Check
Ergonomics: Check (one * due to the usb location)
No other current tablet checks every box, but the A510 does.
I tried Dolphin mode desktop & mobile & other
I tried Chrome
I tried Firefox
I tried the default browser
...
Why when I try to download a small file from my "Owncloud 4.0.7" it doesn't work...
Other websites too, got the same problem and somes difficulties to show flash gallery...
Pad like Transformer are enough powerful to support load of heavy websites.
So the problem come from the app to load correctly websites.
There is a solution ?
Best regards
Bankaiii
Hi,
I use Chrome, Firefox and the stock ICS browser and in general i find browsing on the TF101 to be quite good. I am using Stock ICS.
Apart from ownCloud.org, do you have any other examples of websites you have trouble browsing from the transformer? I can test these out on mine.
To me it seem, that you can't download files from some sites, like sharehosters etc., because they prevent you from using a download manager. When you start a download on your device the download app kick in an is falsely detected as some kind of download manager.
Asolutely not.
I manage my own connection Internet
tell me if you can load the game : www.thesettlersonline.com
But Owncloud that I setup work perfectly on PC but not on my Pad
( Im still use Stock Rom )
I just tried thesettlers and it work with latest firefox nightly. played it for a minute but have no clue how to scroll...
google for firefox nightly android
I set up my fourth. yes fourth, V20 last week (the perils of buying used phones on ebay!) and all seems good. But I noticed a couple of days ago that whenever I try to download the page I'm viewing on chrome, it begins to download but then I get the message,
Download unsuccessful
Download is canceled The content is not valid to download
The pages get the tick in the notification bar and show up in the downloaded section, but when I click on them, there's nothing!
I've tried switching to data and have never had any issues with other phones doing this. I'm still on the stock ROM and not rooted. I'm in the UK and viewing UK sites, this is really odd. Does anyone have any suggestions as I caouldn't find anything when I searched online
This obviously isn't the place to ask for help with a Google app. Contact Google through email about their Chome app.
Would anyone have any (useful) suggestions regarding this? It's highly unlikely to be a chrome issue as I've never had problems on any other phones in similar situations (obviously I tried to contact them and went on their forums but I couldn't find anyone who'd experienced the same issue). I can't get the full UK keyboard due to some random geo lock on the H910, that's why I was wondering if anyone had any V20 specific suggestions?
I'd have happily moved to a Chromium based third party browser but I need the sync capability so that the bookmarks are also available on my desktop, so it's Chrome or Firefox as things stand (not really a fan of Opera).
As an aside - I've not found a solution to this and it's NOT limited to Chrome, it is the same when I run Brave, a Chromium browser. So the issue isn't purely Chrome.
It's a sizable pain in the posterior when travelling - it's great to be able to download a selection of web pages before setting off into areas with very patchy signal. I used to use Pocket, but I'd much rather know why I can't use the native function.
It's time to show a little more love for arguably the best browser for the NST/G
I've been reading up on the whole TLS 1.2 thing and bemoaning the gradual eroding of the NST/G internet capabilities as various apps wink out of usefulness due to the recent change. I felt the same way about Opera Mobile 12.10, especially when I had finally figured out an app for Google News, only to find that many of the external links could not be opened, presumably due to this new security protocol.
Imagine my surprise today when I revisited the configuration screen for Opera Mobile and saw that even on this nearly prehistoric app there is an option for TLS 1.2!! Once I had selected that I could suddenly navigate to all kinds of sites that were previously snubbing me! Woo-hoo!
The procedure, in pictures, below. Love live Opera Mobile (at least until TLS 1.3).
Edit: I should mention that this has nothing to do with the recent NST/G update to 1.2.2. B&N only added TLS 1.2 handshaking for their own purchasing system, not anything else. I have one device running 1.2.1 and one updated to 1.2.2. They are identical in their need for and response to this change in settings for Opera Mobile.
Edit, Edit: I've been looking at this issue again recently and found sites that actually test the browser and recommend changes in settings. It turns out that ONLY the TLS 1.2 should be enabled, not older protocols. One site also recommended disabling the SSL v.3, but my tests with two devices trying to access the same sites indicated that was a bad idea.
My most unexpected discovery was a post on an Opera board somewhere that suggested simply clearing cache (from the Menu: Settings>Privacy>Clear Cache) will often allow access to sites that initially give a security connection error. This actually seems to work in many cases. I have no idea why, but it prompted me to try unticking ALL cache settings except for "Empty on Exit" (last screenshot below). Don't forget to "Save" at the end of that section before exiting.
This is great, thank you!
Has anyone gotten this tweak to allow you to sign into Overdrive (online library) websites? New York Public Library's Overdrive page, nypl.overdrive.com still won't let me sign in, even with both TLS 1.1 and 1.2. For the record I think I'm still actually on firmware 1.1.0
jptiger said:
This is great, thank you!
Has anyone gotten this tweak to allow you to sign into Overdrive (online library) websites? New York Public Library's Overdrive page, nypl.overdrive.com still won't let me sign in, even with both TLS 1.1 and 1.2. For the record I think I'm still actually on firmware 1.1.0
Click to expand...
Click to collapse
That was the second thing I tried. No joy. Unfortunately there is zero information in a logcat of my unsuccessful session, almost as though the system was ignoring the browser activity entirely, so nothing to work with there.
Out on a limb here, but it could be a case of no contact with systems older than the oldest one to still support an Overdrive app (2.3, I think?). When I encounter a site that still won't connect with Opera Mobile, despite the addition of TLS 1.2, I think that's similar. Such an old browser (and OS) is seen as a security issue. Now exactly how the determination is made, that I don't know. It seems unlikely that it's something as simple as the User Agent string, as I have two NSTs, one running 1.2.2 and the older one with 1.2.1. I'm pretty sure I have not done anything with the UA string on the 1.2.2 device (it's a beast to type in) but I know I altered the other one to match the original stock browser on the device. I'll have to run down both values to see if there's something about the OS in there.
If the sites have a way of querying the system to recognize whether it is "safe" or not, then there's not much to be done. There was that one older version of UC Mini Browser which was able to negotiate a login at one time, but even if you could get into the library's Overdrive section, the closest you would come to a book is downloading the acsm file and then what? AFAIK there is no way to deal with it on the device itself. It would have to be processed on a PC and then transferred to the NST.
Login would allow you to checkout Kindle books and even confirm the download at the Amazon site (painful as that is), but I don't see how to make the epub thing work solely on the device any longer short of a new OS. That's way beyond my pay grade. I'm curious about it but recognize that it's not something I'm going to pick up at this stage of my life. Too bad the few projects directed at that weren't more modest in their goals. A change to just Gingerbread would have made a huge difference, although even with that, the handwriting is surely on the wall.
but even if you could get into the library's Overdrive section, the closest you would come to a book is downloading the acsm file and then what?
Click to expand...
Click to collapse
Open the file with Aldiko! I actually used to do this all the time, it was the main way I used to interact with Overdrive for years. Worked great... until I wasn't able to log into Overdrive sites and access my holds any more.
You might need a specific old version of Aldiko, I'd bet I found it on these forums somewhere. I'm writing this on my phone on a subway, otherwise I'd link here. Moot point atm anyway.
jptiger said:
Open the file with Aldiko! I actually used to do this all the time, it was the main way I used to interact with Overdrive for years. Worked great... until I wasn't able to log into Overdrive sites and access my holds any more.
You might need a specific old version of Aldiko, I'd bet I found it on these forums somewhere. I'm writing this on my phone on a subway, otherwise I'd link here. Moot point atm anyway.
Click to expand...
Click to collapse
There may yet be a magic version of Aldiko that can do this, but I think the operative word in your response might be "used" to interact with Overdrive.
I don't know why but I decided to look at this issue again and stumbled on @straygecko's post re: Overdrive and Aldiko here: https://forum.xda-developers.com/showpost.php?p=35917607&postcount=2
I scrounged around for a "2.0" version of Aldiko and came up with 2.00.081 (maybe close enough?). Anyway, it does install and the first few steps of the procedure @straygecko outlines actually work great, even the sign in with Adobe--which I found shocking. I was able to painfully add my local library's Overdrive URL to the "My Catalogs" section and actually "browse" to the URL, if you can call it that. If we think Opera Mobile is antique, think more along the lines of the stock NST browser. Mostly floating text appears here and there, lots of broken images, and Search does not seem to work. Oh, and scrolling up the page? LOL! If you can get lower on the page to something like "available now", the screen will not update. It may not be absolutely necessary but while I was chortling and grimacing I also tried the "sign in" option. In little tiny letters across the top of the screen comes the "oops! something went wrong" message, all too familiar.
I hope, I really do hope that there is another version of Aldiko 2.0 that would work. But the post by @straygecko was from 2012 and while at my age that seems not so long ago, in the world of Android, it might as well be 500 BCE.
For your entertainment, I attach the version of Aldiko I was able to scare up. YMMV.
Odd. I think you might be trying to make Aldiko do a different part than I was referring to. Here was my usual workflow after installing Aldiko and logging into my Adobe ID on it:
1 open opera mobile
2 navigate to my library's overdrive page
3 sign in (not currently working)
4 browse and check out an epub ebook
5 download the ascm file
6 when prompted about what to do with it open it aldiko
7 Aldiko then downloads the epub using your Adobe ID and shows it in your library until it expires
If those are the steps you're following, where do you hit the unreadable text? After the book downloads?
jptiger said:
Odd. I think you might be trying to make Aldiko do a different part than I was referring to. Here was my usual workflow after installing Aldiko and logging into my Adobe ID on it:
1 open opera mobile
2 navigate to my library's overdrive page
3 sign in (not currently working)
4 browse and check out an epub ebook
5 download the ascm file
6 when prompted about what to do with it open it aldiko
7 Aldiko then downloads the epub using your Adobe ID and shows it in your library until it expires
If those are the steps you're following, where do you hit the unreadable text? After the book downloads?
Click to expand...
Click to collapse
You're right, those were not my steps. On my local library Overdrive site it is not possible to check out an eBook without eventually signing in. Catch-22.
nmyshkin said:
It's time to show a little more love for arguably the best browser for the NST/G
I've been reading up on the whole TLS 1.2 thing and bemoaning the gradual eroding of the NST/G internet capabilities as various apps wink out of usefulness due to the recent change. I felt the same way about Opera Mobile 12.10, especially when I had finally figured out an app for Google News, only to find that many of the external links could not be opened, presumably due to this new security protocol.
Imagine my surprise today when I revisited the configuration screen for Opera Mobile and saw that even on this nearly prehistoric app there is an option for TLS 1.2!! Once I had selected that I could suddenly navigate to all kinds of sites that were previously snubbing me! Woo-hoo!
The procedure, in pictures, below. Love live Opera Mobile (at least until TLS 1.3).
Edit: I should mention that this has nothing to do with the recent NST/G update to 1.2.2. B&N only added TLS 1.2 handshaking for their own purchasing system, not anything else. I have one device running 1.2.1 and one updated to 1.2.2. They are identical in their need for and response to this change in settings for Opera Mobile.
Click to expand...
Click to collapse
Wow. I have tried every other browser. This is definitely the only one that works. Thanks so much for the info.
lz199366 said:
Could you share your Opera Mobile.apk? I can't get opera 12.1.0 install on my NST(firmware1.1.2).
Besides, which app did you use to take screenshot in Black&White color ? I tried screenshot ER before. It is good but producing shots in colors only.
Click to expand...
Click to collapse
Opera Mobile: https://ftp.opera.com/pub/opera/android/mobile/1210/
For screenshots, I made two apps. The original produces slightly gray b&w images. The second gives better quality color images. Here: https://forum.xda-developers.com/nook-touch/themes-apps/app-screenshot-t3648855. When I post images I always convert to greyscale anyway since that's what will be seen on the device.
That older firmware may be a problem. B&N did actually have reasons to update firmware now and then. If the Opera Mobile will not run you might try Opera Classic. Some people said it worked for them.
Some additional discoveries
Just a bump to bring this post back up again. I've done some additional tests with different settings lately and have improved the connection success rate quite a bit. Changes reflected now in the original post.
Since you're bumping the thread maybe you can help me with a problem? I think I've tried this APK on my last three Nooks (Glowlight Plus, NG3, and now Glowlight Plus 7.8) and every time I launch Opera Classic from my launcher I get a short splash screen that says "Opera Mobile" and then it immediately dies. Nothing shows in my "running process" screen either (so it's not just hidden in the background).
Any idea where to start looking as far as logs, etc. go? I've never really had much use for a browser on a Nook before, but with the 7.8" display my interest is somewhat piqued again...
spedinfargo said:
Since you're bumping the thread maybe you can help me with a problem? I think I've tried this APK on my last three Nooks (Glowlight Plus, NG3, and now Glowlight Plus 7.8) and every time I launch Opera Classic from my launcher I get a short splash screen that says "Opera Mobile" and then it immediately dies. Nothing shows in my "running process" screen either (so it's not just hidden in the background).
Any idea where to start looking as far as logs, etc. go? I've never really had much use for a browser on a Nook before, but with the 7.8" display my interest is somewhat piqued again...
Click to expand...
Click to collapse
Mmm.....first, this is Opera Mobile 12.1, not Opera Classic, although I don't think that is the issue. Not sure about the Glowlight Plus, but I think the others run at least KitKat? My first suspicion was that Opera Mobile (or Opera Classic) might be too old for those devices, but I just tried installing it on my SIM-less KitKat "phone" and it did just fine.
So maybe screen density? It's hard to know. Like @Renate NST says, a logcat might reveal the cause of the crash--or not. Meanwhile I should think that with a KitKat device there must be a number of more modern browsers that would work OK. I recommend Via Browser. Slick and simple, small footprint. Requires Android 2.3 and up (too bad the NST just missed it...). I run it on my Oreo 8.1 tablet and love it.
nmyshkin said:
Mmm.....first, this is Opera Mobile 12.1, not Opera Classic, although I don't think that is the issue. Not sure about the Glowlight Plus, but I think the others run at least KitKat? My first suspicion was that Opera Mobile (or Opera Classic) might be too old for those devices, but I just tried installing it on my SIM-less KitKat "phone" and it did just fine.
So maybe screen density? It's hard to know. Like @Renate NST says, a logcat might reveal the cause of the crash--or not. Meanwhile I should think that with a KitKat device there must be a number of more modern browsers that would work OK. I recommend Via Browser. Slick and simple, small footprint. Requires Android 2.3 and up (too bad the NST just missed it...). I run it on my Oreo 8.1 tablet and love it.
Click to expand...
Click to collapse
Ah yes, I forgot that the original NGP was where the jump to KitKat occurred which opened up more options for apps. I'm going to give Via a try - thanks for the quick response!
First problem:
Our (at least my) /system/lib/libgui.so does not have
status_t GraphicBuffer::lock(GGLSurface* sur, uint32_t usage)
The Opera libOS15.so requires it
Eclair had this function, I don't think KitKat has it.
I think this Opera "Opera_Mobile_12_1_Generic_Opera_Armv5v7.apk" was designed for Eclair and uses stuff no longer in KitKat.
You need to find a different APK.
@myshkin Once again, you've answered one of my questions before I asked it! I am going to use an NST to interact with my online scheduler for a sweet e-ink, easy on the eyes, scheduling unit.
First I want to thank for well written guide how to set things up to make any browser (in this case obviously Opera) working on NST. I read several threads about browsers and wondered how those could be solved. It seems to me that some of those problems could be solved using web grabber or offline browser or some of those plugins that redirects to cached version of the web page on Wayback machine (Brave browser is gone incorporate that option so I have been told). Naturally that might work for reading cached content on NST inside your browser if it supports page rendering and so. Still for pages that need user/reader interaction that won't solve anything. Would application like Gapps browser resolve at least some of the issues you experience? It should run on Eclair but I am not sure will it run on NST. That need to be tested.
SJT75 said:
First I want to thank for well written guide how to set things up to make any browser (in this case obviously Opera) working on NST. I read several threads about browsers and wondered how those could be solved. It seems to me that some of those problems could be solved using web grabber or offline browser or some of those plugins that redirects to cached version of the web page on Wayback machine (Brave browser is gone incorporate that option so I have been told). Naturally that might work for reading cached content on NST inside your browser if it supports page rendering and so. Still for pages that need user/reader interaction that won't solve anything. Would application like Gapps browser resolve at least some of the issues you experience? It should run on Eclair but I am not sure will it run on NST. That need to be tested.
Click to expand...
Click to collapse
I had never heard of Gapps browser but I can tell you now that it does not work properly on the NST. It never gets past a partial, immobile screen of Google News. None of the other options do anything at all.
While I still prefer Opera Mobile for general browsing and value its ability to open local HTML files (something I have exploited in a number of my news apps), Opera Mini 7.6.4 also functions on the NST and can skirt around some of the SSL issues because the pages are initially picked up by Opera's up-to-date servers, rendered, and then passed on to the user. However, sites with complex constructions and modern WebView requirements will not display properly, if at all. Opera Mini also has a "picker" that will allow you to open media files (like videos) in an external player. This is something Opera Mobile will not do. It just refuses to deal with them at all.
On the whole, the browser issue is the proverbial straw for the camel's back when it comes to older Android OS. I have seen this working with KitKat ROMs where already many sites cannot be accessed because of the outdated WebView. Lollipop, which is the first OS version with a WebView that can be updated, is a little better. But custom ROMs (or ROMs like on the NST) that are not properly updated for SSL are never going to be able to hold on forever in this regard.
Thanks for thorough reply. I fear that it is not only updates of the software that is hampering factor but very nature of e-ink devices that hold us back. Even Kindles from Amazon have the issues in that regard and it is certainly not from lack of funding that firm can provide to solve the problem. That is why I mentioned web grabber approach. As last resort someone might try to print some web page as PDF for later reading but that would not solve problems like logging in some web services etc. I even considered text based browsers as alternative. My friend who is proficient in programming, web administration and computer related stuff said me the same thing as you did that Opera is by far best browser for mobile device.