Kindle For Android Taking up 1GB!

[zebradude]

Originally Posted by Blossom

I figure it's a KitKat bug of some type with the Kindle app. I am not rooted so I wouldn't even know where to look where the database file is kept on the Nexus 7.

The older versions which I do have are not KitKat compatible.

One of the biggest issues with Android is the Fragmentation issue. this is the main reasons I left Android to live in ios.

How can you ever get a APP to live in a environment where you have GingerBread users still out there Honeycomb Tablets still plugging away and the newest greatest crowd Jelly Bean/Kit Kat!

And I know I am ...

sorry "rant off!"

[sirmaru]

If the problem is a bug in the Android firmware version update, then Amazon may not be able to help you.

I just hope Amazon doesn't upgrade our Kindle HDX 2013 to that version of Android. We may encounter the same problem.

I did notice from browsing the Android forum for Nexus 7 2013 that there are lots of problems with the latest Android firmware. One I noticed was the "Sleep of Death" where the Android just shuts down spontaneously.

Here is the link to that thread:

http://forums.androidcentral.com/goo...ing-sleep.html

I've never noticed that problem on the HDX 2013.

Here is a quote from that thrad:

"For some reason my new N7 2013 (my first Android device) is crashing/turning off, but only while its asleep. Its not consistent, but it is annoying. Ive tried resetting to stock but I still have the issue."

[Blossom]

Originally Posted by sirmaru

If the problem is a bug in the Android firmware version update, then Amazon may not be able to help you.

I just hope Amazon doesn't upgrade our Kindle HDX 2013 to that version of Android. We may encounter the same problem.

I did notice from browsing the Android forum for Nexus 7 2013 that there are lots of problems with the latest Android firmware. One I noticed was the "Sleep of Death" where the Android just shuts down spontaneously.

Here is the link to that thread:

http://forums.androidcentral.com/goo...ing-sleep.html

I've never noticed that problem on the HDX 2013.

Here is a quote from that thrad:

"For some reason my new N7 2013 (my first Android device) is crashing/turning off, but only while its asleep. Its not consistent, but it is annoying. Ive tried resetting to stock but I still have the issue."

Yeah My Kindle Fire HD does that at random but not my Nexus it's solid. I know you are trying to help and I thank you but this issue you are posting about has nothing to do with the Kindle App and KitKat 4.4.2 update.

Originally Posted by Blossom

Yeah the play website says 4.2.0.151 but when It installs it says 4.3.0.38 in settings on my N7 so I have no clue why that is.

AnemicOak has the 1st gen Nexus 7.1 rather than the newer 7.2. I wonder if that makes a difference in which app version is available for it?

[Blossom]

Originally Posted by jswinden

AnemicOak has the 1st gen Nexus 7.1 rather than the newer 7.2. I wonder if that makes a difference in which app version is available for it?

According to Amazon the latest version is 4.3.0.38 I was wrong before that there was 4.3.0.36 which I never got. So I can't test that one but I think it's pretty much a given that it's a KitKat 4.4.2 issue.

[DaveSp]

My 2013 WiFi Nexus 7 is on 4.4.2 with latest 4.3.0.44 Kindle app. I have about 225 books loaded on it, including a few very large ones (pictures), and I have 643MB data used, about what I would consider normal. Manual synch has no effect.

Dave

It seems like the Kindle for Android app is the unwanted, bastard child of Kindleland. Amazon usually updates this app long after they have updated the other apps, and it lags way behind in features. Clearly they don't put their A Team on this project. It seems so strange that the iOS app is always lightyears ahead of the Android app. I don't mind of course since I much prefer iOS to Android.

[sirmaru]

Originally Posted by jswinden

It seems like the Kindle for Android app is the unwanted, bastard child of Kindleland. Amazon usually updates this app long after they have updated the other apps, and it lags way behind in features. Clearly they don't put their A Team on this project. It seems so strange that the iOS app is always lightyears ahead of the Android app. I don't mind of course since I much prefer iOS to Android.

Here is a link to the latest iOS 7 problems:

http://www.gottabemobile.com/2013/11...tinue-surface/

It appears all operating systems and all devices have their share of problems. In the end we go with brands we like and either tolerate or work around the problems.

Nothing is perfect.

Some prefer iPads, some prefer Nexus and I prefer Kindles. Each to their own. At least the Kindles are cheaper than the iPads.

Why should Amazon devote more time to improving their apps for competing devices over improving their own devices?

If I purchased a Nexus, I would use friendlier reading apps than the Kindle app and buy my eBooks from sites more friendly to the Nexus. If I purchased an iPad, I'd only read iBooks and only play iTunes - why bother with a Kindle app in those cases?

