search

anusha-gogineni / adw-launcher-android

Automatically exported from code.google.com/p/adw-launcher-android
0 stars 0 forks source link

Unable to backup ADW Settings #333

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Access ADW Settings
2. click Backup and Restore
3. click Backup ADW settings
4. receive error "error backing up ADW settings"

What is the expected output? What do you see instead?
Expected that settings would be backed up successfully :)

What version of the product are you using? On what phone? What Android
version?
ADW v1.3.6 standalone
Phone: Samsung Fascinate (rooted)
Android version: 2.2.1 - issue has existed since installation of any Froyo 
build.  Current ROM/Kernel is ED01 Community ROM v1.1

Please provide any additional information below.

Original issue reported on code.google.com by mike.mcm...@gmail.com on 26 Apr 2011 at 10:29

GoogleCodeExporter commented 9 years ago 
Does this occur in all custom ROMs or is just the one you're using now?

Original comment by rmacg89 on 17 May 2011 at 3:47

GoogleCodeExporter commented 9 years ago 
the issue has occurred with any Froyo build for the Fascinate: EA28, EB01, 
ED01, and EB16

Original comment by mike.mcm...@gmail.com on 17 May 2011 at 4:29

GoogleCodeExporter commented 9 years ago 
Could you grab a logcat when it happens and attach it on this issue?

Original comment by rmacg89 on 17 May 2011 at 4:44

GoogleCodeExporter commented 9 years ago 
took me awhile to get all the components, but the logcat is attached.

Original comment by mike.mcm...@gmail.com on 17 May 2011 at 7:21

Attachments:

GoogleCodeExporter commented 9 years ago 
Attached Ander to this issue so that he can see the logcat

Original comment by rmacg89 on 17 May 2011 at 7:43

GoogleCodeExporter commented 9 years ago 
Same issue here.

ADW v1.3.6 standalone
Phone: Samsung Galaxy S (rooted)
Android version: 2.3.3
Current ROM/Kernel DarkyROM v10.0

Original comment by gdb...@gmail.com on 22 May 2011 at 10:44

GoogleCodeExporter commented 9 years ago 
From memory Ander and the guys at LevelUp have discussed this before and
it's due to Samsung. They moved stuff around and it causes issues like
this...

Original comment by rmacg89 on 22 May 2011 at 10:48

GoogleCodeExporter commented 9 years ago 
I am having the same issue with an official Samsung Android version, 
FROYO.XWJS7. ADW worked fine with the initial version that came with my phone, 
FROYO as well but I don't have the build number any more.

Original comment by khinsen....@gmail.com on 30 Aug 2011 at 7:06