Database Develop

[Q] Phone on Doc's ROM suddenly locks up and upon reset apps go crazy.

Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.

This is not a reason to start a new thread in the Development forums.
Support and Q&A for custom roms should take place in their appropriate threads. Use a bit of common sense, courtesy, and patience -- people will help you.
Please read the rules of posting new threads again here: http://forum.xda-developers.com/showthread.php?t=788800

anoneemooz said:
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
Click to expand...
Click to collapse
1) Lock ups most likely due to removing drm file from system apps.
2) Your using lagfix (I assume) and when you pull battery data corruption is very likely on some configs.
3) Read rules before posting.

[Q] Boot loop & CWM backup question

I decided to do a reboot just to have a fresh start after adjusting some app. The phone was stuck at the flashing Darky logo for indefinite amount of time. After a minute or so of flashing logo, phone vibrates shortly and continues flashing the logo. That repeats each minute.
Taking out the battery and retrying didn't help, same thing.
In the past 48h since last boot, I've installed a bunch of apps, mostly games, so it's natural to look for a culprit among them. However, right now I can hardly do anything with the phone. I can access the recovery menu, download mode probably as well and that's it.
I'm ready to flash the Resurrection Edition, but first I'd like to exhaust other options for fixing the problem or at least backing up everything I can. I have partial backups but would very much like to access the latest changes that weren't backed up.
My questions are:
1) Is there some kind of boot logging that I could turn on, access and which would point to the problem? I'm comfortable using ADB if it's needed.
2) I did a CWM backup. What did it backup? Primarily, what about contacts, SMS messages?
3) The most important question: If I reflash the ROM and then use CWM restore, will the problem repeat itself? (If an app is the source of the problem and all apps are backed up and then restored, I'm afraid the problem won't go away. I see few big image files in the backup folder which suggests that everything will be restored as it was. Bootloop too?)
Additional hints for experts on what might be causing the problem:
There are only two incidents that come to mind.
First is that I did a wipe flash of darky 9.1, then a regular flash of 9.2. After I discovered my GPS simply doesn't work on 9.2, I did a regular flash back to 9.1. This was about 2 weeks ago. Is there something in this procedure that might leave some problems that would show up in the future?
Second thing is a incident I had 2 days ago (the time last reboot was done and last time I've had a successful boot).
I left the phone ON over night, and in the morning found it turned off. I thought it might be a dead battery so I plugged it in. It wouldn't start for few minutes but then booted normally.
During that day I found it OFF one more time, for no apparent reason. This time battery was nowhere close to low. It turned off while in standby/locked screen mode so I can't say that it was doing anything in particular.
(Even the turning off during the night is suspect. It had sound on, it was near my head, and I'm sure that low battery warnings would wake me up. It might just be the case it turned off for no apparent reason like it did during the day.)

i think, that when you flashed 9.1 over 9.2, it could leave some weird things, because everyone is talking bout updating, and no-one even think about downgrading rom.
Answer 1. If you used SpeedMod kernel, I think you can turn Logging in Tweaks Menu at RM, and start phone with plugged USB cable to computer (running adb).
Dunno bout other kernels.
Darkyy normally turned off logging, because ROM was bit faster without it.
Answer 2. Probably contacts were synced to Google (contacts.google.com) <--- try it
I think SMS messages are backed up together with whole ROM (contacts too).
Answer 3. Probably yes, problem will repeat. I don't know but maybe there is some way you can restore only some things, not whole system.
I think you should make "Backup Everything" in CWM, then try flashing 9.2 again.
Weird that GPS were not working there.
It seems something bad was happening that caused random reboots.
What apps that require root, you were using? Swapper, Galaxy Tuner, Overclocking?

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

[Q] Woke up to a less functional Captivate..

Long time lurker, first time poster.
I woke up today to see my captivate screen showing blank screen (active black screen with buttons lighted up) being unresponsive. It was on it's charger from the night.
I pulled the battery to shut it down. It rebooted. I thought nothing about it until I tried to use it about an hour later.
I have had it on stock Froyo, with no root. Never have flashed any other ROM besides updates through kies.
Problems and things I've noticed so far:
No puzzle lock screen. Can't find it under "set screen lock". Only None, Pattern, PIN, Password available.
Home button and search button do not function(they light up like they are pressed, but not action occurs in any apps or home screen).
No data. Usually i'd see edge or 3g, but I have no data connection.
Text messages wiped. None available through "Messages"(though call log shows history of messages).
Keyboard was on stock android rather than swype(since changed back to swype).
Holding power button only shows "Power off" option. Before there was at least Airplane mode.
GPS was on(I hardly ever use it).
Location settings seemed to be default("use wireless networks" was unclicked)
Most other settings/app data seems fine.
About phone info:
Model Number: SAMSUNG-SGH-i897
Firmware version: 2.2
Baseband version: I897UCKB1
Kerner version: 2.6.32.9
Build number: FROYO.UCKB1
Click to expand...
Click to collapse
Other related things:
Day or two before I received a text message from AT&T to download Kies and use Froyo(Don't remember exact wording, lost the text message, but something to the effect it looked like a mass mailing text to update to Froyo using Kies). I was already on Froyo(flashed as soon as I found out it was available few months back).
I also got a text message about downloading their at&t app to manage my minutes and pay my bill(also already had that app).
My Captivate would randomly freeze/unresponsive a few times, but I didn't think much of it.
Google Music app seemed to randomly start playing the audio file i paused(just in my pocket, or once when i put headphones in to make a call).
Searching the forums, haven't found too much related.
One thread suggested using "home switcher", which I have tried(both Froyo and regular versions, though can't press home button for Froyo version). Neither seems to know what my default Home App is, but it only sees TwLaucher(I only have TouchWiz).
Tried installing an alternative launcher(ADW,LauncherPro), still no home/search button.
I'm without my computer for the weekend, so I can't backup my files and reset to factory just yet.
Anyone have any thoughts to fix this or know what may have went wrong?
I might finally make the jump to a Custom ROM if it'll fix this.

Yes, you should either flash a custom rom or do a factory reset. I will say an event similar to this, also involving text messaging, is what made me make the leap to Assonance, and then Serendipity, and I haven't looked back.
Sent from a state of Serendipity

At the least, try a master reset.

You're not alone....
Two Saturdays ago, I woke up, grabbed my phone to see what time it was and my phone was going haywire. It as blinking, flickering and rebooted on its own a couple of times...without me touching it.
When I DID manage to access the phone after a reboot there was no connection. I couldn't call, send/receive texts, nor could I access most of the features (during one of the haywire moments, the phone popped open my "Gallery" folder and started running a slideshow and then shut down. Again, all without me touching it!) There was a distinct blue circle with a slash where the 3G bars used to be on the top right corner of the phone.
I did a factory reset and didn't help. Wiped everything off the phone, but the device was still going nuts.
I got the phone in mid-December and have absolutely pampered that thing. Never dropped, never scratched, never abused. So I was surprised when I took it into the AT&T replacement center that the lady told me that my battery was wet! Not the phone, but the battery. Those two white-that-turn-pink indicators are so close to each other on the phone that I can't see how one gets wet while the other doesn't.
So they give me a new phone. One thing I noticed right away was that my data usage went WAY UP with the new device. To put it in perspective, I used 100 mb of data in 29 days and 64mb IN ONE DAY with my new phone. I thought it may be a one-time fluke, but it's not. I am only 10 days into my new month and am already at 164mb out of 200mb in my plan. I have NEVER used 164 mb in the 6 months previous, let alone in 10 days.
Fun's not over yet. I noticed a lot of crashes and "Force Closes" with the new phone too. I didn't even have any apps downloaded yet and things were still crashing. Last night I pull my phone out to take a picture and...nope. Screen was all kinds of whacked out and it crashed. And still does now every time I open the camera function. I managed to get in camera mode fast enough to do a reset, but didn't work. The screen is fine otherwise. So looks like I'm back to A&T tomorrow for another round.
I'm glad you posted this, cause the same morning all this happened -- literally, within 10 mins of me waking up -- my computer (brand new - 2 days old) went berserk and shut off and my stereo started flipping channels, turning the volume, treble, bass up and down..BY ITSELF without me touching ANYTHING! It was pretty freaky. I wondered if I was struck by lightning the night before.http://media.xda-developers.com/images/smilies/eek.gif

I was finally able to get back home today and do a factory reset. This (somewhat) solved the problem. Everything is mostly back to normal(home button and search button work on home screen, lock screen is there).
Lost a couple of game saves as I had no method to pull a save file(was doing adb pull on some known file locations).
I did run adb logcat before resetting, and home button and search button seemed to trigger something, just not follow through(Search button did work in a card game as a forward button and home button worked in the kies app to exit, just never as a return to home button in apps).
I'll be looking to root and flash a custom ROM, especially root so I can do a proper backup in case anything like this happens again.

I just want to say thank you posting in q&a and doing research before and after your flashing started. Then searched after your problem. You're a new member of a breed that are few and far between. I will hit your thanks when I get on my computer, app doesn't have it. You will go far here.

[Q] Captivate loop soft reboot???

I am a broadcast engineer and have been a Linux user for the last decade. So when Android hit it was only a matter of whose device. After a lot of research and waiting for 6 months for the initial “teething pains” to pass selected the Captivate for several reasons.
As a broadcast engineer 24/7 reliable cellular communication with data is a professional necessity not a convenience. For that reason my wife always has the same phone as I carry as a backup. If mine gets broken or unusable for any reason we switch SIMs and I am back to work. So we both received our initial “trade up” Captivates at the same time. About 25 days after receiving our phones mine started randomly shutting itself off. After three warranty replacements finally got one that stayed on. Six months later wife's was replaced due to no audio from the speaker. Later after my father past my mother merged into our family plan and choose Captivate as well.
So we have three Captivates in our family. Love the phones. Mine by my nature is loaded with “all the bells & whistles.” Lots of app, widgets and rooted. As soon as I am comfortable with my choice and feel prepared will take the plunge and try flash a custom ROM. More than likely several through ROM manager of some kind. I really like to looks of the four tap lock and other features only a custom ROM is going to get you. Besides I am a “power user,” which my wife thinks translates to “if it works, it doesn't have enough features.” My wife has a few widgets & apps as well as my mother to a lesser degree.
In the last 90 days we all three have been experiencing something that I describe as a “loop soft rebooting.” Started with my wife, she described it a “loop rebooting.” Every weekday from 10:00 to 10:20. Once I had a chance to observe I found it does not do a complete reboot. It does not show the shut down animation like a controlled shut down. Or the turn on animation like a power up after a complete shut down or OS crash. I would describe it as more like a “soft boot.” Almost like a launcher crash, but it also has to rescan the SD media. It vibrates once with the screen off or on, in use or out. then twice more, another 8 to 10 seconds another vibrator alert then the launcher appears and starts to load widgets, apps & scan media. Completely unresponsive to any key input until after the launcher reopens. The wife has never used anything but the AT&T/Samsung stock launcher. I did all the usual things. Backup, factory reset, restore. Still does it. Backup, Hard reset, restore, still doing it. Hard reset, rebuild from scratch, no restore, stayed completely vanilla, no apps or widgets at all. It still does it. Then mine started doing it. I was using ADW Launcher, switched to Launcher Pro, have even dropped down to using the original launcher since it acts like a launcher crash. No affect. Went through all the above same process with the same results. Mine does it's act between 5:00 & 5:20. About a week later my mother reported hers does the same thing between 4:00 & 4:20. Interesting side note, if we turn off the radio (airplane mode) it does NOT do it, completely stable in PDA mode. But when we turn the phone back on, it then starts the process and runs for 20 minutes and stops. I have been collecting logs off my wife and my own phone but work duties have not given me the opportunity to read through the thousands of lines of logs to find a “smoking gun.” Now in the last week we see the same activity more often and for longer periods. Because turning off the radio stops the activity there has to be a trigger from the network. It also uses lots of data during these periods. Maxed out my wife's data plan the last 3 months. We have Lookout Security installed on all three phones and it reports no Trojan's, viruses etc... Also the Hard reset should have killed anything like that. I have done hard resets three time on my wife and my own phone and rebuild from scratch now. We have left her phone completely factory fresh only adding back her contacts through Gmail. I have Titanium Backup and have tried “freezing” & unfreezing” everything I can think of. Nothing but turning off the radio seems to effect this issue.
Has anybody out there experienced anything like this???

Damn dude, can I get the cliff notes?

If you're thinking of taking the custom rom plunge, I would say to go for it. The reason I suggest this is that most custom roms will also flash a different modem, which might allow your phone to connect to the towers in a way that will prevent the hot reboots you're seeing. Just make sure to do the normal backups (Titanium backup) of stuff you want to save before flashing.

^ +1
sound74145,
yeah since ur rooted, i would suggest flashing a different modem (radio) if u don't want to flash a Dev Rom yet.
What is ur Baseband version now... i897uckb1 ?? If so try i897ucKH3.
Check the modem stickied thread. It should be attached behind the paperclip at the title of the thread.
Sent from my SAMSUNG-SGH-I897 using xda premium

hysterical