Ever since I learned to root, flash and hboot. The only Rom I have used is SynergyROM | NIGHTLYS | 2.3.4 | SENSE 3.0 |. build r197. I really like it..
I have the MR 2.75 radios (can't use them deployed). I use WIFI all the time till back in the states. I tried Tibu, no luck. I tried downloading napster again, and no luck with different mp3 players.
The problem happens when the screen shuts off. Napster will play through the whole song it was playing, then stops when done. It won't continue to other songs until I wake the phone up. TuneIn stutters when the screen shuts off. It comes and goes and you can hear it shut off in the speakers, then come back on in couple seconds.
I am still learning this rom. Is there a setting I can use to stop this from happening?
Thank you for any help.
That is odd. The only thing I can think of is if you have your phone underclocked too far when the screen is off for the apps to function properly. Hopefully someone with some more insight can give you some advice because that is the only thing I can think of and its really just a guess.
Sent from my HTC Thunderbolt
That was my guess too. But I am just unsure how to overclock or other things to try to get it to work. Funny thing is Panadora works fine when the screen closes. Napster is/was my most used with all the songs I have saved on my phone.
I have found and read about people overclocking to fix things but can't find a ahow to for this rom.
When I use my phone as an mp3 player either through google music, amazon or tune in, I have to set the min to Atleast 700+ min so that it doesn't slow down too much when the screens off.
Oh and napster sucks. I have all my stuff added to gmusic.
BTW, grab setcpu. That's how you can easilyvoc and uc.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
I don't want to ask to many noob questions, but what do you mean you set the min to "at least 700+ min"?
As soon as i get off work i'll check out set cpu.
Yeah, I know napster sucks. But I get a military discount of $10 a month and download any all songs the wife, kids and I want. Then I run them through a convertor to make Mp3's to put on anything. Not a bad gig really..
Try installing an app from the market, Advanced Wifi Lock. I had a similar problem when using wifi - seems even though I had sleep policy to "never" it would still time out once the screen turned off.
Sent from my ADR6400L using XDA App
Nevermind, I think. I pride myself on trying to figure things out. I found setcpu zip on here and can donate to the builder. Loaded it. Shh, downloaded it to work pc, burned to disc, loaded it to my laptop then to phone.
I see the main auto detect button. I hit that and it shows 768 MHZ
960max
768min.
Is that normal/stock??
Plus it is on Lagfree.
I found you can set profiles and found screen off
I went to set it and it shows what the main is
960 max
768 min with a priority 54 for lagfree.
I don't want to screw any thing else up on the phone, just want napster or other music to not close when screen shuts off.
noobynoo said:
Nevermind, I think. I pride myself on trying to figure things out. I found setcpu zip on here and can donate to the builder. Loaded it. Shh, downloaded it to work pc, burned to disc, loaded it to my laptop then to phone.
I see the main auto detect button. I hit that and it shows 768 MHZ
960max
768min.
Is that normal/stock??
Plus it is on Lagfree.
I found you can set profiles and found screen off
I went to set it and it shows what the main is
960 max
768 min with a priority 54 for lagfree.
I don't want to screw any thing else up on the phone, just want napster or other music to not close when screen shuts off.
Click to expand...
Click to collapse
I have my max at 1.2ghz.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
McLabia said:
I have my max at 1.2ghz.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Click to expand...
Click to collapse
Is that what you have set on the main screen?
Do you have any battery saver type of profiles or other setup?
I tell ya what.
I'll go read the setcpu thread and see if I can find something and search the thunderbolt Q&A and general section.
I guess we can underclock and overclock because of ziggy's kernel. very nice..
noobynoo said:
Is that what you have set on the main screen?
Do you have any battery saver type of profiles or other setup?
I tell ya what.
I'll go read the setcpu thread and see if I can find something and search the thunderbolt Q&A and general section.
I guess we can underclock and overclock because of ziggy's kernel. very nice..
Click to expand...
Click to collapse
I've been running Ziggy kernels for a while... they're interesting creatures and his governors are sometimes a little odd. His kernel SHOULD run Pandora or the media player just fine at 122MHz on the lagfree. At least it does on Gingeritis3D. The Powersave governor is useless unless you like your device crawling along pretty much all of the time and don't mind setting your min_freq stupidly high. My current minimum and maximum clock are 122MHz and 1.57GHz, but most of the time it hovers around 1.03GHz in normal use. My time-in-state usually shows 80% or so at or below 245MHz, which equals power savings. I don't run the lagfree governor at Ziggy's settings though. It's kinda tweaked up with a script to set frequency min, max, governor, voltages, and governor parameters. If 245MHz isn't enough to do almost any job with the screen off, I'd be wondering what needs such muscular resources to and why.
Just realized i've been on 192 all day without any cutouts. So I dunno anymore. I've been streaming gmusic all day.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Yeah, weird.. I have tried different settings and made a profile for screen in the setcpu and have found the stupid a$$ napster will only work when screen off with min set to 768. Regular screen on main cpu setup is min 245-max 1190. Everything works fine now. Plays like a champ with screen off.
I have read a lot of post by you Mclabia, so don't let this get your head any bigger, but....Thank you for your help. I will probably stay with this rom for awhile. R197 seems to work nice. All this because i got bored at the end of deployment and wanted to make sure my phone didn't update when landing back in the states so I could call the family..
Thank you others for input too. Maybe i am not the only one that has had this problem and hopefully this can help someone else out.
Now just to wait and see a fix for the capture video shutdown in MMS(go SMS) and all will G-U-D(good).
noobynoo said:
Yeah, weird.. I have tried different settings and made a profile for screen in the setcpu and have found the stupid a$$ napster will only work when screen off with min set to 768. Regular screen on main cpu setup is min 245-max 1190. Everything works fine now. Plays like a champ with screen off.
I have read a lot of post by you Mclabia, so don't let this get your head any bigger, but....Thank you for your help. I will probably stay with this rom for awhile. R197 seems to work nice. All this because i got bored at the end of deployment and wanted to make sure my phone didn't update when landing back in the states so I could call the family..
Thank you others for input too. Maybe i am not the only one that has had this problem and hopefully this can help someone else out.
Now just to wait and see a fix for the capture video shutdown in MMS(go SMS) and all will G-U-D(good).
Click to expand...
Click to collapse
The latest 205 fixed that and a few other issues. Lol. Also, now that you're past your min posts threshold, hop in the synergy thread and say hi. Lol.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Son of a..... I saw the latest on the site last night. It was 204. I'll pop over to the other forum now and make stupid comments and noob questions there.
Can't post there yet. Apparrently i can't count. I need 10 post
this should be 9
And now that I have bumped this thread up enough to bug the crap out of everyone with real problems (Sorry everyone).
this should be 10.
Related
Just moved from my Nexus One to the Fascinate because I need to get on a better network than T-Mo. Rooted about 15 minutes after I pulled it out of the box, and removed all the ****e already. Trying to figure out if SetCpu is going to have any real benefits for me yet. When I loaded it, it read a conservative govenor, and a min. of 100 - max. of 1000.
What I don't want to do is set a sleep downclock or change the governor settings and cause anything to go haywire. Anyone have any input on this? I know the device is new, but it's a Galaxy S variant, and there's lots of dev work already in process. Any input would be awesome.
Edit: My apologies for wrong section. This should have been in General.
I managed to lock up the device with a few profiles, like 200-400 on sleep and 200-800 on charging. Mainly when I get a notification or plug it into usb, it would lock up and require a reboot.
Basically doesn't quite work yet.
It locks up my fascinate when the device screen goes off.
+1 to the not ready yet.
Sent from my SCH-I500 using XDA App
Input appreciated. Figured as much. I'm sincerely hoping we'll see some development after 2.2 hits. I'm used to the flurry of activity in the Nexus section, and am a bit of a "flashaholic" lol.
I don't dev, but I damn well donate.
I hope I made the right call with the jump to a Fascinate. If we get out developed by the Droid Xers, I'm going to cry.
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
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Actually when I was on the second ics leak, and setcpu worked fine. I know this because I benchmarked before and after setting frequencies
Sent from my ADR6425LVW using XDA
benchmarking doesn't mean it wasn't running at full tilt when you didn't need it to. unless your kernel magically doesn't include perflock, it was.
also, there are some combinations of setcpu and monitoring that will work. at one point if i used setcpu, cpu monitor, and one other which i forget now, it would work, kind of. definitely not recommended.
Thats why I deaded mine. Phone was constantly overheating
Sent from my ADR6425LVW using xda premium
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
tspderek said:
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
Click to expand...
Click to collapse
Agreed. I had set CPU try to disable perflock and limit to 1200mhz on conservative and it ended up being worse battery and slower overall.
You're exactly right I advise everyone I discuss the topic with to make sure and avoid trying to over ride perflock with a CPU management app. It causes a conflict in my opinion which is a huge battery drain and also causes excessive heat due to the process of fighting for its life.
Sent from my ADR6425LVW using xda premium
I've been saying this I even started a thread to smash this rumor of ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels.
THERE WAS NEVER ANYTHING WRONG WITH ANY ICS LEAKS. JUST USER FAULT
Sent from my ADR6425LVW using XDA
richii0207 said:
I've been saying this I even started a thread to smash this rumor if ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
con247 said:
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
Click to expand...
Click to collapse
My favorite part is when they try to sound like a dev, I guess everyone's a dev on here ;-P. At least I only say something I know from EXPERIENCE and not what I read ;-)
Sent from my ADR6425LVW using XDA
jayochs said:
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
Click to expand...
Click to collapse
the widget i posted is what you want. it should be scaling up and down, and settling eventually when nothing is really going on. the system panel that you tried clearly affected the perflock in some way. from what i understand, some apps/widgets look at the cpu itself, while others hit up the kernel for status. the ones that hit up the kernel are the issue. i'm not 100% on this, that's just what i've been told. all i know is my experience seems to match this.
tspderek said:
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Click to expand...
Click to collapse
Hmm, that's weird, cause I've been using setCPU with ICS on the Rezound for months and it works great! My CPU scales fine and hits all the frequencies its supposed to. The min and max frequencies do change around seemingly randomly, but anyone can see by watching the current frequency display that it is always somewhere in between the range I selected, and always appropriate for the system load.
I've always had CPU Master installed. I just removed it, we'll see how it goes.
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!