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...
I have been having troubles with my O2X ever since I did the LG online upgrade to baseband 0725-V10? with Froyo.
The main problem was dead periods for approximately 3 to 4 seconds while on calls.
I tolerated this and waited for the official LG Gingerbread update thinking it would fix the problems.
After upgrading to Gingerbread, not only did the dead periods continue, but I had a few new problems:
- people were sending me SMS messages which never arrived
- people would try to call me and get a disconnected signal
- I would occasionally get failed SMS messages when trying to send
- I would occasionally get a dead tone when trying to make a call
- people were complaining that they could hardly hear me during a voice call
Last weekend I decided to try fixing it myself.
I followed Paul's instructions and back-graded to the old 0622-V20a baseband for Gingerbread to see if this would fix things (I left LG Gingerbread on the phone).
I thought I had smashed the problem until today... when I had the phone tethered to my notebook, the phone "locked up" and would not allow me to call or send an SMS.
Going in and out of airplane mode was enough to fix this... but it was very disappointing that the phone is still not working properly.
In addition, for some reason, the phone now sometimes switches to a strange screen after sending an SMS.
I am afraid to forward-grade to 0725 again because it seemed to be worse than 0622.
Does the problem sound like the baseband, Gingerbread or other?
I have downloaded 0725-V20l and 0725-V20q and am toying with the idea of installing one of them.
Judging by the symptoms, does anyone know whether one of these two basebands would cure the problem?
If not, do I have to bite the bullet, root the phone and lose warranty, and maybe install Modaco or another version of Gingerbread?
Thanks
Hello guys
Ran into a snafu yesterday, clicked home a N6 demo-ex from one of the internetstores here, it was cheap and I've always wanted one. Of course it came with a pre-unlocked bootloader and everything else you'd expect from a used Nexus, but I wasn't too bothered about that, I would have unlocked it myself anyways. Flashed MM on it as soon as the images were available. I played around with it for a few more hours, then late last night I decided I should move my simcard to the N6 and try Speedtest and a few other goodies. Speedtest went just fine, got the usual 64 Mbit over LTE, then .. I'll call my automated bank just to check the earpiece and speakers. "Dial .... call ended". Try again. "Dial... call ended". Put the simcard back into my Nexus 5, dialed the same number, worked perfectly. Back into the N6, same number, it dials, then just as it's supposed to start ringing, "call ended". Has anyone got any ideas as to what could be wrong here?
Done so far to find the error:
*Reboot *duh*
*Reflash MM
*Flashed 5.1.1, thinking it was a new modem and my simcard didnt like it. Sim is about 2 weeks old by the way.
*A couple of factory resets, just to be sure
This is the very last Nexus 6 these guys had on the shelves so I would really, really rather not have to return it but of course a phone that you can't use for phonecalls .. I already own a Nexus 7, don't need a miniversion of it. Bright ideas or even far fetched guesses appreciated!
Hey bud, I had a similar issue with my phone as well and the way to fix it is by rebooting exactly 6 times in a row....literally. Power on, power off power on power off etc........ Ive encountered that issue several times, it usually happens when i left my phone die and then reboot after full charge. I could only use data, no voice/text and sometimes it would be backwards, no data, voice text only
Hello!
My first thread on this one of a kind forum! So here's my problem: sometimes, when I get a call, the phone lights up and shows the caller name and call receiving interface, but no matter how many times I swipe left or right, it hangs and eventually the call drops. But on the other side, the call keeps on ringing. Which means the person on the other side thinks I am a lazy bum who never picks up :| (ie. My mother :|) There are good days and the bad days, meaning, I experience only one or two call drops on some days and then there are days when every freaking call gets dropped.
Solutions I have tried:
1) I noticed the problem first when I updated my phone to lollipop (official update). So I figured maybe the update was at fault. When the problem got severe I decided to roll the version back to kitkat. So I unlocked the boot loader and flashed the firmware.
2) Unfortunately, the problem persisted even then. It's important to understand this problem only started after the update. First four months with original firmware were total bliss.
3) Since even the original firmware gave me a lot of hell I decided to bid adieu to the whole institution of moto firmware and flashed cyanogen 12. The problem is still sometimes evident. Not as much as the moto firmware. But it's still there.
What to do? Is my hardware at fault? I hope not. If not the hardware, then how to fix this software problem? And why is it happening in cyanogen if it's a moto firmware issue? What can I do? Please help! Thanks.
Dear friends
I'm using Nexus 6
I droped my phone in water and immediately I got it out, but after that my speakers stopped working only for media, was working for notifications. I thought factory reset will help. After doing that speakers still not working and phone started rebooting again and again, and also started overheating, then after few minutes my speakers started working and after two days overheating issues is also resolved,
But now I Insert Sim then its not detecting, the I tried to find solutions on YouTube then I got to know it happens due to IMEI Number, so I checked my IMEI Number was Unknown and Baseband is also unknown.
Please help me with this issue....
Djvickky9 said:
Dear friends
I'm using Nexus 6
I droped my phone in water and immediately I got it out, but after that my speakers stopped working only for media, was working for notifications. I thought factory reset will help. After doing that speakers still not working and phone started rebooting again and again, and also started overheating, then after few minutes my speakers started working and after two days overheating issues is also resolved,
But now I Insert Sim then its not detecting, the I tried to find solutions on YouTube then I got to know it happens due to IMEI Number, so I checked my IMEI Number was Unknown and Baseband is also unknown.
Please help me with this issue....
Click to expand...
Click to collapse
You either have hardware failure... Or you need to reflash the factory images
have you solved problem about imei , becouse im too belong from that problem , help me if you got out
Sent from my Nexus 6 using XDA Free mobile app