I figured I'd make a thread about some of the weirdest stuff you've had happen to your SGS. Only a few minutes ago I had a little incident which made me wonder, what kind of weird stuff do other people deal with?
I'll start.
A few seconds ago I tried playing Angry Birds. After it loaded I clicked play and the screen didn't change. Instead random dark lines started to appear horizontally across the screen. At first there was one and then slowly many, many more started to appear. None of the capacitive buttons worked, nor did the home button. Eventually it got really bad and I lost all hope so I held the power button and it reset. All seems fine now.
The time before that I was flipping through some menus fast and I started getting mass FC's. I decided to restart the phone. Upon booting up ALL info that I downloaded or came from Bell was gone. The Remote PVR app and everything, was gone. The factory reset button in the settings menu didn't even work. After doing a reset via the 3BC everything worked again.
Now, what kind of crap have you had to deal with?
hmm... how about a double weird even of the same magnitude?
So, here i was doing stuff happily with the SGS on me, suddenly i hear the phone have restarted on its own i was like OMG!!!!! WTF!!!!
it was just once, and i was doing stuff, so i disregarded it and continued with my life.
then shortly after (30min ~ hour) the same thing happened so i was left pondering and started to investigate, only to find out that the belt letter case that i use have an exact opening to activate the buttons (never paid attention to it before) and when i sit down the rugged parts of the Jeans will press exactly right into the spot where the On/Off button is located mystery solved
solution move the belt case a little bit more to the front to avoid the hard edge of the jeans plies
But!!!.... that's not over... the SAGA continues!!!....
not long after at around the same time (a day or 2 later) the phone did it again, it rebooted on its own IN FRONT OF MY EYES (i was texting in the toilet), so i said it aloud WTF!!! this definitely was not a Jeans/Belt combo issue, it was not the SMS / XDA App program causing it.
so i started to investigate, i installed a new app recently that i was testing (superpower), it worked really good for the first roughly 12~24 hrs i was using, made some options changes
then it worked even better, however the reboot was caused by the app that i installed it.
removed the app and now the phone is back to normal ever since.
How's that for excitement?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every now and then, when using it to play music in the car, it will turn itself off. Not a graceful shutdown though. It will be playing one minute, then BAM, it's turned off.
Holding down the power button for 5 seconds won't turn it back on. Even multiple tries.
But holding the power button down for a solid 10-12 seconds will turn it back on. Then after it boots up, everything seems normal again....
well, I was showing the phone to a friend, he has an iPhone 4, he saw the Angry Bird icon, he said, ok let's compare the game between ur SGS and my iPhone4
I won the battle, size of screen depth of colors were my weapons but
when I pressed the home key it went back to home, then suddenly screen started getting brighter, more and more, I wasn't able to see anything after few seconds, and I was so shocked casue I read some topics about Super Amoled going brighter and then dying for ever I immediately restarted it using the power key, and never played angrey birds again this was before a month, my screen is still fine
Related
a lot of people are reporting this problem when the phone is off
http://androidforums.com/htc-evo-4g/106893-i-just-notied-my-evo-glows-dark.html
JoshHuman said:
Here is the problem on a 002 15 second exposure in complete darkness.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
The way I see ut is that the button panel has its own backlight and is meant to turn on in complete darkness, but some evo's do it when the phone is off given enough power since the panel's software run a separate lower powered chip, but I'm no engineer. It can be fixed with a firmware update, probably.
Mine did this once. I turned it back on and killed a bunch of apps with advanced task killer, and then it quit. Think it was just a fluke because it hasn't happened since.. and that was about a week ago. If it's happening constantly even after reboots, I'd assume you have installed something that is acting retarded in the background.
actually it's not a software problem... I hard reseted and kepted the phone clean and checked at night. still LED problem being lit. I took it to a store and they are willing to replace the phone
Yes this happens to me alot and i have to remove the battery and put it back in i left the phone like that for 10 minutes and i click every button but does not come back on so have to remove the battery
My wife's has been doing that and it will not stop. Ive rebooted cleaned all apps and nothing. I'm trying to return it but am waiting for bestbuy to call me when they get more phones. Any one have a solution?
Sent from my PC36100 using XDA App
I have the opposite problem. Mine never seem to turn on in complete darkness. >_<
I just noticed this for the first time last night. Haven't seen it before or since.
Sent from my PC36100 using XDA App
TheBiles said:
I have the opposite problem. Mine never seem to turn on in complete darkness. >_<
Click to expand...
Click to collapse
wish i had that problem. i really have no need for back lights on the menu. the bleed they cause is terrible when looking at dark movies.
on the droid, in froyo at least, the menu buttons dim when watching a movie or you can use LEDsHack to turn off the lights.
I posted this issue a couple days ago and got no replies. I have noticed this issue on my phone. Sometimes pressing volume up/down will cause the lights to come on too.
I wonder if this is the cause of poor battery life. It's almost as if the light sensor is still functioning when the phone is supposed to be sleeping.
I noticed this also on both mine and my girls 0002 models... You can see it during the day too if you cup your hands around the bottom of the screen just over the buttons and look under. Wasn't sure what that was all about. Looks like just another glitch to me.
Is this good enough reason to request exchange? Does this drain battery faster in any way?
apexi350z said:
Is this good enough reason to request exchange? Does this drain battery faster in any way?
Click to expand...
Click to collapse
yes it is a good reason. kills battery
delete please.. double post
I thought the whole time that the "glow in the dark" was a feature. Its something I certainly don't mind, as I have found it rather useful.
But since its not a feature... then... defect? Haha. Well, this EVO is going back to the store anyway.
I have a weird problem with my Wildfire's screen after I did an OTA upgrade to Froyo.
First, the top of the screen stopped working. The taskbar wouldn't work and I the top wasn't responding. All of a sudden, after approximately a month or so, it started working again.
It worked fine for a few weeks and then the right side of the screen has a problem. All of a sudden it started automatically hitting the spot on the screen where the letter "P" would appear on the keyboard. When I was trying to type out a message, the letter "P" would get hit on its own over and over again. When the keyboard was not open, it would still happen.
I felt it might be a virus, so I did a hard reset. This still didn't stop. So I switched off my phone and kept it in a desk for 48 hours. When I switched it on again, this problem stopped, but the right side of my phone was not responsive (approximately 4 milimeters of it).
I can see that this is clearly not a hardware problem and has something to do with the firmware/OS. I'm not too sure what to do. I've tried flashing new ROMs on to my phone, but it remains the same way.
Incidently, when I tried flashing "TheNextSense" ROM on to my phone, the phone started hitting the portion of the screen where the "P" key would appear. When I switched back to CM7, it stopped, but the right side was unresponsive.
Is this something to do with the memory? Or is this a known issue with upgrades/certain ROMs?
Any help will be appreciated. This is driving me crazy
why do you think its not a harware problem ?
for me it sounds like it is one. (temperature or short circuit problem)
IANAHRM (I Am Not An HTC Repair Man) but I think the touch screen connector has just slightly worn loose, perhaps due to temperatures. It sits on the right side of the main board (left side of the phone itself). I know the Wildfire can survive quite a motion shock so that shouldn't be it (I hope).
Nandroid backup and restore jobs heat up my phone quite a bit, did this occur on your device as well while you were installing roms? That might explain the change in behaviour.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
henkdv said:
IANAHRM (I Am Not An HTC Repair Man) but I think the touch screen connector has just slightly worn loose, perhaps due to temperatures. It sits on the right side of the main board (left side of the phone itself). I know the Wildfire can survive quite a motion shock so that shouldn't be it (I hope).
Nandroid backup and restore jobs heat up my phone quite a bit, did this occur on your device as well while you were installing roms? That might explain the change in behaviour.
Click to expand...
Click to collapse
Nope. It's never heated up till now. This happened all of a sudden, and it gets worse with upgrades. It's like, for some reason, the phone isn't able to function properly with any ROM other than the stock ROM. I'm going to try to put back eclair on it today and see whether it works. Will keep you posted.
stavro said:
why do you think its not a harware problem ?
for me it sounds like it is one. (temperature or short circuit problem)
Click to expand...
Click to collapse
Because it doesn't always occur. It kind of gets fixed on its own after a few days. It's like my phone has a ghost in it
I put back the stock Froyo ROM and now the problem is 50% better - much of the portion of the screen that was dead earlier is now responding. But the rest still isn't. Any ideas? :-(
Hello, I've been best friends with my Atrix since a little over a year now. We have had many experiences together and our relationship has bloomed a lot with time. I confess I haven't completely looked after my phone, I'm a little clumsy, specially if I don't get to sleep enogh. So almost a month ago, after getting up very early, I was reading a notification when my phone fell. I tried to grab it but I pushed it even more. It went straight to a cornered tile on my bathroom. This was the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And trust me, it's much worst in person than you can see there. Surprisingly enough the touchscreen works just as fine as it always did, even the notification area works fine (the top of the screen has been the more affected area), although I can't use the front camera anymore because there's a big scratch on top of it. Also something happened to the headphone jack because I can't use it anymore. Regardless of all this, the phone itself keeps working like a charm. I have been unemployed for a couple of months now, have a couple of bad debts so I don't have any money to fix it for the time being, so I have no choice but to use it like this.
But I have two weird errors, which has caused me to write this. The first one is related to the proximity sensor. Everytime I answer a call, the screen turns off as it should, but after the call end the screen doesn't come back on and there's no way for me to turn it, so I have to pull the battery and reset it. I tried to mark the option for the screen not to turn off when I pick a call but it keeps doing it regardless, so I suppose what I should do is to try to take the phone apart and see what's happening on the inside.
This pulling of the battery has led me to the discovery of the second error which I think it's the most interesting: 1 out of maybe 20 times that I do that, for whatever reason, a random app gets uninstalled from my phone. The first time it happened I blamed the app (growlr was the first), but then I saw it happened to Twitter, then to Google Plus, then to Script Manager. And it's not like it gets deleted completely, if I go to the app manager I can see it on the list but not with the regular name (ie: com.twitter.whatever instead of just Twitter). I'm using Neutrino but I'm not sure if I could blame the system, I think it's caused from the battery pulling in the same way turning off a computer by force can produce errors on the file system.
So has any of you come across problems like these before? Do you have any suggestions?
Hi guys Ive got a new problem with my nexus 4 (this time not user inflicted :angel on friday my phone was at 80% battery and i turned it off, it had been working fine these past few weeks but now it wont turn back on, i've tried the following things:
Charging overnight with original charger from the mains
holding the buttons in all combinations then putting the charge lead in and holding them for at least 30secs
The phone doesn't have a notification light of any kind
Any advice would be greatly appreciated
ps the bootloader is unlocked so i guess sending it back isn't an option
Some people have said they sent it back with unlocked bootloader without issues. I don't see the issue as long as you still have stock.
You can try removing the battery and reinserting it, then charge. Or replacing the battery.
eksasol said:
Some people have said they sent it back with unlocked bootloader without issues. I don't see the issue as long as you still have stock.
You can try removing the battery and reinserting it, then charge. Or replacing the battery.
Click to expand...
Click to collapse
Ok thanks i might try that
Ive called lg and im going to send the phone in under warranty, ill let you know how it goes:fingers-crossed:
I think I got the same problem -kinda. I clicked reboot and then went on to stare at my laptop screen for a while. The last thing I notice is that it's at the bootanimation. The next time I look at it again, it's dark. well, of course, since I naturally thought the screen is off but the problem is nothing happens no matter what I do -just like OP. oh, and there's no blinking red light or whatever.
One thing I notice is that the device is listed under adb. If the device is off shouldn't there be nothing listed there? So, is this damn device still turned on?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your ADB is enabled but is not activated for your connected device, it is activate by the popup notification in the phone.
Do a factory reset.
sometimes for some whatever reason phones can get stuck in adb sideload mode(i saw only 2 phones do that, and one was GS3 with cm installer, the other was an old galaxy ace).get a rom zip and take a look and see if adb sideload Works.
fixed it. I've charged it the whole night before I posted that screenie. I've approved the rsa fingerprint or whatever before the phone dies so technically it should connect since I've even pushed some files around before that. What i'm trying to point out is that even though the phone is dead(?), why does it appear under adb? I could fathom fastboot but adb? So all the while I'm charging it overnight and frantically raping the power button pressing it like some nuts, the N4 is actually booted up? damn.
Anyway, I charged it for a couple more hours since my last post and then just now, I pressed the power button for about a minute (connected to pc) and suddenly the notification on my pc went nuts. It's saying the N4 is being connected and disconnected over and over again -goes on for about a minute and all the while the cursed red light appears though it goes off after a while. Hit the power button again after the light disappeared and voila -it booted up normally like nothing happened :curses: --talk about acting innocent.
Tried doing some reading on why it even happened but I don't get it at all. Oh well, whatever. I just hope it doesn't happen again.
Glad you got it sorted, lg sent me an email saying they are sending me the phone back, they haven't asked for any money so i assume they've fixed it under warranty
Got it back today, says the phone has had a new battery and flex. Could the damage have been caused by the wireless charger?
Here is the deal both Google and System UI crashed on my S5e last night while I was reading and now I am unable to reboot/power down the tablet using either the Power button or the onscreen controls. As you can see it is just the 2 onscreen buttons that I get and n othing happens expect they dissapear when I try and tap either. Also I am unable to use ADB in this sitution to force a reboot/power down as can be seen in the second image. At this point I am at a lost on what to do besides wait for the tablet battery to die which in its current state could take days if not a week+ considering that nothing is showing up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You try a 20+ second long press on the power button (if that's correct for that model) to do a hard reboot?
Yes I have I have held the button for a bloody minute aka 60 seconds and no reboot/poweroff
Montisaquadeis said:
Yes I have I have held the button for a bloody minute aka 60 seconds and no reboot/poweroff
Click to expand...
Click to collapse
The only other thing you can do is physically disconnect the battery or wait for it to discharge.
If you get it to reboot go into safe mode and backup all critical data. Then factory reset.
If that fails it will need reflashed or the hardware issue causing it fixed.
That is what I thought and as I said it can take up to a week+ for this to discharge since it was nearly full when it happened
If you used a SD card as a data drive and it's not encrypted at least the data can be salvaged.
It may not be as bad as it looks but I'm thinking a mobo failure. I've never seen this type of behavior with any of my Samsung's.
Recertified ones can be had for $200 or so but will likely be upgraded to the latest OS version for it. If you're running on Pie you may not like it.
I bought this one for $275 back in 2021 and ended up receiving a used one when Amazon said it was suppose to be new so yeah something like this was bound to happen sooner or later
Montisaquadeis said:
I bought this one for $275 back in 2021 and ended up receiving a used one when Amazon said it was suppose to be new so yeah something like this was bound to happen sooner or later
Click to expand...
Click to collapse
I would've returned it. I use one vendor where I got a new N10+ a little over a year ago. His prices aren't real low but he's trustworthy. Their price is $600 for your model. He buys lots of unsold new devices. There's lots of scamming going on, something I noticed when I was shopping.
Apparently you have to hold power and volume down to force power off a Samsung device so you missed a step there. Also the tablet seems to be working fine now after doing so
Montisaquadeis said:
Apparently you have to hold power and volume down to force power off a Samsung device so you missed a step there. Also the tablet seems to be working fine now after doing so
Click to expand...
Click to collapse
Correct. Hard reset is both buttons; something I never have to use. However long pressing just the power should force it to shut down.
Try clearing the system cache from the recovery menu.