Firmware 6.3 and its bugs!

[hn333]

Originally Posted by Skydog

There will always be bugs on new devices, particularly for first adopters. More important is how quickly such bugs are resolved. Amazon has a pretty good track record, IMO, for addressing customers' concerns. Certainly better than most. That said, if we are still whining about the same bugs months from now my opinion may change.

I really hope people are sending feedback reports to Amazon and not just whining about it here. That said the Android os is just awful.

[sirmaru]

Somehow, I have not seen any of the bugs mentioned here. On the other hand I only use Amazon eBooks and Android Apps approved for the Kindle Fire on the Amazon Store.

I have noticed bugs in some of the Apps like the following for the Tecarta Bible and the fix I implemented which solved it;

Tecarta Bibles' index failed and verses could not be located. Solution was:

1. Go to Settings \ More \ Applications \ All Applications \ NVSB Bible
2. Clear Data under Storage
3. Inside the Tecarta App, Go Menu \ Settings
4. Reset Local Content
5. Then restore font and font size and scroll access and scroll speed.

I also found some bugs in Badass Battery Manager Pro. A simple Shut Down usually fixed it and just clearing the data under Storage as shown above for Tecarta also fixed it when the Shut Down was insufficient.

For you folks, who detected bugs in the Kndle Firmware, have you tried: Settings \ More \ Device \ Reset to Factory Defaults?

[Blossom]

Originally Posted by sirmaru

For you folks, who detected bugs in the Kndle Firmware, have you tried: Settings \ More \ Device \ Reset to Factory Defaults?

Yep that was first thing I did. These are bugs in the firmware and we can only hope a fix is on the way soon.

[Blossom]

Originally Posted by hn333

I really hope people are sending feedback reports to Amazon and not just whining about it here. That said the Android os is just awful.

I emailed them a really long email but haven't heard anything back but at least it should help.

[Skydog]

The only anomalies that I have discovered (and submitted to Amazon) are the inconsistency of covers appearing on personal documents and the inability to sync pdocs both ways between Fire and eink Kindles. Certainly not show-stoppers but a fix would be welcomed.

[Blossom]

Originally Posted by Skydog

The only anomalies that I have discovered (and submitted to Amazon) are the inconsistency of covers appearing on personal documents and the inability to sync pdocs both ways between Fire and eink Kindles. Certainly not show-stoppers but a fix would be welcomed.

Speaking of pdoc covers. I had a pdoc come through last night that had both covers! It was a first for me. I had to do a double take.

[Anabran]

"Somehow, I have not seen any of the bugs mentioned here. On the other hand I only use Amazon eBooks and Android Apps approved for the Kindle Fire on the Amazon Store."

I too am not experiencing any of the reported bugs since they slipped the 6.3 update in on my device.

I am currently running 90 applications
only seven of them are "official" Amazon apps made for the kindle ( pulse, gallery app ,Comixology etc) and those seven are still there only there because I can not delete them without rooting.
The other 83 are all sideloaded android apps & 3D & 2D games.

All of my books are side loaded Epubs that I am reading with Aldiko pro.
and I am running Go Launcher EX with rotating wall paper instead of the ugly stock launcher&Carousel.

So sticking faithfully to the "official" amazon eco-system does not seem to be a factor in the bugs at all
I ordered my kindle on Dec 1 2011.
well after the "preorder' period.

[Blossom]

Originally Posted by Anabran

I too am not experiencing any of the reported bugs since they slipped the 6.3 update in on my device.

I am currently running 90 applications
only seven of them are "official" Amazon apps made for the kindle ( pulse, gallery app ,Comixology etc) and those seven are still there only there because I can not delete them without rooting.
The other 83 are all sideloaded android apps & 3D & 2D games.

All of my books are side loaded Epubs that I am reading with Aldiko pro.
and I am running Go Launcher EX with rotating wall paper instead of the ugly stock launcher&Carousel.

So sticking faithfully to the "official" amazon eco-system does not seem to be a factor in the bugs at all
I ordered my kindle on Dec 1 2011.
well after the "preorder' period.

That's because the bugs are in the Kindle Reader and Launcher if you're not using it then you won't have those issues.

[sirmaru]

Originally Posted by Blossom

That's because the bugs are in the Kindle Reader and Launcher if you're not using it then you won't have those issues.

You just solved your own problem. You have an incompatibility problem between the Kindle Reader and Launcher and your pdocs and calibre converted epub ebooks.

Place an order for a Nook Glowlight coming out on May 1, 2012, and move all your stuff to that device. That is device specific to read epub books and pdocs.

Then only use the Kindle Fire for its apps, videos, etc.

