Related
http://www.oliy.co.uk/download.asp?dir=\software\OmapScaler
it is working fine in my wizard but some ppl complain about causing soft resets or not working at all:
about resets: ver .11 have a "max clock step" option, try to reduce it, my wizard works fine with 50 but some ppl r using 25 or even 20...
about not working at all:
1- unpack
2- copy to windows folder in device
3- copy also omapclock.exe to windows folder in device
ftp://xda:[email protected]/Wizard/Misc/OmapClock_v0.2.zip
4- create an icon or run manually
5- set ur desired options and press save
6- copy the .lnk created to windows\startup so it stats with windows everytime (but test it carefully before doing so or u can end with a neverending soft-reset cycle)
my config (working)
- overclock marked and 240mhz (some ppl report soft resets over 220,
reduce this number also)
- above 70%
- underclock marked and 120mhz
- below 30%
- default speed 214mhz (this is the speed center, used if u dont mark
overclock or underclock)
- max clock step 50 (if u have soft resets reduce this number)(mine
work fine at 50 but resets over 70 as example)
- update period 2000 i guess this is the time between system
monitoring of speed in miliseconds, but please correct me if im wrong
- clock threshold 2 (i guess this is the step between clock changes,
but im not sure what is a period...maybe an internal clock tick?)
ok, i tested this one, if u increase it it takes more time between clock changes,
another thing to try to solve soft-resets, i tested 3 and 4...and takes more time
between changes...
some comment: it speeds up depending on the cpu usage but for some reason it dont get along fine with agile messenger in my setup...if agile is connecting it appear as if the device hang but in fact it resumes operation in 10 secs or so...so try to test it first without loaded applications...then load 1 by 1 and test...
lets talk about this and try to solve problems for the ones that have them...
btw...im using molskis rom and working flawlesly...
hi, there,
I followed your instruction fully.
however, when I clicked Omapscaler, I got an "error exception".
I wanted to show you the details..... but I couldn't "copy & paste" the message.
Noted that, I have been running smartskey + Omapclock at 252 stably for long time, and now with Risidoro 2.26 ROM.
hope to get it working.......
thanks,
ecchi
Cool, I'll give this a try ASAP and report back
Activesync quits
I installed the Omapscaler. It seems to work fine. I have it set fairly conservative - middle at 200, underclock at 170 and overclock at 230.
If I am connected to activesync, it quits after a few minutes of idle time. Have you noticed this?
-Kal.
Mine does the same, but in my case it puts a red cross over the green circle, it didnt sync anymore but i can explore the wizard files...and it does it also without the omapscaler, i guess that that have some relation maybe with the proccessor clock losing sync with the pc...dunno...but in my case is not related to omapscaler...but related with the overclock...
Yeah, I saw the same problem with ActiveSync and rom updates.
Just disable the omapscaler, run omapclock and set the speed to 200 or so, then try again.
Oliy, great program, thank you
Again...in my case i tested activesync just using omapclock (NO omapscaler) and does exactly the same...
Since I got the "error exception" with Omapscalar.witrh my current ROM (risidoro), I have started trying XCPUScalar. However, it is not any more stabler as some ppl had mentioned.
Bottom line:
Omap + smartskey ==> most stable, tried at 252, but about 1 day of battery only.
XCPUscalar ==> fixed at 232, stable. fixed at 247 reboot sometimes. Autoscaling b/t 117 and 247 reboot 50% of the time when you launch/close/activesync. I am testing now autoscaling between 117 and 232. Hope it will work.
soft resets with max clock step at 10
I had the max clock step at the default 50, and got a soft reset. Then, per the advice on this thread, I reduced it all the way down to 10. It still soft resets. I have top speed at 230, default at 200, and bottom at 170.
So, I am giving up on this program.
just a q. it stays at least some seconds or die instantly? omapclock alone works?
Yes, it stays up for a while. It seems like it stays up until it goes into standby mode, or I put it in standby manually. A bit after that, it soft resets.
I have not used Omapclock by itself. I have never felt the need for it. But, something that automatically scales up and down to suit the load seems very useful to me; so I tried it. I am willing to keep trying it, if there are bug fix versions.
-Kal.
Maybe ur problem is with the overclock per se, not omapscaler...try using the device with omapclock fixed...if ur device resets then omapscaler is not the faulty...also, what rom do u have? maybe we can pinpoint the problem to a specific rom or set of roms...
hmm... the problem cannot be overclocking, because it goes into the soft reset directly from standby mode. I would think it would be *underclocking* when it is on standby mode, no? Let me do some experimentation with both overclocking and underclocking using smarskey with omapclock, and see what I can figure out. But somehow I doubt that is the issue.
I have standard stock Cingular 2.25.11 rom.
-Kal.
I have been running Omapclock at 230MHz for a while now, with no problems. The Omapscaler would have definitely reset by now.
And what device exactly and with what rom do u have?
It's a Cingular 8125 device, ROM version 2.25.11.1 WWE (stock ROM that came with the device from Cingular).
Omapclock has been running for almost a day now, with no problems, so the problem must be with the scaler.
-Kal.
A theory...
In case the developer is monitoring this thread:
I saw in the other thread on this forum that someone reported that XCPUScaler has the same problem as I have with resetting when in standby mode on a Cingular 8125 with stock rom as well. It may be that these units have some kind of daemon processes that run even while the unit is standby (I know for instance that my unit retreives email when in standby mode), and that causes activity that pushes the scaler to try to scale up. And maybe the unit (or the rom os version) doesn't like the processer speed being mucked around when in standby mode. Or maybe, even that the API call to sense the CPU load craps out when in standby.
This is a conjecture of course, but it seems to me that there can't be very heavy activity during standby. So, could the developer please try to disable scaling when in standby mode? This may solve the problem. Or maybe, just make that an option that people with this kind of a problem can select.
Just a suggestion...
-Kal.
error exception log
I can run omapclock with smartskey @252 stable.
But when I reconfig my wizard to use omapscaler, I got the following exception on launch:
=============================================
OmapScaler.exe
Exception
CompareInfoRef::.ctor+0x35
CompareInfoCache::GetCompareInfoRef+0x9c
CompareInfo::GetCompareInfo+0xc
CultureInfo::get_CompareInfo+0x19
DataTable::RecomputeCompareInfo+0x11
DataTable::Reset+0x6
DataTable::.ctor+0x113
DataTable::.ctor+0x6
ConfigDB::setupConfigDB+0x32
ConfigDB::Load+0x2a
ConfigManager::setupConfigDB+0x14
ConfigManager::Get+0xc
ConfigManager::get_ocLoad+0x15
CpuClocker::readConfigSettings+0xb
CpuClocker::.ctor+0x56
MainForm::MainForm_Load+0xb
Form::OnLoad+0x15
Form::_SetVisibleNotify+0x1d
Control::set_Visible+0x1f
Application::Run+0x7
MainForm::Main+0xa
==========================================
I have a Molski Rom WWE (30MB) G3 Wiza, installed with CE Star (language tool), and some 7 today plug-ins.
any idea?
astromusic said:
In case the developer is monitoring this thread:
I saw in the other thread on this forum that someone reported that XCPUScaler has the same problem as I have with resetting when in standby mode on a Cingular 8125 with stock rom as well. It may be that these units have some kind of daemon processes that run even while the unit is standby (I know for instance that my unit retreives email when in standby mode), and that causes activity that pushes the scaler to try to scale up. And maybe the unit (or the rom os version) doesn't like the processer speed being mucked around when in standby mode. Or maybe, even that the API call to sense the CPU load craps out when in standby.
This is a conjecture of course, but it seems to me that there can't be very heavy activity during standby. So, could the developer please try to disable scaling when in standby mode? This may solve the problem. Or maybe, just make that an option that people with this kind of a problem can select.
Just a suggestion...
-Kal.
Click to expand...
Click to collapse
i have read around that there r several levels of standby, full, partial, etc...maybe he only need to modify it to work only on "full on"...
but maybe we r both wrong thinking about it a lil longer...maybe he already thought about that and omapscaler dont work when on any kind of partial standby, in any case the device is in standby, u r not going to notice if it takes 20 more seconds downloading the mail as example...
and btw, xcpuscalar didnt worked for me also, random softresets, but omapscaler worked like a charm (now im using batterystatus solution and also works fine)
After much searching I am lost...here's the deal...
I am running on Dutty's newest ROM and everything is working great except for one stupid little thing...
After I go into the backlight settings and set the timeout to 10 secs, It will return to 20 sec or 5 minutes at any given random interval. I check the setting menu say 2 hours later, and it says 30 sec or 5 min. Any ideas??? it's driving me nutso and killing my battery quicker.
Sounds like a poltergeist issue. Can you flash a Shaman?
Well....hmmm, that's not a viable solution unfortunately, leave it to me to find a bug that nobody else has...does anybody have any ideas...i've manually edited the registry and it still seems to change on its own...is there a 3rd party program that i might try to control it?
sorry boss im running the same rom and just performed a few tests for you but my device is acting normal.
This may not mean much but did you do a hard reset after the flash?
yeah i hard reset and it didn't go away and then I flashed duttys newest rom I believe the apr16 one, and it still does...i'm wondering if it's software related, maybe tomtom or something...i'm about ready to try with a clean rom install and no 3rd party software and add one program a day until I see if one is doing it...i'm lost at this point!!!
here's the story: my Tytn II was running fine for some months
one day I was travelling and need to use the GPS until there was just around 8% battery level
then everything started to get slow (GPS map couldn't even redraw)
ok, I though it was in some "slow-clock mode" to preserve battery
then I reseted it and, when I came synced it at home, ActiveSync said it couldn't sync (don't remember why) and it would have to send all the information again
but it was taking forever, so I stopped it and did it again later, when it said it was success
I then noticed my speed dial numbers had been lost, but that's not a big problem
the biggest problem here is that for the last 5 days my Tytn is slowing down very often (like 5 minutes after I reset it), even after I removed all startup programs!
What I'm noticing:
1) GPS maps doesn't redraw (I waited more than 2 minutes... it should take like 1 second)
2) Freecell cards are animating very slow after a completed level
3) touchscreen responsiveness is slow
4) I have TodayAgenda... after I change the date of a calendar item, it doesn't get displayed in the new day (just if I reboot)
5 and probably most important) mstli.exe is using 80 to 98% CPU
any hints?
Lem0nHead said:
here's the story: my Tytn II was running fine for some months
one day I was travelling and need to use the GPS until there was just around 8% battery level
then everything started to get slow (GPS map couldn't even redraw)
ok, I though it was in some "slow-clock mode" to preserve battery
then I reseted it and, when I came synced it at home, ActiveSync said it couldn't sync (don't remember why) and it would have to send all the information again
but it was taking forever, so I stopped it and did it again later, when it said it was success
I then noticed my speed dial numbers had been lost, but that's not a big problem
the biggest problem here is that for the last 5 days my Tytn is slowing down very often (like 5 minutes after I reset it), even after I removed all startup programs!
What I'm noticing:
1) GPS maps doesn't redraw (I waited more than 2 minutes... it should take like 1 second)
2) Freecell cards are animating very slow after a completed level
3) touchscreen responsiveness is slow
4) I have TodayAgenda... after I change the date of a calendar item, it doesn't get displayed in the new day (just if I reboot)
5 and probably most important) mstli.exe is using 80 to 98% CPU
any hints?
Click to expand...
Click to collapse
What rom are u using? Sometimes its good to make a hardreset.
Mikulec said:
What rom are u using? Sometimes its good to make a hardreset.
Click to expand...
Click to collapse
I'm using L26
Since I didn't change anything else, not installing/uninstalling programs and so on, I don't like the hardreset idea (there's a lot of work to set everything back again )
Lem0nHead said:
I'm using L26
Since I didn't change anything else, not installing/uninstalling programs and so on, I don't like the hardreset idea (there's a lot of work to set everything back again )
Click to expand...
Click to collapse
There's often alot more work in diagnosing exactly what the cause is. If you haven't installed anything else then a hard reset (not a reflash) isn't to much work and it gives you the opportunity to progressively reinstal and test any additional software you do use. When you find the app that when installed or configured/used causes the slowdown, then you've found the culprit. Major slowdowns don't just happen out of the blue without changes to the software unless it's due to hardware failure and a hard reset will quickly pick up that sort of issue.
By all means wait to see if others with the same setup have experienced the same issue and if so what they did to solve it but I suspect you'd have it fixed sooner, going down the hard reset route.
Flying Kiwi said:
There's often alot more work in diagnosing exactly what the cause is. If you haven't installed anything else then a hard reset (not a reflash) isn't to much work and it gives you the opportunity to progressively reinstal and test any additional software you do use. When you find the app that when installed or configured/used causes the slowdown, then you've found the culprit. Major slowdowns don't just happen out of the blue without changes to the software unless it's due to hardware failure and a hard reset will quickly pick up that sort of issue.
By all means wait to see if others with the same setup have experienced the same issue and if so what they did to solve it but I suspect you'd have it fixed sooner, going down the hard reset route.
Click to expand...
Click to collapse
I couldnt say it better. I flash and hardreset my phone very often, its a little bit painfull but u will get used to it.
Do not be afraid of the hardreset.
just letting you know I remembered in this same day I had the battery problem, I changed a setting on IP Dashboard (configuring it to keep max 500 KBs history)
I now removed IP Dashboard the problem stopped
will try some other program later, or the old config
thanks
I've been using Incubus26Jc's Froyo v. 12 and My Vogue has been freezing over and over all the time. Seems not to be app specific, and seems to happen when its charging and when its on battery.
Any chance I've got a setting wrong? My guess is that my phone is dieing. Any advice?
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Is my situation the same? I'm running SagaROM Froyo Ultralite [v1.2.1, 7/28/10] and every time the screen goes to sleep and goes into lock mode, it reboots. What can I do to fix this? Please & thank you!
deltagamer said:
I've had this problem on the earlier versions, but now on release 12, I have only had 2 freezes... Sometimes you just have to let the phone sit. I guess it kinda gets overwhelmed and needs a little rest :/
Click to expand...
Click to collapse
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.
evilclosetmonkeynate said:
i have to agree my phone was doing this all day today, after using gps and apps heavy
rebooted a few times and let it sit for a while working much better now
Click to expand...
Click to collapse
Try going back to RLS10.5 with the 15-07-2010 version of Zimage. That eliminated the freezes for me. And it seems a lot faster.
Thanks @richardk3 ... I have the NBH, but I didn't save the 10.5 install file. Anyone have a link?
Update: Searching the forum didn't find it but a Google Search did: http://www.mediafire.com/?ond2tmmzolggtmm
If you search the main Froyo thread, incubus put up a link to the archive of recent releases.
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
This is pretty consistent across all builds in Eclair and Froyo. I've reached the point where I basically accept that this is always going to happen and I'll need to reboot. It's worth the trade-off, though, since this build is so amazing and Android is so much better than WinMo.
Johndixon, if you're running from nbh then you may need to clear the dalvik cache from the boot screen menu. Worked for me when the freezes came fast and furious.
jstrom23 said:
I went back to RLS10.5 and the 7/15 zImage per richardk3's suggestion. At first I did notice less freezing and overall better performance. But then I made a long call (over 5 min) with BT headset and the phone became unresponsive. BT and the call were still working fine, but the phone was unresponsive and had to be reset at the end of the call.
QUOTE]
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12, and a couple of zImages.
Other than this, it's super fast and stable... But it would be great to figure out what is causing the freezing.
Click to expand...
Click to collapse
eugene2007;7515857
I'm having the exact same problem... always becomes unresponsive at the end of the call when using Bluetooth. I've tried combinations of RLS10.5 and RLS12 said:
I'm having the same problem without using Bluetooth.
Can you gather the debugging info that DZO needs, as described here:
http://208.100.42.21/showthread.php?t=712310&page=180
Click to expand...
Click to collapse
Just as the title says. For example, if i set the time in android as the same of windows mobile and go to sleep, i am probably miss my bus-because after one night passes the clock will be nearly 12 min late.
Is there someone who could tell my how to solve this problem plz?
Lots of thanks.
icehust said:
Just as the title says. For example, if i set the time in android as the same of windows mobile and go to sleep, i am probably miss my bus-because after one night passes the clock will be nearly 12 min late.
Is there someone who could tell my how to solve this problem plz?
Lots of thanks.
Click to expand...
Click to collapse
Same here....
There is a problem with WinMo return from Android. My phone's hour is always incorrect. This is even after a hard reboot of the phone, even after pulling the battery. This does not happen with WinMo even if I set the time incorrectly and boot.
I know littlel of how our Android interacts with the phone's hardware. I have had a similar problem with Gparted. When trying to boot computer afterwards, the cmos was farklet and I needed to reset it.