Hello everyone. I am new to android and rooting ans these forums. Just bought a thunderbolt about a month ago and absolutely loving it. Being an iPhone jailbreaker, I immediately rooted my thunderbolt. So I've been playing around for the past few months and settled on cm7.
My problem is with lockscreen lag. When I click the lock button from screen on, the screen just very slowly dims out, much slower than when I ran stock or das bamf. Worse is that when I click the lock button from the blank screen soon after locking, it first shows what was on the screen for a second or two, then goes to the lockscreen. If I click the lock button from a black screen that has been locked for awhile, it slowly fades on before I can unlock it.
This is very annoying because I often lock then decide to unlock, and between the lock lag and unlock lag, I have to wait some 3 seconds. Dad bamf, stock, and omfgb all had very good lockscreen reaction time with no lag.
On the mr1 radio, cm7 rc0.6, tried rc1.1, same problem. Under timeout settings before screen goes to lock, I have both set to immediate. Furthermore I tried doing a complete wipe, dalvic, data, format system, reset battery, everything.
Is this normal or just my thunderbolt, any suggestions how to fix it?
LowFatBlood said:
Hello everyone. I am new to android and rooting ans these forums. Just bought a thunderbolt about a month ago and absolutely loving it. Being an iPhone jailbreaker, I immediately rooted my thunderbolt. So I've been playing around for the past few months and settled on cm7.
My problem is with lockscreen lag. When I click the lock button from screen on, the screen just very slowly dims out, much slower than when I ran stock or das bamf. Worse is that when I click the lock button from the blank screen soon after locking, it first shows what was on the screen for a second or two, then goes to the lockscreen. If I click the lock button from a black screen that has been locked for awhile, it slowly fades on before I can unlock it.
This is very annoying because I often lock then decide to unlock, and between the lock lag and unlock lag, I have to wait some 3 seconds. Dad bamf, stock, and omfgb all had very good lockscreen reaction time with no lag.
On the mr1 radio, cm7 rc0.6, tried rc1.1, same problem. Under timeout settings before screen goes to lock, I have both set to immediate. Furthermore I tried doing a complete wipe, dalvic, data, format system, reset battery, everything.
Is this normal or just my thunderbolt, any suggestions how to fix it?
Click to expand...
Click to collapse
Yeah, I had this same problem, but then I turned on the option for the tv animation on Device awake and it went away. It seemed much snappier.
Go to Settings > CyanogenMod Settings > Display > Screen-on Animation
Lag is probably from the cpu not kicking up to a faster speed in time to deal with the animation. Enabling that extra animation you mentioned most likely just gives it a little more time to kick up the cpu enough to stop the lockscreen itself from lagging.
yareally said:
Lag is probably from the cpu not kicking up to a faster speed in time to deal with the animation. Enabling that extra on you mentioned most likely just gives it a little more time to kick up the cpu enough to stop the lockscreen itself from lagging.
Click to expand...
Click to collapse
Yeah this is what I was thinking. So the animation is pretty much just a placeholder or something to look at (it still seems snappy with the animation on) until the CPU kicks in.
Yareally, so do you get this problem as well? How would you suggest I fix it? I am running imoseyon's lean minimalist kernel for cm7, its running at the "normal setting" which is undervoltes then overclocked to 1.41ghz. I've tried all the governors for it ondemandx, interactivex, smartass, all the same problem. Admittedly I haven't tried the stock kernel with "performance" governor. But I'm sure there are many people who use power saving governors who do not have to contend with this issue?
Sent from my ThunderBolt using XDA App
It's an issue with the kernel/kernel governor most likely and most of the kernels I believe for AOSP and GB Sense are based on Imoseyon's which from being on BAMF 2.x and CM that it's not the ROM's doing. The threshold for the cpu to raise the clockspeed on the initial wake of the lockscreen by default isn't enough to kick it up from 245mhz.
Pretty sure this issue has been around for quite a while, just most people (including myself) most likely figure the amount of effort to fix it would be more than the annoyance. Setting a profile to keep the min speed on screen off to 384mhz or whatever comes after 245 on the toggle scale would probably fix it, but obviously raise your clockspeed some. It could also be the undervolting while the screen is off is too low as well and so it causes it to lock up somewhat while the voltage rates go up a bit.
If someone hasn't mentioned it to Imoseyon or looked through the long thread of his Sense/CM kernel, then I would recommend doing that. I recommend reading first though. I've only tried his kernel and Nerozehl's but I know Nerozehl's was a fork of it and has the same issue. The governor settings are just a pain to deal with and it's probably something Imoseyon is already aware of, but just hasn't fixed it yet.
If you want to try a quick fix (for lag), use ondemandx and not the other governors. That might fix it right away.
The lockscreen taking a second to kick in though I think is a CM problem that will just get worked out eventually.
I have this too on the liquid aosp rom. I figured it was rom related because no kernel fixes it. I hope this gets fixed.
Turn Autobrightness off and try it for a while.
Mine did this until I updated to cm7 RC 1.5.2
Sent from my ADR6400L using XDA App
Absolute_Zero said:
Turn Autobrightness off and try it for a while.
Click to expand...
Click to collapse
i always have that off.... what kernel are you guys using?
fixxxer2008 said:
i always have that off.... what kernel are you guys using?
Click to expand...
Click to collapse
RC 1.5 is very snappy and seems to have fixed all the issues of lag. I would recommend trying that before anything else. I am not sure slayher updated it here yet, but if it's not, it's also on rootzwiki.
I am on CM7 and have never had that lag.
Sent from my ADR6400L using XDA App
yareally said:
RC 1.5 is very snappy and seems to have fixed all the issues of lag. I would recommend trying that before anything else. I am not sure slayher updated it here yet, but if it's not, it's also on rootzwiki.
Click to expand...
Click to collapse
Im not on cm7...im on liquid v2.6.
fixxxer2008 said:
Im not on cm7...im on liquid v2.6.
Click to expand...
Click to collapse
pretty sure he's pulling from the cm7 source, so technically you are
I am guessin whenever he pulls from the source again to update, it'll fix your issues.
Related
So recently my eris has been lagging really bad to the point where its pissing me off. it was working fine for a couple of month then the lag started so i factory reset my phone but the lag is still there. it would lag from 30 seconds to mins... I have the latest sensable rom on my phone and i dont think its the rom that is bad..
I was wondering what i can do about this lag.. is my phone broken? Another thing to add is that when the lag started my trackball also started to mess up it occasionally... a lot... moves the left. connection?
If your trackball is starting to scroll to the left at random times, then the lag could definitely be a hardware issue. I had the same issue before I got a replacement Eris. If your phone is still within warranty, then I would take it in and ask for a replacement.
i bought my phone used off of ebay... so i dont think i have warranty...
mannnn said:
i bought my phone used off of ebay... so i dont think i have warranty...
Click to expand...
Click to collapse
I remember seeing a thread long time ago with a guide about cleaning underneath the trackball. Removing lint and other particles might help your situation.
Just did a search. There are more thread regarding it, but here is one: http://forum.xda-developers.com/showthread.php?t=716681
Have you changed your cpu frequency lately? It might not like the speed you are running it at. Also if you are using the setcpu widget that can cause problems.
Sent from my Droid Eris using XDA App
thanks for the tip on fixing the trackball. it kinda works for me it doesnt scroll to the left as often now. but im still laggggggging like crazy.
i dont know how to change the cpu... i never messed with oc. just install the rom and thats it.
mannnn said:
thanks for the tip on fixing the trackball. it kinda works for me it doesnt scroll to the left as often now. but im still laggggggging like crazy.
i dont know how to change the cpu... i never messed with oc. just install the rom and thats it.
Click to expand...
Click to collapse
What ROM are you using? Many of the custom ROMs have SetCPU built in. It is fairly simple to use. Just adjust the slider bars for the minimum and maximum speeds. If you set it too high, it can cause kernel panic, which may result in random reboots and lag at times. Higher speeds also consume more battery power. If the minimum is too low, it might take a bit longer to wake up, once the screen is off.
I'm using senseable Rom. There isn't the setcpu app.
mannnn said:
I'm using senseable Rom. There isn't the setcpu app.
Click to expand...
Click to collapse
Just download it.
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'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
What I'm running:
Latest NEAK kernel + AOKP build 36.
Issue also occurred in Phonebricker + NEAK (sammy version).
My issue:
Occasionally the OS will get extremely slow, like you would expect if the phone were running at 100mhz or something. Everything continues to work, just reeaaallly slow. For instance, music playback gets very electronic-y as sounds are stretched out, tapping one of the capacitive buttons takes 5-10 seconds before vibration/feedback, and another 5-10 seconds before a menu pops up. I managed to get the NEAK configurator open and scrolled to the CPU tab, and it claimed I was at 1200mhz - though the phone didn't even get warm so I'm skeptical.
I'm guessing since I've done a full wipe between phone bricker + NEAK and AOKP + NEAK, the only thing in common are my apps and the NEAK kernel, so it stands to reason it would be one or the other causing this. My wife's GS2 is running AOKP + NEAK as well though and we haven't experienced this problem on it yet (but it's intermittent so it might be there, just hasn't happened yet). I'm currently running conservative governor + SIO, but it has also happened on conservative + NOOP.
While I could just change a bunch of sh!t and hope it goes away, I'm more interested in figuring out what's causing it, and fixing it properly. How can I figure out what's going on? What will log this kind of thing? What do you guys recommend?
Thanks!
this is really easy/simple. flash a different kernel. all devices are not created equally so you need to just try everything that we have and see which best fits your device.
if you had this issue on 2 different roms with the same kernel then you've answered this question in your post for yourself. it wasnt even necessary to post this dude. change kernels. done.
some phone like neak kernel, some phones dont. some phones like siyah, some phones dont. you cant "fix" that unless you get a different phone and try neak again. but even then it my not "fix" this issue because nothing is broken.
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Eckyx said:
Well, what if it's something as simple as the governor I'm using or an undervolt setting? I'll probably flash back to your kernel though, but again it'd be nice if I could figure out exactly what the phone is doing when it's "super-lagging".
Click to expand...
Click to collapse
If you're undervolting when this issue is happening, change it back to regular voltage.
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
I can attest to the slow downs and the screen lock ups. I have been using Tasks kernel for the past week and a half. Going back to try NEAK one last time. If it gives the same results I'll have to give up on it. I don't under volt hardly at all by the way. Like maybe -25 per step so it isn't that, and when I first experienced the issue I tried Evey possible io scheduler / governor combo under the sun. All yielded same darn results.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Simba501 said:
+1, my problem was with typing as well. Stock voltages, several kernels.
Sent from my Galaxy S2
Click to expand...
Click to collapse
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Eckyx said:
I've only used Task's (CM9) kernel and NEAK, and I haven't yet experienced any slowdowns with Task's, but I really have no idea what kind of optimizations his has, haven't found any information on it published so I can't say what's different between his and the NEAK kernel.
What kernels have you had problems on?
Click to expand...
Click to collapse
Stock & Siyah. My issue with it wasn't major; it just isn't as polished as GB. The difference is noticeable.
Sent from my Galaxy S2
When mine gets laggy, I usually pull out the battery and put it back after 10 min or so. If you are leaving the phone on more than 2-3 days at a time, that could really hurt the memory and phone performance. The phone usually runs on 300 mb but it will run about 700mb ram after 3 days (even force closing everything).
It is not mentioned so I just wanted to cover all bases
After posting about giving NEAK another try, I did. And within 10 minutes got an extreme lag slow down while typing. Didn't touch any settings kernel side. So I flashed siyah kernel and so far no problems. Sux too. I liked NEAK.
Sent from my SGH-I777 using xda premium
I have been running Siyah with Task's AOKP and have had zero lag and great battery. No UV or OC.
Sent from my SGH-I777 using xda premium
Posted this in NEAK thread but also posting it here:
I just installed the new AOKP, used kernel clean script and installed NEAK 2.0.5x, then went into the NEAK Pro config and changed my governor to Conservative and sched to SIO. Rebooted, opened Scramble with Friends and immediately got superlag.
Turning off the screen and waiting 20-30 seconds fixes it (long enough for the phone to go to sleep), but nothing else short of a reboot will help. I can leave it like that for an hour (if I don't let it sleep) and it'll still be uberslow.
Please go easy on me, here. I know how to search forums, I just don't always understand what I read on here. :laugh: My husband has always helped me with most of my Vibrant issues, but he has recently defected to his HTC One S.
My Vibrant is getting unbearably slow. I'd been running a Fishman rom on it, and it seemed very, very slow. We then decided on the Slim Ryder rom. The first day or so it was unbelievably fast. That, unfortunately didn't last.
I have only the minimum apps on there and only one updating widget (BeWeather time and weather. Used to use Beautiful Widgets but it began superimposing the time over itself so I couldn't read the time...).
I'm a realist, and I know that my Vibrant is old. I know it isn't as fast as The Hubs' new HTC. I'm only comparing it to itself. Here's where I've noticed the slow downs:
*when switching portrait/landscape (sometimes tries to show half a landscape screen in portrait mode)
*when touching a text field, it is very slow to bring up the keyboard...sometimes i have to tap multiple times
*when Swyping or using Swiftkey, it sometimes hangs on a letter
*it takes several seconds to bring up my text messages, dialer, call logs...basic phone functions.
*using the browser is unbearable.
I've done the old standard...Master Reset, cleared history, caches, cookies, etc. I have wiped call logs and clear out my texts every other day. I don't store music on my phone (Google Music) and have my photos upload to my Google+ account via wifi so I don't get a lot of that stored up. I do not use a live wallpaper.
I'm not eligible for an upgrade until November. I am absolutely open to trying other ROMs, but as a mama with little people and no landline, having the ability to reach 911 from my phone is non-negotiable. Can anyone offer me any ideas on how to limp through until my upgrade?
Thanks in advance.
My vibrant was pretty slow with 2.1~2.2 using almost any rom;gingerbread was a huge improvement and ice cream sandwich is just blazing fast. I would suggest flashing ICS passion http://forum.xda-developers.com/showthread.php?t=1362961 or another rom that supports 911. Right now, the developers are working on porting jelly bean to our phone, and when its stable, go grab it!
2.1 and 2.2 roms I heard are a lil slow so try to use an ics rom like passion chimera or zenwick
Sent from my SGH-T959 using xda app-developers app
You can check out the kernel bible thread and maybe get a kernel with voodoo lagfix, seems to make my phone faster. I'm running 2.2 Blue Frankenstein ROM, it comes with voodoo lagfix.
Sent from my SGH-T959 using xda premium
Try a kernel with voodoo lag-fix as iTz KeeFy mentioned and in the meantime disable any animations.
tc
The_MamaBee said:
My Vibrant is getting unbearably slow. I'd been running a Fishman rom on it, and it seemed very, very slow. We then decided on the Slim Ryder rom. The first day or so it was unbelievably fast. That, unfortunately didn't last.
<snip>
*when switching portrait/landscape (sometimes tries to show half a landscape screen in portrait mode)
*when touching a text field, it is very slow to bring up the keyboard...sometimes i have to tap multiple times
*when Swyping or using Swiftkey, it sometimes hangs on a letter
*it takes several seconds to bring up my text messages, dialer, call logs...basic phone functions.
*using the browser is unbearable.
Click to expand...
Click to collapse
Fellas, if she is using Slim_Ryder, then she is using a kernel that already has Voodoo included, IIRC.
To me, these symptoms sound like you may be getting bogged down on your low-end CPU frequencies. Maybe get something like SetCPU or CPUmaster from the market and up your lowest frequency to the next step. When I am on a 2.2 ROM, I use BaliX1.2 and I have mine overclocked to 1.2ghz but my lowest frequency is 400ghz and not the standard 100-200 that most use. I find that this bogs my system down a bit more than it should. So that is when I decided to test it out and up the lowest in step increments.
You can go to my Battery Guide and in the 3rd post, there is a link to get SetCPU for XDA users for Free. When you use this, you might also want to check the governors as well. Some 2.2 kernels do not play well with On-Demand (BaliX most definitley does not-proven a long time ago). I have mine set to conservative and no profiles set at all. My I/O is Deadline also.
Woodrube said:
Fellas, if she is using Slim_Ryder, then she is using a kernel that already has Voodoo included, IIRC.
To me, these symptoms sound like you may be getting bogged down on your low-end CPU frequencies. Maybe get something like SetCPU or CPUmaster from the market and up your lowest frequency to the next step. When I am on a 2.2 ROM, I use BaliX1.2 and I have mine overclocked to 1.2ghz but my lowest frequency is 400ghz and not the standard 100-200 that most use. I find that this bogs my system down a bit more than it should. So that is when I decided to test it out and up the lowest in step increments.
You can go to my Battery Guide and in the 3rd post, there is a link to get SetCPU for XDA users for Free. When you use this, you might also want to check the governors as well. Some 2.2 kernels do not play well with On-Demand (BaliX most definitley does not-proven a long time ago). I have mine set to conservative and no profiles set at all. My I/O is Deadline also.
Click to expand...
Click to collapse
Thank you very much. It was the Blue Frankenstein 2.2 ROM I switched from to go with Slim_Ryder. Both have been very laggy.
I will definitely try the steps you've outlined for me, Woodrube. I really appreciate it. I know I'm using a Bali Kernel. It says Bali v1.8.8UV.
I spoke with a second-level tech at Tmo this morning and he said I've done all the troubleshooting steps they could recommend. He said at this point it is a hardware issue.
I will try these steps today and research how I can test my 911 capabilities legally. If if can get over those obstacles, I will definitely try an ICS Rom. I just have to limp through until early November.
Thanks again for the help, guys!