I've searched online everywhere but I can not find a solution for adding additional text to speech reading speeds to the kindle fire. I don't get it, they have 3x and 4x reading speeds which are ridiculously fast, yet don't have 1.25x! Does anyone know of a way to add extra ones through rooting the device and editing a config somewhere? There has to be a way pretty easily to add the option in.
Related
Okay, so recently I made a program as part of a course in Java, using Swing, that gave you a prefix and prompted you to come up with as many words using that prefix as you could. To accomplish this, I had it use the dictionary used by Words With Friends (I might switch to a different dictionary like ENABLE, not sure yet), but that's what I've been using so far. I wanted to turn this idea into an Android application, because it seemed challenging enough to be fun, yet not too challenging.
The problem here is, the amount of time it takes a computer to load in an entire dictionary into an array of Strings of 173,139 words delimited by newlines in a .txt file is very small. The amount of time it takes to do the same in Android is slower, not to mention the fact that it needs to do this every time it starts up if I want to keep using the array.
I still wanted to make the app, so initially my idea was to do the array thing but use AsyncTask to show a loadscreen and use binary search to optimize the searching for the word in the dictionary every time the user hits a "Submit" button. This proved to be overly difficult (this is my first real Android app besides "Hello World" and a button that opened a "Hello World"...) and still quite slow.
After some searching, I decided what I really should do is make a database and have it search the database for the word when the user hits "Submit". I'm still going to use AsyncTask for downloading the database (I'd rather not bundle it with the .APK for fear of bloating it) and possibly for checking for the word in the database, depending on how fast the searching of the database ends up going.
Is this the best possible way I could go about doing this? Is there something that could give me better, faster results? From what I've seen, the database seems to be the easiest way to make sure I don't have to load in the list of words each time, but will searching the database be fast enough to appear responsive when a user wants to submit a word and see whether they got it?
I'm about to begin coding it using the database technique, but I thought I'd put this out there in case there's a better way I can accomplish this.
tl;dr: what's the quickest/best way to load in and constantly search a large (173,139 words) dictionary I have?
Thanks!
import antigravity said:
Okay, so recently I made a program as part of a course in Java, using Swing, that gave you a prefix and prompted you to come up with as many words using that prefix as you could. To accomplish this, I had it use the dictionary used by Words With Friends (I might switch to a different dictionary like ENABLE, not sure yet), but that's what I've been using so far. I wanted to turn this idea into an Android application, because it seemed challenging enough to be fun, yet not too challenging.
The problem here is, the amount of time it takes a computer to load in an entire dictionary into an array of Strings of 173,139 words delimited by newlines in a .txt file is very small. The amount of time it takes to do the same in Android is slower, not to mention the fact that it needs to do this every time it starts up if I want to keep using the array.
I still wanted to make the app, so initially my idea was to do the array thing but use AsyncTask to show a loadscreen and use binary search to optimize the searching for the word in the dictionary every time the user hits a "Submit" button. This proved to be overly difficult (this is my first real Android app besides "Hello World" and a button that opened a "Hello World"...) and still quite slow.
After some searching, I decided what I really should do is make a database and have it search the database for the word when the user hits "Submit". I'm still going to use AsyncTask for downloading the database (I'd rather not bundle it with the .APK for fear of bloating it) and possibly for checking for the word in the database, depending on how fast the searching of the database ends up going.
Is this the best possible way I could go about doing this? Is there something that could give me better, faster results? From what I've seen, the database seems to be the easiest way to make sure I don't have to load in the list of words each time, but will searching the database be fast enough to appear responsive when a user wants to submit a word and see whether they got it?
I'm about to begin coding it using the database technique, but I thought I'd put this out there in case there's a better way I can accomplish this.
tl;dr: what's the quickest/best way to load in and constantly search a large (173,139 words) dictionary I have?
Thanks!
Click to expand...
Click to collapse
In my opinion, your best option, especially if you plan on using larger dictionaries over time, would be to have the actual computing done on a server which returns the array in a JSON object that you retrieve from your app.
I have both kindle and Nook simple touch.
I notice a cool feature on kindle, when reading scanned pdf, it can automatically wrap word - it breaks one line of words into multiple lines, which makes reading pdf much enjoyable on Kindle.
I tried to find a similar solution on Nook, but failed.
I tried Orion viewer with kindlepdfviewer mod. it is functional but not stable at all...
I know a couple android apps that support such feature, but it cannot run on android 2.1 - what an old version nook is using
Does anyone know a solution?
libpdfhost.so (which does the bulk of the stock reader) switches into reflow mode when things get too "awkward".
You can set the font to really big and it will reflow.
I have on my big list of things to do to set the threshold much lower or have an on/off toggle for this.
yekniw said:
I have both kindle and Nook simple touch.
I notice a cool feature on kindle, when reading scanned pdf, it can automatically wrap word - it breaks one line of words into multiple lines, which makes reading pdf much enjoyable on Kindle.
I tried to find a similar solution on Nook, but failed.
I tried Orion viewer with kindlepdfviewer mod. it is functional but not stable at all...
I know a couple android apps that support such feature, but it cannot run on android 2.1 - what an old version nook is using
Does anyone know a solution?
Click to expand...
Click to collapse
advpro is an open-source pdf reader that supports text re-flow and runs successfully on Android 2.1.
As I can't post external links, google for apvpro-0.4.0-all.apk and the official download site (on code.google.com/p/adv/ ) should be the top hit.
jaset_uk said:
advpro is an open-source pdf reader that supports text re-flow and runs successfully on Android 2.1.
As I can't post external links, google for apvpro-0.4.0-all.apk and the official download site (on code.google.com/p/adv/ ) should be the top hit.
Click to expand...
Click to collapse
Tried that on my NST and it only displays half of the page.
So just got my hands on one of these. One thing I noticed/realized that would be a big deal for my intended usage is being able to enable multi-user functionality so each person that uses it can log in to their own profile.
So far on researching I have seen very little discussion on this matter. At best I see no option in the stock rom and no mentions in third party roms. If this is indeed available in third party roms I would not be averse to giving them a shot. I have also seen build.prop edits to enable that and they seem to be the same edit across devices so I'm assuming it is a standard android thing. I haven't had a chance yet to root my Player but is there a chance adding these build.prop options could also work on the stock rom?
Thoughts? Btw, I have already updated to Marshmallow however I did find a post around here that seems to indicate it is still relatively easy to root so once I get time today I am going to go down that route regardless.
I've seen a workaround that has you side-load gmail apk onto the nexus player, which in turn lets you add an account. Then, there are some apps that check for multiple accounts. Haven't tried yet, I think it might no longer work with YouTube like it used to.
Let's get this escalated to google - star this issue to get it some attention.
https://code.google.com/p/android/issues/detail?id=170121
I would really like some info on this! cr08 if you are going to mention builprop edits please at least consider linking the info you refer to haha thanks!
So I was wondering how many of you had gone through with implementing the buildprop change that enables Google AI. I decided to do it the other night and have been fiddling around with it since then. If you haven't done it, it basically turns Now-on-Tap into "Voice Search by default," but you can still do screen searches for things like USPS Tracking and Phone/Address Lookup. Voice searches are vastly improved; it will auto-start Navigation, fetch links as a list of cards (for example, miniaturized news feeds), open apps instantly (provided the phone isn't locked), and essentially just be all around snappier than Google Now/Now-on-Tap.
That said, it does bother me that the phone literally had to be rebranded as a Pixel to make this work. A) It's not the most stable change, and 2) that change is now reflected on any device/prompt that interacts with my phone. It managed to be picked up by adware on a sketchy site (don't ask what sketchy sites I go to), and my desktop also mislabels it on USB connection. Does anyone know if Motorola allows you to change the device name for USB connection? I know LG lets you.
But yeah, those are my thoughts on it. I might try it out for a week or two, and if I'm not exactly bowled over by it, I'll probably just go back to Now-on-Tap. But I wanted to hear your guys' thoughts.
I don't even use now-on-tap, and I've done the assistant bulildprop trick before, and it made little to no difference on how often I use both of them. I understand what you mean by having to rebrand it to a pixel though - Google shouldn't make this Pixel exclusive
Hello,
I've spent most of my evening searching through threads to figure out some answers and couldn't find all of them, so I apologize if this was posted somewhere and I missed it.
I have some relatively minor vision issues, but they make reading difficult & even harder when there is glare. I did research and found that the Nook Simple Touch or Simple Touch w/ Glow were the best options because they didn't have an LCD and were easiest to mod.
1. I often use text-to-speech when reading & Ideally, I'd like to use Mycroft AI. It's available to build in Android studio & compile into an apk, will it be doable to enable text-to-speech and use Mycroft for the voice?
2. For my purposes, which is a better idea, NST or NSTG?
3. (I Found threads on this but was confused) After rooting, can I still buy books in the marketplace?
I am completely new at all of this and really appreciate everyone's patience and time.
D
PixieD said:
Hello,
I've spent most of my evening searching through threads to figure out some answers and couldn't find all of them, so I apologize if this was posted somewhere and I missed it.
I have some relatively minor vision issues, but they make reading difficult & even harder when there is glare. I did research and found that the Nook Simple Touch or Simple Touch w/ Glow were the best options because they didn't have an LCD and were easiest to mod.
1. I often use text-to-speech when reading & Ideally, I'd like to use Mycroft AI. It's available to build in Android studio & compile into an apk, will it be doable to enable text-to-speech and use Mycroft for the voice?
2. For my purposes, which is a better idea, NST or NSTG?
3. (I Found threads on this but was confused) After rooting, can I still buy books in the marketplace?
I am completely new at all of this and really appreciate everyone's patience and time.
D
Click to expand...
Click to collapse
With USB Audio enabled TTS certainly can work, at least the Pico TTS does. I'd be amazed if the Mycroft AI can be compiled as an app to run on Android 2.1 (and first you need to run down an old version of Android Studio...). But it might work.
There's no real difference between the NST and NSTG except the obvious one. They now even use the same firmware. Used NSTGs tend to run a little bit more, but you might find a good deal.
Simple rooting (like with NookManager) will still allow you to purchase books from B&N. You should register the device before rooting.
Be aware, the batteries provide long life when the devices are used as marketed. USB Audio uses considerable power. I listen to a time-shifted NPR program on Sunday mornings for about 2 hours. Now that means WiFi is also running, but I see a battery drop of nearly 30% during that time.