I only read Kindle eBooks and have had no problems with the Kindle Reader and Launcher.

[Anabran]

"That's because the bugs are in the Kindle Reader and Launcher if you're not using it then you won't have those issues."

I see
that makes more sense now
Amazon needs to address this ASAP.

[Blossom]

Originally Posted by sirmaru

You just solved your own problem. You have an incompatibility problem between the Kindle Reader and Launcher and your pdocs and calibre converted epub ebooks.

Place an order for a Nook Glowlight coming out on May 1, 2012, and move all your stuff to that device. That is device specific to read epub books and pdocs.

Then only use the Kindle Fire for its apps, videos, etc.

I only read Kindle eBooks and have had no problems with the Kindle Reader and Launcher.

Wrong it's not solved. I have loaded non calibre docs and they still have issues. The problem is with Personal Documents periods. I have loaded Smashwords, Fictionwise and I have loaded Amazon books that are DRM free sent through the Pdoc cloud plus various sources like mobileread books and almost all have cover issues. So this isn't a Calibre issue.

Why in the the world would I want a Nook?!? How I am going to sync my other Kindles with a Nook? I'd get a T1 before I ever get a nook. B&N is the one store I try to avoid if I can.

My conversion source isn't just epub you know. I use html, Doc, RTF, Lit, PDF and I get the same results no matter what the carousel cover doesn't show or the doc tab cover doesn't show.

I only use my Kindle Fire for reading and have no other uses for it except Goodreads.

[sirmaru]

Originally Posted by Anabran

I see
that makes more sense now
Amazon needs to address this ASAP.

Why would Amazon even want to enable reading of competitor ebooks?. They want a monopoly and, if anything, would probably want to make it even less possible to read calibre converted epub ebooks or run apps to read them.

From the reader's viewpoint, there should be a standard DRM protected eBook design to be able to buy eBooks from anywhere and read them on any device from any manufacturer.

So far as I know, print books never did require just one brand of glasses to read them.

@Blossom,

If you really want perfect compatibility with the AMAZON Kindle Fire, you may have to get used to just buying Amazon eBooks. They have MILLIONS of ebooks almost half of which are FREE. Plus, if you buy Amazon Prime ($ 80 per year), you get one free eBook per month which normally costs money and free 2 day shipping on all Amazon products without any order minimum.

Prior to 1955 I only purchased Book of the Month Club print books. After 1990 I only purchased Microsoft Reader eBooks. Then I switched in 2007 to Sony eBooks (epub) only. Now I only buy Amazon eBooks. One just has to adjust to the reality of the ever changing eBook market.

[Jessica Lares]

If you would look deep into the Kindle's files, there is a icon that says Otter Beta which pertains to the launcher and reading app.

I decompiled the launcher the other week, It is HUUUUGE. Just one tiny little file gave me 400+ entries of code they stuffed in it.

[Anabran]

"Why would Amazon even want to enable reading of competitor ebooks?. They want a monopoly and, if anything, would probably want to make it even less possible to read calibre converted epub ebooks or run apps to read them.

"

Well as despite what some would think of amazons motives, the fact remains that under that"consumeresque "custom interface resides a 7 inch tablet running android 2.3"ginger bread"

We have the option of staying with Amazons intended gateway to their Ecosystem and user experience/interface

we can sideload and change the appearance for a more "traditional" android user interface
and we can go full on android and root the device leaving amazon behind altogether.

I happy with my $200 USD KF purchase considering we could have been in the same situation as the blackerry playbook buyers who are forced to own a blackberry phone just to "sync" new data and I read the next iteration playbook will prevent sideloading all together.

[Blossom]

Originally Posted by Jessica Lares

If you would look deep into the Kindle's files, there is a icon that says Otter Beta which pertains to the launcher and reading app.

I decompiled the launcher the other week, It is HUUUUGE. Just one tiny little file gave me 400+ entries of code they stuffed in it.

It is uses more resources on my device than anything else. I do think someone slipped up and I hope the fix comes soon.

We will just have to use Work Arounds till then.

For the white cover issue there are two methods.
Sideloading the book first then opening it before sending it as pdoc so the cover will be already created when the pdoc is added or you can Clear the Kindle Data when the server isn't busy.

For two way syncing. You need to remove the pdoc from the Fire and then redownload and it will open up in the correct spot you last read.

Sideloading Books can be done by Force closing the Kindle app. It will force the shelves to reload themselves.

Thanks to all those who have posted these work arounds. You're the best! Please keep reporting the bugs to Amazon via the feedback app or their email: kindle-fire-feedback@amazon.com