Database Develop

[Q] Do you have to wipe out your user data frequently due to data lose?

I have found out that many people is having problems with at least NAND installations losing data from time to time. I saw myself rebooting and experiencing "Force Closes" and missing applications/data/configurations.*
This seems to happen with every build I tested, and it's especially prone to happen when you have to soft reset the device due to a "random" hang (console screen with mirrored text) or for any other reason. Well, this actually happened to me even when powering it off normally.
Is is a problem with the NAND blocks that get corrupted somehow? Have you had this problem?*
Please, give your feedback: this is a major issue.

I haveexperienced the problem many times. It usually starts with google framework exception and then half of the apps FC.
Sent from my European Vogue using XDA App

I have this with incubus builds..
It happend often to me when the device turned off due to a surprising 15%->off ;D
Im running freshfroyo (odexed i think 26.7) for a while now and it looks good, i had some resets but still all data available and no fc.
It looks like a problem with useraccounts??.. Often i had to do the first start wizard but after this there were some apps as leftovers not in the app manager or market but in the launcher and dont work => only help to wipe data.

can nothing add, besides i have exact same experiences on nand with different builds!

I have this issue. In the boot screen it actually says its cannot find data blah blah blah. I have not wiped my data in some time and have been considering that as a solution, butI hate to loose all my hard work setting up my phone.

I have never had this problem on my vogue, though I do change/upgrade to new releases. However I have ran a couple builds for 3 or 4 months and never had this problem.

it also happens to me but more complicated... my Kaiser stuck on android splash screen and won't start...if i reset , it stuck at Android boot - just after boot menu ... and i am trying to reinstall system but androidinstall file deleted - system can't find....
and more interesting - if kaiser can boot somehow with itself , it returns to old builds that i complete deleted from system and SD... i am using VanilijEclair 10B and it returns to VaniljFroyo

Hi! I've finally "NANDed" my device with the DZO fresh Froyo about two weeks ago. And I think it's really OK. But in this two weeks I've experienced 3 situations like this.
- first time after a FC needin' to soft reset; after the reboot I had to reinstall the system and wipe my data to solve the problem definitively;
- second and third time (last just yesterday) I've found my contact canceled apparently without reason; I've had to go in Application / Contact / Erase Data and resync my device. Now all seems to be OK;
TY for all and bye-

Market Force Closes...How Do I Stop This?

Problem: ROM Manager in the market is in a constant state of "downloading", sometimes it will show its downloading going and reaching 100%, but then it just goes back to "downloading". IF I try to cancel the download, the Market force closes.
Ok, so I noticed this problem after flashing one of the CM Nightlies, so in order to try to fix it, I wiped everything, went back to RC2, problem still exists. I think it was caused by Froyo's automatically restore of apps. I would think that in the initial bootup, maybe turning off those options could fix it, but that would require another wipe. And I've already done 8 or 9 in the fast few days and am just exausted from re-setting my settings. Normally I'd use Titanium Backup to solve that issue, but every time I do a restore, it soft reboots.
Anyone have any ideas?

tehseano said:
Problem: ROM Manager in the market is in a constant state of "downloading", sometimes it will show its downloading going and reaching 100%, but then it just goes back to "downloading". IF I try to cancel the download, the Market force closes.
Ok, so I noticed this problem after flashing one of the CM Nightlies, so in order to try to fix it, I wiped everything, went back to RC2, problem still exists. I think it was caused by Froyo's automatically restore of apps. I would think that in the initial bootup, maybe turning off those options could fix it, but that would require another wipe. And I've already done 8 or 9 in the fast few days and am just exausted from re-setting my settings. Normally I'd use Titanium Backup to solve that issue, but every time I do a restore, it soft reboots.
Anyone have any ideas?
Click to expand...
Click to collapse
You know... actually I've been experiencing a similar issue.
At one point with Market it would take at least 30 seconds for anything to show up when I open Market. Then to look for any updates by clicking Downloads it would take another 30 seconds or so. Not a big deal. But then somehow and for some reason it started showing up almost instantly! I would download and install the updates but then Market would forceclose almost immediately after the app finished installing. It made updating or installing several apps almost impossible. I tried wiping the data, clearing the cache, clearing the dalvik cache, etc. However the problem still occurs but not all of the time. It's pretty strange actually. I'd say about 75% of the time I get forcecloses and each time I try to get a logcat I don't have the problem. Go figure.

[Q] Foce close error all installed apps not showing 2nd time...

Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.

i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run

Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.

I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.

nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later

I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.

read this
http://forum.xda-developers.com/showthread.php?t=793404

Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...

I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?

Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.

Ridiculously easy to corrupt settings - Normal?

