Related
OK guys...so I was plagued with this problem like a lot of other people using the g-tab. I tried all of the other fixes like installing a different kernel, keeping wifi and/or cpu alive while sleeping, wiping and re-installing, etc. None of these worked for me like many others. I started experimenting, and I decided that the problem had to be something involving CPU load. I created a profile in SetCPU that reduced the CPU frequency to a minimum value while the screen was off and/or sleeping, and !!! Problem solved. I can turn screen off for a second, a minute or an hour and when I push the power button, the tab wakes immediately. This definitely solved the problem for me, and I would like some feedback as to whether this fixes it for anyone else. As a side-note, I am running the Vegan-GingerBread as advertised (STOCK).
Cheers!!!
what was the profile that you set on set cpu? And did this help the wifi from disconnecting when it sleeps?
camblue said:
what was the profile that you set on set cpu? And did this help the wifi from disconnecting when it sleeps?
Click to expand...
Click to collapse
In SetCPU I created a profile that was "Screen Off" MAX: 216, MIN:216, and it fixed all of my issues!!!
Try my latest kernel (version9) with no setcpu and let me know how it goes
Question...
clemsyn said:
Try my latest kernel (version9) with no setcpu and let me know how it goes
Click to expand...
Click to collapse
KK...will do, and I will let you know!!! Why has GOJIMI not implemented this if it fixes the problems though??? Is this recent?
subyfan said:
KK...will do, and I will let you know!!! Why has GOJIMI not implemented this if it fixes the problems though??? Is this recent?
Click to expand...
Click to collapse
Yes, just uploaded recently. Lmk how it goes. I also fixed Bluetooth
I hate to keep asking but does your kernal fix the wifi not coming back on from sleep?
Thank you will try it but does that affect the battery strength at all?
subyfan said:
In SetCPU I created a profile that was "Screen Off" MAX: 216, MIN:216, and it fixed all of my issues!!!
Click to expand...
Click to collapse
camblue said:
Thank you will try it but does that affect the battery strength at all?
Click to expand...
Click to collapse
I would think that it would only help battery seeing as how you are forcing the CPU down to it's lowest frequency.
subyfan said:
KK...will do, and I will let you know!!! Why has GOJIMI not implemented this if it fixes the problems though??? Is this recent?
Click to expand...
Click to collapse
Im gonna guess because what may be a "fix" for you is not for everyone. These tabs are tempermental at best and what works on some does not work on others. Demanding a dev include something you think is a fix in his work is kinda arrogant don't you think. If you can do better where is the link to your custom rom?
Moved to Q&A.
What are you talking about?
thebadfrog said:
Im gonna guess because what may be a "fix" for you is not for everyone. These tabs are tempermental at best and what works on some does not work on others. Demanding a dev include something you think is a fix in his work is kinda arrogant don't you think. If you can do better where is the link to your custom rom?
Click to expand...
Click to collapse
Did you read the thread? I am not talking about GOJIMI implementing MY fix...go back and actually read. Clemsyn, a VERY reputable g tab dev, has found a universal fix for the issue.
You think so? There is no universal fix for most issues. Clemsyn and pershoot have been battling this issue for months. Gojimi is a VERY reputable g tab dev as well. Along with several other people. What your not getting is that some of these tabs are slightly different enough that what you think is unversal may not be so and demanding one dev include another devs work because you think you know what your talking about is assinine
BTW....some don't have the issue at all and never have.
thebadfrog said:
You think so? There is no universal fix for most issues. Clemsyn and pershoot have been battling this issue for months. Gojimi is a VERY reputable g tab dev as well. Along with several other people. What your not getting is that some of these tabs are slightly different enough that what you think is unversal may not be so and demanding one dev include another devs work because you think you know what your talking about is assinine
Click to expand...
Click to collapse
Lol @ you dude...have a good day.
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.
Whether rom&kernel I used I always have lag on phone while the graphic chip is being used, for example in YouTube application when the video started it becomes too laggy and when I paused or stopped it becomes normal, and when i opened a game when i turn off the screen the crt animation becomes too laggy, too, and in bencmarkes my 3d points lower than other Evos, what do you think the problem is and how to solve it?
Not a gpu issue. What CPU gov r u using. When I use interactive it just stays at the minimum so it could be that
Sent from my HTC EVO 3D X515m using XDA App
thre3aces said:
Not a gpu issue. What CPU gov r u using. When I use interactive it just stays at the minimum so it could be that
Sent from my HTC EVO 3D X515m using XDA App
Click to expand...
Click to collapse
No, I've tried every kind of governor even the performance governor its the same. And its not the interactive governor which stays minimum, its powersave governor.
darkblooded said:
No, I've tried every kind of governor even the performance governor its the same. And its not the interactive governor which stays minimum, its powersave governor.
Click to expand...
Click to collapse
Seems as if you've tried many different troubleshooting options and still are experiecing this issue. I haven't seen many reports of it and it does seem very odd.
If this option is possible, I would load 100% stock software back on the device and see how it operates. If it is still really slow, there might simply be something internally wrong with the hardware and I would look into returning/exchanging.
I'm on 100% stock and have been since June '11. I've never seen any lag during the screen off CRT animation. Lag at that point seems awfully odd unless you're in the middle of some type of graphics/cpu intensive program .. even then .. I would have a hard time seeing consistent lag at that point to be legitmate behavior.
Hope that helps!
joeykrim said:
Seems as if you've tried many different troubleshooting options and still are experiecing this issue. I haven't seen many reports of it and it does seem very odd.
If this option is possible, I would load 100% stock software back on the device and see how it operates. If it is still really slow, there might simply be something internally wrong with the hardware and I would look into returning/exchanging.
I'm on 100% stock and have been since June '11. I've never seen any lag during the screen off CRT animation. Lag at that point seems awfully odd unless you're in the middle of some type of graphics/cpu intensive program .. even then .. I would have a hard time seeing consistent lag at that point to be legitmate behavior.
Hope that helps!
Click to expand...
Click to collapse
Thanks for your answer, I've tried stock Europe RUU and its the same and i don't have guarantee to exchange what to do now?
And I remember, I wasn't having these issues before, after trying too much ROM and kernel it happened, I always wipe everything before installing a rom, but do we have a full cleaner, kernel cleaner eg.?
darkblooded said:
Thanks for your answer, I've tried stock Europe RUU and its the same and i don't have guarantee to exchange what to do now?
And I remember, I wasn't having these issues before, after trying too much ROM and kernel it happened, I always wipe everything before installing a rom, but do we have a full cleaner, kernel cleaner eg.?
Click to expand...
Click to collapse
Using the real RUU will restore all stock partitions with the stock images.
I suppose, if you wanted to go the extra mile, boot into the custom recovery and format each partition, then run the RUU, but don't think I've ever heard of people doing that before an RUU so not positive if there would be any adverse side effects.
If you're on the stock RUU and experiecing issues, it would seem hardware related in my opinion as I'm on stock and have rarely seen those issues.
The only other thought which comes to mind is sometimes when people overclock they perhaps allow the device to become "too hot" and I suppose this could cause some minor but permanent damage.
Another thought, I know in my EVO last year, had a bright spot appear on the screen from "over heating" although I never overclocked, it was essentially a design flaw many experienced.
The only other suggestions I can think of would be to back to stock, knowing you've cleared all custom software off and perhaps load a basic kernel which supports voltage/speed adjustments and see if tweaking any of those help with the graphics lag.
Good luck!
joeykrim said:
Using the real RUU will restore all stock partitions with the stock images.
I suppose, if you wanted to go the extra mile, boot into the custom recovery and format each partition, then run the RUU, but don't think I've ever heard of people doing that before an RUU so not positive if there would be any adverse side effects.
If you're on the stock RUU and experiecing issues, it would seem hardware related in my opinion as I'm on stock and have rarely seen those issues.
The only other thought which comes to mind is sometimes when people overclock they perhaps allow the device to become "too hot" and I suppose this could cause some minor but permanent damage.
Another thought, I know in my EVO last year, had a bright spot appear on the screen from "over heating" although I never overclocked, it was essentially a design flaw many experienced.
The only other suggestions I can think of would be to back to stock, knowing you've cleared all custom software off and perhaps load a basic kernel which supports voltage/speed adjustments and see if tweaking any of those help with the graphics lag.
Good luck!
Click to expand...
Click to collapse
Thank you again I've started to think of a hardware problem cause I used overclock kernels such as unity v2 and leedroid kernel and i oc'd to max and used and I think these kernels oc'd gpu, too, but I never oc'd gpu and the problem is always the same and I'll try to format every partition as you said cause whether I wiped It's not getting completely formatted and from last format some of my bookmarks was left?
darkblooded said:
Thank you again I've started to think of a hardware problem cause I used overclock kernels such as unity v2 and leedroid kernel and i oc'd to max and used and I think these kernels oc'd gpu, too, but I never oc'd gpu and the problem is always the same and I'll try to format every partition as you said cause whether I wiped It's not getting completely formatted and from last format some of my bookmarks was left?
Click to expand...
Click to collapse
Great point, I actually had forgot about the sdcard. Some bookmarks are stored on the sdcard!
I wouldn't think any important settings are stored on the sdcard, but if you wanted to be even more thorough, you could backup all your sdcard contents to your desktop and format your sdcard.
That should ensure no settings remain after running the RUU.
So many details to remember! Hope that helps!
joeykrim said:
Great point, I actually had forgot about the sdcard. Some bookmarks are stored on the sdcard!
I wouldn't think any important settings are stored on the sdcard, but if you wanted to be even more thorough, you could backup all your sdcard contents to your desktop and format your sdcard.
That should ensure no settings remain after running the RUU.
So many details to remember! Hope that helps!
Click to expand...
Click to collapse
Ooohh yeah I took a point! I've tried other browsers, and now I'm using dolphin, and while I'm using maxthon browser I played 1080p video and I've turned off and on screen without any lag! But if I use YouTube application, or play video from the phone with its own player or es video player it lags, and in games lag has gone too, its getting interesting every time
Aha I've got one more point too! I used MX player and when in hardware mod the lag happens, but if i choose software mod, the lag goes away!
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
I have searched our Forum for anything on this phone overheating and there is one thread that I came across, but most people did not really have this issue at all. I mean in normal usage doing pretty much nothing my phone holds at 45-50C, given that is with all four cores operating, and if I play a game the cores have reached 70C and up, I am almost certain that is simply too high for this phone to be operating at. Also, even when I use eco mode the phone still idles around 40C and will reach temps as high as 64C. I am just wondering if I am alone or people have actually tested this also and have results similar to mine. I was hoping maybe there might be potential fixes for this or would I need to get a replacement device?
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Pony Express said:
Don't have a great answer for you but I can tell you the phone has some safeguards in place. One that I am aware of is the screen brightness will self-dim until the phone temp drops.
Arlington- as in TX.?
Click to expand...
Click to collapse
Yeah, I live in Arlington, TX. Yeah, I noticed the self-dim feature, but that happens way too much, and too often, I mean I rarely get to use the phone at 100% brightness and no phone should be like that in my opinion. I am just curious if other people are dealing with similar issues, but I am checking eco mode now and my temps on idle are 36C-38C, its when I actually use my phone as a quad core phone, shocking, that it gets waaay hotter. I mean its hot on the back of the phone when I touch there and when I check the temp with an app. I feel I should be able to use my quad core as a quad core when need be, not have it get so hot its unbearable to hold, plus I don't want to do any damage with it reaching 70C temps.
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
All og's get hot like that when playing games, etc. It is just how it is designed - like it or not / love it or leave it, lol.
I would have preferred they make the phone a little thicker with more heat sink so it could run full speed all the time when needed.
But they didn't. So, oh well. Maybe my next phone will fix that someday.
Jason
Sent from my LG-E970 using Tapatalk 2
Pony Express said:
Me, too in Arlington.
I would definitely say based on that it would be a good idea to exchange it, those temps are a bit much.
Click to expand...
Click to collapse
Darn, I was hoping for something else, ha. Oh well, guess I will be dealing with that then, meh.. By any chance could you tell me your temps you are getting? So, I know what is normal for the device?
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Pony Express said:
With 5 mins. light use (wi-fi, web, phone call, 2 texts, no gameplay) 25.4 C
---------- Post added at 03:28 PM ---------- Previous post was at 03:16 PM ----------
If you are using a phone for AT&T network on T-mo, it is possible that is adding to the temp prob, not an expert here just an educated guess that the more it tries to find network signal the warmer it may get.
Click to expand...
Click to collapse
Yes, but this happen on wifi only with data and no sim card installed, I am waiting to get an at&t sim card, lol. Shouldn't have done it online, but it cost 99 cents, instead of $15 bucks in the store.
Good call... hope it helps !!
Pony Express said:
Good call... hope it helps !!
Click to expand...
Click to collapse
Well, the strange thing is that I reverted back to stock everything, no root, or unlocked boot loader, and my overheating issue has been solved.. Weird. I only get around 35C even doing a benchmark with all four cores running at the same time. I think the Base rom and kernels still have some bugs that need to be worked out. I idle at 22C now, woot!
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Pony Express said:
Glad to hear that!! Nice work.
am using the new build from Team Nocturnal with no probs. You might want to read through the thread first as some are having issues.... point is, no overheating and battery life seems good so far.
One thing I learned by testing, even going to the extent of exchanging my phone 2 days ago - if you charge your phone while it is off and unplug the charger it will drain the battery because it does not shut down the charge animation. The workaround is to simply turn the phone on and let it boot, either leave it on or then it is ok to turn off.
Click to expand...
Click to collapse
Oh wow, I did not even know that was an issue, ha, well, thanks for the heads up on that and I think I have to send my phone off to LG sadly, according to AT&T, but when I get it back I will be looking into their new base rom, I did skim the thread a little, and I am glad to hear there is no overheating. I am not sure if it was a kernel issue or the base rom itself, which is puzzling.
You may have selected Sk8's kernel during The Base's installation. I can't speak for it myself, but it's different than the stock kernel and may have been causing the problem?
Speculation at best.
No worries, Its what I am doing right now, just speculating, I mean I actually selected both kernels in the base rom, and tested them out. I was trying to figure out what the issue was. I think it might not have left me do a clean install, as I did select Sk8's Kernel first. So, I am thinking that the kernel stuck, even when I did a full wipe, before reinstalling and using the other kernel. I also was getting Kernel crashes, and it kept showing up a kernel crash screen, and asked me to go into download mode to store the dump file on my computer. I am new to android/Linux things, I am far more familiar with Windows based things, but android is the freedom OS of mobile devices. I like the customizations and things you can do with it, lol. Its sweet, and I am learning everyday, so that I can possible become a Dev later on. I have ported some things before and I know other forms of coding, just not the required programming languages for Linux.
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
bleached45 said:
My guess would be Sk8's kernel as well, I know it has the gpu overclocked, so if you are running graphics intensive apps it doesn't surprise me that you can be getting overheating issues.
Maybe try the bootloader unlock again to reinstall the freegee kernel...
Just a suggestion.
Click to expand...
Click to collapse
v1:
- initial release
v2:
- added GPU OC and UV settings
v2.1
- revert GPU settings until i get them more stable
- add voltage control via sysfs (use system tuner to select your custom UV settings)
- fix the black screen issue for alot of users
v2.2
- fast_charge on usb (icon will still show as slow charge but it will actually charge faster)
- cpu tweak to enable use of all freqs in high stress times like games and benchmarks
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Zekk98 said:
v1:
...
^ That is the change log for Sk8's Kernel, the gpu isn't overclocked anymore, it was in the initial release. So, I know its not that, and as I stated in a previous post I tried both of them, but even when I wiped everything, I think that Sk8's kernel was sticking. The reason I say this is even after a fresh install and selecting Freegee Kernel during installation, when the rom booted back up it would show Sk8's Kernel, and I would get Kernel crashes, which would also lead to a Crash screen, asking me to go into download mode to save the dump file. Though even after messing with that and monitoring it for several days, its hard to tell what it was, but I do know I am not having the issues anymore when I brought everything back to stock, I can assume it was one of the kernels, a combination, the base rom, but I am not 100% sure.
Click to expand...
Click to collapse
Shows what I know, lol.
I was going by what I read for the Base ROM Aroma installer description, maybe the Base is still using an old version, but if you installed it on your own, then you should have been the latest.
Sorry, lol.