It appears the only device really needed and not yet on the market would be an eReader marketed by Calibre and specially tailored to their software. There are lots of Calibre users here who are handicapped by not having their own custom eReader fitting all their specific needs.

Kindles fit my needs as they are part and parcel of Amazon which supplies all my other consumer goods needs.

[tomsem]

Originally Posted by jswinden

It seems like the Kindle for Android app is the unwanted, bastard child of Kindleland. Amazon usually updates this app long after they have updated the other apps, and it lags way behind in features. Clearly they don't put their A Team on this project. It seems so strange that the iOS app is always lightyears ahead of the Android app. I don't mind of course since I much prefer iOS to Android.

Amazon has its priorities, and when it comes to Android, their A Team is going to be working on the Fire. They cannot afford for that to fail, as it most likely would if they cut back on Fire development. Hence a relatively mediocre reading app, no Instant Video app, etc. They can get away with this because Android isn't making much money for anyone, and the return on investment is low. Google itself does not seem to expend much energy on Google Play Books, so Amazon doesn't have to do much to match up to it.

iOS gets love because Apple users almost by definition are willing to spend more money than the average person, and ROI is much higher. Many Apple customers are Amazon customers, but at this point they are not going to trade in their iPads for a Fire, and lose access to their iTunes library. So it is important to offer a decent alternative to iBooks and entice with Amazon Instant Video, offer web storefront experiences optimized for iPad, make sure Audible and Amazon MP3 apps can access iTunes library, support Air Play etc.

I would expect an update to the Android app in the next week or two. If you go back and look at the version history, there have been several updates specifically for Nexus 7 issues and this seems to be another one.

[Blossom]

Originally Posted by DaveSp

My 2013 WiFi Nexus 7 is on 4.4.2 with latest 4.3.0.44 Kindle app. I have about 225 books loaded on it, including a few very large ones (pictures), and I have 643MB data used, about what I would consider normal. Manual synch has no effect.

Dave

Oh! It looks like they updated it again! 4.3.0.44 is a new version! Maybe it's fixed! I sent the bug report yesterday.

Oh it now has turn publishers font on and off!

[Blossom]

Nope not fixed in the newest version. I thought it might be but checked 10 minutes later and it doubled in size the continues to grow. Dave you might want to check that Data size again. It didn't do it right away I'm now at 1GB again.

I checked my Kindle Fire and it's Kindle data is at 450MB. I have more books on it so I suspect that is where this Kindle Android app should be around. This is ridiculous!

[sirmaru]

Originally Posted by Blossom

Nope not fixed in the newest version. I thought it might be but checked 10 minutes later and it doubled in size the continues to grow. Dave you might want to check that Data size again. It didn't do it right away I'm now at 1GB again.

I checked my Kindle Fire and it's Kindle data is at 450MB. I have more books on it so I suspect that is where this Kindle Android app should be around. This is ridiculous!

Did you ever think that one eBook is clashing with that app it the way it is stored? Maybe take off all your eBooks and then load them one at a time while checking the data size each time. If one causes the data explosion, then remove it permanently.

An encyclopedia and / or PDF eBook could cause that kind of problem.

No one posting here or on the Android/Nexus 17 2013 forum is reporting a similar problem. Thus, it must be due to something unique on your Nexus. Maybe one of your Calibre formatted eBooks has a formatting error.

Originally Posted by Blossom

Nope not fixed in the newest version. I thought it might be but checked 10 minutes later and it doubled in size the continues to grow. Dave you might want to check that Data size again. It didn't do it right away I'm now at 1GB again.

I checked my Kindle Fire and it's Kindle data is at 450MB. I have more books on it so I suspect that is where this Kindle Android app should be around. This is ridiculous!

With Android 4.4.2 build KOT49H installed and Kindle 4.2.x.x installed, 89.91 MB of data.

After installing, but prior to running, Kindle 4.3.0.44, 90 MB of data.

After initially running but not syncing Kindle 4.3.0.44, 100 MB of data.

After running and syncing Kindle 4.3.0.44 about a dozen times, 102 MB of data.

I don't seem to be able to replicate the error/bug. However, note I do not use calibre to create anything. All my docs are built with Sigil and Kindle Previewer. Books of course are pure Amazon. No docs are side loaded. All docs were put in Cloud via Send To Kindle app.

[Blossom]

Originally Posted by sirmaru

Did you ever think that one eBook is clashing with that app it the way it is stored? Maybe take off all your eBooks and then load them one at a time while checking the data size each time. If one causes the data explosion, then remove it permanently.

An encyclopedia and / or PDF eBook could cause that kind of problem.

I have no books on the app at the moment.

Originally Posted by Blossom

I have no books on the app at the moment.

Any personal docs loaded yet? If so, did you create them with calibre? Did you side load them directly onto the Nexus 7.2 or send them to the Kindle Cloud?