Related
I've found this neat tool: http://www.nuerom.com/BlogEngine/page/nueDynamicClock.aspx
Has anyone used this on their X1 and did you notice any changes? I don't think you can use it for overclocking an X1. But I'm thinking about setting clock frequency to 19 MHz on Suspend, to get more out of my battery.
I've got this tool, not sure if it made much of a diff when I overclocked it to 528
( or just set it to the base clock speed since they have it underclocked @ 400 mhz ), wanna try the lower speeds, but not sure whether it will have a negative effect.
I uninstalled it..
found that any apps (such as gps cycle computer, audiomanager etc) that played with the screen on didn't work very well when the speed was lowered. Also had quite a lot of instances when the screen was corrupted after coming out of suspend..
I use it since yesterday, so i can't say anything about changed battery lifetime. But i got it working only after setting min-clock to 384MHz. With lower settings the phone got frozen in standby mode after a while. I'll try it for a few days for testing a (hopefully) enhanced standby time...
PS: i use 384MHz in suspend mode and after idle time of 5s, didn't change max clock or voltage settings (all to "auto"). Maybe setting idle time to 2s would care more battery life, but i don't know how the cpu will stand changing the clock so much often...
Been using it since v1.0. Seems to have some battery gain (10% over 8 hours better) - set to default 528MHz, down to 256MHz idle and 122.98MHz on suspend and screen off. Needed 123MHz for clean audio playback in standby.
Only screen corruption (inversion) issues I had was when set too low (19MHz) at standby. Now using these settings for a few days and no issues so recommended for use with TFlo3D2.
Unless you're running WM6.5 with WM7 titanium - makes it very slow to respond out of standby.
And it doesn't overclock - 528MHz is default clock speed.
I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?
Mark A Cilenti said:
I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?
Click to expand...
Click to collapse
I have a standard R2A ROM and it works for me. Can't tell you what's the problem with your installation, though.
Anyway, I found since I installed the tool my device is worse than before. It sometimes interrupts audio playback when display is off (ALthough frequency in that case is still at 3xx MHz!) and sometimes it takes very long (5 secs +) to suspend and to wake up again. So I think I'm gonna remove it.
I only turned down the voltage to 1.1 instead of 1.325 running on 528MHz.
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
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
If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.
jbjarko said:
If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.
Click to expand...
Click to collapse
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?
jenisiz said:
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?
Click to expand...
Click to collapse
Not really, seems normal to me. Should I try turning it off, and see if that fixes it?
By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App
kdaz said:
By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.
Ok, downloaded setcpu, what specs should I put it at?
jenisiz said:
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.
Click to expand...
Click to collapse
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.
kdaz said:
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.
Click to expand...
Click to collapse
IMHO...that's really low.
Where do I set it for screen off? All I have are two sliders?
jbjarko said:
Where do I set it for screen off? All I have are two sliders?
Click to expand...
Click to collapse
you have to go under the profiles tab and enable then you can set different profiles.
Still doing the same deal. SetCPU is at 400-800 during screen off. Haptic feedback is off.
Any ideas?
I'm not even running SetCPU and I get this happening.
Anyone have any more suggestions? It's not a huge deal, but it sucks watching my battery drop 10% every time I have to pull the battery and reboot.
I have a T-Mobile G2 that's been rooted and flashed several times (cm6, virtuous, supervillainz, senseginger, cm7) and through I think all of them I noticed an issue with coming out of sleep where the screen doesn't turn on
it still reacts to touch (ie I can slide to unlock), and the bototm touch keys light up, but there's no backlight or picture on the actual screen
sometimes it takes several off-on cycles to get it to work... I've recently noticed (and may be just imagining it) that the trackpad wakes it up with a much better success rate
details:
HTC Vision (G2)
Android 2.3.3
Baseband 12.28b.60.140eU_26.03.02.26_M
Kernel 2.6.32.28-cyanogenmod-g58d929e [email protected] #1
CyanogenMod-7.0.0-RC2-vision
any ideas would be welcome before I lose it and start poking at the kernel, radio and whatnot
thanks,
L
happens to me in virtuous, never happened to me on CM (i havent tried cm7 yet)
i believe its a problem with the cpu scaling, ie when the screen is off, processor drops to 245mhz and when the screen turns on, speed doesnt scale up fast enough
i usually underclock my g2 to 599mhz (governer set to on demand) but if i go any lower than that, getting the screen to come on becomes a frustrating project lol
I have the same problem, its so annoying especially when someone calls. Its been mentioned in other threads and I'm sure its a known problem but like u I need a fix. Stock ain't so bad as long as u can see who's calling and what time it is without trying to wake the phone 20 times. Please will someone finally answer this question? Or do we all need to revert to cm 6.1 or stock????? Small problem but big outcry.
Sent from my HTC Vision using XDA Premium App
thanks, I downclock to 200mhz on screen off
I'll up it and see if it makes a difference
Are you using the screen off animations in CM7?
Sent from my HTC Glacier using XDA App
screen off yes, screen on no
Try disabling the animations all together and see if it helps. Also are you OC'd above around 1.2ghz?
Sent from my HTC Glacier using XDA App
I've disabled them for now, gonna see if it helps...
yeah OC to 1516MHz, do you think this affects it?
There was a known issue with CM7 not too long ago where if you had the screen off/on animations activated in conjunction with being OC'd at around 1.2 or above it would cause the sleep wake issues. Took 3 or 4 on/off cycles with the sleep button on order to get the screen to come back on.
The solution was either to disable the screen animations or not to OC very high.
The other remedy recommended earlier is also legit. Set your screen off CPU profile to around 300 or 400mhz. Your problem should be solved by tinkering with all 3 variables. Failing that I would recommend a wipe/reflash and/or hitting up some folks in the CM7 thread to see if anyone else has that issue after tinkering with the above solutions.
Good luck man, I know those little bugs can be frustrating.
Sent from my HTC Glacier using XDA App
thanks for the tips...
I've now upped the minimum clock to 400 across all profiles and turned off the screen off animation... if that doesn't do it, I'll turn down the maximum clock, and if that still fails disable setcpu completely
I will report back any findings
allixsenos said:
thanks for the tips...
I've now upped the minimum clock to 400 across all profiles and turned off the screen off animation... if that doesn't do it, I'll turn down the maximum clock, and if that still fails disable setcpu completely
I will report back any findings
Click to expand...
Click to collapse
I see you have a strange problem.
I use 275mhz when sccreen is off and about 476 mhz when screen is on and nothing like this has happened to me.
Sent from Mars
Seems like nature of the beast. I get it too. Are yall using setcpu? I think its an issue with it. U might try cputuner and see what happens. But it rarely happens now that i set my setcpu to conservative or smartass.
Sent from my HTC Vision using XDA Premium App
this is indeed an issue with downclocking the phone on screen off profile... as soon as I set the screen off profile to anything below the stock 806 mhz, the issue appears
I've reenabled both screen off and on animations, the issue still hasn't reappeared... so it's the downclock :/
I have seen it on Sense ROMs but not CM7, doesn't clocking your phone at 800 when display off eat up a lot of battery also?
I am, unfortunately, not that techno-savvy when it comes to cellphones. But I am having the same problem.
The most I get is a bit of back light, but everything else about the phone seems to be working. Is there anyone who could possibly help me figure out how the hell to fix this?