Related
Android comes with a seriously awesome web browser. It can easily browse regular desktop versions of web pages even over EDGE with no major problems. I'm so glad to leave crippled mobile versions of web pages behind me forever.
EXCEPT
Google, of all places, seems to have some kind of lock preventing the Android browser from gaining access to the desktop versions of their websites. They come up with the mobile versions by default, and even if you click the button to switch it to the desktop version, it doesn't. It takes you to yet another mobile version that is just styled a little closer to the desktop version, but it's by no means identical.
Google built this browser, they know that it can handle desktop webpages, why won't they let us do that with their own sites? I find it really annoying to deal with crippled versions of Google's web pages. In Gmail I can't edit my contacts, in YouTube... I don't know what the hell's going on... all I see is large ugly text, in Google Search I don't have the convenient switch to image search while viewing web results. It's FRUSTRATING.
chefgon said:
Android comes with a seriously awesome web browser. It can easily browse regular desktop versions of web pages even over EDGE with no major problems. I'm so glad to leave crippled mobile versions of web pages behind me forever.
EXCEPT
Google, of all places, seems to have some kind of lock preventing the Android browser from gaining access to the desktop versions of their websites. They come up with the mobile versions by default, and even if you click the button to switch it to the desktop version, it doesn't. It takes you to yet another mobile version that is just styled a little closer to the desktop version, but it's by no means identical.
Google built this browser, they know that it can handle desktop webpages, why won't they let us do that with their own sites? I find it really annoying to deal with crippled versions of Google's web pages. In Gmail I can't edit my contacts, in YouTube... I don't know what the hell's going on... all I see is large ugly text, in Google Search I don't have the convenient switch to image search while viewing web results. It's FRUSTRATING.
Click to expand...
Click to collapse
I really dont know why your browser does that, but I have access to the regular google.com classic view page. I can pic between web, images, local, news.. etc.. I can also log to igoogle.com
I can aswell
Most mobile sites have a link to view the regular site. Google has this.
go to www.google.com then you see on the bottom Mobile is default choice, click on CLASSIC to view the regular website version
Anyone else having an issue with the browser where after a while it no longer renders the pages?
It shows the progress bar filling up and done, but just a blank page.
quedijo said:
Anyone else having an issue with the browser where after a while it no longer renders the pages?
It shows the progress bar filling up and done, but just a blank page.
Click to expand...
Click to collapse
Yes I've had that problem as well as not being able to get into market have no clue why. Frustrating!!!
I keep having this problem too. The only thing that seems to solve the problem is a restart. I dont know if it has anything to do with me clearing the cache but it IS verry annoying.
Yeah, even killing the browser process doesn't do it either.
quedijo said:
Anyone else having an issue with the browser where after a while it no longer renders the pages?
It shows the progress bar filling up and done, but just a blank page.
Click to expand...
Click to collapse
thats network issues with thew the 3g when i disable 3g it worked but sometimes it wont
i think it has to do with your cache i wish they come out with a new firmware that lets you save programs to sdcard or cache to sd card
I'm having the same issues. It was working when I first got the phone, but now it only gives me the option for mobile view.
I found a solution to the most annoying, biggest mistake from Google. For those who loved iGoogle and cant find it, here it is:
www.google.com/ig/i?source=mofe
And here is an alternate BETA site from Yahoo as backup:
http://beta.m.yahoo.com/
brooklynite said:
I found a solution to the most annoying, biggest mistake from Google. For those who loved iGoogle and cant find it, here it is:
www.google.com/ig/i?source=mofe
And here is an alternate BETA site from Yahoo as backup:
http://beta.m.yahoo.com/
Click to expand...
Click to collapse
I guess Google found out the shut down the site.
Yahoo's Beta sucks.
So before I was wondering if I could edit my saved google docs or create new ones. I tried on 2.1 and couldn't do it.
Today I logged in to Google Docs on my N1, running froyo with flash 10.1 and was able to edit saved documents through the web interface.
Now it is not ideal editing documents on the little screen but when we get a tablet like the upcoming galaxy tape, a fold out blue tooth keyboard and I don't have to carry a laptop back and forth to school anymore. That will really be sweet!
Wow... this is something I've wanted for some time. Thanks for the info! To clarify, do you need Flash to edit the docs?
I guess because I couldn't do it with 2.1. I have not checked to see if google docs actually use flash or not. You need to set you UA string to Desktop just like you do for the Hulu thing.
Put about:debug into your browser then go to settings and go down to UAstring and set it to desktop.
Have you tried the GDocs application? you can edit, save, etc...its free too. I used it with my G1, MT3g, and N1...
Does Gdocs support the spreadsheet in google docs too?
I'm using it for simple text lists, but nothing fancy yet. Does it handle the spreadsheets too?
arw01 said:
I'm using it for simple text lists, but nothing fancy yet. Does it handle the spreadsheets too?
Click to expand...
Click to collapse
Seems like even Android 1.6 support Google Docs spreadsheet editing
I have read that it's possible to use google books on the NST (or NTG) but i can't find it in the market place. and every time i try and side load the apk i get INSTALL_FAILED_OLDER_SDK. I downloaded google play books 2.3.5 apk which is supposably built for 2.1. I thought the NST/NTG was on 2.1 (or is it 2.2?) so im curious why this doesn't work... anyone care to comment?
If i just have the wrong version please let me know the correct version to use.
You can try apktool-ing the apk and see what version it specs in AndroidManifest.xml.
You could modify the version and see if it crashes.
We're running Eclair, 2.1, API level 7 on the Nook Touch.
Any luck OP?
EDIT:
Tried this one: http://www.iapktop.com/google-play-books-2-4-3.html since it said compatible with 2.1, but I had no luck.
Then I tried this one: http://www.iapktop.com/google-books-1-4-5.html and it looks to be working! I saw my library in the window and I have it downloading one of my books now for reading to test.
EDIT2: AAaaaaand... works. Perfectly I might add. The only thing that doesn't work is the side buttons don't switch pages. I think because they are bound to PAGE_NEXT or something. Changing them to Right and Left arrow should do it.
EDIT3: Yep. A quick change to the keylayout lets me page with the right hand buttons. It does break the ability to page in the stock reading app though with those buttons. For now I'm leaving it with paging in Google books with right side buttons and paging in Nook with left side buttons. I'll probably go all in later.
What I did was edit /system/usr/keylayout/TWL4030_Keypad.kl and switch RIGHT_NEXTPAGE to DPAD_RIGHT and then switched RIGHT_PREVPAGE to DPAD_LEFT.
Hopefully that makes sense. If not I can probably make it easier for you by pulling the file itself, but I figure I'd try to "teach a man to fish."
Dynamic button remapping; getting rid of page-turn animation
(Interested lurker speaking. I don't have a NST, but a rooted Sony PRS-T1, which is similar, but running Android 2.2. Please take what I say with a grain of salt.)
The latest version of Google Play Books that does not require 3D hardware (for its carousel view and its page-turn animation) and that is available for older Android versions appears to be version 1.5.4.
I'm using that version on the PRS-T1, but was annoyed by its flickering slide animation when turning pages. If you're comfortable with the Android SDK and apktool, here's a hack I did to remove that animation:
mobileread.com/forums/showthread.php?t=187741
The problem of different Left/Right key bindings for different apps plagues the PRS-T1 as well. This led me to look for a solution to remap these buttons dynamically, depending on which app was currently running in the foreground. Here's my hack for the PRS-T1, which a semi-experienced developer could port over to the NST. I'd be happy to accept patches.
mobileread.com/forums/showthread.php?t=187054
github.com/altruizine/pgdn
(Sorry for not posting direct links – I'm not allowed to post links yet.)
altruizine said:
(Interested lurker speaking. I don't have a NST, but a rooted Sony PRS-T1, which is similar, but running Android 2.2. Please take what I say with a grain of salt.)
The latest version of Google Play Books that does not require 3D hardware (for its carousel view and it page-turn animation) and that it available for older Android versions appears to be version 1.5.4.
I'm using that version on the PRS-T1, but was annoyed by its flickering slide animation when turning pages. If you're comfortable with the Android SDK and apktool, here's a hack I did to remove that animation:
mobileread.com/forums/showthread.php?t=187741
The problem of different Left/Right key bindings for different apps plagues the PRS-T1 as well. This led me to look for a solution to remap these buttons dynamically, depending on which app was currently running in the foreground. Here's my hack for the PRS-T1, which a semi-experienced developer could port over to the NST. I'd be happy to accept patches.
mobileread.com/forums/showthread.php?t=187054
github.com/altruizine/pgdn
(Sorry for not posting direct links – I'm not allowed to post links yet.)
Click to expand...
Click to collapse
That's awesome! I only just got this device last night so haven't got too far into hacking it, but I have plenty of other Android experience. I'll see if I can replicate.
Sent from my HTC One S using xda premium
So close!
ViViDboarder said:
Then I tried this one: .iapktop.com/google-books-1-4-5 and it looks to be working! I saw my library in the window and I have it downloading one of my books now for reading to test.
EDIT2: AAaaaaand... works. Perfectly I might add. The only thing that doesn't work is the side buttons don't switch pages. I think because they are bound to PAGE_NEXT or something. Changing them to Right and Left arrow should do it.
Click to expand...
Click to collapse
Thank you so much for posting this!
I installed the1-4-5 apk without incident and all my books synced beautifully, including where I left off in them. I was pretty sure I was home free at this point but I've found that the actual content of the books never loads. I get the spinning loading icon off into infinity.
This is the way for all my books. Looks for all the world like it should work fine but just never loads the actual content.
I've tried a system reboot, scanning around between pages, fussing with text size/line spacing and same outcome.
I tried the 2-4-3 apk and got a parsing error when i tried to open the package.
This is so close I can taste it. Any ideas anyone?
Thank you
Update:
I found that if I toggled on "Original pages" in the book options the content would load. After I did that once I could switch back to "flowing text" and adjust as needed.
Update 2:
I still intermittently have issues with book content loading. Probably once per day the loading icon displays indefinitely. The flowing text/original pages workaround I listed before was likely a flook, I haven't been able to find a way to reliably get around this problem. It's terribly annoying.
Update 3:
I tried using the refresh option on the library view prior to loading my book this time and it popped up immediately afterward. I'll continue to experiment with this to see if it works consistently.
Update 4:
That's unreliable as well. There doesn't seem to be any good way to prompt my book to actually load the content of the book. Super annoying.
Version 1.0.16
jorgenric said:
Thank you so much for posting this!
I installed the1-4-5 apk without incident and all my books synced beautifully, including where I left off in them. I was pretty sure I was home free at this point but I've found that the actual content of the books never loads. I get the spinning loading icon off into infinity.
This is the way for all my books. Looks for all the world like it should work fine but just never loads the actual content.
I've tried a system reboot, scanning around between pages, fussing with text size/line spacing and same outcome.
I tried the 2-4-3 apk and got a parsing error when i tried to open the package.
This is so close I can taste it. Any ideas anyone?
Thank you
Update:
I found that if I toggled on "Original pages" in the book options the content would load. After I did that once I could switch back to "flowing text" and adjust as needed.
Update 2:
I still intermittently have issues with book content loading. Probably once per day the loading icon displays indefinitely. The flowing text/original pages workaround I listed before was likely a flook, I haven't been able to find a way to reliably get around this problem. It's terribly annoying.
Update 3:
I tried using the refresh option on the library view prior to loading my book this time and it popped up immediately afterward. I'll continue to experiment with this to see if it works consistently.
Update 4:
That's unreliable as well. There doesn't seem to be any good way to prompt my book to actually load the content of the book. Super annoying.
Click to expand...
Click to collapse
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
finitary said:
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
Click to expand...
Click to collapse
I may have to give this a shot. I am frequently annoyed with this bug. Thankfully the books I'm reading actually fit perfectly on the screen when viewing the scanned versions.
Just wanted to bump and see if you're still getting good results with that version of Google Books. I haven't switched yet (started reading something on Kindle) but I'm about to start a new book on Google Play.
Seems to work!
finitary said:
Here is an older version that I found somewhere on the web. It is version 1.0.16...I installed it and it seems to work excellently so far. The bug where version 1.5.4 often never loads the book doesn't seem to be present. :cyclops:
Click to expand...
Click to collapse
I just loaded up the 1.0.16 version and the book loaded right up where as 10 minutes ago it stubbornly refused. I'm not going to get my hopes up yet but I'll try and remember to give an update after some more use. Thanks for the post!
goodereader.com has version 1.5.2 for download. Worth a try.
Success!
jorgenric said:
I just loaded up the 1.0.16 version and the book loaded right up where as 10 minutes ago it stubbornly refused. I'm not going to get my hopes up yet but I'll try and remember to give an update after some more use. Thanks for the post!
Click to expand...
Click to collapse
Seems to be working consistently with this version of reader.
jorgenric said:
Seems to be working consistently with this version of reader.
Click to expand...
Click to collapse
Awesome! Thanks for the update.
Finally got around to rooting my Nook Touch, as I wanted to utilize the syncing feature of Google Play Books. They now let you upload your own epub files to your library, and I have been reading mainly on my phone or Nexus 7 as a result.
Unfortunately it looks like the 1.0.16 version does not support user uploaded books. All of my purchased books appear, but none of the many I uploaded. 1.5.2 and 1.5.4 both have the book not loading issue.
Anyone have any thoughts or other versions to try? Would love to get this working.
urinsane said:
Finally got around to rooting my Nook Touch, as I wanted to utilize the syncing feature of Google Play Books. They now let you upload your own epub files to your library, and I have been reading mainly on my phone or Nexus 7 as a result.
Unfortunately it looks like the 1.0.16 version does not support user uploaded books. All of my purchased books appear, but none of the many I uploaded. 1.5.2 and 1.5.4 both have the book not loading issue.
Anyone have any thoughts or other versions to try? Would love to get this working.
Click to expand...
Click to collapse
I'm in the same boat. I can see my uploaded library in play but it's not loading the book. I think it has loaded the book but it's not ending the load part of the function. Just guessing.
Hope we can get this worked out.. This would help me tremendously being able to read on the N2T and sync across my computer and Nexus.
*update For some strange reason this started working for about a minute. Book I'm reading synced right to the exact page. Exited and went back in to see if it would still work and it went back to the looping circle page. It's so close I can taste it.
*update Managed to get 1.5.2 working but only in offline mode only. I've noticed the more pages the book has the slower it is to load, but it's loading none the less 9/10 times. Progress, so it is possible to get this working.
ForSquirel said:
I'm in the same boat. I can see my uploaded library in play but it's not loading the book. I think it has loaded the book but it's not ending the load part of the function. Just guessing.
Hope we can get this worked out.. This would help me tremendously being able to read on the N2T and sync across my computer and Nexus.
*update For some strange reason this started working for about a minute. Book I'm reading synced right to the exact page. Exited and went back in to see if it would still work and it went back to the looping circle page. It's so close I can taste it.
*update Managed to get 1.5.2 working but only in offline mode only. I've noticed the more pages the book has the slower it is to load, but it's loading none the less 9/10 times. Progress, so it is possible to get this working.
Click to expand...
Click to collapse
I'm not really sure what version I am using now but it loaded once on my NST. However, the next time I tried loading a book it took forever to load (and I eventually closed the app). It might have to do with memory... Who knows... The funny thing is that once it has loaded the book it works like a charm. Really fast (I would say as fast as the native app). The only thing that don't work are the hardware buttons but it was quite expectable.
enekomh said:
I'm not really sure what version I am using now but it loaded once on my NST. However, the next time I tried loading a book it took forever to load (and I eventually closed the app). It might have to do with memory... Who knows... The funny thing is that once it has loaded the book it works like a charm. Really fast (I would say as fast as the native app). The only thing that don't work are the hardware buttons but it was quite expectable.
Click to expand...
Click to collapse
Any updates? Looks promising....
Here's a link to an old version that worked for me (I later uninstalled it,finding better sources for books).
nmyshkin said:
Here's a link to an old version that worked for me (I later uninstalled it,finding better sources for books).
Click to expand...
Click to collapse
Sorry meant the 1.5.2 or up version. I have uploaded books on Google Play that I hope to read.
I'm also searching for this solution. I have tried the older versions, but there doesn't seem to be a solution. Best I've got is installing an old Google Drive apk, and downloading from there. Box also works, but it's Drive for me.
Some don't like it but I really like google currents so far. However there is a button for linking to another app. In there I currently have Bluetooth (what would that do?) google+ (not sure what that would do either) gmail andftp (Why it would put my ftp app in there I have no idea...) and colornote that I have installed. All seem useless except colornote, but what I really want is open link in chrome. I wonder/suspect if I install another browser it may show up but why isn't chrome there? Or is there another method of opening an article in a browser.
My motivation is to keep or bookmark an article if desired. I wish currents had a means of bookmarking or 'starring' an article to permanently store the article similar to pulse.
But I'd be happy for now having open in browser. Is there a way to do this or control what appears in the link button?
I too would very much like to be able to share with Chrome. I tried "Andmade Share" but it wasn't able to expand my options very much.
Download an app called Flashify: https://play.google.com/store/apps/details?id=com.nightshadelabs.anotherbrowser&hl=en
Once you've installed, open your article in Currents. Click the 'share' button and select Flashify, and then choose your browser .
It works only from the 'Share' menu, so it won't appear in your app draw.
I have FF Aurora installed and gives an option to send to FF Sync. I just tried it and don't see it popping up on my N7 in Aurora or on my PC in FF.
I also have a send to Gtasks option which I have installed. It sends there as a task with no problem. I can open Gtasks and click the link and it gives me option to open in Aurora or Chrome. And it ends up on all my PC's since I use Google Tasks.
What warrants an app getting in the share list?
I have: Bluetooth, goog+, gmail, flipboard, 7notes with mazec, IM+, andftp, tubemate. and colornote.
Of the above, only colornote is of any use. Why would I want to send a google currents link to flipboard?!
Is this just borked or is there some logic as to what apps go in there?
sark666 said:
Some don't like it but I really like google currents so far. However there is a button for linking to another app. In there I currently have Bluetooth (what would that do?) google+ (not sure what that would do either) gmail andftp (Why it would put my ftp app in there I have no idea...) and colornote that I have installed. All seem useless except colornote, but what I really want is open link in chrome. I wonder/suspect if I install another browser it may show up but why isn't chrome there? Or is there another method of opening an article in a browser.
My motivation is to keep or bookmark an article if desired. I wish currents had a means of bookmarking or 'starring' an article to permanently store the article similar to pulse.
But I'd be happy for now having open in browser. Is there a way to do this or control what appears in the link button?
Click to expand...
Click to collapse
Try my app "Currents Web Viewer" (play.google.com/store/apps/details?id=com.emseedroid.webviewer), it's exactly for that! It will let you open Google Currents articles in any browser of your choice.
You can also use the free lite version "Currents Web Viewer Lite" (play.google.com/store/apps/details?id=com.emseedroid.webviewerlite). Lite version only limitation is that you have to use embedded web browser but it's fully functional and allows a very unobtrusvie full screen mode.
Hope you'll find it useful. If so please give it a good rate on the play store!
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.