Develop Bugs

Slow typing keyboard Black 2.5

Does anyone have a problem with a slow lagging keyboard while typing text messages. I noticed it after I installed the Black 2.5 rom. I have installed the keyboard mapping fix but that did not help the lagging issue.

I been typing like crazy today on my 8525/2.5 with MSN Live Messenger. Seems very fast to me..

I had the same delay...Can't remember if disabling the word completion took care of it or installing the memory performance cab from JJ that took care of it. I'm banking on the memory performance cab though.

I have noticed this issue a little bit, but if I remember correctly Ive had the problem even before isntalling any of the roms, and it only happened for the first set of characters that I types (usually the first word).
Has anyone else noticed this with the standard wm5 roms?

I've experienced the same issue.

I wonder if it was one of the patch cabs that I installed cause I have not seen a lag at all [yet]. Perhaps it is just waiting to pop up on me.

odie3 said:
I wonder if it was one of the patch cabs that I installed cause I have not seen a lag at all [yet]. Perhaps it is just waiting to pop up on me.
Click to expand...
Click to collapse
Are you talking about the pop up keyboard?
I think what the OP was taliking about is that when you first start typing with the pull out keyboard there is a slight lag, like with me, I'll start typing - it hesitates - and then it like catches up. Not only that but the screen even goes dim for a moment .
I don't remember if I had this issue before or not.

Nope, I was talking about the pull out keyboard. Seems to work very well so far. I just retested it in Work and in MSN IM.

odie3;1250895 said:
Nope, I was talking about the pull out keyboard. Seems to work very well so far. I just retested it in Work and in MSN IM.
Click to expand...
Click to collapse
Oh well.
I'm not going to concern myself too much with it, because I'm hoping by tomorrow I'll be running 3.0

Similiar typing issue here on 8525
I've noticed the same typing issue using both Black 1.2 and Black 2.5 were it often lags or simply skips a letter (usually "h" after "t" leaving "te" instead of "the" or "s" after "i" leaving "I" instead of "is")
I tried uninstalling and reinstalling the 8525 keyboard fix cab, but it does not help.
Two things I have noticed:
1.) The typing problem does not seem to appear until several days after I flash the ROM.
2.) It really only seems to affect the Messaging app. (When I type into PIE forms or Notes, the problem does not seem to exist)
Definitely did not have this problem in WM5, so I am hoping that the problem will be gone in Black 3.0

this is a real problem. I have experienced it with all wm6 roms I have installed. I have a strong feeling its related to the suggested word list that comes up....but this is a rediculous problem for us to have to deal with and should be fixed. I also agree that its limited to the messaging app.
Ezra

yes the problem i was originally talking about is with the messaging app only. i have no problems in word, or IE. I have the memory performance cab installed but noticed it before that as well. does anyone see a difference with the suggestive words disabled?

Put 3.0 on Hold
njmarchetti said:
...clip...I am hoping that the problem will be gone in Black 3.0
Click to expand...
Click to collapse
I'll PM JJ and ask him to hold off on the release of 3.0 until he's sure we won't have this issue.
Just Kidding. .

