Hello folks,
first post, pleasure to be part of the group
Arc LT15i, 2.3.4, doomkernel#11, 4.0.2.A.0.42
more than 10 seconds to wait to be able to answer a call
takes 3-4 sec to light the screen (it's an eternity when you have to answer), and often first appears the unlock screen, then after seconds the sliding green botton.
really sorry for the noobhood, but any ideas?
thanks a lot
Cavin
I updated my phone to latest official firmware and i alos have this lag, but not that much. It takes 2 seconds for the screen to show who is calling and to be able to answer it, and it takes around 0,5 seconds when pressing the unlock button to light up the screen.
same problem when i was using stock rom
but when i moved onto MIUI,the phone is pretty fast and answer screen appears pretty quickly
Which CPU scheduler are you using? I have seen that using smartass or other schedulers which reduce the clockspeed on standby can reduce the responsetime of the answer screen.
setxperia raise the clockspeed on incomming call to make the response a bit better.... ;-)
Sent from my MT15i using Tapatalk
Thanks guys for answering
You're right! It's due to the clock's settings. May be, i'll come back to the former firmware any hints?
upgrading clock's frequencies works well, but drains battery faster (and this setup requires already a lot of energy ).
using "no lock" app, gains few secs
last night came up with the same good idea of using the incall profile
i noticed that using a too low min clock freq, the device is less reactive, although using "interactive", "smartassv2" or "ondemand". "scary" profile seems to work slightly better on incall reactivity. any experience?
Thanks
Cavin
If you use smartass (v1/v2), there's no need to set any profiles for screen off. The governor will stick to the lowest available frequency.
Smartass v1 used to have wake issues (on HTC Desire, at least), but v2 seems to be fine, I'm using it on the Arc S, I haven't experienced any lags with either stock or CM7 ROMs.
I'm not familiar with Setxperia and its settings, though, could something be set wrong, causing poor performance? Just a guess...
thanks
i noticed some lags with a very low min clock (e.g. 122), disappearing setting min at 8-900mhz (max 1.2ghz)
actually dunno why, but if i succeede in changing the rom discovering what to wipe, gonna tell you more
Cavin
Related
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
macfan74318 said:
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
Click to expand...
Click to collapse
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
sino8r said:
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
Click to expand...
Click to collapse
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
seancneal said:
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
Click to expand...
Click to collapse
Still happens to me when I try that. It occurs when you press the power button twice in succession.
Hi there,
anything new on this topic? I'm currently experiencing this annoying problem as described.
I've already tried to set the minimum clock to 368 Mhz but the bug still exists. Even setting CPU to standard clock (Max/Min @800) didn't solve the problem.
Is it possible that the reason is located already inside the overclocking kernel?
Greets
dktnecro
Generally if you're overclocking and you have lockscreen issues that are not present @ stock speeds, then it sounds to me like the overclock is too much and your system probably isn't stable.
Based on my experience overclocking computers, things can very well appear stable but if you do stress testing (8+ hours straight) things often crop up and show you that it is in fact not stable. This sounds like one of those things. And that's not good. Who knows what other corruption could occur during your use at that speed? I had the same lockscreen issues myself, and once I realized it was due to overclocking too much I ended up solving another issue I had where half of the calls I received were garbled to the person on the other end. No more lockscreen issues or garbled calls since backing off the o/c a bit.
If the issue doesn't happen at stock speeds then maybe it's just the kernel, and hopefully that isn't putting you at risk of any kind of corruption, either.
Keep in mind I really can't be 100% if overclocking will cause corruption on a phone, but based on a lot of time spend overclocking pc's I would have to guess that it can. I'm surprised that this isn't brought up more often on device forums.
Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.
In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).
You could try using cpu tuner instead. Gives you way more options.
CM 7
You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?
My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
thanks bro, i OC'd to 1017 and there are no issues
ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.
im having a problem with incoming calls. half the time it works fine, screen pops up...no issues. the other half the phone will ring/vibrate/light will blink but the screen wont pop up.
rooted, currently running CM 7 RC4, but any rom ive loaded does the same thing. any fixes anyone knows of? i also downgraded to CM stable 6.1 and it does the same thing.
is your phone overclocked or underclocked? are you using set cpu and have a screen profile set?
Are you overclocked? If you are, search for "wake issue" to find a solution. Basically, you need to increase the max of your screen off clock speeds until it goes away.
Sent from my HTC Vision
yes overclocked, using setcpu. not using a screen profile set...i will look into that now. also look into the wake issue. thank you.
make sure if you set a screen profile no to set cpu speed to low or you will have the same issue
ROM: Virtuous 1.0.2
Kernel: Virtuous Advanced 2.2.0
I'm having trouble with my screen struggling to turn on when I wake my phone if the cpu speed is anything above stock. If I push the power button once the capacitative buttons light and nothing else happens, if I push it a second time the lights turn off again and I briefy see my lockscreen flicker before my pained eyes
If I do this cycle many times over eventually I'll get lucky, but there's no pattern to the success and it's very frustrating.
The symptoms are similar to this thread: [Q] Phone unlocking screen issues. The method described there to solve the problem was to turn off on/off animations. I don't think this solution applied as I'm not using CM7.
I think the touchscreen input is recieved despite the screen itself having no picture - for example I can unlock my phone by swiping down (stock Sense lockscreen). If I touch the touchscreen in the right place to open the dialer while I've "unlocked" it in this way, when the phone finally wakes after frantic power button pushing, the phone will be in the dialer app.
I think it might be related to Sense as I tried a stock Sense from rmk - [ROM]Vision_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_12.5 0.60.24_26.08.04.16_M and overclocked using both Virtuous Advanced 2.2.0 and Pershoot's Kernel. In both cases I also had wake issues any time I tried to wake when the cpu was clocked above stock speeds (even 900MHz).
Further evidence towards a sense problem is that I don't have any issues when I'm at 1.4GHz when using CM7. I missed the sense apps too much to stay with CM7, however.
I have a workaround using CPU Tuner with a screen off profile of 246-806 Mhz, and I can then overclock freely afterwards. I can live with this but if anyone has an idea why this might be happening then I'd appreciate a solution.
As I've been lurking on XDA for a while but this be my first post, thanks to all you incredible developers who have made it possible for me to customise my phone in these fantastic ways.
Set your screen brightness to something greater than 50%. It's not a fix but a very reasonable workaround .
Sent from my HTC Vision using Tapatalk
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
The screen off issue is thoroughly discussed in the Virtuous kernel thread. I forget the exact explanation, but its got something to do with the CPU stepping while the screen if off.
The common fix is a SetCPU/CPU Tuner screen off profile, as you seemed to have discovered. But adjusting the governor type in addition to minimum CPU clocking seems to be the common solution used. I think the interactive governor seems to work best to prevent screen wake issues.
http://forum.xda-developers.com/showthread.php?t=967153
Yeah, I read that thread fairly extensively but the solutions there didn't help. I can easily replicate the problem by setting my cpu with the performance governor to anything above stock speed (i.e. the cpu will be at one single speed the entire time, I think?). The over 50% brightness solution works very well (at the expense of more noticeable battery drain)!
Atomcracker said:
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
Click to expand...
Click to collapse
I had seen the workaround mentioned on the CyanogenMod forums yesterday: http://forum.cyanogenmod.com/topic/20943-screen-doesnt-always-turn-on-from-sleep/
I recently have bought a Defy plus.
Stock 2.3.4 ROM used so far with LauncherPro.
Doing OK with battery life so far, but now starting to look at the CPU over/underclock capabilities. Started with Antutu CPU Master and CPUTuner also.
One thing I haven't seen as yet is the ability to underclock clock below the min 300MHz.. or even whether this makes sense. I guess undervolting is the other option, but perhaps someone can guide me here.
use setvsel to oc/uv, thats the easiest and best app imo. although underclocking your phone below 300mhz may cause instability and makes the phone wake up much slower in my experience.
sent from my cm7 defy...
I agree with zakoo2: Going below 300 will not be a good idea and it will most likely not improve your battery life in any significant way:
My Defy is running between 300-600Mhz and right now the LCD screen is the biggest consumer: Changing the (auto-)brightness settings in CM7 will do *much* more to your battery life than going below 300mhz.
What really helps saving battery life: use setvsel and leave the minimum clockspeed at 300MHz, but set a vsel value of about 20 for it, then scroll down and enable "limit to vsel1 while screen is off".
Also, going below 300MHz will probably make the phone sluggish when waking up from sleep like if a call comes.
Sent from my MB525 using XDA App
im just change from 300mhz to 330mhz lowest. 300mhz will make my defy+ lag when got incoming call. im using smartass govenor.
I heard some guy out there got 80 MHz and running, but I'm not sure of it.
As people said, clocks lower then 300 MHz would make your phone run horribly while waking up (i.e., it would take a long time for the screen to turn on when receiving a call, and you would probably miss it most of the times). Setting 300 as VSel1 and limitting to it while screen is off (2nd-init enabled bootmenu has this option, and downloading SetVSel - free at Android Market - will also do the trick if you have a rooted, but stock ROM) will help you save a lot of juice. Using a lightweight launcher (I personally recommend MetroUI or Zeam) also boosts up batt saving. Last, but not least, setting brightness to auto or minimum (using frosted/mat screen protectors will help a lot while using the phone under direct sunlight) also saves loads of charge.
Obviously, using a light ROM (I think Barebones may be a good option, though I think it's not suitable for me, but it's a personal matter) and calibrating your battery in a monthly basis (via manual calibration - you can find how to do so by googling -, wiping batt stats in custom recovery and/or using the batt calibration app included in most ROMs - but also free at AM) also help.