Related
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
I called today the customer service of my carrier "oi" and I spent kinda 30 minutes talking, trying to solve a problem.
When I saw, my phone was in a bootloop with the cyanogenmod boot and I was continuing to talk, without any interrumption.
The only difference was thet the phone was hot!
Running at 1.4 with the last netarchy kernel my max was 38!!! (low)
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
slowz3r said:
Random reboots are a S/W problem, Google is aware of the issue and will be pushing out an update that fixes the problem.
there is nothing your carriers can do about the issue
Click to expand...
Click to collapse
I hope so!
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Serious_Beans said:
So does EVERYONE has this problem? Is it a software problem?
I'm running on CM7 RC1 with Netarchy 1.2.4, reboots quite frequently, and it's annoying. Just had another odd bug, phone froze and wouldn't turn on and vibrated non stop for 30 seconds. Phone is buggy when ending a call, it freezes a lot at that point too, anyone else having these problems?
Click to expand...
Click to collapse
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
No random reboots here, got it on the 3rd. Phone runs smooth as silk. I'm on stock 2.3.2. Out of all the phones I've owned this has been the most stable.
Could my phone possibly be from a different batch? I'm not experiencing any of the issues alot of other people are besides 100% init process, which I solved with keeping USB debugging on.
Sent from my Nexus S using XDA App
ruben8448 said:
Your running netarchy 1.2.4 which is still in its test phase. That's where your issue is. If you switch to a more stable one then you should be fine
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I don't think it's the kernel, even stock users have the reboot problems.
I don't have any such problem on Cyanogenmod 7 rc1...
iKitsunee said:
I don't think it's the kernel, even stock users have the reboot problems.
Click to expand...
Click to collapse
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
ruben8448 said:
We get random reboots from time to time but with the freezing and all the other issues it sounds like the kernel. I tried that kernel and I had the same issues. I just switched to 1.2.2 and I was good to go
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ah, I'm actually using that kernel as well, hasn't happened to me but I suppose it might vary from phone to phone.
jerrycycle said:
Just a couple of questions. Are you using a frequency changer app example, setcpu cpu tuner? Do you have the set on boot checked for main profile? I have found if the set on boot is check to have random reboots on calls. I uncheck and no longer have the reboots on calls. That was the only time I ever had the reboots happen. Just a question and something to check in your settings.
Click to expand...
Click to collapse
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Serious_Beans said:
I have it set on boot,but I'm running at stock speeds. I am not overclocking and still having these problems. I'm going to try a bunch of other roms and kernels and see what my results are, it COULD be the phone it self, but I doubt it.
And thanks everyone for all the responses.
Click to expand...
Click to collapse
The kernel is set to default at stock setting so no need to have it set on boot. It isn't going to overclock unless you raise the cpu past 1g
google have already said that the problem its just s/w and they are going to fix it with an update and it's not the new 2.3.3! Hope it don't take much longer!!
Sent from my Nexus S using XDA App
There is a stock kernel for cm7 out that has all the voodoo engagement and ext 4 hack
I've had random reboots and it only happens to me when I'm using bluetooth.
Sent from my Nexus S using XDA App
its been over one month now and i never had such problem with mine..its running smoothly both with stock and cm7..
I experienced my first random reboot today. Installed clocksync and was fine. Today I loaded the app... screen was blank then saw the boot animation.
Sent from my Nexus S
I experienced 2 reboots in a row trying to retrieve a service from my mobile operator. I got so frustrated ´cause the mobile operator service takes too long,
the last time I looked, elapsed 7 minutes, few minutes later, reboot...
Became afraid to call again from the nexus, not trusting anymore
wifi on, sync on, bluetooth off, gps off, it was charging with the regular charger, factory rom and kernel, not rooted, launcher pro
I also have random reboots. it's strange though, it goes to the boot animation for some time, looks like the phone reboots, then all the apps and launcher is reloaded, but if you check the phone boot time under settings -> about, the uptime is not reset.
can you guys confirm that your boot times are also no reset during the randon reboots oft he known google android software issue for nexus s?
thanks,
Automatically rebooting problem. Please help. Tried hard reset, but no luck. Don't know when it is happening.
Sent from my GT-I9000 using XDA App
ramanadodda said:
Automatically rebooting problem. Please help. Tried hard reset, but no luck. Don't know when it is happening.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
How often is it rebooting?
Does it boot at all?
Can you reach desktop?
If not, have you flashed previously your rom?
Please supply more details.
Virnik0 said:
How often is it rebooting?
Does it boot at all?
Can you reach desktop?
If not, have you flashed previously your rom?
Please supply more details.
Click to expand...
Click to collapse
Some times once in a day, and sometimes more than a week, basically it is rebooting when I am playing games for more than 10 minutes.
As a phone it is working fine. I am still not rooted.
Build version : FROYO.DDJP6
Firmware Version : 2.2
FYI - One more thing, I bought this mobile just 20 days back. Anyway thank you for quick reply.
Twenty days i would return under warranty for a fix ..
jje
Exchange it, if you have not done any changes to rom, as this firmware has no such bug, probably its a hardware issue.
Is your cell get heat up while playing?
ramanadodda said:
Automatically rebooting problem. Please help. Tried hard reset, but no luck. Don't know when it is happening.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App
Monu123 said:
Exchange it, if you have not done any changes to rom, as this firmware has no such bug, probably its a hardware issue.
Is your cell get heat up while playing?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yes, sometimes it heats gets heat while playing.. I am going to shop now, to replace it.
This seems to be some sort of ROM bug. Just reflash to Gingerbread, and be fine.
You can use my howto for that, for example:
http://forum.xda-developers.com/showthread.php?t=818556
Virnik0 said:
This seems to be some sort of ROM bug. Just reflash to Gingerbread, and be fine.
You can use my howto for that, for example:
http://forum.xda-developers.com/showthread.php?t=818556
Click to expand...
Click to collapse
I flashed with Gingerbread... My God.... Now the device is working like a rocket.... Thanks
ramanadodda said:
I flashed with Gingerbread... My God.... Now the device is working like a rocket.... Thanks
Click to expand...
Click to collapse
Did you found my howto working? If so, leave comment in that thread concerning little explanation of your own feelings about it (was it easy or complicated), thanks
Sent from my GT-I9000 using XDA Premium App
same
I got the same problem happens very often when im making phone calls
im on 2.3
MIUI RC6
Just restarts when im making phone calls (sometimes 2 minutes in the call sometimes 15..)
Any ideas?
slimx91 said:
I got the same problem happens very often when im making phone calls
im on 2.3
MIUI RC6
Just restarts when im making phone calls (sometimes 2 minutes in the call sometimes 15..)
Any ideas?
Click to expand...
Click to collapse
I found the issue with Advanced Task Killer. I am using Android Booster. Now it is working fine.
This has happened to me twice in 4 weeks on jvk. Talking on phone then it quickly boots up. Faster than a normal off then power on though.
Also.
Maybe why the screen goes to sleep during a call...
If you set screen off to say 10 mins, when on a call the screen stays active for duration of call except when held to ear, then screen off sensor kicks in and its working normal. Seems screen off setting also switches off phone screen at set time instead of staying active.
Sent from my GT-I9000 using XDA App
slimx91 said:
I got the same problem happens very often when im making phone calls
im on 2.3
MIUI RC6
Just restarts when im making phone calls (sometimes 2 minutes in the call sometimes 15..)
Any ideas?
Click to expand...
Click to collapse
Try flashing new CM7 SGS platypus kernel 20110425 03 whatsitsname, fixed it for me.
slimx91 said:
I got the same problem happens very often when im making phone calls
im on 2.3
MIUI RC6
Just restarts when im making phone calls (sometimes 2 minutes in the call sometimes 15..)
Any ideas?
Click to expand...
Click to collapse
flash zach's antlion kernel or tk4-glitch kernel. the 'twoface' kernel might be the problem
Mine also rebooted, but it was on 2.1. The problem was that there was a bug in samsung's code. When I tdisabled the power saving mode under Settings > Display. The phone stopped rebooting.
I have 2.2.1 now and power saving mode is enabled without any problems.
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705
Thanks, I will try that out tonight and report!
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.
Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!
Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...
need help also
Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?
xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time
When placing phone call my device crashes with purple led flash.
cell signal normal, text messages work, cell data works
I'm not sure if problem lies in hardware or software(bad flash, radio, ect)
I replaced the digitizer
Currently running Kang ICS RC0-9.0 | faux123-v025
Had same problem with Neutrino 2.1
Any ideas or test suggestions?
PROBLEM SOLVED, WHERE DID MY FRIDAY NIGHT GO THOUGH?
*deleted post incorrect information
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
dac1227 said:
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
are you already on 2.3.4.91 ?
chamoy said:
are you already on 2.3.4.91 ?
Click to expand...
Click to collapse
No, I couldn't get the zip for 4.91 to flash for some reason so I did Neutrino 2.5 after sever data formats.
update: on on GB 4.5, same problem persists
SOLVED
How did you solve the issue?
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Well the issue was less solved but minimized in the end.
After many fastboot formats and CWM flashes, I ended up fruitcaking back to 2.3.4, that's when the problem started to be less of a hassle; meaning the screen would come back on and buttons/soft-keys were again responsive and a battery pull wasn't needed.
I re-installed Turls ICS and the problem is still present, but it doesn't hinder making or receiving calls, I just hold my breath with each.
I'm suspecting that when flashing either the kernels or roms, things are not getting cleaned and formatted as well as they ought to be. I know there is a universal CWM zip floating around somewhere (seen it in the skyrocket forum). We've had similar issues in the skyrocket forum where remnants of previous flashes were being persistent, or resistant to format attempts.
I messed with it for hours trying to fix so I cannot say for sure what I did to make it a non-immediate issue, but if others describe like problems I try and help.
xscottishx27 said:
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Click to expand...
Click to collapse
I was having the issue with Neutrino 2.1, 2.5; Turl ICS, and stock 2.3.4. The latter seemed to be the most effective method I employed to fix, without bricking.
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
a67543210 said:
That's called the black screen of death. It's an ICS bug. For now, rebooting seems to be the only solution ice seen on xda.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I can't believe this ! Is this a SAMSUNG or an Android/ICS problem ?
My version is:
4.0.3
IM74K.XXLPQ
Any custom ROMs addressed this issue or how can you avoid this on ICS? Is the only solution to go back to Gingerbread ?
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Its a bit like continual posting in the wrong forum nobody knows why ??
jje
rumz82 said:
Hi guys, hope your well.
I am having a similar issue too. I am on Hydrogen AOKP Rom, and I get exactly the same. However, apart from just the blank screen, my phone gets extremely hot too.The only way to get it back on is to remove the battery. Very annoying!!
I cant seem to figure what it is. I have tried to search here on XDA for the resolution but to no avail. Could it be the Kernal? The Modem? Tweaking via SetCPU? or a combination of all? Atleast if I could get pointed to the right direction that'll be a start! lol
Are you guys getting the overheating problem too?
Click to expand...
Click to collapse
No overheating (yet) you can help if you can keep logcatting through usb cable till it lock/standby freezes and your screen won't come on when pressing power ..
Install SDK + Drivers, write in commandprompt:
adb shell logcat > save.txt
Wait for the error / freeze where screen won't come on.
Then paste here or upload somewhere might contain a lead to a solution!
Double - sry - galaxy forgot login
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
thedadio said:
It's a kernel issue. I had exactly the same problem. Flash the latest siyah kernel that should sort it out. I went through 10 different Roms till I worked it out
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Nah!
It's there on all the kernels. I myself am a Siyah user.
I moved back to GB for this weird and terribly serious issue, but that time i didn't know it was a common problem.
This is ICS' best feature for sure.
I really CAN NOT believe how this issue is NOT yet known well and haven't brought in to front line. Google knows about it and yet I haven't seen any official statements about it. How ****in unbelievable or not perhaps? Google way?? Well **** it.
Utter Nonsense. What i wonder is, really, does any Android user actually use the phone but show off only??
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
gtcardwhere said:
I can almost reliably reproduce this problem.
I'm on ICS LP7 stock XEU version. When I have downloads running with Ttorrent, there's an almost 50% chance that the screen will not turn on once it goes to sleep. The phone is not frozen as my downloads continue to run; just that nothing is being shown on the display. If you hold the volume down button you will feel the phone vibrate to tell you it went into silent mode, which means the phone didn't freeze. After about a minute or so if I try again everything will work as normal, until I put the screen to sleep again.
Click to expand...
Click to collapse
Do the logcat as I provided the correct command to extract it to a file.
Then do your torrent thing, and make it crash- so we can debug !
Used to happen, since I installed latest hydrog3n-ICS rom (13-05) never had those again!
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
sunshean said:
have you uv your phone so much?
i tried to uv my phone so much, and it can't turn on screen when i lockscreen about 1min
Click to expand...
Click to collapse
uv?
ultra-violet ? is my phone in danger of skincancer ?
dezzadk said:
I recently wiped all of my phone (factory+cache) and installed the latest 4.0.3 official update from SAMSUNG.
I also enabled the FULL DISK ENCRYPTION while doing this.
I am now waiting to decrypt it to see if this problem persits if I turn the encryption off.
The problem is that if I leave my phone locked for a few hours/minutes it randomly won't turn on the screen again, when I press the power button.
A hard reboot (holding) fixes this everytime. But this is not a fix, we all know.
It never happened on Gingerbread 2.3.5.
I am beginning to suspect there's a bug in the ICS firmware, although it's 4.0.3, it could slip through.
It's hard to say what's causing the trouble. I have connected the phone to USB now. Waiting for the symptom to show again. I assume I can get a good logcat.
adb shell logcat > logcat.txt
So I'm waiting for an error / event of POWER button at this moment, and will keep logging till it produces the same error again.
Regards,
Click to expand...
Click to collapse
Hi,
It happened to me as well after the ICS update and I tried to plug the AC charger to see what happens, and surprise...the screen turned on .
It's not a fix (especially when away with no accessories) but it's better than nothing, hope this helps; also you should try plugging the USB cable. Tell me if it helps.
Thanks,
dezzadk said:
uv?
ultra-violet ? is my phone in danger of skincancer ?
Click to expand...
Click to collapse
Haaaaahahah! He means under volting. I don't know if you was serious lol but just saying. I'm on cm9 but don't have this problem :-/.
Sent from my GT-I9100 using xda premium
Yep,I mean under volting, you need to look your kernel, and I think it doesn't work fine because your kernel has under volting so much.
Sent from my GT-I9100 using Tapatalk
Reading around and installing load monitor from play store should fix this until a better solution is found
Sent from my GT-I9100 using Tapatalk 2
Best solution is to stay on GB because is more stable, until ICS gets better cooked!