Losing Data on Reboot

by droozen » Fri, 10 Apr 2009 21:35:59 GMT


Sponsored Links
 So, I made a mistake and I still had the debug version of my app (from
Eclipse) on my phone when I tried to install a signed version. The
install failed, but I could no longer access the debug version in
Manage Applications to uninstall it. I was at work and couldn't
reinstall the debug version in order to uninstall, so I did a complete
factory reset of my phone (using MyBackup Pro to backup stuff).

Now I can install my app. However, now I notice upon reboot that my
app loses all of its data from shared preferences. I'm not entirely
sure that it's not a problem of mine somehow, but does anyone know why
it is doing that and how I can fix it? I may have left the
debuggable=true on in the version I'm trying to test. Would that cause
this problem?
--~--~---------~--~----~------------~-------~--~----~



Losing Data on Reboot

by droozen » Fri, 10 Apr 2009 22:07:30 GMT


 If it helps at all, I've discovered that this only happens if my
bootup service tries to read certain preferences and install an alarm.
I've used this process to install several other alarms, but for some
reason the latest alarms I've added have been causing me to lose all
my preferences on a reboot.

I'm not doing anything different that I can tell, but maybe there's
some known problem that can caused shared preferences to crash and
disappear like this?



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Losing Data on Reboot

by ellipsoidmob...@googlemail.com » Sun, 12 Apr 2009 02:25:34 GMT


 Are you certain the problem is related to the changes you have made?
Just wondering if there could be a simpler explanation, like you're
not writing the preferences in or before onPause(), or maybe you're
not always calling commit() on the preferences editor?
--~--~---------~--~----~------------~-------~--~----~



Other Threads

1. Power Management on Android

I'm grappling with this:
if one has a device driver that's to be "ported" to Android, are there
any specific steps / guidelines that need to be followed to be
"Android-compliant"?
Or is it just the "usual" Linux driver stuff?

I would imagine some callbacks for PM can/should be hooked into...I
found some doc stating that the callbacks are:
android_register_early_suspend(android_early_suspend_t *handler)
android_register_early_resume(android_early_resume_t *handler)

However these don't even seem to exist in a recent 2.6.29 Android
kernel tree. ?? Are they outdated?

Do we use wake_[un]lock? Is there documentation/guidelines to state
how exactly we're expected to hook into PM stuff in *kernel* space?
(I know abt the PowerManager etc classes in userland).

Would appreciate any help!

TIA,
-kaiwan.

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: 

2. Building kernel for ADP1

Hello group moderator,

I apologize in advance if my question is without merit.  I am trying
to rebuild the kernel for an ADP1. I want to port a touchscreen
driver.

I am cross developing on a linux-x86 platform running Ubuntu.

I downloaded and built the latest android platform using the
instructions at source.android.com/download and source.android.com/
documentation/building-for-dream using the latest instructions for
donut.

I have searched the web and sent a direct question to HTC, for concise
instructions for building a new kernel for the ADP1.

I have purchased and received an ADP1 just last week (Oct 09)

I have downloaded the htc phone kernel source from <developer.htc.com/

I have downloaded the .config file from the phone.

I have noticed in the phone .config, that it used kernel version -.25
vs. -.27 in the msm_defconfig in the kernel source.

I placed the htc kernel source tree into ~/mydroid.  I copied the
phone .config to the kernel root.

I added the toolchain path "home/tes/myfroid/prebuilt/linux-x86/
toolchain/arm-eabi-4.4.0/bin" to my .bashrc and rebooted. After
reboot, echo $PATH shows the toolchain in the PATH.

I then ran the sequence:





The make failed trying to compile board-trout.c:
  CC      arch/arm/mach-msm/board-trout.o
arch/arm/mach-msm/board-trout.c:391: error: 'H2W_UART3' undeclared
here (not in a function)
arch/arm/mach-msm/board-trout.c: In function 'configure_cpld':
arch/arm/mach-msm/board-trout.c:395: error: 'H2W_UART1' undeclared
(first use in this function)
arch/arm/mach-msm/board-trout.c:395: error: (Each undeclared
identifier is reported only once
arch/arm/mach-msm/board-trout.c:395: error: for each function it
appears in.)
arch/arm/mach-msm/board-trout.c:406: error: 'H2W_BT' undeclared (first
use in this function)
arch/arm/mach-msm/board-trout.c:424: error: 'H2W_GPIO' undeclared
(first use in this function)
:
:
arch/arm/mach-msm/board-trout.c:513: error: unknown field 'get_clk'
specified in initializer
arch/arm/mach-msm/board-trout.c:513: warning: excess elements in
struct initializer
arch/arm/mach-msm/board-trout.c:513: warning: (near initialization for
'trout_h2w_data')
make[1]: *** [arch/arm/mach-msm/board-trout.o] Error 1
make: *** [arch/arm/mach-msm] Error 2

Did I miss some steps?

Thanks and best regards.

Kevin


--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: 

3. gdbserver android patch

4. :Training on Advance C and Linux System Programming from Expert

5. What does the "Home" button do?

6. security enforcemen

7. Problem with Wi-Fi connectivity with Android 1.6