I actually started a thread about this a while ago but titled it in reference to skipping keys because I type so fast with the thumb keyboard that the device cannot keep up and omits some of my key-presses. However, someone suggested something that I had tried with WM5 (but it didn't work then) but hadn't thought to do with WM6.
Go to Settings>Input>Word Completion(tab) and change the "Suggest after entering" setting to something such as 3 or more letters. I have mine set to 4 letters and have zero problems with skipping or slow typing unless in a third party program such a TomTom.

a little out of topic...
but after changing to black 2.5 my time zone seems to be weird....i had tried to set it to GMT+8 Singapore time....but after a while it will change to another country thats GMT+8 but when i change it back to GMT+8 Singapore time.....it will be one hour early.....

I have the slow keyboard problem too.. Its making me mad.. And the black2.5 rom seems to slow down a heck of allot after a week or so use.. Any ideas why would this be aswell?? I only have 4apps installed.. One on today screen and rest only when i use it..

a slow keyboard is one thing, but skipping letters is another. (This issue pertains to not only Black, but also Custel, LVSW, and Dutty)
The thing is, when i text message, i start typing immediately after the window pops up. But for some reason, it lags, and then when it catches up i notice that my first 3 words are so are all butchered cuz letters were dropped. I didn't experience this issue with my MDA Vario / 8125. The worst that would happen is the text would lag, but would eventually catch up to my typing. And it WOULD NOT drop any letters. With the new wm6 roms for hermes, im noticing lag and letter dropping. I've tried the suggestion of even turning off autocomplete, and setting 1 word, 2 words, 3 words, and 4 words. Still having the same issue. I opened a thread about it long ago, but it just got closed because they "supposedly" deemed it a fixe issue. Well its not!
To clarify: I'm not trying to bash any of the rom chefs' work, as i am very thankful for what they do. But it would be very nice to have this issue addressed and fixed.

Has anyone tried changing the Up/Down Control repeats....
Settings/Buttons/Up Down Control?
I put mine up to max, and seems to have fixed my problem....

@ **Milo**
Hi and thanks for the sugestion , i tried it and my slow typing issue has gone. As an experiment i switched the rate back to where it was (about one third of the way up the slider) and its still gone. It seems switching the slider up to max cleared whatever setting was causing the slow down.
Im going to leave the phone on standby for a while then try it again to see if this has any effect on it.

*MILO* said:
Has anyone tried changing the Up/Down Control repeats....
Settings/Buttons/Up Down Control?
I put mine up to max, and seems to have fixed my problem....
Click to expand...
Click to collapse
And it seems to have cured mine too. Thanks mate.

Schap's 3.60a crash after phone call!!!

it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?

iluvgillgill said:
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
Click to expand...
Click to collapse
I use this rom with 1.51 radio till the rom is issued. I never had to soft reset because the rom crashed. The only really annoying issue i had is the bluetooth's one (Time to time, it is impossible to reactivate bluetooth without SR. This is why i do not desactivate it anymore ). We can always argue on choices, taste and colors but this rom is quite stable and fast enough for what i do.
EDIT: BTW check also which applications you have loaded. Did you reinstall a backup done with SPB after coming from another rom? I experienced many problems with that. Even if not pretty, i always reinstall now all my applications after installing a new rom (and i use pimbackup for calendar, contacts,... infos)

I have same problem too, thx

Post in Schaps 3.60 thread...

Not so as you think
I don't agree with that the ROM issue after call. Your deveice may be has some problem. What about bluetooth yes, there is some interesting moment that you select open bluetooth, it doesn't open, as soon as you mark to open you should restart your deveice, then it starts with opened bluetooth. BUt when you are going to turn the bluetooth off there is no problem.
I'm sure, Schap as a great moderator will solve this problems in next generation of his ROMs. The variation 3.60a (has posted), may be 3.60b, then 3.60c may be. Or he will post something interesting like Iphone platform.(I want him to do it)

iluvgillgill said:
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
Click to expand...
Click to collapse
I have the same problem too, what I have discover is that during the call and the screen is off (either it off automatically after a time or you press the power button) then anytime you power on the screen again in between the call or after the call in a short time the problem tiggered.
the only way you can 'fix' it is to wait until call end then off and on your screen once then the 'start menu' back or wait for an amount of time until the phone lock tigger (that one with number pad)
I said 'fix' (with quote) because this definitely a temporary solution to deal with this problem
hope schaps can get more idea in how to trigger the problem and can fix this soon
other than this issue, the rom is really very great
cheers.

To the OP,
If you are using a Hermes I suggest you reflash from scratch ie Schaps ver 3.6 rom, then use radio rom version 1.47.10..
Install ALL your applications from scratch, manually. DO NOT restore from a previous backup using, say SPB Backup; that will screw your installation. Make sure all your apps are the latest versions, capable of running under WM6.
Preferably install one app at a time, as you would anyway, then test the phone and make sure it is working before installing another app, and so on.
Don't install a theme changer or other similar software until you are absolutely sure your installation works. Leave the performance parameter settings as they are, ie at default.
If all else fails use the ROM combination in my signature below. Rock solid installation, no problems or crashes.
Let us know how you get on.
Cheers
WB

have same problem also has anybody found that if you use internet shearing and recive a call you cant hear anyone and phone searches for network
thankz,
jdc21

no crashing for me..
the rom is really stable.
apart from the bluetooth issue its really good..
really stable and fast enough..
works really great for me..
Thanks Schaps for such a great rom.
waiting for 3.60b

Take care that Phone Dialer Skin could cause this kind of problem

wacky.banana Is maybe right
I have Schap's 3.60a along with my trusty Radio 1.47.10
No BT Issue till now
I use BT also with DrYAR-Bluetooth 1.6 (Whoopy!) No Issues at all either starting or Stopping BT
I'm using It for two days now It's OK
Did I mention that this rom Is even FASTER than the previous 3.5x?

i hav the same problem

When did this problem start?

I didnt have the bluetooth turn on just using it normally.and all application i install is fresh onto the phone memory.never install any program on the SD card.about the dialer skin i use Schen Kaiser 3G dialer.
Anyone got fix yet?

Same issue, not just Schap 3.60a
massimo729 said:
When did this problem start?
Click to expand...
Click to collapse
I've had this same issue for weeks now, ever since the newer ROMs have come out for the official releases (i'll have to track back the build numbers). I had it with Sleuth's last release, the vp3G 3.0 release, and now Schap's 3.60. I've done what other posters have said and hard reset, not loaded any apps, and still have the issue.
I believe I have tracked it down to do with X-button, as that's one of the few apps that is installed without customizations in both Sleuth and vp3G (and I run it in Schap 3.60a). My next step is to run vp3G 3.60 lite, without X-button, and see if that really solves my problem.

