Hi, everyone,
to cut to the chase, here's my problem (video):
They don't allow me to post video since I'm new here, so please check it out on YouTube, it's called Samsung Galaxy S GT-I9000 weird OS problem? (by Getz01)
I used my phone just like any other day, took a few photos while battery was almost done (about 20% left), and then it started breaking all of a sudden in the focus settings menu, and so on.
When I switched to the start screen, this strange occurence from the video appeared.
I tried turning it off, and then turning it on again, I tried taking out the battery, and reducing RAM (I thought it might not have enough of it).
It's Galaxy S I9000 model, I use stock Android that came with it. Phone was bought completely new in a licensed store last year, its OS wasn't meddled with, or anything like that. I like to keep things new, I mean, not to touch its software or hardware unless I have to, like it seems now.
Version: 2.2
I9000XXJPP
Kernel ver. : 2.6.32.9
[email protected] #1
FROYO.XFJP9
Any advice/help is more than welcome!
That is really wierd. I've had an SI for just over 2 years and never seen anything like that. It seems like you have a problem with the digitizer. Have you installed any apps prior to the problem occuring? If yes, uninstall them. If no, then you should maybe back up everything and do a factory reset. If that doesn't work I don't know what to suggest.
Getz01 said:
Hi, everyone,
to cut to the chase, here's my problem (video):
They don't allow me to post video since I'm new here, so please check it out on YouTube, it's called Samsung Galaxy S GT-I9000 weird OS problem? (by Getz01)
I used my phone just like any other day, took a few photos while battery was almost done (about 20% left), and then it started breaking all of a sudden in the focus settings menu, and so on.
When I switched to the start screen, this strange occurence from the video appeared.
I tried turning it off, and then turning it on again, I tried taking out the battery, and reducing RAM (I thought it might not have enough of it).
It's Galaxy S I9000 model, I use stock Android that came with it. Phone was bought completely new in a licensed store last year, its OS wasn't meddled with, or anything like that. I like to keep things new, I mean, not to touch its software or hardware unless I have to, like it seems now.
Version: 2.2
I9000XXJPP
Kernel ver. : 2.6.32.9
[email protected] #1
FROYO.XFJP9
Any advice/help is more than welcome!
Click to expand...
Click to collapse
It seems that you have to reinstall the rom, backup anything with titanium backup app and reinstall, i hope that helps
you can follow this tutorial to reinstall: http://forum.xda-developers.com/showthread.php?t=1583026
I have tried with the factory reset (I've made the backup of the phonebook as the most important thing) and the problem still persists.
I've tried to "squeeze" gently the limits of the screen and it did help a bit, but then it got back to the same.
Related
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...
Hi Guys and Gals
Hoping someone can help meor point me to somewhere/one who can please
Recently picked up an i9000 which is on the orange network and was running:
PDA: i9000bvjm5
PHONE: i9000bvjm1
CSC: i9000orajm3
everything worked just fine, i was getting tons of battery life out of it in idle, until i noticed that when i had 'anti-shake' ticked in the camera mode, it wouldnt allow me to adjust the exposure, so i contacted samsung and they told me that upgrading my firmware to 2.3.3 via Kies would solve the problem, i promptly did so and yes, it fixed the problem (hurrah!)
HOWEVER!
i now have a much larger issue with my phone in that before updating the firmware it would eat about 5% of my battery in 24hrs if not in use
Now i need to charge this thing twice a day minimum even when im not using it!!! aaaaaaaarrrggghhh!
i've shut off all unneccessary services like background data etc etc etc still no help, digging into the battery stats themselves tells me its the android OS thats eating 78% of my battery, while its idling! WTF! previous to this it was the display that ate the battery, but it cant be that when the displays off can it!
How on earth can i get back to my original firmware (eclair) or update to a newer version where this problem is fixed please?
i am a bit of a nob/noob at this so please try to K.I.S.S.
I cant live like this!!!! lol
will a factory data reset do the trick? or doesn't that affect the firmware?
Any help greatly appreciated
Yours in desperation x
Dan
If you google "Android OS bug" you'll see that this is a common problem. You said you upgraded to 2.3.3, but I believe they didn't correct this issue until 2.3.5—although I may be wrong about that.
You can update to whatever firmware you want by flashing your phone. This will void your warranty. Likewise, you can flash back to 2.2 if you so please. You can flash your device using a program called Odin or Heimdall. Search for tutorials, you'll find plenty.
As for the actual bug, in my times of testing a ROM that was susceptable to the Android OS bug, I usually just restarted my phone and saw it go away. Clearing the cache may help as well, but I really couldn't say for sure. Try a simple reboot and see if the problem persists.
big props upichie!
i had exhaustively googled this problem before troubling you guys but it appears i was using the wrong words, doh!
alas im still none the wiser ( all the guides i can find 'assume' i know too much already about their terms for things and im lost
i turn my phone off, within 5 minutes of restarting it the OS is once again draining my battery completely
i clear my cache every 5 minutes and within 2 minutes its flippin eating me again
is odin or heindall another thing i install onto my pc (not my phone?) like kies to revert back to the old firmware? eclair 2.1 i had nailed! if it aint broke dont fix it, why dont i listen to myself!
and why the funk would they release a firmware that does this in the first place?
my head is spinning with the retardedness of all this, i come from a background where testing things exhaustively is part of the job, so i cant for the life of me understand why they would launch with something that sucks sooo bad!
im also at a slight disadvantage because i have the orange firmware and slightly different settings to most who have eclair, i think
jesus wept i just dont know anymore lol i think ill just throw the thing in the bin and go back to my old sony w810i cos that lasted 7 days on battery!
funk this firmware, funk this nonsense and funk this 12 hrs battery drain when not even using it, what a funkin palava!!!!
oh and funk you too samsung for telling me to upgrade my firmware you funkers!!!!!
im going to cry now lol
No worries! We've all been there. The terminology is confusing, but once you get a good grasp of it, you realize how simple it is to know what you need to know. I'm here to help.
Odin and Heimdall are programs for your PC, although I don't believe either need to be installed (they're just standalone executables). They both are programs designed to flash a new firmware onto your phone. You simply download the firmware files (for Odin it comes in 1 to 3 files, but Heimdall if I recall correctly only uses 1 file) and then use the program to flash the new firmware.
Just so you're aware, if your Android OS is showing a high percentage, that percentage will not go away until you fully recharge the phone, as it would keep the record of the Android OS previously draining your battery.
I'm honestly not entirely sure how to help you. You could download the app called BettterBatteryStats and do some digging to find out what is causing your phone to not be able to enter/maintain deep sleep (otherwise known as a "wakelock"), but you sound slightly inexperienced and probably wouldn't be thrilled with that idea.
Alternatively, is there any option in Kies to downgrade to 2.1 again? Maybe contact Samsung and see what they have to say. You upgraded from 2.1 to 2.3 because of their suggestion, and now your phone is getting unusable battery life. It only seems logical they'd have a way to downgrade.
If you have any questions about terminology, how things work, or anything at all related to your i9000, please do not hesitate to ask! We're here to help in any way that we can.
Try to flash xxjvt with semaphore 1.8.2 kernel. If i not use my i9000 just for calls/maild and music my battery lasts 2 days with 3g and wifi on.
Try to wipe your battery stats after a full charge.
Sent from my GT-I9000 using xda premium
Hi All
New to the forum.
I did search this topic but didn't find anything finite.
I have had my Note for 3 weeks now.
In that time there has been 2 occasions in which my phone seems to have shut down while asleep.
There was a brief mention in another topic about it being the TWlauncher or an SD card problem.
I'm just really looking for any advice as to whether there is any settings i could change to stop this happening.
Thanks
Edit:
I am on Stock Rom 2.3.6
Do you have installed any anti virus apps?
What apps do you have installed?
Does it shut down when it's in your pocket or just leaving it alone on the table?
Edit:
Maybe you can upload a logcat output?
I have the same problem. But I do not remember what the phone was doing at the time. But I will be back if this happens again .
I had that kind of problem with an HTC Desire some time ago and HTC changed the motherboard , problem was solved.
I had this problem with my Galaxy Note but I was never able to locate the cause because it also happens on a stock firmware, There were a couple of similar posts before but they were never solved, same deal at a local forum a few people had the issue custom ROM or stock. When I started to use RevoNote HD with V3 I think these 'Sleep of deaths' stopped AFAIK.
Army92 said:
Do you have installed any anti virus apps?
What apps do you have installed?
Does it shut down when it's in your pocket or just leaving it alone on the table?
Edit:
Maybe you can upload a logcat output?
Click to expand...
Click to collapse
- I do have antivirus installed (AVG)
- I have many apps installed (the list would be too big to put here)
- It shut down whilst on the table
- Sorry but i am not aware how to view a logcat output
Well, I read in a german forum that anti virus programs can cause those shutdowns/reboots. I personally don't believe this but you can try to uninstall it.
You can find logcat here:
https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result&hl=en
Just install it and let it run. Wait for the problem to occur and then reopen this app, save the log and put it up here.
It also can be "just" a black screen.
So that the phone is awake but the screen is black, so it seems like it's down.
It can help to push the power button again.
(For example this problem sometimes occurs at CM9.)
Thanks for the help.
I have download CatLog. Fingers crossed that i wont have to use it
I had read about the black screen problem and that it could be linked to a lock screen issue so I have downloaded WidgetLocker as an alternative to see if that makes any difference (I don't hold too much hope for this as it is only ever running on top of the touchwiz lockscreen but i may aswell try)
i just got my note a few weeks ago and have been suffering this problem as well. it has happened twice now where the note has switched itself off, and my morning alarm has not gone off! which is quite tragic as i rely on it to get to work.
i wonder if this is a software or a hardware problem...
any other owners facing the same problem?
I've had my Note around three weeks and in the first week I had this happen to me twice. I cannot say what caused it (I'm on Stock Rom), as I went a bit app happy and downloaded all sorts of apps when I first got it. After the first week I cleaned up a lot of the apps (Which included AVG, GoLauncher) and I've only had it happen one time since.
I was using the app "My Country" or "Airport City" and I think it was being slow, so spammed it with commands - causing it to reboot. Which is probably unrelated to the previous problems, I have however looked into CatLog - so if it happens again, I will post some details up here :]
Hi I have a strange problem with my Samsung Galaxy S Vibrant (I9000M) running 2.3.3 stock.
Description:
a) Booting the phone would show the big S animation and bong sound however after that the animation repeats in a loop with no more sound. The phone never reaches the home screen. I notice this mostly in the morning when I wake up.
b) Usually during the morning when I wake up to check the time the screen doesn't turn on but it seems as if the phone is still working; the chime for plugging in the charger sounds. (I thought the battery was dead but it was actually at 60%)
What I've done so far:
a) I brought it back to the vendor and got a new phone.
b) Holding the power button would turn off the phone, then I would turn it back on. Sometimes it requires that I pull out the battery which results in losing all my data on the internal memory like a factory reset.
Question:
I'm highly concerned. I've gone through two of these phones and problem "b" is always a prelude to problem "a". I'd like to know if there is a possible solution and/or what the problem might be?
Note:
a) The problem started happening a day or so after I started using Samsung IM. (Skype was installed but never used)
b) The problem started the morning right after I installed Skype. (I have since uninstalled Skype, it's still happening )
You should not be losing data on your SD card by pulling the battery.
Did they give you a new phone or a refurb?
What's the build number of your phone? Should be a number under the battery in YY.MM format.
Hi Black Rose
I was talking about the internal memory not the sd card.
It's a new phone.
The build is 11.11.
If you are running stock 2.3.3 and having those issues, I think the phone is faulty.
My wife is running 2.3.3 on an 11.03 build and has no problems.
The fact that you are losing data when you pull the battery sounds like the internal memory is failing.
Alright, thanks. Do you have an idea what causes the screen to not turn on for the second phone? (This new one doesn't loose internal memory on battery pull)
I had that happen to my own phone (also an 11.03) once with Froyo 2.2 and once with 2.3.3.
With Froyo I was able to plug in the charger and the phone "woke up".
The only time it happened on 2.3.3 I received a couple of notifications at the same time and had to power it off to get the phone to work again. It never happened again in the several months I was running 2.3.3.
Okay!
Thank you Black Rose for giving me some useful information. I was just worried that this would lead to something a lot worse.
Much appreciated!
This is my 3rd phone had the exact same problem as you I heard it was something with the mother board there is a board in here dedicated to the problems with the gt-i9000m
Sent from my GT-I9000 using Tapatalk
Thanks for letting me know bambam1978; I hadn't realized there was a whole topic for all the problems. I've been searching for the specific problem where most have customs roms which is why I started this one.
Hi Guys,
I have this phone for many years, but suddenly the random reboots started approx 2-3 months ago, running originally KitKat 4.4.4 at this time. Before that I was rooted the phone and I supposed it could be something with that. However, flashing back & factory resets didn't help at all, clearing dalvik caches as well. What I tried up to now:
1. Upgraded/Downgraded the bootloader -- no change
2. Tried different recovery modes -- CWM & TWRP(the current one)
3. Different ROMs -- no change, the sudden restarts persist.
(4. Updated the radio -- the signal got quite better)
Three days ago I've upgraded to Lollipop 5.1.1 (the Cyanogenmod 12.1), the same story continued after a while (different applications installed).
There's one thing for sure: flashing the factories always results into a very stable phone at the beginning, installing some more applications leads to the same state -- random and frequent restarts.
I've checked the hardware -- the power button looks ok, it's definitely not the main cause b/c it reboots without touching! The CPU temp & free memory look quite good too.
Now, the current situation is as follows:
- flashed ROM (official one): 2016-03-03 Poland (T-mobile) 4.4.4 I9305XXUFOL2 I9305TPLFOL2 (seems like the most stable till now)
- installed ATK (Advanced Task Killer) -- configured to kill all applications aggressively when the screen goes off.
For me it looks like the ATK helps much, although I don't know the reason. Also, memory checked, I've executed all kind of possible tests up to the phone -- all appears as OK. Also, I don't know if it's related to the issue but I moved all possible apps installed to the SD card. The internal memory has been formatted via TWRP before the last ROM installation... Does anyone have any idea what could be the reason for the sudden restarts? It restarts even in Safe Mode, without any obvious reason and not touching the phone at all. The CPU load at the times of restart is quite low, the temperature as well. I doubt if the RAM is corrupted or maybe the NAND has some bad blocks. Are there any useful utils for tests that could be executed?
PS: I attach some log file, which I gathered once I was running the Cyanogenmod 12.1 (Lollipop). As I stated above the situation is the same when running 4.4.4 and 5.1.1. Sometimes after such a restart, it sticks in a boot-loop (if I boot manually via the GUI in recovery or download mode it will not).
Current versions:
---------------------
Android: 4.4.4
Baseband: I9305XXUFOA1
Kernel: 3.0.31-4282983/[email protected] #1
Build: KTU84P.I9305XXUFOL2
SELinux: Enforcing
Recovery: TWRP
I beg for your help on this! Cheers!
Same problem here...
Hi there
I'm having this same annoying issue with my Samsung GT-I9305. It suddenly restarts without doing absolutely nothing but looking at the screen or scrolling a text or just sending a sms/whatsapp/whatever.... I started trying to restart the phone (nah) turning it off and back on (nah) changing the battery for another one that I have here with me (nah)... After that, I extracted the SD Card and leave the phone only with internal storage (again, nothing happened but restarting randomly). I tried not installing apps such as FB, even Pebble App or just stopped sycronizing my phone with my Pebble Time via Bluetooth, but with the same and well known result: still restarting suddenly. I have noticed that when Google Play detects that there are few apps with a newer version asking to be updated, the phone restarts too! I tried deactivating this option in Google Play, just letting me to decide when and how to upgrade my apps, but It seems that it still detects the app upgrading needs and keep doing it the same way.
About a year ago, I found the same problem with my phone, but in that time it was related to the power button, it seems that it was pressed all the time and the device felt into a rebooting cycle. I check some blogs and I solved the problem cleaning the button with this electronic cleaning spray. I almost drowned my Samsung but I let it dry for a few hours. It worked fine, until now.
My cellphone is still in Android 4.3 (I9305ZHUCNB1) I don't know why I can't upgrade it to a newer version, even when I see that the 4.4 is available for this model. Right now, I'm thinking about change the cellphone and just forget the whole problem. But I'm just exploring again to see if I can find a last solution that tackles this annoying issue.
Did you manage to solve this problem??
Thanks in advance!
Unfortunately not, I had to buy a new phone. I guess the processor or other element suddenly broke, there's no other explanation to me. Also, as you see no any reasonable support in the forum.. Anyway, wish you a good luck with this.
Not so good here too...
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
fjpp81 said:
Thank you. But unfortunately for me too... Today my phone went black screened suddenly, when booting only got to Samsung GTI9305 logo... I tried to restart through secure mode and the other one you get pressing power plus home plus volume high, and when tried to do a cache cleaning and rebooting it showed some mmcblk failed issues. So I couldn't do so much to revert this situation. I already bought a new phone, not Samsung of course. I have read that some people had the same problem as me just because they let the battery reach a very low level in one opportunity, and something in the internal memory went broke. So it was a great phone, for three years and half, but it's so bad that it fails this way unexpectedly and without any apparent reason...
Yeh... There's no much support here, especially with old flagship cellphones...
Click to expand...
Click to collapse
Sorry for bothering this thread also... I got success by replacing the display!