Related
Anyone one else get the email for this?
Version 1.56
Haven't seen any new stuff, but haven't really had a chance to play with it yet
Rellikzephyr
-------------------------------------
Sent via the XDA Tapatalk App
RellikZephyr said:
Anyone one else get the email for this?
Click to expand...
Click to collapse
NOPE Any chance you could PM me a dload link? Thanks
logger said:
NOPE Any chance you could PM me a dload link? Thanks
Click to expand...
Click to collapse
ditto
10char
Link in email is
https://beta.swype.com/android/get/
At work, but will try get apk uploaded to share, via pm of course, can't be naughty
Rellikzephyr
-------------------------------------
Sent via the XDA Tapatalk App
Ooh, got the email too. Gonna go play with it.
Edit: Ok, the beta swype link does not recognize my phone as an android phone if I'm using Dolphin Browser HD... had to use the stock browser to download the installer.
Got the email couple of hours ago, and just updated right now. Doesn't seem much has changed. Anyone else know whats new in this version?
Thnks, email Link is just to the installer which needs a Beta username and PW to run so no use for non beta members. But a link to the actual APK via PM would be great. Cheers.
New features/fixes are:
Added better context sensitivity for the “magic button” (go/search/enter/smiley)
Added automatic apostrophe insertion for contractions (e.g. won't, don't, wasn't, etc)
Added the Italian language dictionary
Improved sensing of field type to prevent the display and addition of passwords to the UDB (user dictionary)
Improved suppression of auto-spacing in fields such as URLs and email addresses
Updated the built-in dictionary to include several common words that were previously missing
Rewrote some settings descriptions to be more clear on their functionality
Fixed licensing issue causing “Limited Functionality” errors when rebooting devices running Android 2.0 and later
Fixed licensing issue causing some users to receive an “Incorrect ID” error when installing Swype
Fixed a bug where manually typing some words with word-prediction enabled would cause Swype to crash
Fixed a bug which caused some words added to the UDB to erroneously override other words when word-prediction is enabled
Many other minor bug fixes!
Click to expand...
Click to collapse
Source AndroidGuys
LevitateJay said:
New features/fixes are:
Improved suppression of auto-spacing in fields such as URLs and email addresses
Source AndroidGuys
Click to expand...
Click to collapse
That alone would warrant an upgrade. Text entry in URLs and emails is the reason I gave up on Skype beta. So looks promising.
Gimee gimee.
Wow! Works very VERY well
Can I uninstall the installer after I've upgraded?
I see there is a link to the APK over here if anyone else is after it.
http://forum.xda-developers.com/showpost.php?p=6740224&postcount=234
On my N1, I still had to go into Swype settings and tutorial to actually activate it. Straight away I can see the URL stuff is better. So back to using Swype for me. Yee ha...
uansari1 said:
Can I uninstall the installer after I've upgraded?
Click to expand...
Click to collapse
Sure. You dont need it at all.
logger said:
Sure. You dont need it at all.
Click to expand...
Click to collapse
Thanks bro...
The word recognition is so much faster than the original beta.
I got the email about 4 hours ago (on my N1), downloaded the software and installed it. You have to remove both Swype and the older installer else it fails. I am sure there are tons of underneath the hood improvements, but the one that I saw immediately was when you enter numbers, they show up in the suggestion list in blue.
...and pecking keys is now so much more do-able. ie when you want to enter a non word such as a password. THANK YOU Swype devs for listening and fixing those two major bummers that were there before and are fixed now. Good Stuff.
Actual swiping doesnt work for my N1 on Froyo, all stock - any thoughts? - Only outlines the texting field in blue on the edges and then no text shows up - only allows me to type like normal - this is with the 1.56
Thanks for the heads up. I did not receive the email yet but downloaded it anyways. It seems much faster so far. I guess we will see how well they did after a few days of testing.
Thanks heaps!
After installing UVJI6 (I received it OTA), I am unable to see some apps from the market, in particular, ones that I use frequently. Is there a way to fix this or has someone found some sort of documentation from Samsung/TMobile on this?
Thanks!
This has been addressed, please learn to use search kthx
Yes, I've seen others report this though I don't recall seeing a fix. I'm still a little annoyed at how long the swipe needs to be now to unlock the screen.
Zylograth said:
This has been addressed, please learn to use search kthx
Click to expand...
Click to collapse
I did search and didn't see it. Would you mind sharing the link if you've seen it?
The answer is easy: Google/Samsung haven't authorized the latest updates Market yet. When they authorize it the missing applications will show up. You will have the same missing apps if you go through Kies, OTA, or Odin. You can put a hack in place to get around it but I would not recommend it. The hack causes your market to identify itself as JFD instead of JI6. In theory that could cause missing new apps in the future.
Have you tried the Android 2.2 style Market app on Vibrant?
@spiz516, I also had the same problem after using ODIN to perform my update (following a failed OTA push). I like kmfisher's answer. But if you absolutely can't wait, and you are rooted, here's how you can do it:
forum.xda-developers.com/showthread.php?t=804763
See post #24.
After I performed this fix, I was able to see a few missing applications. However, I also noticed that this also brought back a horrible Market application lag. So, I will probably send it back since I've downloaded the two applications I needed that were market locked.
Good Luck!
ScratchSF said:
@spiz516, I also had the same problem after using ODIN to perform my update (following a failed OTA push). I like kmfisher's answer. But if you absolutely can't wait, and you are rooted, here's how you can do it:
forum.xda-developers.com/showthread.php?t=804763
See post #24.
After I performed this fix, I was able to see a few missing applications. However, I also noticed that this also brought back a horrible Market application lag. So, I will probably send it back since I've downloaded the two applications I needed that were market locked.
Good Luck!
Click to expand...
Click to collapse
Awesome, thank you for the response. Much appreciated!
Clear Cache too. I don't have any worse lag, this has nothing to do with anything that would break something like market speed besides old cache maybe.
Hi!
I've updated my Kindle Fire manually to 6.2 since I read it improves performance and was still rootable. However, I've also read several reports about the Kindle Fire automatically updates itself without any user's choice of yes/no.
My question is therefore: Is there any way to disable automatic updates? If Amazon releases 6.3 and 'fixes' rooting, I probably don't want to upgrade immediately. I guess when ICS ROMs enter the scene this won't be a problem, but until then...
Update 20/12: Various reports about these suggested solutions so far. It seems like solution 2, renaming OTASilentInstall.apk, is a method many have had success with so far. Not too sure about solution 1 yet.
Solution 1
Add this line to your host file:
127.0.0.1 s3.amazonaws.com
Click to expand...
Click to collapse
It will reroute connections trying to reach s3.amazonaws.com to localhost, and therefore won't connect to the Amazon servers.
Solution 2
Rename system/app/OTASilentInstall.apk to OTASilentInstall.apk.bak or something like it.
Well, I have, and the only thing I found was this post, which suggest to de-register the Kindle. I was hoping for a more 'elegant' solution.
I find many threads discussing the 6.2 update itself, but I'm not able to find much information about disabling the automatic update feature - while keeping it online with a registered Amazon account.
That means there's still no solution for this, you can use a cooked rom, or deal with it peacefully.
Installing CM7 disables automatic updated
If search doesn't yield an answer, there isn't one. Best bet is to find what address/ip it tries to connect to for it and block it on your router or hosts file on the kindle.
Or, install a diff rom.
Wow I am surprised how often people get flamed in this forum. Treating people with an elitist snippy attitude when they ask a question degrades the quality of this forum.
Added: I read somewhere that if you rename system/app/OTASilentInstall.apk to OTASilentInstall.apk.bak that could do the trick.
Glasairmell said:
Wow I am surprised how often people get flamed in this forum. Treating people with an elitist snippy attitude when they ask a question degrades the quality of this forum.
Added: I read somewhere that if you rename system/app/OTASilentInstall.apk to OTASilentInstall.apk.bak that could do the trick.
Click to expand...
Click to collapse
Thank you so much! That's really worth a try. I'm glad someone finally answered to this thread with the main goal of helping Good to know that it's allowed to ask questions.
Appreciate it!
hachiueno said:
Hi!
I've updated my Kindle Fire to 6.2 manually since I read it improves performance and was still rootable. However, I've also read several reports about the Kindle Fire automatically updates itself without any user's choice of yes/no.
My question is therefore: Is there any way to disable automatic updates? If Amazon releases 6.3 and 'fixes' rooting, I probably don't want to upgrade immediately. I guess when ICS ROMs enter the scene this won't be a problem, but until then...
Click to expand...
Click to collapse
Use the sqlite method as explained for the nook tablet. Look for the Kindle fota.mode value and change from automatic to manual. Here is the thread.
http://forum.xda-developers.com/showpost.php?p=10973887&postcount=1
Keep it nice and friendly.
Thread cleaned
Glasairmell said:
Added: I read somewhere that if you rename system/app/OTASilentInstall.apk to OTASilentInstall.apk.bak that could do the trick.
Click to expand...
Click to collapse
That is not proven yet to actually work yet. Won't know until the next update.
Thanks a lot for your help! I updated the first post with your hints so that it should be easier to find for the next guy searching for this.
Your help is appreciated! Looks like my Kindle is ready for the future... at least its rooting
Curious that this is marked as Solved.
Solution 1
Thanks to hwong96 for this link. It's a working solution for the Nook Tablet, and obviously work for the Fire as well. However, as hwong96 wrote, the name of the fota file will differ from the BN.
Click to expand...
Click to collapse
Did you actually try this. I'm curious where you found the fota file since I don't see a similar file on the Kindle Fire. What was the fota file named and what database was it in that you found that had this option in it?
Solution 2 Yet to be proved?
Thanks to Glasairmell for this solution. However, someone said it's still to be tested until the next update is out, so not sure yet.
Click to expand...
Click to collapse
Many have made this change, but until the next update, nobody will really know.
There is no sure fired way that I've seen to prevent the next update.
Actually, there is a sure fire way... just turn off your WiFi connection. Without that, you can't get the update. Makes the device a bit useless at that point, but...
Did you actually try this.
Click to expand...
Click to collapse
Nope, thought he was sure about his advice. That's why I also wrote obviously, as I'm not sure. Maybe I should add it later after I've tried.
Many have made this change, but until the next update, nobody will really know.
Click to expand...
Click to collapse
Yes? Isn't that exactly what I wrote?
Actually, there is a sure fire way... just turn off your WiFi connection.
Click to expand...
Click to collapse
Without WiFi my Kindle would be... totally useless. No browsing, no news, no downloading... can't see the reason anymore. If I had to choose, I would rather loose root and have WiFi
Yes krelvinaz is correct. Some of the solutions above are not really proven solutions until we see what happens with the next update.
I heard that when somebody did that while off of wifi before the update, it didn't work.
Sent from my Kindle Fire using Tapatalk
Could we find the source of the update alerts/files and block them via the hosts file?
EDIT: looks like updates come from https://s3.amazonaws.com/kindle-fire-updates/update-kindle-6.2_D01E_3003020.bin
So, if we add s3.amazonaws.com, we should block the update from downloading.
Edit 2: added to my own hosts. Now we wait.
Sent from my Kindle Fire using xda premium
I'm about to receive an un-sealed KF next month, that means it's still on 6.1 (I guess), so can you guys recommend the most effective solution to disable update ? I will try and report later (if 6.3 has't come out yet)
So, if we add s3.amazonaws.com, we should block the update from downloading.
Click to expand...
Click to collapse
Excuse me, but how can I do this ?
mr_gem said:
I'm about to receive an un-sealed KF next month, that means it's still on 6.1 (I guess), so can you guys recommend the most effective solution to disable update ? I will try and report later (if 6.3 has't come out yet)
Excuse me, but how can I do this ?
Click to expand...
Click to collapse
You must have root. Use your favorite root file viewing tool, navigate to /etc, open the hosts file in the text editor and add a new line at the bottom of the file that contains the following
Code:
127.0.0.1 s3.amazonaws.com
What this does is redirect any requests to s3.amazonaws.com to 127.0.0.1, aka localhost (your kindle), causing a timeout.
EDIT: alternatively, you could use an application such as AdAway and add it to the blacklist through such a app as well. Most android ad blockers work by modifying the hosts file.
Sent from my Kindle Fire using xda premium
kjwalker said:
You must have root. Use your favorite root file viewing tool, navigate to /etc, open the hosts file in the text editor and add a new line at the bottom of the file that contains the following
Code:
127.0.0.1 s3.amazonaws.com
What this does is redirect any requests to s3.amazonaws.com to 127.0.0.1, aka localhost (your kindle), causing a timeout.
EDIT: alternatively, you could use an application such as AdAway and add it to the blacklist through such a app as well. Most android ad blockers work by modifying the hosts file.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
i did this then opened a browser and put in s3.amazonaws.com and it still loaded... rebooted, same thing so i would say this doesn't work
screwyluie said:
i did this then opened a browser and put in s3.amazonaws.com and it still loaded... rebooted, same thing so i would say this doesn't work
Click to expand...
Click to collapse
I am skeptical that this will prevent the OTA (simply could come from another source), but when I added this to the hosts file, the site will not load using that URL.
In the silk browser... Web page no available.
In Opera Mini... Network problem loading site.
So I am guessing you didn't do something. ??
Hello,
I've had my NST rooted with TouchNooter and used it mainly for Ankidroid app. Some time ago 1.2.1 update sneaked through, rendering rooting inactive. Afterwards I've rooted it again with NookManager, but now Ankidroid crashes. I've been wondering whether some other users here are using Ankidroid on NST and whether they had any problem after the latest update of software (particularly those using NookManager).
Cheers
Hello gliomarto,
Please install the SendLog app, and execute it just after the crash.
Then post the resulting log here.
Thanks for your feedback!
Nicolas Raoul
Nicolas Raoul said:
Hello gliomarto,
Please install the SendLog app, and execute it just after the crash.
Then post the resulting log here.
Thanks for your feedback!
Nicolas Raoul
Click to expand...
Click to collapse
Hello Nicolas, thanks for this incredible app, i just rooted my Nook Simple Touch and was eager to try AnkiDroid on e-ink but unfortunately something goes terribly wrong which led me to this thread.
I also happen to have my device running 1.2.1 rooted with NookManager and here is my issue:
Ankidroid downloads my deck and all goes well up to a point where i tap "Start reviewing" button. The screen blinks and nothing else ever happens;
upon returning back the app displays an input to send an error and feedback, no matter which deck I choose.
I attach is my log from SendLog, the issue starts at 19:37:29
Hello Nicolas,
I'll join in to thanks for that extremely useful app.
I've attached the log, hope it helps.
I have the exact same issue as Imarooned (I hope he will forgive me relief I feel hearing that I'm not the only one having that problem). It is worth noting that the crash caused by this situation — after attempting to review any deck it blinks and sends me back to default deck (I guess it would send to the first in the list, were there another), and after attempting to go back crashes. It is also may be worth noting that crash sends report(s) about issue 1253 that was presumably fixed some time ago.
Cheers
gliomarto said:
Hello Nicolas,
I'll join in to thanks for that extremely useful app.
I've attached the log, hope it helps.
I have the exact same issue as Imarooned (I hope he will forgive me relief I feel hearing that I'm not the only one having that problem). It is worth noting that the crash caused by this situation — after attempting to review any deck it blinks and sends me back to default deck (I guess it would send to the first in the list, were there another), and after attempting to go back crashes. It is also may be worth noting that crash sends report(s) about issue 1253 that was presumably fixed some time ago.
Cheers
Click to expand...
Click to collapse
And me third, exactly the same problem.
Anyone know what version of AnkiDroid should work on the Nook Touch? Also does the Nook need to be upgraded to 1.2.1 or will 1.2.0 work?
shard said:
And me third, exactly the same problem.
Anyone know what version of AnkiDroid should work on the Nook Touch? Also does the Nook need to be upgraded to 1.2.1 or will 1.2.0 work?
Click to expand...
Click to collapse
I use AnkiDroid v2.0.1 and it works fine on FW 1.2.1 (it should also work on 1.2.0).
I've tried upgrading to 1.2.1 to get it to work
I've done a factory reset, put the 1.2.1 zip file on, it's ignored. It seems something in the rooting process stops the upgrade working.
I then tried the 8 failed reboots approach, same problem.
Anyway of forcing the upgrade in? The main thing i want the ereader for is Ankidroid
gliomarto sorted me out with a version that worked
Just need for that fix to be included in the official releases now
shard said:
gliomarto sorted me out with a version that worked
Just need for that fix to be included in the official releases now
Click to expand...
Click to collapse
Is there a way for me to get that version? I just rooted my Nook just for this (LCDs are giving me more eyestrain headaches) and am having the same problem.
Imarooned said:
Ankidroid downloads my deck and all goes well up to a point where i tap "Start reviewing" button. The screen blinks and nothing else ever happens;
upon returning back the app displays an input to send an error and feedback, no matter which deck I choose.
Click to expand...
Click to collapse
The same problem was solved by checking the box: Preferences->Reviewing->Fade Scrollbars (Automatically fade out flashcard scrollbars when not scrolling).
P.S. AnkiDroid-2.0.2
Hey all,
The other day Read It Later stopped updating with the Pocket website online. I'm getting a dialogue that it is syncing lists but nothing else is happening, even if I leave it to try for half an hour. I'm wondering if anyone else is experiencing this!
I'm running a rooted Nook Simple Touch with software version 1.1.0.
Read It Later is the Pro 1.3 version.
I should be clear, the app is no longer downloading new articles or taking them out of the to-read queue when syncing. It is accessing my archive, so some kind of connection is still present!
Edit: found it elsewhere on this site. Will fire it up this evening and let you know if it works!
Actually I came here today hoping someone might share a copy of readitlater.apk with me? My NST recently broke, I bought another, but sadly hadn't backed up all my apks and so now can't get at anything! Pocket are refusing to send me the apk of the old version. If you would be willing to send me your apk, I can see if it works for me -- or if it is now indeed borked for everyone. [I did pay for read it later pro back in the day, I am not trying to nick something, though you'll just have to take my word for that....]
bonacieux said:
Edit: found it elsewhere on this site. Will fire it up this evening and let you know if it works!
Click to expand...
Click to collapse
Any update, bonacieux?
jasonmehmel said:
Any update, bonacieux?
Click to expand...
Click to collapse
Sorry -- still alive here, but life has been unexpectedly busy and I haven't been able to play with my nook. Hopefully this weekend.
Here's my current workaround: I use IFTTT to sync any new Read It Later addittion to Instapaper, and then I use Instafetch (which works on the Nook) to read them there. The free version lets you read 10 articles at a time.
The issue with this is that I need to check off the read articles in Read It Later, since the activities in Instapaper don't sync back to Read It Later.
But there might be an IFTTT receipe for that...
So, did y'all see this post?
I had not. I had followed that thread to get the Kindle working, but it looks like whatever the problem was went beyond Kindle. I followed the directions, starting using the 1.0.1 app instead of 1.3 Pro, and it's syncing again! Hooray!
Read it Later / Pocket was probably my heaviest usage of the Nook so I was really wondering what I was going to do if it was terminally gone.
(My Instapaper -> Instafetch workaround was a bit glitchy...)
Anyone following this follow nmyshkin's link!