edwinyuen said:
I've had this same issue for weeks now, ever since the newer ROMs have come out for the official releases (i'll have to track back the build numbers). I had it with Sleuth's last release, the vp3G 3.0 release, and now Schap's 3.60. I've done what other posters have said and hard reset, not loaded any apps, and still have the issue.
I believe I have tracked it down to do with X-button, as that's one of the few apps that is installed without customizations in both Sleuth and vp3G (and I run it in Schap 3.60a). My next step is to run vp3G 3.60 lite, without X-button, and see if that really solves my problem.
Click to expand...
Click to collapse
As a follow-up, I went to VP3G 3.60.1 install, ran the base install with nothing else installed and still had the problem. Still, the workaround suggested by others (putting the phone in standby and coming out) fixes the issue for me.

Strange lockup

Ok guys, I need some help here. I've been using multiple roms for a long time now but I have a problem with a very strange lockup.
When I change the alarm clock time under 'clocks & alarms', using the analog clock, and I press OK to accept the new time the interface locks up. I've to soft reset to get it active again. But I can also hold the power button to do a cold reset, which actually gives me the Warning pupup asking me to continue, which is strange as the interface seems to have locked up completely.
Something which happens occasionally is that when I press OK to accept the new alarm time all the background processes pop up really quick, like alt tabbing really quick, before a lockup.
This happens randomly, but ususally once my TyTN has had some uptime.
I always flash the official TyTN ROM (without radio) before flasing a new custom rom and I prefer not to use any RBS roms.

ok can you tell me what ROM are you experiencing this issue with

