Related
So I've had the vibrant freeze on me about 3 or 4 times out of the 2-3 weeks I've had it so far. It's gone black with the bottom four buttons still lit but it wouldn't shut of via the power button or respond to any other buttons either. Also, one time it froze yesterday after I did a master reset through the factory reset option. This time it froze while I was trying to do a speed test, the screen stayed on in the speed test window but buttons were once again nonresponsive. I haven't replicated it yet though. I have to pull the battery to get it restarted.
Another issue I've experienced a couple of times is the wifi would freeze when I turn it off through the power widget (my normal method of toggling wifi). It says that wifi is turning off but it stays in that state and never actually does. The green light would dim on the power widget as though it's turning off but it sticks there and under wifi info it just says it's turning off. When this happen, wifi will neither turn on nor off and just becomes unresponsive. I have to restart the vibrant to get wifi back to normal.
Anyone else experienced this or have any ideas on these problems?
Samsung Vibrant Freeze
drgnclwk said:
So I've had the vibrant freeze on me about 3 or 4 times out of the 2-3 weeks I've had it so far. It's gone black with the bottom four buttons still lit but it wouldn't shut of via the power button or respond to any other buttons either. Also, one time it froze yesterday after I did a master reset through the factory reset option. This time it froze while I was trying to do a speed test, the screen stayed on in the speed test window but buttons were once again nonresponsive. I haven't replicated it yet though. I have to pull the battery to get it restarted.
Another issue I've experienced a couple of times is the wifi would freeze when I turn it off through the power widget (my normal method of toggling wifi). It says that wifi is turning off but it stays in that state and never actually does. The green light would dim on the power widget as though it's turning off but it sticks there and under wifi info it just says it's turning off. When this happen, wifi will neither turn on nor off and just becomes unresponsive. I have to restart the vibrant to get wifi back to normal.
Anyone else experienced this or have any ideas on these problems?
Click to expand...
Click to collapse
has any solution been found for this ?? i have similar freezing issues with my vibrant .. i found one possible culprit listed on another site .. there is a way to disable the TeleNavGPS app (as you cannot uninstall) .. it is supposed that this interferes with the phone to the point of complete failure
Are you running stock 2.2 from Kies? I had exactly the same problems.
Sent from my SGH-T959 using XDA Premium App
You could try backing up and doing an ODIN flash to KA6. I've had similar lockups with some builds in the past but they are fairly infrequent. Currently running stock KB1 rooted with KA6 radio and it has been smooth for a long while now.
I've tried some of the 2.2.1 Roms, but I absolutely need wifi calling so I stick with stock.
Sent from my SGH-T959 using XDA Premium App
I have the same issue. On my second Vibrant running stock 2.2. About to send this one back for warranty as well. Mine will freeze from the lock screen, either stuck on the screen and the display stays on, or the screen wont come back on from idle.
FirefighterZ said:
I have the same issue. On my second Vibrant running stock 2.2. About to send this one back for warranty as well. Mine will freeze from the lock screen, either stuck on the screen and the display stays on, or the screen wont come back on from idle.
Click to expand...
Click to collapse
Have you tried another ROM? I thought my phone was broken with stock 2.2. Haven't had issues with Bionix.
Sent from my SGH-T959 using XDA Premium App
No other ROMs, I know there are a lot of good ones, but I shouldn't have to root my phone for it to work correctly. Within a week of this current Vibrant I was having these issues. I didn't purchase the Vibrant to flash ROMs, I bought it because of the specs to remain stock. On a side note..I was told after 3 warranty replacements within 90 days I will be able to get another phone from them.
FirefighterZ said:
No other ROMs, I know there are a lot of good ones, but I shouldn't have to root my phone for it to work correctly. Within a week of this current Vibrant I was having these issues. I didn't purchase the Vibrant to flash ROMs, I bought it because of the specs to remain stock. On a side note..I was told after 3 warranty replacements within 90 days I will be able to get another phone from them.
Click to expand...
Click to collapse
Yeah, know what you mean. It is silly that stock is just broken. Hopefully the OTA will be better than the Kies release. (Are they doing an OTA?)
Maybe they'll swap for a Nexus S.
Sent from my SGH-T959 using XDA Premium App
im rooted on android 2.2 but stock rom stock modem stock everything just root. i have had the same wif issue as the op. i just go to settings>wireless settings> wifsettings and turn on wifi that way. if you notice it will say error. 90% of the time this works and you will not have to reboot. i switch from wifi to 3g a lot. i have not figured the cause just yet but this is a work around for now.
as far as deleting the bloatware i rooted and deleted all that crap like sims, and other apps that i do not/will not ever use. there is a thread on which ones are safe to delete. be careful about deleting apps that are used by google such as google talk.
Unreal, Samsung. I wanted to sell my Vibrant, but can't get anywhere near what it's worth because of these stupid issues.
Sent from my SGH-T959 using XDA Premium App
I'm having the same problems!!!
I am now on the 3rd replacement (that's the 4th T-Mobile's Samsung Vibrant 3G!!!) and still having problems.
My phone will just be sitting on my desk at work and I'll hear it buzz a couple times. I know that buzz. It's something "Force Closing" in the background. I will pick my phone up and it will be unresponsive. It will light up the 4 buttons on the bottom of the device, but nothing else. Normally, it will then immediately start rebooting. It will go through the usual start-up screens. It will then show the status bar at the top; battery life, alarm clock, signal, 3G/WiFi, Media Scanning progress. However, the rest of the screen will be black. It will then vibrate once, then 2 more times and do it all over. It repeats this at least once for around an hour EVERY DAY!!! Other times, it will not restart on it's own and I will have to hold down the power button to manually do so.
I have also gone through ALL the troubleshooting I can imagine. All logs, history, texts, cache... EVERYTHING... has been cleared.
Please forgive me for asking, but it appears that I am to possibly root my phone for a resolution... is this true?
Also, has anyone heard of this "3 Returns Within 90 Days" policy with T-Mobile? I could easily do this with this phone. Has anyone had any luck getting them to do that?
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
kga943 said:
i have had my atrix for 4 days now and its locked up 3 times were i had to take the battery out to restart it anyone else have this problem anyone no how to fix it or should i return it for a new one
Click to expand...
Click to collapse
Did you install any applications from the market? Is your phone freezing while a certain application is open or does it freeze even on the homescreen? If you have a lot of applications installed try to deinstall and look if it becomes better. If not try a factory reset. If it still freezes than return it for a new one.
Would you mind saying what you were doing when it locks up?
If it's during Music, it doesn't actually lock up, it just shows a black screen for about half a minute. Everything still functions, it just doesn't show.
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
I have a feeling there is a bad batch of units out there.
Try factory reset and see if it continues to lock up, if it does, return it for another.
kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Sounds like a broken phone. Try a factory reset (if you return it they anyway ask if you did that) and if that won't help get a new one....
kga943 said:
Two times trying to answer a call the screen would not unlock nothing would work I had to take the battery out and just todayit was sitting on my desk and it would not turn on when I tried to use it
The green message light was on very dim and I had to take the battery out
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Same thing happened to me yesterday, the light was very dim green and the phone did not respond until I pulled the battery. It hasn't happened again.
I've already had to replace my Atrix for another issue. Right now my confidence in this phone is not very high, but it is brand new. Lots of issues will probably pop up and be fixed via software updates- at least I hope thats the case.
It really feels like all the issues people are having with this phone are software related. Maybe motorolla will just cave and give us gingerbread with no blur
I've had the same problem while playing music...over the past 3 days after about 30 minutes of tunes it'll lock up and after another 5 reset itself...i've done the reset after the second and it still does it...i'm bout to take it back and exchange it...i expect glitches but damn.
Motorola Atrix (stock)
AT&T Fuze (Energy.RAPHAEL.21916.Sense2.5.Cookie.2.0.sencity)
I have had the issue happen 2 me twice in 3 days, the last time was when adding the note widget to screen. It was not completely locked up just the touch screen, i could press the power off button but the touch screen would not let me shutdown
something you might want to try if a factory reset doesn't work would be a reinstall from the recovery menu.
power your phone off
hold the down volume key and the power button
release the power button once the phone begins to boot
keep holding the down volume button until you see "fastboot" at the top of the screen
now be careful, the down volume button navigates through the boot options and the up volume selects one
so press the down volume button until you come across "android recovery"
once you see it press the up volume button to select it
once you get to the screen with the exclamation mark tap the bottom right of the touchscreen, this should pop up the recovery menu
select wipe data/factory reset
let the phone do it's thing
good luck
I've seen this resolve some audio codec issues that were causing the phone's mic to not work, dunno if it'll work for your issue but it can't hurt to try.
best of luck
bl4ck0ut
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
mrlinux11 said:
I have found a fix for my lockup issue. If the screen is on and lockup (no touch screen) press the power button 2, turns off the display and turns it back on and everything continues to work fine.
Click to expand...
Click to collapse
I have the same problem (screen randomly locks up once or twice a day, buttons dead) and have found the above "solution" to work perfectly, also. The problem however is that pressing the power button twice and unlocking the phone is not exactly elegant especially if the screen locks while you are trying to answer an incoming call.
I changed my battery settings to "performance mode" as I read somewhere that that might help. I will let you know if that seems to resolve the issue.
Changing battery setting doesn't seem to do anything. I still get my share of frozen/locked up screens a few times a day. Still have not figured out how to replicate the behavior. It really does seem random.
I've been suffering from this as well, I'm going to try to exchange my phone and see if that helps.
Exchanged my phone today. So far I haven't seen any locked/frozen screen issues. I am relieved. Maybe there are just a few bad units out there.
Also for what it is worth ... the lady at AT&T told me that taking out the battery while the phone is on would fix it. Since I never figured out how to replicate the behavior I couldn't verify that her suggestion would indeed actually fix the problem and demanded an exchange anyways.
atrix does lock up and have glitches
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
It happened to me as well. I had installed some apps but when it froze it had been off (the screen that is) so it was sitting then when I tried to open it by pressing the power button the green light came on but it would not wake. I removed the battery, replaced it then it did the same thing again (including the green light). I removed and installed the battery once more then it was fine. It must have been something in the backround but not sure as to what that was. Hasnt happened again though.
pedroosan said:
lock up glitch:
While in standby (screen black), it locks up. You obviously don't know when exactly it happens as it's lying around in standby. When you press the powerbutton to wake it up, nothing happens. You can try what you want, long press, several presses, just dead phone. As if the battery losts juice, but 2 times it happened and the battery was above 50%.
Tired to connect the charger while in that lock-up state. Nothing happens The notification light remains black as well.
The 2nd time this happened to me, I had the idea to call myself and see if just the powerbutton has a glitch and the phone is actually running just remaining in standby with a black screen. But nope, the phone didn't ring or wake up.
Only way to recover is to take the battery out.
I didn't mess with my phone and was very careful in which apps I installed. The only ones I have are very populoar 4+star apps:
extended controls
easy profiles
the other apps are most of the time not even running:
photoaf, vignette, imdb, nytimes, fb, skype, pandora, screen filter, droid light, prozoom5x camera
No games at all installed...
The 2nd glitch that happened to me a couple of times is that the finger print sensor is not working: It doesn't display any message as in " did not verify, too short, ..." it's just dead, the only way to get in is to punch in the number code.
This is typically fixed after switching the phone off fully.
Of course skype also doesn't work on my atrix (well known mic issue)
Click to expand...
Click to collapse
strange, skype worked for me... oh well.
did you ever find a solution for the lockup issue, have the same thing, very frustrating but not as frequent as you thankfully.
My Atrix started to freeze up when I undervolted the CPU using SetCPU and I would have to pull the battery out and restart it. I increased the voltage settings and it hasn't locked up since, so if you have undervolted your CPU and your phone is locking up, you should increase the voltages.
The other day I installed the new CM RC2 rom on my HTC Wildfire. Everything went fine for the couple of days until it went into sleep mode and I could not come out of it. I had to pop the battery and when still problems, I re-installed rom - again with flashed kernal 4.1 and up to date gapps.
Managed to get it working. But then same thing again. Overall I had to re-install 5 times yesterday alone!
Out of frustration I tried to re-install my CM RC1 from before with the kernal 4.1. And this was fine again for about an hour, then again, mobile went into sleep mode, and again was left with black screen. Again not able to come out of it.
Am at a loss as to how to get my mobile back up and running. If anybody can help, this would be most appreciated.
Thanks
Does this happen with all ROM's, or simply CM7? Also, what are your overclock values and SetCPU Profiles, if any?
Have only tried cm7 so far. and cpu was not touched. was left at default settings. Am not able now to even boot into recovery. Totally DEAD!
Probably a hardware issue. I doubt CM7 can have such far reaching implications as to make the phone dead. Anyhow, this issue looks uncannily similar to this
Thats worrying.
If I do manage some how to get it switched on, is there anything that you can suggest to stop this happening again?
Also keeping the battery out of the mobile for a 5 mins, SHOULD that help instead of just taking out and imediatley replacing?
Doesnt sound too good. If you manage to switch it on you could try setting your minimum cpu speed to 245mhz+ Although it sounds like you have more serious issues. If its still under warranty I would consider returning it
Thats what I feared.
Thing is, cause it is rooted, it is out of warranty. I dont think I have a leg to stand on.
Its worth a try, they may not even check/notice that its rooted
Well.......
I managed to get it switched on. And decided to try and install Wildpuzzle as I had that on the phone before with no problems. And so all was well......
....untill just now.
Mobile went into sleep mode, and when I pressed the power button to get into it, black screen. Wouldnt come out of sleep mode. So had to pop battery again and after 10 mins, re booted it.
This seems to be the norm now. If it gets a chance to drop off into sleep mode, then I am stuck.
I am starting to pull my hair out.
Have just read on another thread that should try turning off auto rotation and auto brightness.
Fingers crossed this will work.
If the problem occurs throughout various ROMs it could well be hardware related. Flash an RUU (this will get rid of all traces of root) and return it
Will do.
Thanks
cant access cm7 rc2
any ideas why i cannot access or see any file in the website download.cyanogenmod.com regarding cm7 rc2 for buzz/wildfire?
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Have you tried the new 6.1? I'm running it and it is very smooth. I had similar issues on the att version of Shostock. I can't say whether the full wipe or the new rom fixed my issue, but it is running smoothly now.
You could also try running Greenify.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Gage_Hero said:
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Click to expand...
Click to collapse
I don't think I can change the clock speed with my kernel. I will try that but I'm not sure that's the issue since the phone appears to be functioning even when the screen is stuck off. You might be on the something, if I press too many buttons that's usually how I can cause it to reboot/crash.
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Red_81 said:
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Yes, I am on v5.0 and it's set to 384. The issue might not be the clock speed.
This ROM doesn't have support for manually changing the clockspeed anyway.
Any other ideas?
I noticed we both had 32gb. Maybe the tolerances on the chip are not quite as good as the 16gb. I did play with cpu settings because waze would cause my phone to really heat up.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I have since changed to a different kernel and I have not had the issue yet (~13 hours running).
I can only assume this is a bug with the kernel until I have the issue again. My attempts to recreate it on the new kernel have failed.
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
spirodave said:
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
Click to expand...
Click to collapse
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
XGhozt said:
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
Click to expand...
Click to collapse
Right on .. Sounds like a kernel issue to me also ..I ran into the problem more often when I was playing music with the screen off .. Mind you that was on my tmobile gs2..It seemed to me that when any button was pressed to turn the screen on It was like it wasn't scaling through freqs enough to power on.. Hopefully your issue is resolved ... Now I know if I run into this issue in the future ill know its kernel related
I just wanted to follow up here. I noticed the issue happen again but this time it was right after I made a change. I'm using GO TaskManager EX and there is a setting in here to "Clear when turn on screen" and "Clear when turn off screen". When either of these are enabled then it causes the device to take an extra 15 seconds to wake and/or it doesn't wake at all.
Still not 100% sure if this was the original issue, but I thought I would post it in case anyone else is using this as well. Especially since it caused a similar behavior.
Major face-palm moment.