I dont know if i am explaining this right, but it seems that whenever battery status is running, the pixels seem to get very blurry. For example, the signal bars start shivering, the bars become blurry, and random blurry lines show up in random parts of the screen. has this happened to anyone else, and if so have you fixed it?
Thanks in advance,
Anish88
If by that you mean that the screen starts flickering like a very old CRT monitor, then it does happen when the CPU in underclocked. In my wizard, the view becomes unstable below 100MHz, but it might vary from device to device.
First thing you might want to do is to go to batteryStatus options and disable the CPU scaler (dynamic CPU overclocking) and set the CPU speed to stock 195MHz. If after that the screen becomes stable again, it means that it was a problem with underclocking. In that case you'd need to find a minimal speed on which your screen looks fine - just test all the speeds below 195MHz and set the minimal speed not causing screen problems as minimal speed for the CPU scaller (it's in BS options/CPUScaler)
i believe it happens when ever this an overclocked speed. But it also happens occasioinaly at 195 mhz. is there any fix for this?
any ideas?
nobody else has had this problem????
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.
Hi Everyone
I have OC Widget installed on my phone (htc hero sprint) and I was wondering is there a way to confirm that the speed being reported by OC widget is in fact the actual cpu speed. My reasons for doubting this are that
1) even with a setting 710mhz the phone seems kind of sluggish at times
2) I get notifications of cpu settings changes when turning my screen off to on but I do not see a change in the number displayed in the widget (it is always set at the on screen speed)
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
*edit*
I would be interested in knowing where you read CPU temperature information, though.
Doward said:
adb shell cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
*edit*
I would be interested in knowing where you read CPU temperature information, though.
Click to expand...
Click to collapse
CPU temp huh...i have no idea lol
Since you brought it up I do have a question for you that is somewhat related, can access heat (from either the battery or cpu) cause a reboot (either a complete reboot going through all the load screens or just a reboot to boot back into the home screen).
I was experiencing quite frequent reboots (the later of the two I described above) and had initially thought maybe they were app related but could never determine if that was the cause.
I was over clocking and underclocking so was wondering if maybe that could have lead to some instability issues.
dsMA said:
CPU temp huh...i have no idea lol
Since you brought it up I do have a question for you that is somewhat related, can excess heat (from either the battery or cpu) cause a reboot (either a complete reboot going through all the load screens or just a reboot to boot back into the home screen).
I was experiencing quite frequent reboots (the later of the two I described above) and had initially thought maybe they were app related but could never determine if that was the cause.
I was over clocking and underclocking so was wondering if maybe that could have lead to some instability issues.
Click to expand...
Click to collapse
Clock speed and voltage go hand in hand - if you are adjusting one without the other, yes, you will affect stability. Heat also plays a part - now, specifically can a hot battery cause a CPU malfunction? Yes, but unlikely. More likely, the heat will affect the voltage from the battery and case CPU instability via that path.
Hey guys,
A few weeks back I rom'd my HTC hero with VillainRom 12 and it was working great for awhile. Now however it crashes all the time, or just freezes up and I have to remove the battery.
I have the phone over clocked to about 650mHz. The battery temps seem fine.
Has anyone else experienced this problem before? Any way I can do a debug on my phone to find out what's crashing?
It's really starting to annoy me considering that I use my phone for my business and it's not good when a customer calls and my phone dies and reboots when I go to answer a call.
try overclocking to a lower extent
it might be because your phone cannot handle ur clock speed
(my MAX clock speed is 672... it simply crashes with 691 or higher)
You were absolutely right. It was clocked too high.
I turned it down and now it works great.
Thanks for the tip.
652 seems to be my max.
710 is my max, I can't go below 192 either or the phone starts to have a fit, I wanted to use a lower clock speed in "screen off" mode, but I'll have to stick with 192
I (and several friends that I asked) noticed a mark increase in UI response (laginess) when coming out of sleep, opening app drawers, initializing the keyboards, scrolling between launcher screens, etc. Having random lags is annoying, but having 2-3 second lag spikes when using the keyboard is downright frustrating.
I know that lab benchmarks are way up with the new release, but frankly I don't care about those if my day-to-day functions suffer.
I first began to notice this when I made the stock upgrade to Froyo. 2 days ago, I flashed the EViO 1.5 ROM on my phone, and it seems to be 4x as bad. Paring down the window launcher helps marginally. ADW -> Sense -> Launcher Pro in order of most to least lag. I am currently using Launcher Pro just because it's responding a little better than the others.
In a somewhat related post, one of the developers offers that a lot of lag is due to aggressive garbage collection:
(unfortunately, I am not yet verified so I can't post the link)
I also wonder if the overhead from the JIT compiler or lack of proper memory caching isn't the culprit ... or perhaps this is to what the aggressive garbage collecting is referring.
Who else has noticed this? Can anyone offer up an explanation?
I would be willing to reflash to a new ROM if someone can suggest a custom ROM that they recommend as having faster normal UI response time.
Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag
DirtyShroomz said:
Are you using Juice Defender or do you have off "always-on mobile network?" The lag when turning on the phone is the phone searching for 3G svcs, notice when you are on Wifi there is no lag
Click to expand...
Click to collapse
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.
None of these issues using Myn's 2.2 rls3 Rom and ziggys 11/5 kernel. I DON'T use setcpu. It can cause instability issues. Like the lag time in wake up. Some phones don't like 245mhz when sleep. Try boosting to 384 screen off. Also, overclocking can be beneficial but clocking too high can cause poor responsiveness. It can also affect benchmarking scores negatively if clocked to high. Try ziggys 11/5 kernel, its doesn't support overclocking, but it honestly feels like it is overclocked using this Rom/kernel combo
Sent from my DAMN Evo!!
lag what lag ? my 6.1 is lag free
moodebony said:
No juice defender.
I have my radio set to always on.
Most of my testing at home is done on AC power with WiFi turned on, lag definitely still exists.
There's a good 4 - 5 seconds of lag before I can use my window launcher after waking up my phone. I do have setCPU configured to scale the processor down to 245mhz while the screen is turned off. This may explain the lag after wakeup, but not the intermittent lag.
Click to expand...
Click to collapse
If your setcpu governer is set on something like conservative, it can defintely cause intermittant lag. get away from setcpu and use a havs kernel.
Currently mine is instant, no lag at all, but I had this problem about a week ago. I am running Fresh 3.4.0.1 with Netarchy's 4.2.1 cfs/havs kernel.
What caused my problem with lag was a lack of internal memory. I was down to about 64 MB of internal memory left and it would lag on wake or when exiting apps, and I noticed that it would often have to reload the UI whenever I exited an app. The fix was easy. I moved what apps I could to the SD card and used titanium Backup to remove a bunch of stuff that I do not use. Once available internal memory was over about 100 MB (134 MB is what it was when I was finished) the lag totally went away.
Problem Partially Solved!
SetCPU was indeed the main culprit. I was under the impression that overclocking too much would just cause instability. It seems that moving the ceiling from 1228.8mhz down to 1113.6mhz solved most of my new lag issues with the EViO ROM.
Indeed, upping the screen-off throttle-down from 245 to 386 also seems to have helped the wake-up lag time, though I'm still doing some more testing on this one.
Would I need to set all floor values up to 386 as well, or is that just for the screen off value? What scaling setting do you guys in setCPU? Conservative? Performance? On-Demand? Does anyone happen to know exactly what the differences are in the algorithms that they use?
So can anyone offer up an explanation as to why overclocking would result in lag? Is there some kind of hardware throttle-down that's happening? I had a catch for if the battery got too hot that would throttle back to normal speed, but I never seemed to reach it. Is there a known heat limit where the hardware automatically throttles down?
As for the seemingly normal, random Froyo lag spikes, I'll be monitoring that over the next few days.
Thanks again in advance for any information.
I installed the OC kernel/fast mode from this thread. http://forum.xda-developers.com/showthread.php?t=1906507&page=7
and it works well, but I have a lot of bleeding and ghosting going on. IE. The outline or parts of images stay after I start zooming/panning, basically doing anything. Is there anyway to get rid of the bleeding?
Fast mode does degrade display quality - it's not that good for reading in fast mode, imo - but is helpful for things that redraw the whole screen.
If you just use the overclock and change the governor to performance, the quality of the display isn't affected and you get a performance benefit. I briefly tried locking the cpu at the higher end of the frequency range, which is noticable but I suspect drains the battery more than needed.
Terminater27 said:
I installed the OC kernel/fast mode from this thread. http://forum.xda-developers.com/showthread.php?t=1906507&page=7
and it works well, but I have a lot of bleeding and ghosting going on. IE. The outline or parts of images stay after I start zooming/panning, basically doing anything. Is there anyway to get rid of the bleeding?
Click to expand...
Click to collapse
Try clearing "dalvik cache".
Have you flashed the latest kernel 166?
http://forum.xda-developers.com/showthread.php?t=1906507&page=5
For viewing images I use "JustPictures!". For PDF's, 'EzPDF' and 'Ebooka'.
The ghosting is hardly noticeable.
Here is compare of fast mode and no refresh on my nook. fast mode has a high loss of contrast and a lot of ghosting.I preffer no refresh. Program is EBookDroid.
Thanks for the suggestions, guys!
I'll try them out and see if they work.