Hi All,
I have a weird issue.
When someone is calling me, there is a delay (several seconds) between the ringtone sound and the number appearing on the screen.
Its occur especially after at least 5 minutes of not operating the phone.
Any help?
Yeah me too facing same issue. it takes 1-2 secs to wake up while ringing.
are you using Abyss kernel and under clock CPU to minimum 100mhz ?
I had this problem with Abyss Kernel and set minimum speed of CPU to 100mhz.
using CF-Root kernel now, this problem is gone.
could be 100mhz wake up latency.
Does it work with Rocket v20?
wireless.tech.expert said:
Does it work with Rocket v20?
Click to expand...
Click to collapse
not sure, you can consult with the peeps in the Rocketrom thread, sure they can help you .
Currently on darky rom. not seeing this
Related
Currently running VillainROM 10.3.0 (with Sense UI)
Does anyone get problems regularly on the slightest of underclocking (using SetCPU)?
Min at 245:
- Alarm wont turn off (only snoozes)
- Clock on Lock screen wont update
Min at 128:
- Music player becomes stuttery, took a few minutes for screen to power on to turn off music
Noone else seems to have mentioned it ?
Am I doing something wrong?
And its a bit worrying considering so many custom ROMs come pre-clocked.
Totally a hardware issue. Your phone just can't cope with the lower speeds. Not all can.
Mine will do 19mhz on sleep and wake immediately etc. but most others won't
Villainrom should default to the stock settings unless you install something like setcpu and define oc settings.
Not sure about other roms but I guess they do similar unless otherwise stated.
ah cheers.
i knew that some phones couldnt reach a particular Max clock speed, but didnt know it was a similar case with the Min clock speed too
You should try Cronos Droid. I am having the exact same problem as you on all OC'ed 2.1 roms, except Cronos Droid.
My settings on Cronos:
Screen on: 710 mhz
Screen off: 160 mhz
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
rjmjr69 said:
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
Click to expand...
Click to collapse
I'm running Baked Snack 1.1, doesn't matter what rom or kernel I use though, it still happens.
It doesn't matter if I use overclock widget or SetCpu, if I were to set it so that my phone underclocks to 200mhz or 400mhz while the screen is off it freezes and I have to pull the battery.
Same here im running stock and i've tried setcpu and no matter what i hav to pull the battery out everytime. So i uninstalled it.
Sent from my Epic 4G
I had the same problem set the cpu with min of 400 and max off 800 should fix your problem
Sent from my SPH-D700 using XDA App
It means that there is not enough voltage run that frequency on your phone. Some times these kernel developers undervolt the phone which all phone don't support at all. Try some other kernel like the xtreme kernel. That kernel actually work for me and I can underclock my phone without freezing.
rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
murso74 said:
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
Click to expand...
Click to collapse
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
I'm running Baked Snack 1.3 and found it to be stable at 1.2ghz using OC Widget. With screen on I have it set to min 400 and max 1200. With screen off it's set to min 400 max 600.
I too am having this problem. No mater what rom or kernal I use. It seems as if Setcpu and Overclock widget sometimes cant read the frequencies and let the phone underclock to 19.2Mhz which is probably like trying to wake the dead!
I wonder if it has anything to do with the new Superuser.apk? it always seems like setcpu is trying to get permissions. Maybe, I dont really know. Can one of you really smart people look into this?
In the meantime the only profile that I have set is screen off Max 800 Min 400, maybe that will work?
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
What i've gathered over the last several months, is that SetCPU profiles are buggy with our phone. Its recommended not to use profiles.
I'm fairly certain that SetCPU should not be used without a custom kernel that allows for over/under clocking. If you're on the latest ViperROM then you are using a kernel that we have no source code for, therefore it doesn't support over/under clocking; rendering SetCPU useless and prone to cause problems.
mattallica76 said:
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
Click to expand...
Click to collapse
My SetCPU is using conservative and I haven't had any problems so far. I am running BonsaiROM 1.14.
jemarent said:
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
Click to expand...
Click to collapse
If you have it set to under 200 with the screen off it won't wake up after a while.
I've had the same problem on all builds and ROMs that I've used. The only constant through all the different setups I've used were Advanced Task Killer and SetCPU. I stopped using ATK (with auto-kill on screen off, I use EStaskmanager for manual killing when phone is on) and the problem seems to be mostly fixed. It does still happen once in a blue moon though, say once every day or two.
Phoenix Kernel/Syndicate ROM 2.1
SetCPU: 100min/1200max
Screen off: 100min/200max
Batter < 30%: 100min/600max
Hi,
I have this annoying problem regarding waking up my device when its locked. Normally i should press the power button, or the trackpad as im running virtuous rom, and the screen should give me the lock screen. But this does not happen, intead screen stays black, the keys on the bottom do light up, and it registers my touches on the screen as i can put the music player on again.
This is happening for quite some time, but lately its more often and its really frustrating me because i have to hit the power button for like 10 times in a row before it finally goes on again.
When it stays black and i put it off again, touching the power button, moste of the times the screen will flash the lockscreen and go black again.
Ive tried to find a sort of system in it, like a period of time or somthing like that, but it seems as if its completely arbirtrary when it happens and when it doesnt.. Only thing i remarked was that when it's off for a longer time, it will have more chance of getting on the first time then when its off for a shorter period...
Any suggestions to fix this evil thing?
cheers
This is a very comman problem.
what you need to do is setting up a screen off profile on setCPU
min 245
max 368
scalling : powersave
I agree check your screen off profiles. Also try not to oc too high. You might also want to install the pershoot kernel if you haven't already. I had this issue when I fist installed the virtuous rom & switching kernels and tweaking my cpu profiles resolved this issue.
Sent from my HTC Vision using XDA App
Screen off profile doesnt help, What does work is less oc'ing it... stupid thing is i can only oc to 902 mhz for the screen to turn on all the time... Thats like not oc'ing it at all ><... I'm on the virtuous kernel now, will try the pershoots in a min, i'll keep you updated
Oh sorry, screen off profile does help, didnt enable profiles in a whole ... pershoot kernel helps a lot, with that one and the screen off profiles, i can oc to 1517 and even then its just not going on very rarely... thanks for the help... Only thing thats regrettable is that the pershoot kernel does not have the smartass governor ...
EDIT: I realised i didnt enable the profiles while using the virtuous kernel either, so i installed that one again and guess what, it works!! Every single time i hit that power switch it goes on like it should... what a relieve thx guys
grtz
I found a bug about BLN.
My phone gets freeze when i have more than one missing calls. Somebody gave me two or more calls while i didn't notice my phone. When i noticed it, i can't switch on the phone but doing a battery pull.
It's not related to other mods such as BLD, TW, too low min cpu freq, live OC, deep idle and undervolted. Because i've switched all options on and off respectively under the same scenario when the problem occurred.
Finally i turned off the Blink Status (status can be switched on though), my phone can be able to have more than one missing calls without the problem.
My settings are as follows:
ROM: IMM26 4.0.4 port form ns4g by evilisto
Kernel: Air Kernel v3.4.5
Maybe some devs can solve the problem
kwokyu127 said:
I found a bug about BLN.
My phone gets freeze when i have more than one missing calls. Somebody gave me two or more calls while i didn't notice my phone. When i noticed it, i can't switch on the phone but doing a battery pull.
It's not related to other mods such as BLD, TW, too low min cpu freq, live OC, deep idle and undervolted. Because i've switched all options on and off respectively under the same scenario when the problem occurred.
Finally i turned off the Blink Status (status can be switched on though), my phone can be able to have more than one missing calls without the problem.
My settings are as follows:
ROM: IMM26 4.0.4 port form ns4g by evilisto
Kernel: Air Kernel v3.4.5
Maybe some devs can solve the problem
Click to expand...
Click to collapse
I can also confirm something similar like this. Also AirKernel v3.4.5, 4.0.4 PixelRom (even tho I think I had this on 4.0.3 roms, too). Buttons blink, but can't turn on my screen. Even music went till the end of song, didn't go to next song, and then I removed battery. No LiveOC nor OC, no DeepIdle...
Sent from my Nexus S using xda premium
Doesn't happen here:
Left 3 missed calls in my cellphone, buttons blink as they should, and phone wakes up as it should.
BLN Pro, but didn't happen in the free version either.
robrob777 said:
Doesn't happen here:
Left 3 missed calls in my cellphone, buttons blink as they should, and phone wakes up as it should.
BLN Pro, but didn't happen in the free version either.
Click to expand...
Click to collapse
What rom and kernel do you use?
kwokyu127 said:
What rom and kernel do you use?
Click to expand...
Click to collapse
This is my setup:
http://forum.xda-developers.com/showthread.php?p=22328954#post22328954"
Hi Guys!
I've noticed that some roms (most of them apart of Invicta and sometimes RR) have some delay when pressing the power button to show the lockscreen.
That's pretty annoying since it takes even 5 seconds sometimes!
Any clue or fix?
Thanks guys.
Cheez2553 said:
Hi Guys!
I've noticed that some roms (most of them apart of Invicta and sometimes RR) have some delay when pressing the power button to show the lockscreen.
That's pretty annoying since it takes even 5 seconds sometimes!
Any clue or fix?
Thanks guys.
Click to expand...
Click to collapse
I'm pretty sure that the kernel is offline'ing all but one core in deep sleep (doze), and thus there is a delay when waking up.
If you download an app called "kernel adiutor", you can set the minimum CPU cores from the "little" cluster to 2. This should fix the problem.
negusp said:
I'm pretty sure that the kernel is offline'ing all but one core in deep sleep (doze), and thus there is a delay when waking up.
If you download an app called "kernel adiutor", you can set the minimum CPU cores from the "little" cluster to 2. This should fix the problem.
Click to expand...
Click to collapse
Thanks. I'm trying right now and i'll report back