File name settings not "sticking"

[PatNY]

Originally Posted by chaley

First, note that the new default comes into play only if you have checked no boxes in Settings / File names and you use the content server or cloud connection. With no boxes checked the wireless device is given the file name by calibre, which computes it using the template in the wireless device settings. The calibre template by default has ({id}) in it.

If you check the use template box then the template you enter will be used everywhere in CC. The template in calibre is ignored. Given the situation you describe it is a good idea to remove the ({id}) from the template.

I just noticed today that the file name settings in CC on my 2 Lollilpop devices aren’t sticking. They are fine on KitKat. On the Lollipop devices, I repeatedly set it to “Use CC template everywhere” and when I reopen CC, “Use calibre’s file name” is always checked.

When I first saw this thread, I thought I should check the file name settings in my main Android device (on Lollipop). I noticed “Use CC template everywhere” was not checked, even though I thought that’s what I had chosen in the recent past. So I was confused as to what the settings should be, and that’s what prompted me to ask what the best practices were for these settings going forward. Based on your answer, I went back and chose “Use CC template everywhere.” But checking this morning, I see that it didn’t stick. Repeated testing on my two Lolllipop devices showed this to be the case. But my KitKat devices are fine. This probably has been the case since I got the two Lollipop devices late last year, but I just didn’t notice it before.

All my devices are running CC 4.3.44.

Is this a known problem with installations on Lollipop that has been discussed previously and I just missed it?

(I didn’t know if this belonged in a new thread. Please move it if this is not the appropriate place.)

--Pat

[chaley]

I just tried V4.3.4.4 on 2 Lollipop devices, a Fire new generation and a Nexus 7 2012. In both cases the Use templates everywhere setting sticks. I tried using "back" until the app exited. I "forced closed" the app. I did a backup, reinstalled the app, and restored the backup. I tried checking the other boxes then re-checking the templates box. In all these cases the "Use templates everywhere" remained checked.

Why you are seeing what you see is a mystery. Do you have some kind of auto-backup system in place that might be restoring settings from the cloud?

I can't see what a debug log would tell me, but it is probably worth sending one just in case.

[PatNY]

I just sent you a debug log. If there is nothing that sticks out, I will try completely uninstalling and reinstalling and not use imported settings like I did when I first got these Lollipop devices.

[chaley]

Originally Posted by PatNY

I just sent you a debug log. If there is nothing that sticks out, I will try completely uninstalling and reinstalling and not use imported settings like I did when I first got these Lollipop devices.

The only thing that sticks out is that books are being stored on an SD card in a non CC-private folder (/storage/external_SD/My Files/...). In theory that folder should not be writable and shouldn't work. There were no attempts to connect/transfer/delete in that debug log, so I couldn't see what CC would think.

Have you rooted this device? Did you set the storage folder to be /storage/external_SD/My Files/... using CC's Formats and Folders option on the lollipop machine?

[PatNY]

Yes, both Lollipop devices where I have this issue are rooted. The storage folders on both devices were set manually via CC's format and folders option because when I initially imported CC settings from an existing KitKat installation, an invalid folder path was put into the Lollipop devices.

Also, per your previous question, I do not have any auto-backup system set up on my devices for CC.

Any ideas?

[chaley]

Originally Posted by PatNY

Yes, both Lollipop devices where I have this issue are rooted. The storage folders on both devices were set manually via CC's format and folders option because when I initially imported CC settings from an existing KitKat installation, an invalid folder path was put into the Lollipop devices.

Also, per your previous question, I do not have any auto-backup system set up on my devices for CC.

Any ideas?

No. I can't make it fail, and no one else has reported anything similar. That tells me that it something on the devices is behaving differently, but I can't think of what it could be. It could be that the "rooting" process is preventing CC from storing its settings, but this seems far-fetched. If you are running a cyanogenmod version of Android then all bets are off.

A question that you won't want to answer: does it fail if the device is not rooted?

[PatNY]

No custom ROMs. Both devices are rooted LG stock.

I don't want to unroot to find out if that would fix things. I am going to completely uninstall CC from one of the devices and do a fresh install with fresh settings without using any backups. Maybe that will fix things.

Will let you know.

[PatNY]

On one of my Lollipop devices, I uninstalled CC, reinstalled it from the Play Store, and configured the settings from scratch without using a backup. Everything worked fine. I then reinstalled CC on the second Lollipop device, but this time I imported the settings which I backed up from the newly configured first device. Again, no problems with having the settings stick.

One guess is the problem could have been caused by importing into Lollipop settings which had been backed up on KitKat. Perhaps that somehow screwed up the settings.

Another thought is that it was due to the fact the two Lollipop devices were syncing with Calibre using the same device name, and that somehow this messed up the settings. They are identical LG phones, and I only realized today when configuring the first device that they had been syncing with the same name. It never dawned on me that maybe I should give them two separate names in CC’s settings, which I have now done. Could that have confused the settings and caused the issue?

[chaley]

Originally Posted by PatNY

On one of my Lollipop devices, I uninstalled CC, reinstalled it from the Play Store, and configured the settings from scratch without using a backup. Everything worked fine. I then reinstalled CC on the second Lollipop device, but this time I imported the settings which I backed up from the newly configured first device. Again, no problems with having the settings stick.

One guess is the problem could have been caused by importing into Lollipop settings which had been backed up on KitKat. Perhaps that somehow screwed up the settings.

I don't see why that should happen. However, clearly it did, and I need to keep an eye out for why.

Another thought is that it was due to the fact the two Lollipop devices were syncing with Calibre using the same device name, and that somehow this messed up the settings. They are identical LG phones, and I only realized today when configuring the first device that they had been syncing with the same name. It never dawned on me that maybe I should give them two separate names in CC’s settings, which I have now done. Could that have confused the settings and caused the issue?

The device name is not used internally by CC. It exists only for the convenience of the user.

More important for syncing is the internal device UUID, which is used to control device caching. This UUID is assigned the first time a device connects after an install or a clear data. It is never backed up or restored.