I was just getting over the initial buyers remorse phase for my galaxy (or in my case, flashers remorse, even though I run stock JPY and it's fine, I have this urge to re-exchange it for a SLOWER stock Vodaphone Australia 2.2 version that's probably more buggy, but at least truly stock), when I drained my battery to 1% to test battery life, and shut it off manually.
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) left right and center then went straight back into default first-boot menu, like the very day I received the phone, or after a hard reset. The funny thing was, instead of having default values selected, it had the ones I had already put in. I thought it would be fine after that. Wrong.
I tried rebooting it again to see if it fixed itself, and it does the same with the forced closes. I uninstall my background and re-install it, and save some settings. When it boots it restores the live background back to it's stock settings (the live wallpaper I chose is still there, but the settings for it are not).
At this point I'm scratching my head so I uninstall all apps. This time on boot it doesn't throw up "force close" errors, but instead force-closes a single app or service for me on boot, with the one buzz, then three quick buzzes. Sigh... I have to factory reset my phone. One thing that particularly annoyed me was the fact I moved all my apps (AngryBirds ) to my external SD card, yet miraculously, after the reset my phone doesn't seem to think it's there anymore! Another thing I'm pondering is that if I didn't reset my phone like this, would this still have occurred?
Runs perfectly fine after the factory reset, with no errors or anything on boot as of yet. I have been compulsively rebooting it ever since just to find out, LOL!
Is this a 'normal' sort of thing to happen on the SGS, or is just through shear coincidence the combination of me restarting the phone in it's booting phase + the low battery life screwed up some boot settings while the phone was writing to it, or is it some hardware error? I can see this as particularly annoying if it were to happen every month or so. Coming from an old brick phone with something like 8000 messages on it, it'd be inconvenient to say the least to start deleting everything periodically... I guess I can use apps to back-up data when this occurs, but some apps don't even work after it's been erroring out on me. *Pulls hair out*
TL;DR:
Reset my phone while it was booting (still on the GT-I9000 screen) on a low (1%) battery and it broke my phone settings. Forced closes unknown app/service on boot with no 3rd party apps installed, but still boots to home. Force closes 3rd party apps frequently if they're installed. Factory Reset/Wipe. Problem Solved. Annoyed. RAGE.

next time something like this happens use adb logcat to figure out what is actually going wrong

exclamationmark said:
...
On the walk back to the recharger in my room I accidentally turned it back on, and I immediately tried to turn it back off again, without letting it go past the 'GT-19000' logo in fear of the battery draining. It just restarted again and I decided to let it boot this time. Mistake. It then started to randomly vibrate and shut off apps (mainly, my live background, shake them all) ...
Click to expand...
Click to collapse
you are not alone . after draining battery , starting it accidently up (drained) in middle of booting , killed it for me, well not killed but wouldnt boot for me and I had to the the factory reset. oh and since the nice bzz ... bzz bzz bzz I hear more often I would like to ( here was I ignored crying about it http://forum.xda-developers.com/showthread.php?t=937938 )

Yeah I'll definitely boot up logcat if it happens again. I'm just hoping this isn't a regular occurrence . As long as I don't do anything stupid like this again, I'm thinking it should be fine.
The third time this happens, it's going back to the service center, so it's got two chances left! Another thing I failed to mention was that it was chewing up like 200mb~ ram with level 1+2 ram cleared, without loading back into the homescreen, before the factory reset. Probably the stupid forced close app/service leaking >.>
Pagot, if that were me and continual factory resets were the only way to fix it (or didn't fix it) I'd flash it back to stock (or just remove root) and return it to the service center if that's an option. Sounds like something got corrupted or didn't get flashed properly. Either way I'd let THEM waste their time sorting it out because no amount of flashing is going to solve a hardware issue if it turns out to be one.

exclamationmark:
(had stock, so just root removing) but I know how our service centers work (and I would have to bring it even to our carrier) they wouldnt even talk to me if I didnt do the factory reset and the first thing they would do "reflash and factory reset"
right now I am not playing on the phone so much anymore. no lust or time so no idae if my apps are still fcing so often . And I installed speedmod and made a backup so I can revert back if something happens. So will see.
Wanted to just write about the battery down +(or) not full boot = corruption

LG Optimus L90 keeps crashing (even after factory resets/flashing stock ROM)

I've had my LG Optimus L90 for 2-3 years and it began to get very slow about 3 weeks ago. Certain apps began to not open at all, and eventually it crashed and got stuck on the lg startup screen with 'fastboot' shown on too I white letters. I looked this up and apparently you have to deliberately enter fastboot mode, so I assume something wonky is up with my software.
Since, I've flashed stock kdz multiple times. It works fine perfectly for awhile, but after a day or two the home screen will begin to flash black and crash over and over, and eventually the phone reboots and gets stuck at the white T-Mobile screen, and sometimes the LG screen before that. Just last night, after yet another flashing of stock ROM, it just crashes out of nowhere without the usual home screen crashing and reboots and I had to flash stock AGAIN.
Am I doing something wrong? Do I have to clear out gunk from the internal or something? The phone works perfectly after I flash stock, and you can't tell anything is wrong until it the home screen starts to crash multiple times and eventually the phone crashes but wont boot up. It only lasts about 2 days max before it crashes again.

Do you have an micro SD inserted? Maybe it's the issue... Try:
1. Starting the phone without SD
2. Backup, remove SD and factory reset, then do NOT add your Google account, then install apps one by one, waiting some time between instalation, maybe one app is the culprit. Do not restore apps using your Google account because it may restore the data that is causing the problem. You can backup Contacts, SMS and call log using some free apps if you need them to use the phone.
If even after a factory reset and no SD you still have problems then probably the internal memory is bad, only replacing the board will fix it.