• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Bizarre - Wallpaper, Home Button, Screen Lock lost overnight

Ambress

Lurker
Hello all,

I woke this morning to find my Samsung Epic with a very strange problem I can't explain the cause of, other than to wonder if Sprint did some kind of update to the phone during the 6 hours or so it was inactive. Namely, my prior wallpaper setting was lost and another image shown, the home and search buttons are inoperative, the password lock was disabled and seemingly cannot be restablished (by pattern or PIN), and when I power off the phone, the menu presented shows only the power off option (no airplane mode, silent, etc.). Apart from that, the phone seems to work OK and all apps are in place per a quick review of the apps drawer.

I updated this phone to DK28 prior to Christmas, had an issue with GPS, then again installed DK28 as a full install after resetting to an earlier image...DK17, DC17?...I don't recall the name now, but know my first upgrade effort was from a later firmware version that I'm pretty certain came on the phone. In any case, DK28 has worked great other than an odd problem that uniquely when in my Contacts, I cannot exit via the return button but rahter must use the home button. With the phone in its current state, accessing Contacts is a big mistake, as I cannot leave the Contacts without the home button functionality. Oh, and as you might also guess, the home button also cannot held down to activate the task manager.

This seems to me to be screaming for a solution of a Hard Reset, which I'll try after work tonight, but I just wanted to throw this group of problems out to see if anyone has ever heard of such an odd combination of issues arising with no action.

Here is some info on the phone, noting that it does report Firmware 2.2.1 which I don't recall installing and may well have been an automatic update at some point, unless that was part of the DK28 installation. I apologize for the lack of more specific details on that installation, but I don't have them available at the moment.

Model: SPH-D700
Firmward: 2.2.1
Baseband Version: S.D700.0.55.DK28
Kernel version: 2.6.32.9
Build number: FROYO.DK28
Hardware version: D700.0.5

Thanks for any insight,

Ambress


UPDATE: A hard reset seems to have established all buttons in proper working fashion, now I just need to reinstall everything, hoping most of that can be recovered via Ti Backup.
 
Well, this is frustrating....After getting pretty much everything restored, including the great majority of apps reinstalled from scratch rather than backup, it is 4:40am and my phone has again entered a state just like it was yesterday morning. I noticed as I was tweaking various user settings that the phone seemed unusually warm, but then I also saw the 4G was enabled and I'm in an area without it, so perhaps constant efforts to connect to a 4G signal just stressed out the phone.

In any case, I was trying to change wallpapers only to find they wouldn't change, when I decided to check the home button and power-off menu. Sure enough, inoperative home and search buttons, and "power off" was the only menu option. Could it be that at this early morning hour there actually was some kind of software update being performed as I had suspected yesterday? There is nothing whatsoever to indicate that. I also recently purchased and installed a Patriot 32GB microSDHC card which happens to be what is also installed at this time, leaving me a little curious if it might be the cause. Only one way to find out I suppose.

Again...although only 1 day has passed, if anyone can off their own suspicions about this, all information is appreciated.

Ambress

UPDATE: Well, this was a real puzzle...first beginning to suspect the new microSDHC as the culprit, that was all coincidence, as problems surfaced when I reinstalled everything using the original 16GB card. Various problems persisted but finally after more than 6-8 flashes of DK28, some due to GPS issues, I finally have th phone working as it should, regardless of which memory card is used. Chalk it up to some strange software conflict that finally got cleaned out.
 
Back
Top Bottom