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...
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
Hey XDA,
I hope you guys can help me with this annoying problem I am having with my Xperia V.
Two weeks ago I flashed UniQue3 on my phone since I was pretty satisfied with the previous version and I wanted to try the new one. (I had stock installed before that, since it had android 4.3).
Then crazy stuff started happening: My phone would just reboot when I was typing a message or browsing the web. No biggy, this happened before sometime as well. This time it was different. It happened constantly. I could not use Whatsapp for longer than 5 min before my phone just rebooted. Funny thing is this only happened when I was not charging it. It happened while charging it as well, but not nearly as often, maybe once every 5 hours.
My phone would not shut down either if I did not use my screen. I can listen to music for hours without it rebooting, but as soon as I try to answer or even read a message my phone reboots...
So I thought it might be the ROM. I installed CyanogenMod and at first it was better. But after two days everything started again. I am really confused as to what is wrong and I can't find a proper answer online. Some say it's Android 4.3, others say it's the battery.
So I was hoping you guys could help me out.
Greetings,
Krytos.
Try flashing the stock Rom and see if the problem still happens
Sent from my HTC One_M8 using XDA Free mobile app
Just flashed the stock rom and it did not help. Issue is still present.
Which tells you it's a hardware prob = bacterie
Yeah, that's what I thought. Gladly I bought a battery like three days ago, so I hope that will fix my issues.
maybe hardware problem of battery or even board.
Try to lock boot loader if it is open.
i'm having some serious problems with reboots. it happens at least once or more a day. i researched some yesterday and some people say factory reset helps others say flashing a custom rom did the trick. i wiped and installed CM12 last night and the phone just froze up on me for about 2 min then rebooted.
is anyone else having this problem?
been happening a few times for me on rastapop rom with elementlx or lean kernel never had one problem when a was on sinlessrom
If you're getting random reboots on stock, flashing custom is not going g to help. Best bet is to flash fully stock after a wipe. If its still a problem, you probably need to be thinking about warranty
In wondering if it's not happening to more people and they don't realize it. I know it's happening when in my pocket as well cause I'll grab the phone at times and it tells me I have several apps available for update in play store. Once I clear that it won't come up again until I reboot the phone.
Sent from my Nexus 6
Browsing around I found this thread that seems related. http://forum.xda-developers.com/showthread.php?t=3013352
Sent from my Nexus 6
DualSportDad said:
In wondering if it's not happening to more people and they don't realize it. I know it's happening when in my pocket as well cause I'll grab the phone at times and it tells me I have several apps available for update in play store. Once I clear that it won't come up again until I reboot the phone.
Click to expand...
Click to collapse
Checking system uptime from the terminal confirms that my phone has definitely not rebooted in 8 days, 20 hours, 34 minutes, and 1 second.
I've been having this problem since I got my phone in November 2014. It happens several times a week. Here's the discussion thread on Google Product Forums. They say they're working on a fix. BTW, I've tried troubleshooting over the phone with T-Mobile tech support and didn't have any luck with what they suggested.
https://productforums.google.com/forum/#!topic/nexus/9aVUBrwdUZU[1-25-false]
So I've been going threw this for a while now. I have had the day of today , early morning went to court for a hearing, pulled my phone it to check the time and it was already rebooting. Figured wth I'll call Motorola today about this. Called them and the noon English speaking women on the phone kept asking me to do a factory reset etc after I tried explaining that I have factory reset the phone 3 times already, 2 times before flashing a factory image (5.1) and once after to get my storage (64gb) to show up properly. Finally I asked for a supervisor. Again another women that barely spoke English (don't think I'm racist or anything here, I just get sick and tired of having to repeat myself and asking them to repeat themselves. It turns a 15 min phone call into a 30-45 min one) and the lady starts asking me to hold the power button for 30 sec etc to hard boot it. Again after I explained that I flashed a factory image to the phone and still have the problem. By the end of the call she was telling me that when I get the replacement phone and it continues to have the reboot problem to hard reboot the phone daily to avoid random reboots. I asked if they all had this problem and she said that they have been trying to fix it but there is no solution. Wtf! So now do I believe this lady and deal with it or do I get a replacement. T-Mobile wants $20 for a replacement to save me the hassle of having to put up $500 while I wait for Motorola to exchange my phone.
Hi all,
I am completely running out of things to try and do now.
After installing Android 7 on my Note 5 I had the strangest issue that i in general have never seen on a phone. The screen is simply black (which isnt that strange) and the phone is fully functional. Bare with me, after reseting it multiple times so it would finally come on the screen goes crazy and turns goes into so many colours (if it turns on that is). Its either that or jumps all around the phone, quite literally it glitches out completely. Its like one of those virus cut scenes you see in movies, it goes different colours, glitches out, jumps around and completely misformats.
From the beginning i knew this was not a broken screen.
So far i have tried.
1. Factory reseting the phone. That gave me about 5 minutes of normal use until i locked the phone and it wouldnt unlock again.
2. Factrory reseting multiple times... again to no avail, it would work for short periods of time and glitch out again.
3. Reflashing stock Android 7 in Odin. - No avail.
4. Flashing Dr.Kretans Rom... worked for 1 day which made me so happy and think that the problem was solved but then the same problem persisted.
5. Installing Arters Kernel.. (arter97-kernel-n920cig-22.0) Nothing... literally did that today and still NOTHING
6. Re partitioning. Quickest process and no avail.
In more detail, if the phone does sucessfully boot, and bare in mind sometimes it takes more than 2 hours to get ANYTHING on the screen (including recovery which doesnt boot up either until the initial apperance of something on the screen)
I tried taking the phone to a phone shop before doing anything myself and since in England this phone was never released theyre refusing to touch it. I tried calling samsung and they dont want to do anything either cause its not a UK variant.
Could someone please tell me anything else i can try. I feel like im totally running out of options here.
My phone details are as follow
Galaxy Note 5
SM-920I Singapore Singtel Variant
Running on 6.01 (i downgraded from Kretan)
And the kernel is the one previously mentioned v.22.0
I would appreciate anyone's help or suggestions so much at this point. All these problems started since the 7.0 update a few weeks back :/
Oh its also running TWRP recovery (arter97-recovery-n920cig-22.0-twrp_3.0.2-0.tar)