titanium backup force close

[Guest]

Hi all

Is anyone experiencing the latest version of titanium backup force closing on R9 after installation?

[Guest Tomdibom]

I've experienced that since 3.4.6 and went back to 3.4.4. Unfortunately the newest update hasn't changed anything...

[Guest Mr Taylor]

I too have had issues recently with it. is weird, as it worked so well

[Guest Elbereth]

Happens for each upgrade. Deleting data for the app fixed it everytime.

[Guest Tomdibom]

Nope, unfortunately that doesn't help...

[Guest giligen]

Nope, unfortunately that doesn't help...

It worked for me as well... (erasing the data).

Take a look at the "preview" of the Error Report Dump, the stack trace might give you a hint...

[Guest Tomdibom]

Wow - that is one confusing stack track! :lol:

[Guest Keramidas]

Hi,

I would be interested to know whether you did one upgrade of Titanium Backup after another (as they appeared on the Market) without ever going back, or whether you downgraded Titanium Backup at one point.

Upgrades of Titanium Backup should really be smooth, in every case, because its own databases (eg: schedules, custom labels, etc) get upgraded automatically when needed. However, downgrades are not really tested, and might cause problems.

If you have any problem such as Titanium Backup not starting, and that problem is not resolved by un-installing and reinstall my app, it's probably because you have the "Auto sync settings to SD card" checkbox enabled, which makes a copy of the TB settings to /sdcard/data/com.keramidas.TitaniumBackup/. If you delete that directory, these issues shall disappear.

That said, I'm really interested to hear about any un-smoothness that occurs when upgrading my app. I'm personally keeping all settings intact on every upgrade, and never had a problem. But as we know, different things can happen with different users :lol:

[Guest Tomdibom]

It works. IT WORKS!!! I've deleted the application data before but it seems as if the "Auto-Sync"-Feature caused the crashs. I deleted the folder on the SD card, reinstalled the app and everything goes smoothly as always. I love you! :lol:

Oh - and for the record: I haven't downgraded before. The first time I did downgrade was after experiencing the crashs.

Edited September 28, 2010 by Tomdibom

[Guest Keramidas]

It works. IT WORKS!!! I've deleted the application data before but it seems as if the "Auto-Sync"-Feature caused the crashs. I deleted the folder on the SD card, reinstalled the app and everything goes smoothly as always. I love you! :lol:

Oh - and for the record: I haven't downgraded before. The first time I did downgrade was after experiencing the crashs.

Ok, thanks for your feedback!

I'm glad this is resolved now :-)

[Guest Mr Taylor]

It works. IT WORKS!!! I've deleted the application data before but it seems as if the "Auto-Sync"-Feature caused the crashs. I deleted the folder on the SD card, reinstalled the app and everything goes smoothly as always. I love you! :lol:

Oh - and for the record: I haven't downgraded before. The first time I did downgrade was after experiencing the crashs.

Me too, same thing. happy now B)

[Guest]

Ok, thanks for your feedback!

I'm glad this is resolved now :-)

It worked for me too. Thank you so much. Got the donate version and loving it.

[Guest brooknam]

can someone advise me as to where this folder is located, i am having the same issues. tia.

[Guest Tomdibom]

/sdcard/data/com.keramidas.TitaniumBackup/

[Guest Keramidas]

A user sent me a zipped version of his /sdcard/data/com.keramidas.TitaniumBackup folder and I looked at it.

When Titanium Backup is newly installed, it attempts to grab its settings from the SD card (at the aforementioned location) if they exist there.

Then, if the settings were saved by an older TB version, it upgrades them as necessary. It's a database. In this case, the database structure was already upgraded to version 2, but was still marked as version 1 for a mysterious reason. So the upgrade from v1 to v2 is attempted by TB, and it results in a FC.

I have looked at the Android sources and I don't understand how this can happen. The DB schema upgrade and the version number marking are supposed to happen as a single transaction...

[Guest Tomdibom]

I have looked at the Android sources and I don't understand how this can happen. The DB schema upgrade and the version number marking are supposed to happen as a single transaction...

I'd suspect Steve Jobs to have his finger in the pie. :) At least the issue is easily resolvable ...

[Guest Odroid]

I'd suspect Steve Jobs to have his finger in the pie. :) At least the issue is easily resolvable ...

I also had some trouble with fc's and updating apps on R9 WIP.

I'm using A2SD+, and in some cases, like with Titanium Backup, the problem was fixed by moving the app back to the phone from within Android (which is actually the SD-card :-)) and then updating the app again.

[Guest gigimom]

Hi,

I would be interested to know whether you did one upgrade of Titanium Backup after another (as they appeared on the Market) without ever going back, or whether you downgraded Titanium Backup at one point.

Upgrades of Titanium Backup should really be smooth, in every case, because its own databases (eg: schedules, custom labels, etc) get upgraded automatically when needed. However, downgrades are not really tested, and might cause problems.

If you have any problem such as Titanium Backup not starting, and that problem is not resolved by un-installing and reinstall my app, it's probably because you have the "Auto sync settings to SD card" checkbox enabled, which makes a copy of the TB settings to /sdcard/data/com.keramidas.TitaniumBackup/. If you delete that directory, these issues shall disappear.

That said, I'm really interested to hear about any un-smoothness that occurs when upgrading my app. I'm personally keeping all settings intact on every upgrade, and never had a problem. But as we know, different things can happen with different users :)

[Guest gigimom]

No luck with the prescribed fix. TB worked until I made a donation (all of 1 day), received my key. Deleted directory, deleted txt file from SD card. Deleted UniversalRoot and have gone through the entire process again - several times. No luck. Am still receiving 'force close' message. Am stumped. Not very experienced - obviously - and would really appreciate help.

[Guest Elbereth]

Last update from Market (3.5.2) claims to fix this problem. Haven't tested myself (no R9 upgrades since 21/09)...

[Guest Keramidas]

No luck with the prescribed fix. TB worked until I made a donation (all of 1 day), received my key. Deleted directory, deleted txt file from SD card. Deleted UniversalRoot and have gone through the entire process again - several times. No luck. Am still receiving 'force close' message. Am stumped. Not very experienced - obviously - and would really appreciate help.

If you have Android 1.5/1.6 this is normal. The fix I have added to handle the force close we're talking about, involves a workaround to prevent Android from downgrading the version of my database, if we install a lower version of Titanium Backup on top of a newer one. But unfortunately, that fix involves an Android 2.1-only method call, which crashes on Android 1.5/1.6.

The next Market version will fix the Android 1.5/1.6 problem and then everything will be great :)

[Guest Keramidas]

If you have Android 1.5/1.6 this is normal. The fix I have added to handle the force close we're talking about, involves a workaround to prevent Android from downgrading the version of my database, if we install a lower version of Titanium Backup on top of a newer one. But unfortunately, that fix involves an Android 2.1-only method call, which crashes on Android 1.5/1.6.

The next Market version will fix the Android 1.5/1.6 problem and then everything will be great :)

This problem should be history now. If anybody sees it again, please let me know.

Thanks!