Hello everyone,
I was really struggling with the sleep of death after flashing comrom 2.0 and finally figured out the cause; Set Cpu. Any way, I might just be inept at setting it up correctly, but if anyone else is getting SOD, try disabling Set Cpu. It worked for me.
P.S. Im using the PBJ kernel
Im pretty sure it says not to use set cpu in the op, and use voltage control that is provided in the rom
Sent from my SCH-I500 using XDA App
Nevermind just saw your ps
Sent from my SCH-I500 using XDA App
Yeah, that was pre-2.0 when they still bundled voltage control and the kernel. Any way, I reinstalled vc from the market after removing setcpu and it seems to be running great. So, your right
I have been running com rom 2.0 and pbj with set cpu. No SOD issues here. Been running since 2.0 release.
Related
Hey all, I'm getting some weird freezes starting today. I'm running Fusion 1.1 w/ JACs @1.2Ghz and Voodoo.
I haven't done anything different to my phone in the past 24 hours, but any music player freezes if I try to forward to another song or when the current song finishes. I've tried it on MixZing, Winamp, and Doubletwist. (Slacker and Pandora work though). I've tried rebooting, pulling the battery, reseating the SD card, etc.
Any ideas what might be causing this?
I asked the same question yesterday n no one answered
Sent from my SGH-T959 using XDA App
Oh and I was on bionix 1.9.1 so I thought it was the rom. Flashed to fusion 1.1 jac w voodoo n it works. Not sure why though
Sent from my SGH-T959 using XDA App
I had the same issue. Used different roms with no improvement.
It turns out that it's a bug with the OC/UV kernel.
justanothercrowd stated that it's probably an issue with the undervolting. Go back to the stock kernel and it'll be stable again.
Grrr... it's weird because I've been fine on an OC/UV kernel for weeks now. And all of a sudden I have problems.
Well, strangely enough, PowerAmp works. I wish it had better sorting, but it'll do for now. (seriously don't want to give up the overclock, even though music a huge reason for owning this phone)
Kubernetes said:
Grrr... it's weird because I've been fine on an OC/UV kernel for weeks now. And all of a sudden I have problems.
Click to expand...
Click to collapse
Yep, same thing for me. I was on JACs kernels for a while, and then suddenly my phone locked up every time i played music and the screen went dark. There's a bit of discussion in JACs kernel thread on the subject, but not much. Apparently on the OC/UV kernels, when the phone goes to sleep and the processor clocks down, it causes some fault with the music trying to play in the background which locks up the phone.
glad to hear you've found a workaround though!
What version of Jacs are you or were you running? I had random freezes with his 1.1 kernel, flashed the 1.0 kernel and have not had a single problem.
Sent from my Vibrant running Bionix Final w/Jacs kernel and Voodoo using XDA App
Br1cK'd said:
What version of Jacs are you or were you running? I had random freezes with his 1.1 kernel, flashed the 1.0 kernel and have not had a single problem.
Sent from my Vibrant running Bionix Final w/Jacs kernel and Voodoo using XDA App
Click to expand...
Click to collapse
i think my own problems may have started when i began using 1.1. I haven't gone back to 1.0 yet to see if it works as normal
reuthermonkey said:
i think my own problems may have started when i began using 1.1. I haven't gone back to 1.0 yet to see if it works as normal
Click to expand...
Click to collapse
1.0 is the answer. I know Bionix roms come with 1.1, i usually dl stock rom version and flash Jacs 1.0 over it. All the UV, none of the FC.
Sent from my Vibrant running Bionix Final w/Jacs and Voodoo using XDA App
It was 1.0, and I don't think it was the kernel. Last night I flashed a bunch of different kernels and still had the same problem. Finally reflashed the full Bionix Fusion 1.1 and then JAC's 1.0 Voodoo kernel on top. Fixed!
I definitely had some kind of corruption, because all kinds of things were off, like Quadrant would hang, Youtube wouldn't work, and most music apps froze. Reflashing solved everything.
Those who installed setcpu, have y'all set it to auto detect device and set minimum to 200?
Sent from my GT-I9000 using XDA App
crazy25000 said:
Those who installed setcpu, have y'all set it to auto detect device and set minimum to 200?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
yeah i had done that too. no dice.
I got the same problem with my vibrant, anyone can help me out?
AS far I my phone is concern, it running stock froyo, no flashing no rooting.
same thing here. Running stock Froyo on my vibrant. any ideas?
PowerAmp seems to be the only player that doesn't freeze when switching tracks...
dn7309 said:
I got the same problem with my vibrant, anyone can help me out?
AS far I my phone is concern, it running stock froyo, no flashing no rooting.
Click to expand...
Click to collapse
I agree, not only does it freeze but it restarts but it gets stuck on the boot logo. It gets really annoying
Sent from my SGH-T959 using Tapatalk
Just an idea, but it could be the sd card got corrupt. Have you tried backing up your sd card, formatting it, then moving your music back?
Sent from my SGH-T959 using XDA App
Try oding back to stock that will fix it. By any change you download torrents on your phone?
Sent from my SGH-T959 using Tapatalk
my music is stored on my phone's internal storage. I did apply the voodoo lagfix and then remove it (because of battery drain). but voodoo doesn't do anything to the storage partition which is fat32. i'll check the partition for errors.
dougstoner said:
Just an idea, but it could be the sd card got corrupt. Have you tried backing up your sd card, formatting it, then moving your music back?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i am on stock froyo from samsung. i don't download torrents on my phone ... why do you ask?
iwillkillyou said:
Try oding back to stock that will fix it. By any change you download torrents on your phone?
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Recently got Droid X Overclock and have been playing with it. I've seen the CPU Benchmark and Quadrant threads, got some decent scores but seems to be most stabile @ 1300 Undervolting.
What exactly are the benefits, what's the difference between the voltages? Currently undervolting because my impression is it'll give me longer battery life, but read some threads saying it is somewhat a myth? Can anyone that truly understands this comment?
Im going to make this as simple as possible. I can only tell that it makes a difference in benchmarking.
Sent from my DROIDX using XDA App
ksizzle9 said:
Im going to make this as simple as possible. I can only tell that it makes a difference in benchmarking.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Same here... lol
Neither of you can tell a difference with battery life?
I've been wanting to overclock/undervolt, but I was curious as well. Do I have to overclock each time I flash or upgrade a ROM? I'm currently on Liberty 1.0, but once they come out with an update would I need to overclock once again?
Thanks in advance.
I am on Apex 1.3 and have noticed increased battery life but not sure if its due to the ROM or undervolting.. will most likely check out Fission or Liberty tomorrow.
Sent from my DROIDX using XDA App
I OC/UV to 1.3 ULV settings in liberty lastnight. My phone has been on for 10 hours, display on with heavy use for about 45 mins, still at 90%. So far, that is a bit better then any other OC setting I used, and it's very stable. I noticed with other settings, I had weird reboots, so I think a lot of it depends on what works for your phone the best. I would test them out and see the results.
Since recent updates I've been getting popping in audio. This ONLY occurs when I touch the screen. For example when I have a song on and I swype I can hear popping as I move my finger across the screen. Is anyone else having this issue? Using voodoo control plus with version 8 driver.
EDIT: Emailed supercurio. He is working on a fix and I am testing it for him. The only tweak he said he found so far to improve this is using the command "echo 0 > /sys/module/printk/parameters/time" in adb shell. He said it should improve noise popping and he was exactly right. The popping is still noticeable but has much improved! He said he will consider integrating it in a future version.
EDIT (5/16): To be clear, Supercurio says this is a flaw in the Froyo kernel whether stock or not. I recently odined back to DL09 to do OTA to EB03 and still have some issues. Being on complete stock, the issue is not nearly as bad and doesn't occur when I interact with the screen. The issue of sound popping occurs about every 8-12 seconds when playing back audio of any kind. Here is one of his exact messages in our email conversation.
"François SIMOND - supercurio to me
show details Apr 28
Hi Zachary!
This is an issue with the [Froyo]* kernel itself, which is poorly implemented.
Gingerbread kernels are not affected anymore. Is it really bad in ED01 ?"
* Was added in for context.
Sent from my SCH-I500 using XDA Premium App
Zacisblack said:
Since recent updates I've been getting popping in music. This ONLY occurs when I touch the screen. For example when I have a song on and I swype I can hear popping as I move my finger across the screen. Is anyone else having this issue? Using voodoo control plus with version 8 driver.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Yeah, same here! I noticed it as soon as I got set up cause I use my fassy religiously as an mp3 player!
Jrex said:
Yeah, same here! I noticed it as soon as I got set up cause I use my fassy religiously as an mp3 player!
Click to expand...
Click to collapse
Glad I'm not the only one!
Sent from my SCH-I500 using XDA Premium App
Zacisblack said:
Since recent updates I've been getting popping in music. This ONLY occurs when I touch the screen. For example when I have a song on and I swype I can hear popping as I move my finger across the screen. Is anyone else having this issue? Using voodoo control plus with version 8 driver.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
What rom/kernel?
Sent from my SCH-I500 using XDA Premium App
Community Rom and the included rom by nemesis2all. I just reverted from jt's alpha gingerbread and it happened on that too. Dont think it's a ROM issue but rather a voodoo sound driver issue. Just seeing if it's just me or if others are also noticing.
Sent from my SCH-I500 using XDA Premium App
Yeah I'd revert back to the previous kernel with voodoo 7.
Sent from my SCH-I500 using XDA Premium App
I too am having the same problem and it's driving me nuts! It's not only when you touch the screen, but whenever the processor load ramps up, so it's pretty much whenever the phone does any thinking. Very annoying.
Doesn't happen for me (imnuts -50). But I'm using MortPlayer, not the stock Samsung.
If you're on the nemesis kernel, try changing some of the enabled clockspeeds?
Doesnt help. This also happened when I was on CM7 when I wasnt on nemesis2all's kernel. I realized this didnt happen until voodoo driver version 8. I emailed project voodoo to see what they have to say.
Sent from my SCH-I500 using XDA Premium App
Have you checked the scheduler you are using? It almost sounds like the phone is decreasing the priority devoted to decoding the mp3 too much or it is giving too much cpu to the ui. Drivers
Sent from my SCH-I500 using XDA Premium App
I had this the other day. Odin to ebo1 and flash back to comm rom fixed it.
Sent from my SCH-I500 using XDA Premium App
I've noticed popping only since I flashed Jt's CM7 rom. I'm not currently on the rom, but the problem still exists. I'm thinking there's something in that rom that has messed up my phone's audio (hopefully not permanently).
Im having this strange pops too. I have a SGS i9000 and am using the Voodoo control plus app. Theyre very noticeable when i put on my headphones, horrible really. Id like some help or feedback on this. I wont mess with internal stuff since the app supposedly loads on top and doesnt change anything per se.
Try switching to the CFQ scheduler in Voltage Control app, if the problems did improved and rarely show up then switch to BFQ.
BFQ is the best for latency dependent data transports. I'm using the latest voodoo sound without any crackles or pops.
sound pooping; ehrrr... "popping"
Tkun said:
I've noticed popping only since I flashed Jt's CM7 rom. I'm not currently on the rom, but the problem still exists. I'm thinking there's something in that rom that has messed up my phone's audio (hopefully not permanently).
Click to expand...
Click to collapse
an interesting theory - I've now got the popping-when-touching-the-screen issue too. although i'm currently running imnuts 100 kernel; the voodoo 8 (plus) app; and stock ED01 debloated - I did tryout the cm7 roms recently also.
I expect that's just coincidence - many of us here play with various roms and such...
also - the popping issue happens with all the sound apps I've tried (tw music player; pandora; npr; tunein radio, etc).
bmeek said:
an interesting theory - I've now got the popping-when-touching-the-screen issue too. although i'm currently running imnuts 100 kernel; the voodoo 8 (plus) app; and stock ED01 debloated - I did tryout the cm7 roms recently also.
I expect that's just coincidence - many of us here play with various roms and such...
also - the popping issue happens with all the sound apps I've tried (tw music player; pandora; npr; tunein radio, etc).
Click to expand...
Click to collapse
I believe JT1134 and imnuts used the same SIO default scheduler, you should verify with imnuts.
Changing schedulers doesn't work. I emailed supercurio and its just an issue with froyo kernels and his driver so it wont be fixed until the new version of voodoo sound most likely.
Sent from my SCH-I500 using XDA Premium App
Zacisblack said:
Changing schedulers doesn't work. I emailed supercurio and its just an issue with froyo kernels and his driver so it wont be fixed until the new version of voodoo sound most likely.
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Yes it does.. "I/O scheduler latency problems" IS Froyo kernel problems.
http://forum.xda-developers.com/showthread.php?t=1071087&page=2
beray5 said:
Yes it does.. "I/O scheduler latency problems" IS Froyo kernel problems.
http://forum.xda-developers.com/showthread.php?t=1071087&page=2
Click to expand...
Click to collapse
I don't know if you have this issue or not, but I didn't spend time writing this thread for nothing. I've done troubleshooting and have followed steps to fix it and even emailed the man who created the drivers. He mentioned nothing about schedulers just said that the Froyo kernels are poorly implemented and he will have to find a work around for it. He also mentioned there is no permanent fix for it, only what is in the OP. I can sit here playing with schedulers all day (as I have done), but nothing will change.
i also experienced this after flashing jt's cm7 so im pretty sure it has to do with the voodoo sound driver in the newer kernels as stated above. even after odin back to stock didnt fix the problem. hoping next voodoo update fixes this issue
*edit
problem fixed after going back to stock then installing official froyo
I just loaded the Inintial Contact Rom on my Sprint Tab. I found the voltage control/OC utility and was wondering what settings ya were using. I have searched these forums extensively and have found nothing on what people are using on these tabs. Thanks again
Sent from my SPH-P100 using XDA App
Anybody got a sprint tab with this ROM?
Sent from my PC36100 using XDA App
I haven't seen your ROM or Kernel (which is the far more important component when overclocking) so I'm not sure what it's capable of but you can see a couple of people (including me) share settings here.
Overcome can go up to 1.6GHz so I usually leave it on 800-1400 MHz as a general rule, with the same cascading voltage scheme I shared in the link.
Thanks that somewhat of a baseline to go by. This ROM just came out a few weeks ago and i just got the time to load it. I am running a kernel by rodderick. Fastest I can clock to is 1200mhz.
Sent from my PC36100 using XDA App
Yeah I think that's as fast as that kernel would let you Oc I have the exact same set up.
Sent from my SPH-P100 using XDA App
Overclocking on intial contact
After you move it up to 1200, save the settings. Close the program. then go back in. You should be able to move it higher? I'm pretty sure that's what I did. I flashed initial contact today. I'm keeping mine on 1200 for now... I don't feel like being too risky yet.
Hi
I just flashed lean kernel and gave it a day or two to settle down
I have been trying to over clock it and it just won't stay that way
Every time I restart it just goes back to how it was
What can I do to make it stick
Thanks
Sent from my Nexus 7 using XDA Premium HD app
If you have more than one dameon control installed they may conflict with each other and revert back to "stock" at start up. Are you using set cpu to overclock? Does your rom have overclocking abilities in settings?
Lastly, did you see an option 'set on boot'
Sent from my HTC Vision using xda premium
According to what you've said, its most likely due to the powerhal. The stock powerhal reverts back to 1.3 GHz after a while no matter what you set it on. Best thing if you want oc is to flash imoseyn's 1.5ghz powerhal found in his rootz thread
Sent from my iPhone 5
demkantor said:
If you have more than one dameon control installed they may conflict with each other and revert back to "stock" at start up. Are you using set cpu to overclock? Does your rom have overclocking abilities in settings?
Lastly, did you see an option 'set on boot'
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Yes its ticked as "Start on Boot"
I'm on stock rom but LeanKernel, I'm trying to overclock with ROM Toolbox PRO but it keeps reverting to 1.3ghz, 1.5ghz is used if I overclock everytime I restart but then reverts when rebooted.
markj338 said:
According to what you've said, its most likely due to the powerhal. The stock powerhal reverts back to 1.3 GHz after a while no matter what you set it on. Best thing if you want oc is to flash imoseyn's 1.5ghz powerhal found in his rootz thread
Sent from my iPhone 5
Click to expand...
Click to collapse
Yeah I think your right here mate, did a little bit of research over last few days and it seems PowerHAL is the culprit.
Could you explain what that PowerHAL is and how it effects overclocking etc?
Im guessing its like the native frequency setting?
Thanks !