I've had these problems with almost all WM6.1 roms and am currently running CRCs Release 13.0 - Stable Thread (Build 20270) and I will keep this one for now.
I've also seen this behavior with:
All pervious CRCs roms (development and stable), all PDACornerPro roms up to V22, some pdaviet roms (I've not tried all) and some other roms.

Thats odd, I cant reproduce it (On CRCv13), do you have anything else installed that might be causing any kinda conflict?

Not that I can think off right now, the only item that comes close is HomeScreen PlusPlus.
Anyway, the list of software I always have installed:
ClearTemp
Chi-Tai Dang HomeScreen PlusPlus
J.S. Advanced Configuration Tool
Nav N Go iGO 8
Total Commander
I've also installed other software when using roms but that's always different. I like pure and clean roms for speed
Another point of interest, my TyTN was bricked beyond repair a few weeks ago but I got full warranty and they replaced my device, so I'm running on different hardware than before.

Maldune said:
Not that I can think off right now, the only item that comes close is HomeScreen PlusPlus.
Anyway, the list of software I always have installed:
ClearTemp
Chi-Tai Dang HomeScreen PlusPlus
J.S. Advanced Configuration Tool
Nav N Go iGO 8
Total Commander
I've also installed other software when using roms but that's always different. I like pure and clean roms for speed
Another point of interest, my TyTN was bricked beyond repair a few weeks ago but I got full warranty and they replaced my device, so I'm running on different hardware than before.
Click to expand...
Click to collapse
I think the place to start is hard reset and see if you get the same error without installing anything.
Then work though, one program at a time, and find out what seems to be doing it.
Has this only started happing post getting the new phone? It would surprise me if it was a hardware issue though.

Nah, this also happened with my old TyTN. I was thinking about a hard reset and then letting it run for a while as you just suggested, so I'll do that now.

Problem with TF3D

Hi all,
First I have to say that I'm over the moon with my new TP2!!
I absolutely love it
Today I started customizing it, and I've got one problem.
No matter what task bar I'm installing, after soft reset TF3D won't start.
It just shows HTC, and nothing happens.
At this moment I have the stock Dutch rom that ships with the TP2.
I installed sdkcerts.
Anyone experiencing the same thing??
H.

sorry wrong thread

TF3D
Hi there,
I've had the same issue with my UK spec, a reboot often cures it but it is a bit lame when the software wont even start up.
So far this has only happened to me about 3 times but I have been playing with it immensly and have rebooted it about 20 times already whilst cocking up some Shat Nav software.
Still loving it in general though ;-)

I'm having the same problem, rebooting doesn't solve anything.
A hard reset does, but than I have to reinstall everyting.
Manually starting manila.exe is an option, unfortunately than the time isn't updated.
Anybody has a sollution for this?

My solution was:
1. Go to: Start > Settings > first tab and click on Today > Go to Items Tab.
2. Uncheck TouchFLO 3d and click OK.
3. Do step 1 and 2 agian but then Check TouchFLO 3D.
4. Soft reset.
Done

tried that but it didn't work for me.
Just removed TomTom 7 & SPB Backup and now it seems to start up fine....
That's a bit of a shame, because TomTom and backup are very helpfull apps...

ive had similar issues but only when trying to customise manila theme. kept saying launching touchflo but nothing happens and then reverts to saying tap here to launch manila. if any of the programs you are adding or any of the customisations you are making involve messing with manila then you will have issues! once hard spl is out then all these things wont be an issue any more.

same problem here, don't try to change startmenu things (standaard startmenu/small startmenu, extra rows etc).
If I enable the extra program tab the buttons won't work most of the time.
The stability of the TP2 is not so good yet, hope that there will be a fix or update for it or a very good custom rom from a good chef.

me 2
I have experienced it twice. I got TF running again by unchecking TF3d in the items screen of the today settings, shutting the TP2 down by pressing the on/of switch some seconds, then restarting ,rechecking TF3D and shutting down once more. This has the same effect as a soft reset, only the system is disconnected longer. So perhaps taking the battery out works as well.

