[Q] Black screen, phone unresponsive - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
I have a I9000 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway.
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew

magosalas said:
Hi,
I have a I9000 on TMobile in the UK. Not rooted, just been upgraded to ICS with the official firmware.
Ever since then I've been randomly getting a black screen - i.e. phone doesn't respond to any of the buttons to turn the screen on. Only way to get the phone to work again is a battery pull. Haven't installed any apps from prior to ICS, and prior to ICS I didn't have this problem.
I'm guessing no one's going to have a simple answer to this (although it would be great if anyone does, I've searched and haven't found anything) - but any tips on trying to identify what the cause is? Could it be a bad app maybe?
I tried logcat but didn't really understand it (!) and I wasn't sure if it would record what happened before a battery pull anyway.
Any tips to help get the bottom of this would be much appreciated
Many thanks
Andrew
Click to expand...
Click to collapse
Samsung isn't making ICS for galaxy S .. how were you able to get an official ICS update?

B*gger, wrong thread, meant the Galaxy S2. Sorry, more haste less speed and all that.... Will ask in there instead.
Apologies./

Related

[Q] Soft Keys Not Working

This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?
Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs
That is definitely not normal behaviour.
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.
any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^
I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department
I have the same problem its almost like the soft key is being held down, anyone find a fix for this?
Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.
I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.
I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.
Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492
^^^
Do not do this unless you have a i9000m. You will break your buttons.
electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...

[Q] Plz help with getting froyo on my Galaxy S Vibrant

Hi everyone. Great site, I'm new here. I got a Samsung Galaxy S Vibrant I9000M from bell a couple of weeks ago. I was wondering how to get Froyo on it. I have never mod a phone before, but I have experience modding consoles. My battery on the phone seems to drain very fast even when not using it. I can only get about 1/2 a day on a charge. I'm hoping froyo could fix that.
At this point, should I wait for the official Samsung/Bell release in about 2 weeks? Or should I just go ahead and do it now? I'm worried the bell update will be full of bugs...
I have tried to see if I could get my phone in recovery mode and it worked, by holding Volume up, the home key and Power buttons. Is this the same as the download mode? I don't know where to go from here... witch Rom to use, where to get it and how to get it on my phone.
I also don't know how to backup all my apps/etc. I have kies working but dont see options to backup apps. Should I do a factory reset before starting anything? What is ODIN and is it safe?
Sorry if this as all been asked a million times in the past. I'm just looking at getting the most up to date info to get Froyo on my phone with the less hassle possible. I would appreciate direct help or some links to tutorials. I have looked through the forum, but have a hard time to find what I'm specifically looking for.
Thank you all in advance for your help and time.

[Q] HELP !!! please

hi all i have rooted my New Zealand S I9000T without a problem but everytime i start KIES up and goto update to Froyo i get this error message pop up on the screen
DCAKOREAMITSOBEX
m-obex/security/privacylock
invalid body size
anyone got any ideas ?
i used the search and it appears there is no other mention of this problem in the forums here, i used the regedit to root my phone where i changed the model number from I9000T to I9000M do i have to change it back again in the registry if i do that will it unroot my phone.
any help would be really appreciated thanks and regards to all..
Yeah I read last night that you should have an un-altered version of Kies (on these forums) when updating to Froyo.
You should unroot your phone and uninstall and lagfix if you're going to Froyo anyways... Unless you don't want to get past the Galaxy logo and a black screen!
geesamsungs said:
Yeah I read last night that you should have an un-altered version of Kies (on these forums) when updating to Froyo.
You should unroot your phone and uninstall and lagfix if you're going to Froyo anyways... Unless you don't want to get past the Galaxy logo and a black screen!
Click to expand...
Click to collapse
thanks for the advice but i got it sorted it is now fully rooted and simlock free, i did not run the lag fix as i wanted to see how well froyo was at first, it works fine for me there is no noticeable loss of speed going from one program to another, i am really happy with it.
what i do find disappointing is the lack of control you are given with this phone, it appears to me that there is no way to place different ring tones for each caller or sms text from that person, never mind i can only see things getting better for the android as more and more clever people are jumping aboard for the ride on this fairly new OS.
many thanks and regards....

[Q] samsung captivate wont answer calls

I have a samsung captivate. It is a early model, I got it the day they became available. The phone will not always answer an incoming call. the green answer button comes up but will not swipe. Anyone else have this problem? Will froyo cure this?
Youre gonna need to add some more info....
are you on stock 2.1?
if you did flash a custom Rom which one and which kernel/ modem are you using?
Did you do a restore with titanium? (this is where I had problems when I flashed)
captivate wont answer incoming calls Sometimes
yes complete stock, no mods whatsoever
I had a problem like this when I first got my Captivate as well. My problem was that it wouldn't swipe all the way across the screen. This got very frustrating while driving. The solution, surprisingly, was to make sure my hands weren't completely dry. Without traction on the screen my phone didn't register my fingers.
I don't know if that'll help but there are also other dialers out there on the market that you can try legitimately without rooting or flashing a different ROM (if you're trying to avoid doing those things).
I would do a flash back to stock and do a master clear to rule out any software issues. You can do this without having to root. You just wont be able to back up your apps and system config.
Sent from my SAMSUNG-SGH-I897 using XDA App
It is and always has been completly stock.
Are you rooted? I had this problem every now and then... not very often.. I figured it was due to one of the apps I was running in the background, that was sucking up all the RAM and the phone became unresponsive. I backed up my apps, and flashed stock and then restored only the ones I absolutely wanted... I am sorry, I dont remember which app it was, just know that it was a background process that was collecting some kind of stats! Hope that helps!
By the way how long ago did this start happening?
rskeeters said:
I have a samsung captivate. It is a early model, I got it the day they became available. The phone will not always answer an incoming call. the green answer button comes up but will not swipe. Anyone else have this problem? Will froyo cure this?
Click to expand...
Click to collapse
i had a similar problem even tho i had a custom rom my incoming calls didnt come in at all.i had to Reflash my rom.. idk how similar this situation is but i agree with the other guys.. try reflashing stock
phone is not rooted. I cant tell you how long it has been happening but it appears to be more frequent as of late. The one thing I can ad, when it does it, it may do it several times in a row
Thank you guys for helping the newb.. I appreciat the input!
I occasionally get the same problem on my SGS even before rooting
Sent from my GT-I9000 using Tapatalk
The time it took you to go back and forth on this forum, you could have flashed back to stock and master clear to troubleshoot. The problem isn't going to fix itself.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for all the HELPFUL input
I will try flashing stock
This may be a common sense answer but usually when it doesnt swipe all the way accross for me its because of to much grease ( or sweat) on my hands or on the screen like after lengthy phone calls or if my hands are dirty or something. Try cleaning the screen well, and washing your hands and such. Always fixed for me.
by swipe do you mean it doesnt move at ALL or it goes half way or you cant get it all the way to the other side to answer?
Yeah, i know that when i first turn on my phone and try swiping, nothing will happen, it will just stay green and not respond. After leaving my phone on for a couple of minutes, it usually corrects itself.
This is also a common problem for stock users wanting to use a lockscreen replacement (i.e. widgetlocker).
If you try using widgetlocker without any lagfix, you can get phone call screens you can't interact with for a few seconds.
I have had a similar issue both stock and rommed. I find a lot of time it does have something to do with friction on the screen but also if I have low signal it will happen as well. My phone will actually freeze up to the point of having to remove the battery, this same thing happened on my old Samsung Blackjack II.
Sent from my SAMSUNG-SGH-I897 using XDA App

how to fix turning off issue for samsung i9000 ?

I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...

Categories

Resources