This is strictly a kodi question if anyone can assist.
My living room install running latest 15 runs problem free. The bedroom, same version, starts with "error! failed to start common cache". This has happened in the past and I was able to fix it, but didn't feel like doing trial& error nor posting a log a the org so I just made a backup of my living room setup and restored it to bedroom.
BUT, I had some issues along the way
1. When I tried to restore the backup it gave a warning that this was a different version of kodi (No, It is not, I doubled checked to make sure. Both are 15 released on july 21st) I went ahead and restored it anyway.
2. Eventhough kodi has no obvious performance issues, restoring a backup from the working setup did not fix the "failed to start common cache" issue right after kodi boots up.
Can anyone explain how this is possible? And just an added detail--before I did the backup and restore I attempted to delete the "commoncache.db" file because it's worked in the past. But of course that did nothing. I'm not overly stressed out because kodi runs fine. I can watch videos as long as i want without any crashes and it's actually been buffer free from online and local sources. It's just an annoyance to see that error overtime. Thanks.
Common Cache Problem with me to using Kodi.
I am using 15.2 RC1 issue of Kodi. I have deleted the commoncache.db myself as well.
Does your copy not close properly? Does it seem to take forever to shut down like 30 seconds or so.
When browsers close they can delete cache files. I am wondering if there is a cleanup going on with Kodi closing.
If Kodi freezes on closing maybe there is an issue there. Kodi does not ever close well except when you first install it.
After a few add-ons and slow it goes from there on. Have you gotten any further with your problem. I need to solve
this annoying problem to. Thanks..
-------------------------------------------------------------------------------------------------------------------------------------------------
My living room install running latest 15 runs problem free. The bedroom, same version, starts with "error! failed to start common cache". This has happened in the past and I was able to fix it, but didn't feel like doing trial& error nor posting a log a the org so I just made a backup of my living room setup and restored it to bedroom.
BUT, I had some issues along the way
1. When I tried to restore the backup it gave a warning that this was a different version of kodi (No, It is not, I doubled checked to make sure. Both are 15 released on july 21st) I went ahead and restored it anyway.
2. Eventhough kodi has no obvious performance issues, restoring a backup from the working setup did not fix the "failed to start common cache" issue right after kodi boots up.
Can anyone explain how this is possible? And just an added detail--before I did the backup and restore I attempted to delete the "commoncache.db" file because it's worked in the past. But of course that did nothing. I'm not overly stressed out because kodi runs fine. I can watch videos as long as i want without any crashes and it's actually been buffer free from online and local sources. It's just an annoyance to see that error overtime. Thanks.[/QUOTE]
KLit75 said:
This is strictly a kodi question if anyone can assist.
My living room install running latest 15 runs problem free. The bedroom, same version, starts with "error! failed to start common cache". This has happened in the past and I was able to fix it, but didn't feel like doing trial& error nor posting a log a the org so I just made a backup of my living room setup and restored it to bedroom.
BUT, I had some issues along the way
1. When I tried to restore the backup it gave a warning that this was a different version of kodi (No, It is not, I doubled checked to make sure. Both are 15 released on july 21st) I went ahead and restored it anyway.
2. Eventhough kodi has no obvious performance issues, restoring a backup from the working setup did not fix the "failed to start common cache" issue right after kodi boots up.
Can anyone explain how this is possible? And just an added detail--before I did the backup and restore I attempted to delete the "commoncache.db" file because it's worked in the past. But of course that did nothing. I'm not overly stressed out because kodi runs fine. I can watch videos as long as i want without any crashes and it's actually been buffer free from online and local sources. It's just an annoyance to see that error overtime. Thanks.
Click to expand...
Click to collapse
Finally, I figured out a solution...
Settings>My add-ons>Services>Common plugin cache>Configure>turn off Auotstart with XBMC. Restart Kodi and that annoying error should be gone. Haven't noticed any ill-effects. I assume common plugin cache will be utilized, it just won't autostart with Kodi.
Hope this helps!
so you didn't fix the issue you just hid the messages
Had the same issue went to settings for commoncache and changed port from 59995 to 0 i believe port 0 is always open and hey presto no more problems with failed to start commoncache
Related
[Q] "The application is not registered" error when I launch kindle reader. Ugh.
Very few search results for this error, so I'm out of ideas. It has come up once before but the thread is closed -->
http://forum.xda-developers.com/showthread.php?t=1356441
My reader worked fine for 8 months. Then it updated to version 3.7.0.108.
Now when I click any of the "tabs" such as home, archive, on device, etc... I get this:
"The application is not registered. Trying to register it now. Please try again in a few seconds..."
No book will open, I get an "Invalid Item" error and it suggests I redownload it.
I have a rooted 1st generation KF with GoLauncher on it and ...I dunno if it's a custom rom or what.
I get a blue kindle fire logo when I first power up. I just installed the recommended stuff with the Kindle Fire Utility.
Fixes I've tried:
1. Restarting the device
2. Force stopping the app, then clearing the cache.
3. Going to the play store and choosing "Uninstall". The problem is, this doesn't really uninstall the app, it says something like "this will uninstall all updates to the kindle reader". If I go to settings --> applications, the option to fully uninstall is grayed out.
After doing the google play 'uninstall', the device freezes if I try to launch the reader.
4. Manually reinstalling/updating via the google play store. Now it launches and the device doesn't freeze, but I still get the errors. Also my books are gone but that's no biggie.
I also called tech support. They had me unregister my device from settings --> My Account... and eventually re-register it.
They also had me clear cache. Then those things didn't work they elevated me to level 2 tech support.
I foolishly mentioned I had the go launcher installed, they refused to help any further and insisted the 3rd party launcher was the cause of the problem, and my only fix is to factory reset and stick to the stock software.
So, if you made it this far, thanks for listening... now what?
If you have Root Explorer (or equivelent) for access to system apk files, you could try deleting that app from the /system/app folder, restart the device, go back to the system apps, paste another copy (or version) of that app in there and set permissions to match the other apks in the folder, reboot and hope it might correct the issue. It sounds like a software glitch from the getgo even on un-rooted devices.
howdy, thanks for the idea.
I have root explorer and root access, but when I go to rename or delete anything in that folder, I get "the file cannot be renamed because the file system is read only".
Also, I'm only assuming it's the app called "Kindle for Otter" which is the only one with the traditional kindle reader icon of a dude under a tree reading.
Is there an alternative reader that's still very convenient? Like I don't have to download books via USB or anything, it just monitors the appropriate folders and my freshly-purchased books appear in the list?
CreeDo said:
howdy, thanks for the idea.
I have root explorer and root access, but when I go to rename or delete anything in that folder, I get "the file cannot be renamed because the file system is read only".
Also, I'm only assuming it's the app called "Kindle for Otter" which is the only one with the traditional kindle reader icon of a dude under a tree reading.
Is there an alternative reader that's still very convenient? Like I don't have to download books via USB or anything, it just monitors the appropriate folders and my freshly-purchased books appear in the list?
Click to expand...
Click to collapse
You must just be rooted and not have any custom ROM installed otherwise you could mount the system/app folder as r/w, meaning you probably don't have Superuser installed? Superuser is supposed to be installed when you root the device with the Kindle Utility but I couldn't get it to do it. Since you are rooted then you could try the MoDoCo ROM as it is based on Amazon's own 6.3.1 software and includes the Kindle Reader, Amazon app store and everything that is included with the stock software. In addition it includes the Google services framework and Playstore so you can have the best of both worlds, Google and Amazon. It runs much better than stock and I just flashed it onto my wife's Kindle and she is pretty satisfied with it.
There are plenty of decent reader apps and my suggestion would be try many different ones until you find a suitable one.
Josepho1997 said:
Actually, you just have to click the button on the top of root explorer. It should says "Mount R/W" Click it. Now you should be able to delete it and replace it.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
Yes that is true but if Superuser (or equivelent) isnt present it doesnt work to well
Well, the mountR/W thing worked, and since then I've gone through a bunch of stuff.
And I'm back to square one. But read anyway if you're bored.
I'm a the point where I could reluctantly nuke everything and start over, I guess that would involve reflashing the rom
and reinstalling all apps?
Here's what I've tried:
• Replaced kindleforotter.apk, set permissions, and rebooted, when the kindle came back up it went straight to the stock launcher... weird.
Maybe cuz GoLauncher coincidentally updated.
• At this point I should click that APK, right? But, curious, I went to my books tab.
All my books are there but missing covers. Some have a down arrow/download icon, others don't.
• 4 books without the icon successfully redownloaded after an error, and were readable.
Sadly these are all older books and the other 20 or 30 books would not do anything when tapped.
• Next I tried reinstalling the app by clicking the kindleforotter.apk I downloaded. It reinstalled, I rebooted,
clicking the shortcut still doesn't work but I went back to the books tab in my kindle launcher.
Now, none of the items launch. The "Invalid Title" items give that error again, but this time they do not redownload.
• I tried removing everything from sdcard/Books and sdcard/Kindle and rebooting. Now only those 4 'lucky' books show up.
But they no longer open when tapped. Looks like it's trying to launch the reader but it crashes.
• Tried manually resending the latest book to my kindle via Amazon's website. It didn't show up.
• So I clicked Sync under my settings icon, and that really hosed it. The kindle launcher would infinitely crash and reopen.
• Since that's worse than the original issue I just updated the reader via the play store, getting myself back to square one.
Thanks if anyone has any other ideas... or some less painful way to reinstall this app completely without wiping out everything.
Sounds like a big mess.....you might just have to start over from scratch. At least that "should" clear up the misc. errors you're receiving. You'd have to re-root if but that process is simple. Reinstalling apps might take a little time but would be worth it if it corrects the issue. The Kindle's stock software (or any software) is not immune to undesirable performance.
One basic correction attempt with software and operating systems is to wipe it clean and re-install. I've had many PCs that had to be wiped and the OS re-installed to fix messed up stuff. Usually we try to re-install apps first to see if it corrects it......sounds like you've already done that.
You could always just find an alternative reader
Howdy... I went ahead and tried support one more time (sometimes you get lucky) but they had no ideas other than a factory reset. I'm gonna look into modaco.
edit: on the off chance you come back to this thread,
I factory reset, installed modaco via TWRP, have one problem.
Books work fine. But I can't access my apps.
When I click the "Apps" tab at the top, the screen flashes briefly and then I'm right back to the usual home screen
(aka the default kindle launcher screen).
I seem to remember a notification (with an amazon icon) about pending app downloads, in the bar at the top.
I skipped over it to check on my books. Now it's gone, and I can't get it back or view a list of apps on the system.
What gives?
CreeDo said:
Howdy... I went ahead and tried support one more time (sometimes you get lucky) but they had no ideas other than a factory reset. I'm gonna look into modaco.
edit: on the off chance you come back to this thread,
I factory reset, installed modaco via TWRP, have one problem.
Books work fine. But I can't access my apps.
When I click the "Apps" tab at the top, the screen flashes briefly and then I'm right back to the usual home screen
(aka the default kindle launcher screen).
I seem to remember a notification (with an amazon icon) about pending app downloads, in the bar at the top.
I skipped over it to check on my books. Now it's gone, and I can't get it back or view a list of apps on the system.
What gives?
Click to expand...
Click to collapse
That's odd......I never experienced that with MoDaCo. Did you wipe everything before you flashed MoDaCo (cache, dalvik, factory reset and system)? There were slight bugs with MoDaCo I noticed but nothing like that. Try reflashing but dont wipe sd card
guitarman2010 said:
That's odd......I never experienced that with MoDaCo. Did you wipe everything before you flashed MoDaCo (cache, dalvik, factory reset and system)? There were slight bugs with MoDaCo I noticed but nothing like that. Try reflashing but dont wipe sd card
Click to expand...
Click to collapse
I'll see if I can do that. One worry I had... I see modaco is offered in more than one place, and seems to have some options with the installation...
can you point me to a specific zip file that you know for sure is a good working one? Otherwise, I'll assume my zip is good but my wipe wasn't. I just factory reset and never messed with dalvik and the rest, I'm guessing that's all important...
CreeDo said:
Very few search results for this error, so I'm out of ideas. It has come up once before but the thread is closed -->
http://forum.xda-developers.com/showthread.php?t=1356441
My reader worked fine for 8 months. Then it updated to version 3.7.0.108.
?
Click to expand...
Click to collapse
I had the same problem. Solved it by going back to an earlier version of the app.3.6.0.87.
Hey, just wanted to thank you, I reinstalled modaco, but first did the cache wipe and dalvid wipe from the TWRP menus. Apps tab works fine now. Books too.
So far only one minor hiccup... the apps I had formerly installed via GoLauncher. I logged into google play, redownloaded one of them (DrawSomething) and specified that it send the app to my Kindle Fire from the dropdown. It gave me something like "this app will be installed shortly". But I never got anything... no download, no notification. Did it a second time and same deal. Eventually I downloaded it from the Amazon app store, but I'm worried apps from Google Play won't work easily anymore.
Do you know what I should do if I need an app from Google Play?
Had same problem
In case it helps anyone else. I had the same problem. Turns out that the google play store (which remember doesn't come standard with a Fire) had updated the Amazon Kindle application. I went into the play store and uninstalled (un-updated) the Amazon Kindle app and then everything worked.
Good Luck!
Old version solved it!
mochamoo said:
I had the same problem. Solved it by going back to an earlier version of the app.3.6.0.87.
Click to expand...
Click to collapse
I have a rooted 1st gen KF running a cyanogen ICS ROM where the Kindle app had been working fine for a while, but suddenly wasn't registered and I couldn't even get the register dialog to display. Found the 3.6.0.87 apk online, installed it and it works fine now.
FYI 3.6.0.87 works on non rooted
pofigster said:
I have a rooted 1st gen KF running a cyanogen ICS ROM where the Kindle app had been working fine for a while, but suddenly wasn't registered and I couldn't even get the register dialog to display. Found the 3.6.0.87 apk online, installed it and it works fine now.
Click to expand...
Click to collapse
This fixes the same problem for non-rooted Kindle Fires where you are running an sideloaded launcher and the Kindle book app and need to reregister.
Since recently, my kindle fire space have been losing. From yesterday, I lost 0.01 of a GB. Is that normal? Because it just started recently. In addition, I could not find any app that is causing this. I searched the recent app that i ran and it appears that it have the same amount of space (Oh btw, its the app space that is increasing). What is causing this? Why didn't it happen before?
Update:
Today, I witness it and now I'm sure something is wrong. When i turned off wifi today and went to storage. I was shocked to find that it went down from .81 to .76. The app space dropped too! It i checked it only 5 min before and it was .81. This is weird! I decided to take my time and find out all of the app that is taking up space. The only few I found are related to amazon that is taking up ridiculously large amount of space. I doubt it is amazon app that is causing this because it never occurred before. Help?
Thanks
Maybe do a factory reset if you're running stock or a fresh full clean flash for a custom ROM.
guitarman2010 said:
Maybe do a factory reset if you're running stock or a fresh full clean flash for a custom ROM.
Click to expand...
Click to collapse
Yeah, that is an easy method. But i sideloaded many app and I am looking for another answer. This is why I'm on the forums.
https://play.google.com/store/apps/details?id=com.google.android.diskusage use this and give me screenshot.
Maybe you have a "System Data" - its not a system data) its TEMP files and files form check fs.
This files in /sdcard/.android_sequre (you know how this write ) and big size. And files in /sdcard/FOUND.....
This Files delete from PC in USB-disk mode (example from recovery)
make a titanium backup, and put it on your computer. then reset and get ti backup again and reinstall the backed up apps.
Devices:
Kindle Fire with AlienDroid primary and Modaco secondary
Mount your device's sdcard on your computer, then run a program like DiskInventory X for Mac or WinDirStat for Windows on it.
You may find application data files that are pretty huge. Uninstall the app and delete the file.
After hours of testing and clearing data. I found that American Device client platform (ADCP) and Amazon WebRunTime is constantly getting data. How is this be? Only started occurring recently. Maybe that is normal and something else is causing this? Does this indicate a virus? Because if its not virus, I really dont want to spent more time on this. Take some space i'm fine. Because I'm spenting too much time on this problem.
I did a factory reset. Yet the space is still decreasing. ???
is it normal? Because its amazon app that is taking up the space.
So I have a KF running twa_priv's CM10/sgt7 20121112 build. I was watching a movie on the Freedi Youtube downloader before a parade this morning with headphones. I pulled them out and turned the screen off because there were floats approaching. After the ~2 hour parade, I tried turning it on. It had gone to a(n?) SOD, so I just restarted it like I always do and held down the power button for 10 seconds. I turned it back on and let it run. About 3ish minutes later I look at it and it is still on the blue CM circle bootloader. I forced it off by another 10 sec hold on the power button, then went into TWRP (2.2.2.1) after it turned back on. I chose the fix errors under the advanced option, and also flashed the 20121119 build of the ROM that I had previously downloaded. I wiped cache/dalvik and restarted system. I waited for more than an hour on the CM boot screen before I forced off again. I then went back into TWRP, copied the log to SD, and chose the mount system. I had it connected to my computer, but it didn't show any connected devices, didn't alert me via autoplay choices (or whatever it's called), and when I restarted the adb server, my kindle didn't show up there either. Also, twice during TWRP the KF froze on me and had to force restart. I am sure a complete system wipe would work, but I would rather just have this fixed.
Any ideas?
EDIT------------------------------------------------------------------
And BTW, I have tried reseting the boot menu thingy from initial bootup using the power button which didn't work
Start fresh....save urself some headache
Sent from my SCH-R880 using xda app-developers app
guitarman2010 said:
Start fresh....save urself some headache
Click to expand...
Click to collapse
I know that is the easy alternative, but I have sideloaded so many apps, and have a whole bunch of changed ui options, I am really hoping that there is an alternative.
Maybe Thepooch has some words of wisdom? I think his (your) comments are really helpful, and actually seem to help.
No offense to anyone, especially guitarman2010.
jma9454 said:
I know that is the easy alternative, but I have sideloaded so many apps, and have a whole bunch of changed ui options, I am really hoping that there is an alternative.
Maybe Thepooch has some words of wisdom? I think his (your) comments are really helpful, and actually seem to help.
No offense to anyone, especially guitarman2010.
Click to expand...
Click to collapse
I know nothing compared to Thepooch lol.......I always keep backup apks on my Kindle because I flash different ROMs all the time
.....when you hit the walls of sanity, you have no-where to go.....
I use three different apps for backing up apk file the only downside is significant weight gain. Lots of people use titanium backup I do as well but really only for very little. I also use easy app manager and apk manager but often I`m stricken with considerable consumption of sdcard space so at this point I have scaled back to just using easy app manager for the majority. Things I really want to save I backup on my pc upload to Google drive and dropbox. Seems like overkill but time and time again I will get an update that is horrible and wish revert back to an older version and Google drive and dropbox are a mere download away without sucking away precious and limited kindle space. I don`t believe I know any more than anyone else I just do what is easy for me. I too flash Roms like crazy re-installing is and can be a weekly ritual depending on how smooth things are running. Guitarman2010 is right though A fresh install of your Rom is a very good idea. As for the adb issue there are minor device changes on jelly bean that can affect adb make sure you have the correct settings in developer options. In KFU delete this file and replace it http://db.tt/vXXeuL10 located in the kindle driver folder and reinstall the driver I have been making changes to it with ICS and jelly bean to keep adb working hope it helps.
I usually keep 2 or 3 ROMs handy on the Kindle SD ready to be flashed.......I never take off the Amazon update (6.3.1) just to be safe. My backup apk folder only has 205mb of usage and I use File Expert to make backups of the apks. I too also use the PC for even more backups and 4shared so I can easily transfer apps back and forth from the Kindle to a crappy low-end Samsung phone running Froyo. I'm getting off topic here so I'll shut-up lol
.....when you hit the walls of sanity, you have no-where to go.....
So I wiped cache, dalvik cache, factory reset. I didn't wipe SD card, cause i am hoping to get the files out eventually.Everything seemed fine, but I still can't connect it to the computer! I have it open to TWRP and selected mount, and same as before; no connected devices in device manager, no adb devices, and no autoplay window pops up to let me open files in the drive. I also had the 20121119 cm10/sgt7 in the sd card, so I flashed it, and rebooted, but I am still left at the CM logo. What can I do now? I replaced the file you said to in adb. I happen to have used Titanium Backup, too, a while back, so I have about 2/3 of my sideloaded apps.
Please help!
edit---
I was looking at other Q&A's to help and for help, and saw that Soupkit is recommended to a lot of people.
Would this help me?
OR could I do some sort of terminal commands inside the advanced section of TWRP?
Your kindle isn`t ruined and if your having mounting issues then Soupkit would work great. Before you do anything anything drastic I will take my laptop to work and help you fix your kindle.
I have been trying for the life of me to figure out the way, or if it's possible to keep progress from the game when updating or switching roms. As of now, Titanium Backup doesn't work, or does saving the data/game files and transferring them. Once you try to do either, it says that your unauthorized. Then you have to start fresh and re-download the 2 million gig game and files. I contacted firemonkey and they said rooted devices aren't supported. Don't remember seeing that on play, and it should be. Regardless, I paid for the game.....why am I not authorized to continue progress, and forced to start over from scratch when the newest version of pie is out? There has to be a way to keep progress....?:fingers-crossed:
I'm not sure how much this will help you but maybe it will be what you are looking for:
I recently had a problem where NFS:WM would crash on startup, and apparently the only thing to do (according to firemonkey) is just clear data and lose all progress. Having almost completed everything, I wasn't having any of that.
I'm not rooted but do have my bootloader unlocked so that I can fastboot TWRP to do backups, which also happens to give me root access when booted into TWRP. I made a backup and looked through it to try and and a problem. No luck there, but I did figure out that the game progress is stored in a single file. No config data or anything as far as I can tell, just the progress. So I cleared the data, ran the game through the first level, then copied that old progress file over the new one and I had it back up and going with all progress intact. It's basically a clean install, and since all of the config data is still part of the new install, it didn't cause me any problems.
I did download all of the game data again ultimately, however. But an earlier test of saving "/sdcard/Android/data/com.ea.games.nfs13_na/" and putting it back to avoid the download did work, although it could have been a fluke.
Anyway the file in question is "/data/data/com.ea.games.nfs13_na/files/var/nfstr_save.sb". Just save that one file, install the game from scratch otherwise, run it the first time, then copy that saved progress file over the new one. Assuming that there isn't anything else going on that I didn't find, that should solve your problem.
mtrs said:
I'm not sure how much this will help you but maybe it will be what you are looking for:
I recently had a problem where NFS:WM would crash on startup, and apparently the only thing to do (according to firemonkey) is just clear data and lose all progress. Having almost completed everything, I wasn't having any of that.
I'm not rooted but do have my bootloader unlocked so that I can fastboot TWRP to do backups, which also happens to give me root access when booted into TWRP. I made a backup and looked through it to try and and a problem. No luck there, but I did figure out that the game progress is stored in a single file. No config data or anything as far as I can tell, just the progress. So I cleared the data, ran the game through the first level, then copied that old progress file over the new one and I had it back up and going with all progress intact. It's basically a clean install, and since all of the config data is still part of the new install, it didn't cause me any problems.
I did download all of the game data again ultimately, however. But an earlier test of saving "/sdcard/Android/data/com.ea.games.nfs13_na/" and putting it back to avoid the download did work, although it could have been a fluke.
Anyway the file in question is "/data/data/com.ea.games.nfs13_na/files/var/nfstr_save.sb". Just save that one file, install the game from scratch otherwise, run it the first time, then copy that saved progress file over the new one. Assuming that there isn't anything else going on that I didn't find, that should solve your problem.
Click to expand...
Click to collapse
Awesome. I'll give this a try. :good:
I use MyBackup Pro. I backed up the data and apk from my Nexus and transfered it to me Evo LTE. I restored the apk and data. It does prompt me to reinstall the other game data, which is fine with me. I found if I tried to copy it from one device to the other it would cause the game to crash randomly
Sent from my Nexus 7 using Tapatalk 2
most likely because of the device id (which is the id you see when you type "adb devices" in a command prompt). it's supposed to stay constant in the lifetime of the device (except for factory reset)
I have Kodi 15.2 installed on AFTV1. I few months ago I started getting short of storage capacity, so I plugged in a USB stick and moved Kodi to the USB stick using the AFTV interface. I also moved the Kodi data to /storage/extUsb/Android/data/org.xbmc.kodi/files and modified the file /sdcard/xbmc_env.properties accordingly.
I've been using the trick with IkonoTV and Llama to launch Kodi.
This worked without problems until last weekend. On saturday I wasn't able to launch Kodi using Llama. Solution was using FireStarter instead. This worked fine.
Next problem. After launching Kodi it was looking like a fresh installation, this meant that the Kodi data was not being found.
Then I read the entry in aftvnews on "How to partially or entirely move Kodi data to external USB storage" and found out that for OS 5.0.5 I should be using the path /storage/usbdisk/Android/data/org.xbmc.kodi/files, this means I changed extUsb to usbdisk and modified the file /sdcard/xbmc_env.properties accordingly.
This fixed the problem................ for 3 days
Now I cannot launch Kodi. I just get a black screen and it crashes. I tried renaming the .kodi folder so that a new one is created automatically and maybe I could then copy individual folders in order to find out which one is creating the problems. Surprisingly this worked only once. I tried to do this a second time and it didn't create the .kodi directory automatically anymore. It just keeps crashing. Now I don't know how to continue... any suggestion?
By the way, I tried doing backups of my data with both adbFire and AFTV Utility App but none of them worked. The first one starts but does not finish correctly because I loose the ADB connection after some time (is it because of AFTV screensaver?). The second one tells me "/storage/extUsb/kodi/.kodi does not exist". Any idea on how to get a full backup?
Thank you in advance.
Anyone having similar problems? I was finally able to make the backup of my data so I might try to uninstall and install everything again.
http://www.aftvnews.com/how-to-rest...-after-updating-to-5-0-5-on-1st-gen-fire-tvs/
Thank you. Re-installing and restoring my data fixed my problems. At least for the last few days
i think thispost is more suitable in troubleshooting thread lol but glad you got it resolved