I think this problem is there because TF3D is so much integrated in WM 6.1. So the chance of apps interfering with it is pretty big. I hope with WM 6.5, they remove the big menus's (since they are there already in WM 6.5) and other stuff. Just to get more memmory back, and to make TF3D more compatible with other apps. (still waiting for my TP2)

Error no longer happens
Hi Guys,
I found out that mine was being affected by an old copy of IGO 8 that I was trying to install, since I've upgraded to the new version the TF3D issue has completely vanished.
I noticed that when the TF3D failed it was after a period of low memory or high CPU useage, perhaps using some software that isnt compatible with the TP2 is causing TF3D to screw up.
it's just a theory at the mo... can anyone else share their experiences?

Guys,
this is the third thread about this subject. I have the same problem. HTC is not aware about this problem and encourages those who HAVE these issues to call them. Calling is free...
please do so in order to get rid if this massive bug!

I have been doing some investigation of my own on this one.
I have SPB Backup installed which reboots my phone every night and found that TF3D would not start. Even after a few reboots it would not start. Removed it tried again still an issue.
Hard reset and still was getting some issues.
After alot of rebooting etc I found that if you have a pin enabled on your SIM card TF3D has issues on startup.
No PIN and all is fine.
With that in mind I have just left the phone lock on for now until a fix is found for the bug by HTC

hi, please contact HTC with your findings. if they dont know, they cant fix. calling is free.
thought i disabled my PIN and the problem still persists. although i had a "loading..." once. but it didnt load...

I have contacted HTC about this. I am awaiting a reply from them about the issue.

I had the same problem when installing the .cab to remove the bottom curtain. Soft resets, unchecking and checking TouchFlo3D didn't work. I then reinstalled the .cab and the TouchFlo3D also came back.
Perhaps that will work for you too? Try reinstalling the last program after the problems has occured?

I have the same problem, and i did notice that after uninstalling an application it usually works again. The strange this is that it looks like it is not a specific application that I need to uninstall. It could be a cab for a different clock or tab icons or an g-sensor app, or probably any other app.
Strange .....

Hmz, I soft resetted my TP2 and found out that the TF3D again didn't start. Had to re-install the "Bottom Curtain Remover.cab", soft reset and then it started again.
Looks like ahlung has a point in saying that it doesn't look like it's a specific application that needs to be uninstalled / reinstalled.

It can also be affected by file read errors, including files on the SD Card, if you have corrupt files on the SD Card, this can cause TF to not launch and even lock the device.
Cheers,
Beasty

Same problem here!
I also contacted HTC and told them the issue. They suggested me to do a hard reset! If I couldn't think to do it by myself!

Am I the only one who has touch-screen problems with the vogue on/off? Seriously..

I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..

mine is unresponsive sometimes and i have to tap on the back of the phone to get to work again. i thinks its going out soon

That's what I thought about my old one, I figured I had dropped it to much.. because I did lol but now I got a new one 2 weeks old and I'm running into the SAME problems.. I'm assuming I must be doing something wrong with how I've got **** set-up

j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
j18yo i think that your problem might be that to many programs run when you start your vogue that happened to me before and i hated it but then i heard of a program named "Space Reclaimer" FREE and it made my vogue much more responsive because the program stops any programs that start when you turn on your vogue or any windows mobile phone

I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.

j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
What ROM are you running? I asume that wehn your new device came you loaded it the same as the old one. It has to be something with the ROM you are runnning or a problem with a program causing your issue.

My phone would do this periodically too, with Vin's latest ROMs. I turned off Manila and am running Titanium now. Interestingly - no lags when unlocking since. I'll keep Titanium on for some time to see if that makes it go away. I had an issue with both his current v2 and v4 (which I am running now).

Ive had to replace my screen twice and the whole phone once because of touch screen problems. Thank God for the insurance.

