Related
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
I wanna know if anyone else has this issue or not when click an app like a game it takes up to 10 seconds for it to run and after exiting sometimes the main screen is very delayed and sometimes unresponsive when scrolling left and right. I also have an issue of the phone not wanting to switch back to 4g if in 3g or 1x just stuck until I reboot or restart it. Wanna know if I should get this one replaced or not. Also GPS is horrible never accurate. It say in running little kids on the sidewalk over constantly or running threw people house. I have factory data restored it but same problem. Need to know if I need new one?
Zinsko said:
I wanna know if anyone else has this issue or not when click an app like a game it takes up to 10 seconds for it to run and after exiting sometimes the main screen is very delayed and sometimes unresponsive when scrolling left and right. I also have an issue of the phone not wanting to switch back to 4g if in 3g or 1x just stuck until I reboot or restart it. Wanna know if I should get this one replaced or not. Also GPS is horrible never accurate. It say in running little kids on the sidewalk over constantly or running threw people house. I have factory data restored it but same problem. Need to know if I need new one?
Click to expand...
Click to collapse
It does happen. Try a different kernel or over clocking.
this happens to me occasionally, usually only when the battery is hot/doing a LOT of things at once. (meaning when i'm charging and using pandora over bluetooth, wireless tether, and waze at once) the phone lags up so much that when i press the home button, the haptic vibrate stays on for about 3 seconds.... this is when i know that its happening - and i'll just pull the battery...
If you're running stock & it's been like that since day one, you might consider exchanging it. If you're running a custom rom/kernel, reflash & leave it at default settings for a few days & see if the problems resolve
Sent from my ADR6400L using XDA App
I've never had the lag issue you speak of, however, the gps issue I have seen, but has been fixed in recent custom roms and will be addressed in the update. If you are on stock, you might want to just wait it out for 9 more days till the OTA rolls out. If you are using a custom rom/kernel combo, what are you using?
sublimaze said:
If you're running stock & it's been like that since day one, you might consider exchanging it. If you're running a custom rom/kernel, reflash & leave it at default settings for a few days & see if the problems resolve
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
+1
I also forgot to mention that i'm on BAMF 1.8 with the kernel that it comes with.
If your rooted, i'd recommend unchecking your "set at boot" and profiles in SetCPU, reboot, and see if it continues. As said above, if unrooted... a call to verizon may be in order.
My phone is not rooted every phone I have rooted besides like 2 I have bricked. But yeah I don't get why they didn't run this stupid phone a dule core. I got to play with a phone that had a dule core and response is so amazing.
Then you should take it back to verizon & exchange it for another. Your Tbolt shouldn't be like that out of the box. I've never had GPS issues, even on stock it would lock within a few seconds. And dual core is overrated unless you have apps that actually take advantage of it (not many). No wonder you were impressed with dual core phones lol. My mildly overclocked Tbolt runs Sense just as fluidly as any Atrix runs MotoBlur
Sent from my ADR6400L using XDA App
Okay thanks I have been looking for an excuse to tell them basterds off.
For the pass week I have been experiencing screen freezes / screen lock ups......to the point I have to do a battery pull....I never had this issues before til recently I've tried every rom and it does the same thing after a few days or so I've even ran roms that I've never had any issues with before but i still get lock ups....any ideas!!! I don't wanna take it in cuz I don't want to do the HTC unlocking once they send me a refurb!!
Sent from my PG86100 using Tapatalk
Could it be heat related? Mine is.
I am going for a second refurbished e3d and hitting it with a hairdryer first thing out of the box to see if I can get it to reboot due to moderate heat.
A month ago, refurbished phones were 1.4 hboot.
Can't be heat related I watch movies just to burn my battery dry and nothing goes wrong but idk but it possibly could be heat related
Sent from my PG86100 using Tapatalk
M phone was horribly hot this weekend and was perfectly stable. What the heck?!?
Heat is either a necessary precondition or it is humidity related. Those (and updated apps, as they hit the market) are all that have changed between stability and the previous rebooting abyss.
Maybe random really is random.
Oh, I still can't use the walts kernel that comes with CR 2.5. Something about it hates my phone and causes massive random rebooting.
Freeza's stock kernel is a million times more stable, only leaving me with the more minor rebooting topic we are posting about here.
Try this... http://forum.xda-developers.com/showpost.php?p=18246407&postcount=2861
I'm getting freezes also, anytime my phone screen times out. The phone will lock up and you have to hold power button plus volume up and down to reboot or battery pull.
I just did this fix and testing now, not sure if it fixes it yet...
Sent from my PG86100 using Tapatalk
^^^didn't work for me... Getting the lockups.
Sent from my PG86100 using Tapatalk
Questions - Just trying to help
OP :
Are you using any 3rd party roms - mods - themes- etc.
?
If so, I can tell you , from personal experience, that ViperRom seemed to affect my phone (stock kernel, last version, not the latest) in this way. I was not overclocking, nothing special just the basic rom and it seemed to randomly lock up, and get quite warm. Many, many others however are quite happy with his rom without any issues.
Me personally, I have moved to Virus'es (lol) infected rom, Im loving it, stable, fast, beautiful theme, and it seems like the developer is a little more involved than Viper was.
Just my 2c, Not trying to trash any of the dev's I appreciate all of the hard work hobbyists put into this, once again, just trying to be helpful.
--DT
deathtech said:
OP :
Are you using any 3rd party roms - mods - themes- etc.
?
If so, I can tell you , from personal experience, that ViperRom seemed to affect my phone (stock kernel, last version, not the latest) in this way. I was not overclocking, nothing special just the basic rom and it seemed to randomly lock up, and get quite warm. Many, many others however are quite happy with his rom without any issues.
Me personally, I have moved to Virus'es (lol) infected rom, Im loving it, stable, fast, beautiful theme, and it seems like the developer is a little more involved than Viper was.
Just my 2c, Not trying to trash any of the dev's I appreciate all of the hard work hobbyists put into this, once again, just trying to be helpful.
--DT
Click to expand...
Click to collapse
I'm running virus news rev and I'm getting the lockups...
It happens while I leave phone idle and freezes screen up and requires battery yank or power down and volume button reset.
I just flashed back to virus airbourne and no lockups.
Seems to happen on 2.3.4 roms only.
Sent from my PG86100 using Tapatalk
If you are running any of the roms that change the automatic dimming settings than that may be your problem. For some reason, anytime Steel would add that feature to his rom everyone would start having the lockups and screen freezing. Check to see if your rom has altered these settings and if it has remove that update and you should be fine.
Every single kernel I have tried with the exception of netarchy's silverneedle on 2.3.3 has given me random lockups after about a day of use.
I have since reverted back to the Stock kernel on 2.3.4 and all is well.
Yea i have used vipers newest and even went back to the good ol decks ROM and had lock ups I'm on deck now with no custom kernel so i will do more testing then slowly add things to see what the culprit is
Sent from my PG86100 using Tapatalk
Chauleyboii said:
Yea i have used vipers newest and even went back to the good ol decks ROM and had lock ups I'm on deck now with no custom kernel so i will do more testing then slowly add things to see what the culprit is
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Keep us updated, want to figure these lockups out...
I think its probably more hardware related. I'm stock everything and have had this almost catch fire 3 times now. Not like a little hot, but hot to where I have to put it down. I too have had a bunch of screen freezes lately, only a few force restarts. The high temp thing is random. First was taking video. Second time was uploading a few pics to facebook, third time....this last sunday was a good one. Had it plugged in for about 2.5hrs. My dad grabbed it and threw it down because he didn't expect it to be as hot as it was. I was like WTF? He gave me the phone and it was on fire, with only 25-30 charge. This was using the HTC charging stuff that came with the phone. I keep deleting the battery temp app so i didn't get actual temps at the time. I'm gonna try for a new one tomorrow, hopefully get upgraded to 1.40 from 1.50.
gokart2 said:
I think its probably more hardware related. I'm stock everything and have had this almost catch fire 3 times now. Not like a little hot, but hot to where I have to put it down. I too have had a bunch of screen freezes lately, only a few force restarts. The high temp thing is random. First was taking video. Second time was uploading a few pics to facebook, third time....this last sunday was a good one. Had it plugged in for about 2.5hrs. My dad grabbed it and threw it down because he didn't expect it to be as hot as it was. I was like WTF? He gave me the phone and it was on fire, with only 25-30 charge. This was using the HTC charging stuff that came with the phone. I keep deleting the battery temp app so i didn't get actual temps at the time. I'm gonna try for a new one tomorrow, hopefully get upgraded to 1.40 from 1.50.
Click to expand...
Click to collapse
That's crazy I never had heating issues like that before!! But maybe ill do everything to get my phone working harder to see if I can create that issue
Sent from my PG86100 using Tapatalk
I'm running JT's vanilla GB [over Heimdall'ed stock EH03] on my fascinate.
I use my fascinate as my alarm clock, and I woke up this morning to a extremely choppy ringtone. < and that is is the understatement of the day.
Anyway, I try to press "dismiss" to dismiss my alarm, and it feels like the screen is not responding. I press the power button, and it takes probably like 5 seconds to complete the CRT animation. After that, I can see the screen is still on (hard to tell unless in the dark with the AMOLED), and it won't do a thing after that until I 3-button-combo or take out the battery.
As a side note, it was also doing this on my previous rom, SuperClean3 v8.1. One of the main reasons I switched back to JT's vanilla gb.
The first night the alarm worked fine. [2 days ago] Yesterday, I was watching some video files, I pressed the power button, I left for a few minutes, I came back and it was frozen. [Took foreverrrrrr for the CRT turn-on animation, and screen did not respond].
This is really really annoying, and I would really like to find out what is wrong with my phone.
One more thing I should mention.. this same kind of thing happened once in a while on the stock froyo firmware, when I bought it on craigslist. I would come to it sometimes and turn it on, and the lockscreen would show and the touchscreen wouldn't respond. I had to take the batt. out then cuz I didn't know about 3-button-combo.
The USB would only charge and not transfer files and only would charge.
So I sent it in cuz samsung said I had 1 mo. warranty left, and then they said they fixed everything in the ticked, and I got it back and it seemed to work. [the usb file transfer worked..]
So can anybody give me any advice? Like logcat? Would that tell me what is causing this problem?
Any help is appreciated!
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
k_nivesout said:
Are your CPU settings stock? I've noticed the "sleep of death", which sounds similar to your issue, when I was undervolted too much at 100mhz.
Click to expand...
Click to collapse
Thanks for the reply. I will look into this 'sleep of death' thing.
And I haven't edited my cpu settings. I went to superuser to be sure and the only apps listed are Superuser, Terminal Emulator, and Titanium Backup.
So I just went on a 1-hour trip, and when I got to where I was going, this happened to me again. The screen-on animation was slower than a slug on salt. 3-button-combo reset, I let it reboot, and it was fine.
I just got home 1/2 hr ago and it did it again.
Sigh.. well I only have like 2 apps that always run, 3G Watchdog and Equalizer. I've uninstalled 3G WD just to see if it does anything.
Edit: I will install ROM Manager and set the absolute minimum freq to 200mhz, and see what happens. That would make sense if it's messing up at 100mhz when the screen goes off, and then it's not able to think fast enough to up it back to 1ghz.
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have much expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
k_nivesout said:
It sounds like it might be an issue with your phone if the problem follows you between roms and your kernel settings are stock. That is unless this is a more common issue with those roms, but I don't think they are. The sleep of death issue that I've run into before is simply the phone refusing to wake up, requiring a 3-button reset/battery pull, so I'm not sure about the slowness to respond before freezing that you've run in to.
I'd try setting the minimum frequency to 200mhz with an app like voltage control (rom manager is for rom flashing, backups/restore), maybe that would help the phone's responsiveness regarding waking up properly. I'm not sure though since when I had the sleep of death issue mentioned before, I just lessened the undervolting I had done and it seemed to resolve it. I don't have expertise to share on your specific issue though, I'm sorry. I'd almost be inclined to believe that it might be a more phone-specific problem if you're running stock kernel settings on roms where other users haven't reported the same issue, but trying the 200mhz thing can't hurt.
Click to expand...
Click to collapse
My bad, I meant ROM Toolbox. It has lots of apps built in including a CPU slider. Anyhow disabling 100mhz did not fix anything. So tonight I will set the minimum frequency to 800 or even 1000 mhz because I want to see if that stops the freezing up. If it does, then I'll know it's a clock speed issue.
I should also mention I sent it in for USB repair. It wouldn't connect to PC, it'd only charge. I also mentioned to Samsung it would lock up every so often from waking up. They upgraded froyo to gingerbread and said it passed all tests, sent it back, I never stayed on the firmware they gave me long enough to see if it froze up.
So on the stock roms, do they underclock the cpu frequency by default??
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
k_nivesout said:
I don't believe that the cpu is underclocked or undervolted by default. I'd try flashing the stock firmware (EH03), and seeing if the issue happens there as well. Although I thought you mentioned it happened to you on superclean before, and I think that's just a modified stock rom? But it would be worth trying I suppose, then you could be sure it's a hardware issue and see about possibly getting a replacement. I'm assuming that you're still under warranty if you've sent the phone back recently enough for them to put gingerbread on it?
Other than that, I can't really think of anything else.. Maybe try jumping on IRC sometime and hitting up some of the people (that are generally more knowledgeable than myself) on there, they'd probably be able to give you a good idea of whether or not it's an issue with your specific phone. Although that's what it sounds like to me, I'm no expert.
Click to expand...
Click to collapse
Lol, when I sent it in there was like half a month or so left on the warranty, the person said it expires at the end of this month [Dec] so I figure maybe a day or two.
What's the IRC channel info? freenode?
EDIT: I forgot to ask something. So you are saying, the stock firmware [EH03 or froyo EH09] runs the cpu clock constantly at 1GHz? Even when it's sleeping? Wouldn't that give bad battery life? [lol, speaking of batteries, I just got a new one and it's charging]
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
gotsflat4love said:
I had this happen to me 6 months ago. You my friend need a replacement phone. It has nothing to do with the rom/kernal. I tried everything. Sometimes phones just take a crap. Got a replacement. Ran the same thing I ran when it was happening and haven't had a problem since. Sorry to hear. Just explain it it Verizon and see what they do.
Click to expand...
Click to collapse
This is bad news indeed, since I am not even sure how many days I have on the warranty. But I think I will Odin EH03, and then set the alarm tonight. If I wake up and it's done it again, I will call up samsung and tell them and hopefully I have warranty.
But please, tell me, when you tried to turn on the phone did the CRT animation go very slowly? and then when you pressed power, it wouldn't come on again?
Edit 2: alright! I call samsung and I have warranty until Jan 9. Woot.. So I set up an RMA with samsung, I will Odin EH03 tonight. If I wake up to a choppy alarm and a non-responsive screen, I shall send it to samsung ASAP and I hope they gimme a brand new Fascinate. that would be awesome..
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
k_nivesout said:
Nice, glad to hear you got the warranty thing figured out. I was thinking it sounded like an issue with your phone in specific and it sounds like the other poster's experience would suggest that. Hopefully it's an issue that they can replicate and don't give you any issues getting a replacement.
To answer your question, no, the stock kernel settings wouldn't keep the processor at the highest frequency. The only way I can see that happening is if you set the screen-off profile to "performance", and I'm not sure why anyone would do that because it would indeed yield bad battery life I'd think. I'm guessing the stock kernel defaults to an "ondemand"-like profile, where it would scale the frequency according to load and favor lower frequencies or go in to a deep sleep when the screen is off.
Click to expand...
Click to collapse
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
So this morning, I woke up to my iPod's alarm, which I had set as a backup a few minutes after my Phone alarm should have gone off. I went to see if the phone was frozen, like I was hoping, so that it would reliably broken , but instead it was off. I turn it on, it shows the full green battery.. then it boots up like nothing was wrong. But I think that turning off randomly every night [which I assume it should do every time] is enough for Samsung to realize my phone really is screwed and that they need to do something about that.
So anyway, I printed out the label, packed my phone, and dropped my phone off at the local UPS drop off.
Hopefully I will be receiving some good news from samsung soon [i.e. that they will give me a replacement... ]
mvmacd said:
Oh. well the reason I asked is because you said this: I don't believe that the cpu is underclocked or undervolted by default.
Click to expand...
Click to collapse
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
k_nivesout said:
Yeah, looking back on that, I misspoke. Technically, UNDERvolting/clocking is just reducing the voltage or clock speed from the "default" kernel settings. So technically, since the stock settings are the "default", they (by definition) would not be "undervolted" or "underclocked". I guess all I was trying to say is that I'm sure whatever the default settings are, they're set for a balance of performance, battery life, and stability. Just because the default max frequency is 1000mhz, doesn't mean that the CPU will stay there, that's what kernel governors are for essentially: to tell the CPU how to scale based on load (as I understand it at least).
Hopefully things go well with the replacement. Just curious, why are you dealing with Samsung directly as opposed to Verizon?
Click to expand...
Click to collapse
1. I'm not the original owner
2. I'm not a Verizon subscriber. PagePlus Celluar [A verizon MVNO] is my service provider. They have much better plans, including monthly, and prepaid, if you ask me.
Kernel issue.
sent from my Sensation XD
Yess..
Good news! Got an email saying my phone has been shipped:
Code:
Original Problem:
TECHNICAL INQUIRY - PHONE FREEZING / LOCKED UP - FREEZE/DELAY BETWEEN MENU FUNCTIONS
Problem found:
BAD BGA COMPONENT
Solution:
REPLACED PBA
I guess the PBA is basically the motherboard? I suppose that could have been the cause of overnight freezing, and so my phone should be fixed.
Nice.. Just 2 days left on my warranty. Cutting it kinda close, I know lol
Very well done sir
sent from my Sensation XD
Alright So here it goes:
Problem: EVO 3D CDMA version constantly locks up when in a screen off state, making it where the unlock button does not work. (Holding down Volume -, Volume +, and Power reboots it) which can mean that it doesn't lock up it actually shuts off..maybe.
What I've tried: Somebody gave me the idea to take the 2.08 RUU and go back to stock, take OTA for 2.17 and reroot and unlock the bootloader using HTC's method (keep in mind i've been on hboot 1.5 the entire time). This didn't seem to help (although did fix a random reboot problem, but besides the point.)
I have also tried uninstalling any application relating to the Prox. Sensor (explanation in notes below)
Notes: I believe everytime that I have seen the issue, the screen has been locked and the phone has been put in my pocket. It virtually never happens when it is out in the open which leads me to believe maybe something with the proximity sensor.
Also this does not seem to be specific to any ROM, Although I have not flashed an AOSP ROM as of yet
Any ways any advice would be appreciated, because as you know a mobile device does spend quite some time in your pocket and it would suck to keep having to reboot it everytime I take it out.
even if you can't provide advice, thanks for reading
almost sounds like it would be a hardware issue with the power button itself... have you tried pulling the battery out and booting into your fastboot screen and into the rom itsself?
ther have also been reports of the handset itself being too warm for it to function...maybe try keeping it out in the open and then unlocking it and see how it works from there... post your results please... im curious now
wloftus said:
almost sounds like it would be a hardware issue with the power button itself... have you tried pulling the battery out and booting into your fastboot screen and into the rom itsself?
Click to expand...
Click to collapse
Yea I can do that easily. The power button works fine, I can keep unlocking/locking whenever, it's just whenever I lock the screen and then put it in my pocket, 95% of the time it tends to lock up (or shut off idk what exactly is going on yet) and then performing a hard reset or taking the battery out will boot it back up
see my edit about the over heating... you responded before i could post it fast enough lol
I had a similar issue. It turned out to be an app. In my case, opensignal maps which is a cell tower and WiFi location app.
Sent from my Clean and MeanROM 3D
wloftus said:
see my edit about the over heating... you responded before i could post it fast enough lol
Click to expand...
Click to collapse
Oh ok, Idk if that could be it. Using it I can leave it out in the open for hours (with wifi tether running and it charging at the same time) and it will unlock and function fine.
but without all of that, 5 min in my pocket and done, I get the lockups/shutoff
guitardoc64 said:
I had a similar issue. It turned out to be an app. In my case, opensignal maps which is a cell tower and WiFi location app.
Sent from my Clean and MeanROM 3D
Click to expand...
Click to collapse
Yea I thought it might have been an app, but ive uninstalled every app I could think might cause the problem so I don't know I can't rule that out though
notsointeresting said:
Oh ok, Idk if that could be it. Using it I can leave it out in the open for hours (with wifi tether running and it charging at the same time) and it will unlock and function fine.
but without all of that, 5 min in my pocket and done, I get the lockups/shutoff
Yea I thought it might have been an app, but ive uninstalled every app I could think might cause the problem so I don't know I can't rule that out though
Click to expand...
Click to collapse
i run the wifi tehter app as well and it will heat up your phone substantially putting in your poclet can be insulating it and then your body heat building it up further... but if you leave it out of your pocket and it performs fine... i would definitely explore that route....
wloftus said:
i run the wifi tehter app as well and it will heat up your phone substantially putting in your poclet can be insulating it and then your body heat building it up further... but if you leave it out of your pocket and it performs fine... i would definitely explore that route....
Click to expand...
Click to collapse
Yes it does, but I most definitely don't run it while in my pocket or in another concealed area. I was just giving an example of when it would be substantially hotter than when in it is in my pocket
notsointeresting said:
Yes it does, but I most definitely don't run it while in my pocket or in another concealed area. I was just giving an example of when it would be substantially hotter than when in it is in my pocket
Click to expand...
Click to collapse
it for sure does not heat up too much running the tether but the insulation of your pocket can be causing it... tether on monitors the battery temp... not the internal temp of the phone itself ... id be more inclined to lean to it over heating
wloftus said:
it for sure does not heat up too much running the tether but the insulation of your pocket can be causing it... tether on monitors the battery temp... not the internal temp of the phone itself ... id be more inclined to lean to it over heating
Click to expand...
Click to collapse
And I could go with that, but compared to using things like Wifi Tether I can tell it gets a lot hotter than when I take it out of my pocket and notice it won't turn on.
And I mean 2-3 Minutes and it locks up ,which is why I said it might be tied into the proximity sensor, and it hasn't been in my pocket every single time, but like 95% it has.
notsointeresting said:
And I could go with that, but compared to using things like Wifi Tether I can tell it gets a lot hotter than when I take it out of my pocket and notice it won't turn on.
And I mean 2-3 Minutes and it locks up ,which is why I said it might be tied into the proximity sensor, and it hasn't been in my pocket every single time, but like 95% it has.
Click to expand...
Click to collapse
againt you MAY be right.... i wont negate that... but the battery temp and the phone temp settings are totally different ill leave it at that bc thats all i can come up with but like i said again... you may be right... i still think it is an overheating on the core hardware of the phone itself....
what ROM?
what kernel?
any cpu control apps?
list of root apps?
il Duce said:
what ROM?
what kernel?
any cpu control apps?
list of root apps?
Click to expand...
Click to collapse
Currently using MeanROM, but have also seen the issue in my time using, CleanROM Reborn, and Eternity 3.0.
Always stock OTA Kernel at stock clock speeds.
There have been times when I have used SetCPU and times when I haven't, never a difference.
Root Explorer, Titanium Backup,SetCPU,SuperUser (of Course), Wireless Tether App,
notsointeresting said:
Currently using MeanROM, but have also seen the issue in my time using, CleanROM Reborn, and Eternity 3.0.
Always stock OTA Kernel at stock clock speeds.
There have been times when I have used SetCPU and times when I haven't, never a difference.
Root Explorer, Titanium Backup,SetCPU,SuperUser (of Course), Wireless Tether App,
Click to expand...
Click to collapse
fyi it's quite possible those ROMs set a LOW minimum (sleep) frequency, which SOME devices don't like. stock (like HTC stock) is 384000, but a LOT of devs set theirs to 192000 to conserve battery.
check here and report YOUR value:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
if it's 192000 that's likely your problem, set it to 384000. if it's already 384000 then it's something else, you ever looked at the scripts you have in init.d and what they're doing?
EDIT: and if you REALLY wanna know what's happening and what's erroring, hook up adb and watch the log, pull a last_kmsg, dmesg, etc. Maybe it would help narrow things down
il Duce said:
fyi it's quite possible those ROMs set a LOW minimum (sleep) frequency, which SOME devices don't like. stock (like HTC stock) is 384000, but a LOT of devs set theirs to 192000 to conserve battery.
check here and report YOUR value:
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
if it's 192000 that's likely your problem, set it to 384000. if it's already 384000 then it's something else, you ever looked at the scripts you have in init.d and what they're doing?
EDIT: and if you REALLY wanna know what's happening and what's erroring, hook up adb and watch the log, pull a last_kmsg, dmesg, etc. Maybe it would help narrow things down
Click to expand...
Click to collapse
It was set to 486mhz
And I was going to pull a logcat, but since this seems to happen when in a pocket for some reason its hard to keep it connected to a cable lol, but ill try the others
seriously the most simplest of answera isa the one over looked.....it sounds too basic and the rest are over delving in to the matter sometimes the right answer is tho most simplest.....
wloftus said:
seriously the most simplest of answera isa the one over looked.....it sounds too basic and the rest are over delving in to the matter sometimes the right answer is tho most simplest.....
Click to expand...
Click to collapse
Well I think im going to go back to stock unrooted via RUU for a couple days, this will be the most obvious way to figure out if it is an overheating/hardware problem.
But in using the device, and seeing the conditions this problem arises in , it just doesn't feel like it. but hell you might be right lol , we'll see
notsointeresting said:
Well I think im going to go back to stock unrooted via RUU for a couple days, this will be the most obvious way to figure out if it is an overheating/hardware problem.
But in using the device, and seeing the conditions this problem arises in , it just doesn't feel like it. but hell you might be right lol , we'll see
Click to expand...
Click to collapse
Have you made any progress with this? I think I have the exact same problem you have. At first I thought it was because of the pocket, but now I figured out it only freezes if the screen is turned off and the phone is not connected to a charger.