Hey guys,
I've had CM 7.2 Stable for a couple weeks on my phone. It was
working great until a few days ago when I tried to tweak the CPU
settings a little. Right now i'm using
Governor Smartass V2- Min 352 MHz, Max- 691 MHz
What CPU settings are you all using with CM 7.2???
Since I tweaked it from the default cpu settings I've been
experiencing screen freezes. Sometimes the trackball will work
sometimes it won't. It primarly happens when my phone has been
sitting idle for some time. I'll try to get it out of the lock screen
but it won't respond to my touch. I've tried rebooting, battery pull,
I've also tried lowering and raising the min and max settings. It'll
work periodically and then it will just freeze. Funny thing is I
don't know what the "default cpu settings" were set at. I've been
looking around a lot but couldn't find much.
Thanks!
I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2
kjjjjshab said:
I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot for the input. I'll try to go back to On Demand. If that doesn't work then maybe I'll just re-flash the ROM.
Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE
laie1472 said:
Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
Hi-
I looked at my list of apps to be sure and no extra overclocking app installed. I'm using the default "CyanogenMod Settings" to get to "Performance" and setting the cpu from there. I have not installed any extra lock screen apps or 'lock screen security app' other than what comes preinstalled on CM 7.2. I don't believe I have any app that effects the lock screen. All of the apps I have are fairly simple, mostly developed by google inc. and nothing that tweaks or alters the device (I have Maps, a Speedometer, Navigation.) I try to keep them all closed though with the Task Killer app I downloaded.
I have switched back to OnDemand. So far nothing has changed and it's still stalling up (even though it's only been about an hour.)
Thanks a lot.
Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE
Update
laie1472 said:
Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.
That worked for ONE day
brentmxt said:
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.
Click to expand...
Click to collapse
So that was short lived. Once I did the Full wipe around noon it worked almost perfectly until for about 12 hours. I think it froze right before I went to bed. I woke up and it was completely frozen at lock screen again. I did another full wipe and reinstalled cm 7.2 and it froze again. So I did a second full wipe and it is now working. I really hope it will accept my nandroid backup if it freezes again because it's A LOT quicker. Than doing a full wipe.
Hope this helps anybody who goes through the same thing.
Related
I DL the app from the market. It installs. When I try to run it, it hangs on I/O database writes. Waiting does not produce FC it just sits there (in excess of 5 mins waiting)
Stats:
CM7 RC4
Overclock Kernel 600/1100 (Tried 300/800 no diff)
SD speed boost at 2048 (pny 4g)
Any help is appreciated.
Are you using the most recent OC kernel? There was a problem with one of the older ones. You want to wipe dalvik-cache after flashing a new OC kernel.
Thanks, I have only downloaded 1, it was dated3/31.
Is it ok to wipe dev cache and regular cache with root explorer?
Allsack said:
Is it ok to wipe dev cache and regular cache with root explorer?
Click to expand...
Click to collapse
As far as I know, yes. Your system may freeze after clearing Dalvik-cache, it's a known bug. Just hold down the pwr-button till the nook turns off. Reboot, and you should be good to go.
This is mostly for anyone who runs kifno's rocksteady ROM, along with his scripts. Essentially, I am not sure how to install both of them together properly. It seems the instructions kind of overlap? And I do not want to wipe anything at the improper time. So if someone could edit these instructions so I could follow them in sequence, I would be grateful. If it makes a difference, I will be flashing the uncapped kernel (768mhz).
P.S. - I've been running xda roms for about a year now, and just wanted to say thank you for all your hard work and contributions to the open-source community. To ALL developers
ROM INSTRUCTIONS
Instructions:
1. Backup EVERYTHING (SD Card, Titanium Backup, Nandroid)
2. Wipe EVERYTHING (Data/Factory Rest, Wipe Cache, Format Boot, System, Cache, and Data, Wipe Dalvik)
3. Download and Copy RockSteady & Gapps to your sdcard
Get Rock Steady Here
Get Gapps Here
4. Flash RockSteady and Gapps and Reboot
5. Skips gapps setup and reboot into recovery and wipe data, cache, and dalvik again
6. reboot into system
7. After setting up gapps, in the menu > sense settings > ui setting > check tink ab and make the scale factor 1 instead of 7
8. Long press home screen and create a custom widget with phone as the activity. Then click the phone icon and us es file explorer or gallery and use the transparent.png I provided for you on the root of your SD card. Okay the custom widget and the drag and drop it over the phone button. Do the same for right sense dock button (choose a custom activity of your choice)
9. Add the sense clock by using the fancy widget widget i provided for you.
10. Choose a new wallpaper if you wish by picking one of the sense wallpapers I provided for you on your sdcard's root directory.
11. Please see here about widgetlocker. Please purchase this app from the market to use as the sense lockscreen. I REALLY RECOMMEND IT. And you can easily disable the default lockscreen once you start using this app by going into the cyanogenmod settings > tablet settings > and checking disable lockscreen.
SCRIPT INSTRUCTIONS
Installing Instructions (Recovery Menu):
Difficulty: Easy
Download the Kifno Tweak's Universal Script v1.5 from below:
Get the Capped 691mhz Build Here
Get the Uncapped 768mhz Build Here
Charge phone to 100% and leave on the charger during this process
Put the .zip on the root of your sd card
Reboot into recovery
Backup Everything (Apps, SD Card, etc) & Wipe Everything (Data, Sd-Ext, Cache, System, Boot, Dalvik-Cache)
Flash Rom
Fix permissions if using clockwork recovery
Flash your capped or uncapped build
Delete data, cache, and dalvik
Reboot
Reboot Recovery
Delete data, cache, and dalvik
Unplug Charger and do not plug back in until your phone dies.
Reboot into recovery once it is dead by connecting charger.
Wipe battery stats
Charge to 100% and repeat the discharging, wiping, and charging process about 3-5 times
Enjoy the battery life and performance
The red is the confusing part. Thanks!
Ill post instructions in about an hour or two. Glad to see you're using my work though and sorry for the confusion.
Sent from my HERO200 using XDA Premium App
The Muiu Camera Doesnt Work :[
backup everything
wipe everything
flash rom
flash gapps
flash v1.5 stable
reboot into rom
skip gapps and reboot recovery
wipe data,cache, and dalvik
reboot into rom
then follow my set up instructions for my rom after that process
enjoy
also miui camera works on 4-21-11 it does. are you using the latest version?
Yes I amm
Sent from my HERO200 using XDA App
Jurellz said:
Yes I amm
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Oh sorry didn't see your reply but try the latest one now
My touchpad just crashed while using the stock browser. I'm not overclocked, but I'm using the cm nightlies. The screen just turned black and rebooted. Is it most likely a software issue?
Same thing it happens to me a lot. Idk why, can someone shed light on this one. Thanks.
Sent from my cm_tenderloin using XDA Premium App HP TouchDroid
Boot in Clockwork
* Wipe cache partition
* Advanced -> wipe dalvik cache
* Fix permissions
Reboot
Sometimes, it needs to be done two times
Poussun said:
Boot in Clockwork
* Wipe cache partition
* Advanced -> wipe dalvik cache
* Fix permissions
Reboot
Sometimes, it needs to be done two times
Click to expand...
Click to collapse
Thanks added, Just followed your instructions and my TOUCHPAD its like a new machine no longer freezing/locking up .
Thanks again.
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.
BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).
kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app
You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.
This is to at least avoid the need to boot into CWM recovery every time
Reason:
I immediately flashed my brand new Nook HD+ with the emmc CM 10.1 three weeks ago
The vanilla CM booted in 90 seconds but that was 350 app installs ago and many uninstalls and app updates as well
If I power on the HD+ seem to always get stuck in the boot loop of the CM Logo; I wait up to 10 minutes
It seems booting into CWM recovery via N button on Power on and choosing wipe dalvik-cache allows a rebuild of dalvik-cache for the 350 apps followed by normal boot into CM 10.2
Besides the long delay is there any harm in wiping Dalvik-Cache every time I reboot or poweron?
I believe only this method and CM safe mode are the only way I know to avoid bootloops
Do I need to modify Dalvik-Cache settings/properties to fix bootloops? If not can I automate/ default into the Dalvik-Cache wipe for each poweron / reboot
BTW reason I rebooted a few times is I am still trying to struggling getting USB OTG / USB host mode working
Should I turn off USB debugging if I can not use USB OTG and I also do not use ADB?
TIA
Dave
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Help with automating the Dalvik-Cache wipe
Thanks for the reply Leapinlar!
When I am booting into in CWM recovery and choose the Dalvik-Cache wipe is it wiping out both /data/dalvik-cache and /cache/dalvik-cache?
How long do I realistically need to wait before I can determine I am in a bootloop situation? I do wait 10 minutes but maybe less time?
Does CM 10.1 boot time dramatically increase over time or does adding apps also increase the boot time ?
I found a script on: http://smanager.wikidot.com/scripts:power-scripts[/U "Superclean and reboot "
As a newbie I would like to know which file or directory to put a subset of this script so that it automaticly runs when I poweroff or reboot via the power button even better would be how to add a popup question box asking me if I want to wipe out dalvik-cache as part of the shutdown.
TIA
Dave
leapinlar said:
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
safe mode on CM 10.1
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
leapinlar said:
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
[email protected] said:
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
Click to expand...
Click to collapse
Huh! That is a new one for me. LOL. Thanks.
If it boots faster in that mode, that tells me you have too many apps.
Sent from my Nook HD+ running CM10.1 on emmc.
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Will try disable 'quick render' in the launcher settings.
Aaron thanks for the info * I will see if helps my bootloop issue
I went to Trebuchet settings to uncheck 'quick render' in the Homescreen panel
TIA
Dave
Solution: quick & dirty automating the Dalvik-Cache wipe
Thanks to Leapinlar for great explanations and patience and
Kudos to Bartito for his Shutdown APK!
Just tested the instructions below on HD+ CM 10.1
Leapinlar can you please verify the commands before other users try this as I am still a Newbie to CM
after following these instructions I powered on the HD+ and the dalvik-cache rebuilt 268 APKs without needing to boot into CWM recovery
This will continue for every poweron and reboot until the script /system/etc/shut.d/rmdalvikdata is removed
The boot process is obviously delayed significantly but hopefully no more bootloops!
1) launch terminal emulator app and type these commands from the terminal:
su
mount -o rw,remount /system
mkdir /system/etc/shut.d
chmod 755 /system/etc/shut.d
echo "rm /data/dalvik-cache/*" > /system/etc/shut.d/rmdalvikdata
chmod 777 /system/etc/shut.d/rmdalvikdata
ln -s /system/etc/shut.d /system/etc/shutdown
exit
exit
2) please, download the "SystemScriptsExecutor-cwminstaller.zip"
from: http://forum.xda-developers.com/showthread.php?t=1387692
Note: I saved it the zip file to the MicroSdXc card
3)install SystemScriptsExecutor-cwminstaller.zip from CWM recovery on Nook HD Plus.
Note: I actually used vi on term with a USB keyboard to create /system/etc/shut.d/rmdalvikdata
and I am not sure the symlink is necessary
It looks correct. And I would leave the symlink in. The Executer may need it.
Sent from my Nook HD+ running CM10.1 on emmc.
I saw the same problem on cm-10.1.3-RC2-ovation: "wallpaper quick render" enabled causes bootup to stall on the animated logo. Clearing cache was the only way to complete with it enabled. Disabling restores the ability to boot and reboot normally.
It's a devious bug as you might only run into it days after enabling the feature. In my case, it was a few days after a fresh CM installation, having setup and installed everything the way I wanted. adb logcat didn't show anything obvious within the boot loop. I spent a while building the installation back from scratch with incremental nandroid backups attempting to find the point where things broke. Glad I found this thread instead!
It'd be nice to have it fixed as quick render makes scrolling between home pages noticeably smoother.
Aaron Camp said:
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Click to expand...
Click to collapse
Thank you sir! I have struggled with this and your suggestion seems to have cured the problem. I have spread the word in 2 other threads.
Wish the developer would see this. Then, perhaps, a fix might be in the future.