Ah yes... to what OP mentioned:
I do not beleive it is a more pressure thing. I do not think it is more pressure that is required but rather that the phone is non responsive. If you are unlocking and typing a PIN, it takes the PIN and all but it takes perhaps one digit every 5 seconds. That's my experience anyway. So it is just slower, as if something was consuming the CPU and UI is not responsive.

crazylegs91 said:
I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.
Click to expand...
Click to collapse
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans

j18yo said:
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans
Click to expand...
Click to collapse
Update: I don't think CR erases things as much as it kills processes that won't restart. Thru trial and error, I've adjusted my CleanRAM settings to where I haven't had the problem for a couple of days. I'm able to do a Level 3 cleans on a once a night schedule and during the day if need be. In settings, I have it to close all apps, launch startup progs, and display today screen. I have no exceptions listed for either running progs or startup progs. I have the most up to date version from the OTA update in the program.
The program links in my StartUp folder are: poutlook (original on ROM), sddaemon (original on ROM), WLMUpdate (original on ROM), Glossybars.exe (I added this), biotouch.exe (I added as I thought CR killing this was the source of the problem), pocketwit.exe (I added), and SIPChange (I added).
One thing I did do was delete the link for TouchPal from the Startup folder. I did this for other reasons (I use FingerKeyBoard). Not sure if this was part of the problem.
I can scroll with d-pad and no touch lag.
On a side note, can I delete any of poutlook, sddaemon, or WLMUpdate from the startup folder to save battery power?
I'm probably just a bit above a newb so sorry if I don't make sense.
Update: Just for kicks, I deleted the links for glossybars.exe and pocketwit.exe from my StartUp and it started locking again after running CleanRAM. I put them back in and it works again even after running CleanRAM. Maybe someone with more knowledge can explain this. I'm just keeping it the way it is now...

Hmm weird that you removed something not very important like pocketwit an cleanram caused problems again.. someone has to have some info on this??
I deleted everything from my StartUp folder but my SPB Mobile Shell.. I didn't have sddaemon, but I did have poutlook and WLMUpdate both of which I deleted.. then I had some other programs that aren't necessary for the phone.. I have no problems on restart or anything, and the % showed being used is stays around the 30's now instead of 40s/50s.. and when I run programs it usually reachs 50% tops now instead of 60/70% I used to get.
PS: Pocketwit isnt bad I used to praise the program but now I've tried MoTweets and.. I can't think of the other one now.. ****.. it's really good though but it seems to use a lot more phone power than MoTweets so I went back to that.
Pocketwit kept giving me problems, started saying I need to install that NET 3.5 or whatever but when I try to it says I have a later version already so it won't install, then other times it'll work completely fine.. but MoTweets I like better anyways

Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.

crazylegs91 said:
Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.
Click to expand...
Click to collapse
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...

bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm running a stock Sprint 6.1 ROM. Thanks though.

bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm not using the TouchFLO interface, does that mean its still on though?
I'm not completely up on understanding all this

This was happening with Vin's Rom for me as well. I was tripping out pressing ON so many times with no screen showing up but phone light on! I believe it could be the power settings. I disabled the "Turn off device" which I believe was mentioned in his notes about the rom.

I gave up on this problem for a while but found something when researching how to disable to cube. I used the registry edit in this thread to disable to cube post #69. I didn't do any of the other steps because I'm not having memory probs (42% with pocketwit in the bckgrd).
http://forum.xda-developers.com/showthread.php?t=368269&page=7
I noticed that biotouch.exe never shows up in the running processes menu in CleanRAM and I don't have the "lock/freeze" scrolling problem any longer and I can run CleanRam without the problem occurring. I can press any item on the screen as well with no delayed response.
However, this stops you from being able to finger scroll and do the "side to side" scroll in Messaging. I never really finger scrolled and prefer using the d-pad for scrolling so losing that functionality isn't a big deal to me.
If anyone can figure out how to keep this working so smooth and have the option to finger scroll, I'd be much obliged. It just seems that biotouch.exe craps out sometimes and locks up the d-pad. If they could both work equally well....