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.
Hi everybody,
I'm trying to understand how to fix this problem that's affecting me since I have this device.
I've got it in my hands in the end of November, and I've quickly unlocked and rooted it to install CM7. I don't like motoblur, so I didn't use it until I had CM7 on it. After few hours of happiness, I suddenly started experiencing freezes with black screens (I had to remove battery to unlock it) and auto-reboots.
I've wiped, fastboot-wiped, re-flashed, many times but nothing.
Tried different Roms such as redpill hybrid and dark side...same!
Googling around out there I've found hundreds of users with these two bad issues, and after hours of reading, and observing my own Atrix I've figured out what follows:
There are mainly two different issues. Although they are often considered the same, I think they are separate and I have both:
GPU issue: after playing a game or any app that "stresses" the GPU I have my Atrix not waking up after screen-lock. Black screen but if you call it is up and running somewhere in the background. it appears death, and I have to remove the battery to wake it up again. Device heating at rear-bottom.
RADIO issue: when the signal isn't that good and it changes often spot it reboots all alone.
trying to understand if it is hardware related (not an issue, but maybe small differences in the hardware of different phones) yesterday I went back to stock froyo.
Since then everything seems to work properly. Incompatibility of some ROMs with my device?
I want to stay on stock for some days to a deep test, after that, I will search for a good stock gingerbread firmware to flash.
I hope to find a solution, 'cause since I don't have CM on my device I don't feel it really mine .
Sorry for my English, hope to have made myself clear.
Thanks.
What kernel are you using? Some phones can't handle a high overclock. As for a gb rom I suggest darkside.
Sent from my MB860 using XDA App
Standard kernel @ 1Ghz. I've tried Faux's kernel @1.3 and 1.4, but I did it trying to solve the issue.
After good stock froyo and stock gingerbread experiences, I'm now happily running Aura deblurred.
Thank you, now I'll stay with Aura until CM9...
If you are experiencing the same issue look here: http://forum.xda-developers.com/showthread.php?p=21277632#post21277632
Sent from my MB860 using XDA App
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 just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Just try clearing app data rebooting and reinstalling the app. That problem has happened to me every once in a blue moon and that fixed it for me.
Sent from my SGH-I777 using Tapatalk 2
Thanks, I'll try reinstalling the kernel.
Which app are you referring to? because I had this problem no matter which app I used to change the governor (Extweaks, voltage control, setcpu).
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
bacon_n_icecream said:
Ive used the kernel cleaner every time I installed a new kernel. It didn't seem to work this time. But thanks for responding.
Click to expand...
Click to collapse
It's the lulzkernel for some-reason :|
I have problem goto smartassv2 it's ok just steps heavy
Thanks for your suggestion. I just moved over to ondemand and its been ok for me. Too early to make any judgments but I'll try smartassv2 next.
Not that I'm glad to that you're having problems, but I'm glad I'm not the only one with this issue. Thanks for the response
Winklie said:
Use Jivy's Kernel cleaning script prior to flashing, and try again.
http://forum.xda-developers.com/showthread.php?t=1428530
Click to expand...
Click to collapse
DONT use kernel cleaning scripts. They cause more problems than good.
Sent from my AT&T I777 running AOKP build 3X
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
bacon_n_icecream said:
I haven't had any issues with using the kernel cleaning script thus far.
What kind of harm can they cause? and do you have any recommendations on how to clean up before switching kernels or is just flashing them over ok? (A lot of people recommend the script cleaner and it seemed to have solved a lot of peoples issues kernel issues)
Click to expand...
Click to collapse
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
thanks, I generally do that any way along with the script cleaner
K Rich said:
Wipe cache, wipe dalvik. I've read more problems with the cleaning script than good.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
CPU related as well...
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
kbulut said:
Hi Guys,
My first post here. I am total noob. I rooted and installed the newest ShoStock2 on my at&t galaxy s2. Everything works perfectly. I couldn't be happier. I also went bought the setCPU for overclocking it. That too seem to be working fine.
My question is. I didn't set up any voltage requirements. The only thing I did was to set it to 1600 MHZ and 200 min and change the governor on the bottom to Lulzcrative. Will this work? Do I need to actually do something with the voltage? am I really on 1600 right now? I cannot tell.
I ran a quad test (I now it is meaningless in real world) it came 2818 yesterday. I ran it again this morning ..... It froze and took my battery from 45 to 9 in less than 3 mins!!!!!! The phone got really hot. I took out the battery right of way. The battery life showed 23 percent this time.
I got little afraid of the quadrant testing ... The phone seems to run good without that but I am not sure if it is set up how it is suppose to.
Could someone help me out please? I tried reading the forums and that is where I got the idea in the first place to overclock it.
So to summarize it, I guess phone is fine right now but I am not sure if I set up setcpu out properly.
I am on the newest shostock2. I have galaxy s2 on att. I am pretty good with computers and phones but not sure about voltage and other problems with relating to setCPU.
Thank you advance for helping me out.
Click to expand...
Click to collapse
Lots of questions there. Phone overclocking is the same and at the same time different than PC overclocking. I too bought SetCPU and due to bugs and problems have completely abandoned it. Honestly with the exception of running an epeen benchmark there is little incentive to overclock. Find a newer Kernel (I use NEAK which has no overclocking ability) and install it, performance is stellar. You really have to ask yourself, is my phone slow enough that I need more CPU power to make it faster?
To see what time your CPU is spending at a given clock speed, download CPUSpyhttps://play.google.com/store/apps/details?id=com.bvalosek.cpuspy&feature=nav_result#?t=W251bGwsMSwyLDNd, you will be surprised to see your phone spend very little time at it's max clockspeed.
Due to the immaturity of the fab process for our CPU's (well SoC), what is a stable overclock for one person might not even load for another. These CPU's are not like an Intel Sandy Bridge, with 1Ghz of free overclocking, nearly guaranteed. You can certainly play with voltages to try and attain a higher overclock, but at the expense of CPU lifetime, as well as battery.
Additionally, it takes a new Kernel 3 or so full charge, discharge cycles on a phone to really 'settle in' and 'learn' a particular phones battery, while yours got hot, which to me indicates an endless loop of some kind running in the background.
My advice would be as follows: Choose a ROM you like, feel free to play with different Kernels, again, I use NEAK, which does not work for some folks, or crashes or whatever. Give it several days to 'settle in' and if your still not happy with performance or have stability problems, try a different governor/scheduler. You really need to establish a good, solid baseline of your phones performance and make small changes and give them long enough to establish any changes to your phones overall stability. Basically running cowboy through your phone and making changes will have a negative overall outcome. Make small, documented changes, test and see what overall effect this has to your phone's stability and battery life, and make another change.
bacon_n_icecream said:
I just installed the new Siyah 3.2b1 kernel to run my ShoStock 2.2.2 ROM last night and everything was working fine. I didn't make many changes other than switching the governor to lulzactive and the i/o scheduler to noop.
It was running fine over night (lost 0% battery).
Then today after I used the phone for a few minutes the battery seemed to drain a little quicker. I know its too early to complain about battery life but I decided to investigate. When I checked cpuSpy it showed that all of the frequencies were barely used (mostly spent in deep sleep over night) but the 1200 mhz frequency was used most after that (significantly more than the others). When I went back into voltage control (same thing with setcpu) I noticed that it seemed to be stuck at 1200 mhz. The only thing that fixed it was changing the governor.
Does anyone have any ideas on whats causing this and how to fix it (I had great battery performance on lulzactive before so would like to use it again)?
Click to expand...
Click to collapse
Lulz has known problem in 3.2b2-1
Gokhan has fixed it in 3.2b2 - 2
Wait for ktoonsez to update it for us
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Thank you so much for the information. Could I simply uninstall the setcpu and go back to normal? Simply reflash the rom and/or kernel? I really like shostock2 with the cherry picker kernel for now. I want to give them a week of try to make my mind. Before the setcpu I think.I was better off
Thanks for the help by the way. I appreciate it.
Thanks for the update about the new siyah kernel. Glad it wasn't just me with the issue. I was going to post this question in the siyah thread but am new to the site so didn't have permission so thanks for finding me all the way over here
Phalanx7621 said:
Lol what exactly have u heard? If it was causing problems it would get pulled. The only thing I can foresee happening is someone flashing it and then not flashing a kernel or something. Which would be user error.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
I'm just going off what I've seen in the Siyah/NEAK threads. Most of the lock-ups/random reboots I've heard people having had used the cleaning script. Either that or its just coincidence.
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
bacon_n_icecream said:
I may be wrong but I think that using the kernel cleaning script actually solved most of the lockups. Perhaps I misunderstood the threads.
Click to expand...
Click to collapse
Hmm, well I've just manually wiped cache and dalvik and have never had problems between roms/kernels.
Sent from my SGH-I777 using Tapatalk 2
Hi all. I'm working only friends x2. She was having serious battery drain issues so I downloaded CPU spy and saw it was either idleing at 216 or 1000 MHz (see image below). I thought it may be a bug in the software so I sbf'd to 234 and had no luck. I then flashed cm7 hoping that may fix the issue but nope, nothing. I'm starting to suspect a hardware problem. Any insight to the cause of the problem would be greatly appreciated.
Sent from my DROID X2 using Tapatalk 2
Yea in my experience most problems that cannot be fixed by a good sbf are likely hardware issues. Might be a good reason to get a new phone.
The again, why not give CM10 a shot? Maybe it's a hardware problem that affects the way GB uses battery/CPU throttling, and since CM10 has deep sleep issues of its own maybe it wouldn't cause as much of a problem. Just a guess though.