Develop Bugs

(start menu?) Program menu keeps whiting out. help

Need some advice. My program menu on my xda keeps whiting out.
On an initial start (or after editing the program list) the program list (or start menu) displays fine.
On the 2nd click some icons start doubling up at the bottom and fill the screen.
The on the 3rd click it goes off the bottom of the screen and goes completely white!
What gives? I've editing the number of items, looking in the registry at start menu opetions, deleting programs, but nothing solves it.
Performance etc not hampered but its really annoying. It MIGHT have started after installing a c++ cube program launcher (not sure).
if anyone has ideas to fix it please let me know.
TIA Sean

Hey I just had that exact same issue earlier. I was editing my \Windows\start Menu\Programs folder and making some adjustments when i noticed it happening. I kinda narrowed it down to being something to do with HButton. I was fiddling with the Hbutton display options just after modifying the programs folder. After more fiddling with the HButton display (changing colour and position) and a soft reset, my Start menu started working fine again and I havent had any problems with it again so far.
Probably nothing at all to do with it but thats what seems to have fixed mine as i didnt touch anything else but HButton and it is now resolved.
hope this helps in some way
[EDIT] completely ignore what I just put above, its just happeed again. The only thing I have done this time is Activesync and install a game. Kinda thinking it has something to do with Activesync now.......

lol oh well i guess i'll have to put up with it for now then. half a mind to send it back to O2 but its a software bug, I'll get the problem on the next phone as well.

Try to see in Memory the program values.
In my experience when tou have few program memory, start and today redrow is very difficult.
It happened me some times ago when i tryed a rom with problems of memory allocation.
You can try another rom (today you have many chose )

bigix1 said:
You can try another rom (today you have many chose )
Click to expand...
Click to collapse
Well considering my phone is one a month old I dont think I'll be flashing the rom JUST yet.
And update: for some reason the start menu is back to normal behavior! Absolutely no idea why. Just when i was getting used to it as well.

Tilt 2 Clock issue?

Just received my phone today. I toyed around with the phone and I noticed everytime I select something : task manager, program, volume. When the phone returns to the home screen the clock shows a time of 6:24 then it flips to the correct time. I had the Original Tilt and have never used Touchflo 3D. Is this the norm? It was cute the first time now it's aggrevating.
PS- I'm running stock rom.

Yep it's my location time running behind your normal clock.

I noticed the same thing too. The clock appears to start an hour behind and then flips to the correct time.
Its slightly annoying. =/
Happens on the stock AT&T rom. Don't know if it happens on other ROMs.

Neo.magic said:
Yep it's my location time running behind your normal clock.
Click to expand...
Click to collapse
Ok you lost me. Can you explain?

Actually, mine starts 1:02:00 behind, then it switches to my current time. So I see the hour flip once and the minute flip twice. If you want to recreate this, just tap the notifications up top, close them, and then you'll see the time change. It's as if ATT wanted the clock to flip once when changing focus to it...

im using the tilt with a cooked rom and i have the same "issue. mildly annoying; would be nice to get rid of it

Unfortunately, it's working as designed. I believe it's supposed to be a "coolness" feature of the clock flipping everytime you go to the page.

I'm not sure I agree - you can see the behavior with the digital clock on device lock as well. There, it's not so cool. It really looks like it's doing something wrong.
Anyone know where to set 'my location' if you've gotten rid of TF3D?

me too
I noticed that the first day I got it on the Wednesday. I agree it is annoying and would like to prevent it if possible. I will keep looking to see if anyone comes up with a fix.
The other thing that I have noticed is that the SMS and or Email will just pop up for no apparent reason. I have it set to check my Email accounts every 15 minutes but I dont think it is on that time frame. It seems fairly random. Let me know if anyone else has noticed this that way I can see if it is something I have installed causing the problem.
Thanks, Kevin

Subscribed

It's the Time Zone Auto Fix package that is causing it...Just the way HTC is keeping your time accurate. Try disabling auto time check.

BG4 all also fixes it
Background For All includes a couple of flip clocks (clear and white) and also "fixes" this behavior. http://forum.xda-developers.com/showthread.php?t=572166

At0mAng said:
It's the Time Zone Auto Fix package that is causing it...Just the way HTC is keeping your time accurate. Try disabling auto time check.
Click to expand...
Click to collapse
Where is that setting at?

At0mAng said:
It's the Time Zone Auto Fix package that is causing it...Just the way HTC is keeping your time accurate. Try disabling auto time check.
Click to expand...
Click to collapse
Assuming you meant the settings under 'Phone', this had no effect for me. Still flips. Going to try the Background 4 All & Flip Clock next. Thanks

The time between what's first shown and what it is flipped to / skipped to is about 75 minutes apart (I caught it enough times to see it happen). It's a very odd time to be off / different...

I've got this issue too, and I'm running the stock att rom for now. I agree, very irritating. I thought something was wrong with my phone until I found this thread.

It appears that the time is when I last looked at my phone, as if it's cached (either the time or what seems more likely - the screen) and then is updated and refreshed. I wonder if there's a way to disable this caching, if that's what it actually is...

Probably handled in the LUA scripts as they describe how the page is rendered & what action do what. My suggestion is try to find the Home Page from one of the other TP versions. They don't have the flip clock.
EDIT: The newer Sense 2.1 TF3D does this as well as animated the whole BG with the Weather on the Home page anytime TF3D looses focus & gains focus back. This means when you go to a screen that is not TF3D. An example is just opening & closing the start menu on a 6.5 ROM.

A fix for the clock issue
Here is the manila file to fix the clock issue...To istall you must disable manila and then total commander this file into the windows directory of your phone

gramsey1911 said:
Here is the manila file to fix the clock issue...To istall you must disable manila and then total commander this file into the windows directory of your phone
Click to expand...
Click to collapse
You're on to something there. Fixed the flip but screwed up the clock. Digits are all screwed up.
Any ideas?
Thanks for working on this.
(copied from the tilt2 tips/problems thread)

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....

Struggling to properly display 6.5 UI

I recently updated my TP2 to WM6.5 (from 6.1) and am finding that the unit is not comfortable with displaying the new UI. All menus now appear surrounded by messy line structures which occasionally even leave traces after the menu has gone. I also find that the spacing of items in the new menus is overly-large. Whereas before a menu of five or six items could appear on screen, now only four are visible (landscape mode, 8 in portrait) and it is now necessary to scroll through menus where it wasn't before. Is there anything I can do about this?
Many thanks.

AidanBell said:
I recently updated my TP2 to WM6.5 (from 6.1) and am finding that the unit is not comfortable with displaying the new UI. All menus now appear surrounded by messy line structures which occasionally even leave traces after the menu has gone. I also find that the spacing of items in the new menus is overly-large. Whereas before a menu of five or six items could appear on screen, now only four are visible (landscape mode, 8 in portrait) and it is now necessary to scroll through menus where it wasn't before. Is there anything I can do about this?
Many thanks.
Click to expand...
Click to collapse
Can you post a screenshot of the graphical corruption you describe?
I might suggest reflashing the upgrade before you get much further, some users have reported that doing so has resolved all kinds of odd behavior after the Tmo 6.5 upgrade.\
However, the resized menus you're talking about just sound like the normal change in 6.5. I think there's cabs around here to revert to the old menu styles, but I'm not sure. The idea of course is they're more finger-friendly this way, but you're dealing with the obvious side-effect of that.

Many thanks. Here's a screenshot as requested.
Hmmm ... cabs which allow me to keep 6.5 yet return to the 6.1 menus? YES PLEASE! If anyone could possibly point me in the right direction...?
Cheers.

AidanBell said:
Many thanks. Here's a screenshot as requested.
Hmmm ... cabs which allow me to keep 6.5 yet return to the 6.1 menus? YES PLEASE! If anyone could possibly point me in the right direction...?
Cheers.
Click to expand...
Click to collapse
Ouch, that's pretty ugly! Yes I would start with at least a hard reset, but really I'd suggest just reflashing the upgrade, and see if that makes any difference.
Now I think I've seen cabs for that (the older, or at least smaller, style of WM menus), if not a reg entry...but I honestly can't recall or find where at the moment
EDIT: one more quick question- what carrier are you with?

Thanks for the advice. I guess that will be my best course of action, unless I can track down a menu-changing cab or reg tweak, which would then very possibly negate needing to do a hard reset or flash. I'll give it a while and see if anybody else can perhaps help with such a cab first.
Cheers.

sirphunkee said:
I think there's cabs around here to revert to the old menu styles, but I'm not sure.
Click to expand...
Click to collapse
REALLY!?? WHERE???
Please, I'd give my first born if I had one, I HATE the 6.5 menus, the old ones were friendly enough.

I had the same issue as the OP when i updated to 6.5 ...
Graphical anomolies that looked just like his, and it wasn't just menus getting frozen, it was programs and switching tabs and going from one text to another, switching e-mails...
Perhaps the issue with 6.5 is the graphics driver??
- Mark

Guys just do a hard reset and let everything run its corse. 9 times out of 10 this is the biggest issue with flashing a new rom. It's always best that after you flash your phone you do at least one or two hard resets to set all the files and reg entries where they are supposed to be... why? I have no idea but I know when I flash I always do a hard reset and never seem to have the issues others do.

I tried, Aaron, I tried! I bit the bullet and did a hard reset, then re-flashed the 6.5 update and then did another hard reset. And when it was all done the menus were perfect and everything was the way it's meant to be ... ... ... for about 10 minutes! But then from one moment to the next it was back to how it was before. Grrrrr!

AidanBell said:
I tried, Aaron, I tried! I bit the bullet and did a hard reset, then re-flashed the 6.5 update and then did another hard reset. And when it was all done the menus were perfect and everything was the way it's meant to be ... ... ... for about 10 minutes! But then from one moment to the next it was back to how it was before. Grrrrr!
Click to expand...
Click to collapse
Does your phone feel noticibly warmer after running for that amount of time?

Yes! Absolutely. After half an hour or so of using TomTom - constant screen on - it feels only a little short of worryingly hot.

AidanBell said:
Yes! Absolutely. After half an hour or so of using TomTom - constant screen on - it feels only a little short of worryingly hot.
Click to expand...
Click to collapse
I see...well the reason I ask is because in regular PC's, graphical corruption like that is usually caused by either driver problems, or heat issues...when the processing chips get too warm, they can start to display all sorts of weird things.
I don't know how to eliminate drivers as the cause in this case, other than the fact the issue seems fairly isolated, if there were driver problems we'd probably see a lot more people with this issue.
As for the heat issue, I can offer this experiment for now:
Get a ziplock bag (or something else that won't leak), and put some ice cubes in it...when you've got the phone working where you don't see the issue at first, when you first turn it on, lay it on the bag of ice and let it sit there for a bit while you operate it as you normally would...see if the graphics still go wonky after a while, or if that eliminates it or at least delays it.
EDIT: Yes, it would be a good idea to wrap the bag or whatever with a cloth (shirt, whatever) as well, to keep possible condensation away from the phone. Obviously the point is to keep the phone extra cool for this test, so just use common sense when working out how you prefer to do that.

Make sure you wrap that ice bag in some sort of cloth to absorb the condensation, or you will have a waterlogged rhodium. Even if you were to save a water damaged phone and get it working again, the phone's life would be greatly diminished due to oxidation of components.

Hamsteriel said:
Make sure you wrap that ice bag in some sort of cloth to absorb the condensation, or you will have a waterlogged rhodium. Even if you were to save a water damaged phone and get it working again, the phone's life would be greatly diminished due to oxidation of components.
Click to expand...
Click to collapse
Yes, good point..."problem solving" trumped "think it all the way through" there for a min lol. Thanks Hamsteriel, post updated.

AidanBell said:
Yes! Absolutely. After half an hour or so of using TomTom - constant screen on - it feels only a little short of worryingly hot.
Click to expand...
Click to collapse
Well that's normal. The reason your phone is warm after using tomtom with the screen on for 30 minutes is because the gps is active AND the screen is on so the phone is going under some pretty heavy usage.
sirphunkee said:
I see...well the reason I ask is because in regular PC's, graphical corruption like that is usually caused by either driver problems, or heat issues...when the processing chips get too warm, they can start to display all sorts of weird things.
I don't know how to eliminate drivers as the cause in this case, other than the fact the issue seems fairly isolated, if there were driver problems we'd probably see a lot more people with this issue.
As for the heat issue, I can offer this experiment for now:
Get a ziplock bag (or something else that won't leak), and put some ice cubes in it...when you've got the phone working where you don't see the issue at first, when you first turn it on, lay it on the bag of ice and let it sit there for a bit while you operate it as you normally would...see if the graphics still go wonky after a while, or if that eliminates it or at least delays it.
EDIT: Yes, it would be a good idea to wrap the bag or whatever with a cloth (shirt, whatever) as well, to keep possible condensation away from the phone. Obviously the point is to keep the phone extra cool for this test, so just use common sense when working out how you prefer to do that.
Click to expand...
Click to collapse
Even after reflashing the phone like he said he did that its a little more then that and it's likely hardware..... ie.. warranty issue with HTC. Go to your carrier and show them the phone. They'll do one of two things, the first give you a new phone on the spot.. the second fill out a form and have it so you are shipped a new phone, when the new phone comes you use the prepaid packaging HTC sends with their warranty phones and put your own one in. If you have flashed a custom rom you have to remember to put back your stock rom and get rid of the HardSPL

I must agree with Aaron. I don't consider overheating when using TomTom to be an issue.
I'm afraid you misunderstood my situation Sirphunkee. The display problem is permanent, allways there. It was only "not there" for about 10 minutes after I did the re-flash and hard re-set, since when it's been permanent again. I don't believe I have an over-heating issue, and I can't see how the menu problem could be heat-related, since it's there 100% of the time, even when the unit is stone cold.
If only someone ... anyone! ... could come up with the link to the cab or reg-tweak that returns WM 6.5 to the 6.1 menus, not only would that very possibly solve my problem but would also return me to the much, much better menus.

I think I've discovered what my problem is. I can't give details, but I think it's the "Winterface" UI that I am using. Just now I had cause to replace all the Winterface files, and blow me, suddenly my menus are fine again! That was two minutes ago, so it remains to be seen how long this will last!

UPDATE:
OK, here's the latest: unfortunately within minutes the menus were bad again. I've now updated to the latest version of Winterface, however that hasn't solved the issue. Although the obvious answer would be to change my UI, I am extremely loath to do that as I'm very used to and very keen on Winterface, so I'd like to first try to tackle repairing the issue. Now that we know that Winterface is behind the problem, can anyone offer any suggestions how to address and repair?
Incidentally, I can confirm that it is Winterface that's causing the menu problem. In between uninstalling and reinstalling the two versions of Winterface I played extensively with the device and all the menus were normal.

Have you tried downgrading the rom to 6.1 again to see if the problem persists? And have you searched here ------> Windows Mobile Development and Hacking Specifically the "Windows Mobile Development and Hacking General" Forum?
You're odds of finding the answer will probably drastically increase by doing a search for your answer there. I swear I saw a thread once in there about getting 6.5 menu's on 6.1 Although I dont recall if it worked the other way around.

After Installing Android CAB and download apps Screen Stop Working

My Screen has totally stop touching and Ive searched and searched for a solution.... and yet havent found any. I deleted the ts-calibration file and yet still screen no work

BUMP Help!

You mean that the screen is not working within android of with windows mobile?
If you mean windows mobile then your screen is broken or if you think it is because of the cab, you can try a hard reset.
If it is only in android then uninstall this version of android and download the .rar and extract it to your SDcard.

I have sort of the same issue. My screen doesn't work (most of the time). For some reason it is responsive sometime (not clear how to recreate that). I can see the screen is responding, although if I go to the menu and try to select a icon with my finger it holds the icon and drags it (and I cannot let it go)
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Deleting the calibration file doesn't work for me. Also I have tried hard resets and rom upgrades several times, with no succes. It looks like installing android changed something, but doesn't set it to his old state after removal.
Anybody?

This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.

yea i was having the same problem and couldnt figure out a solution, i deleted the ts-calibration, i've tried deleting all android files and starting over but the problem still exists. I think it might have something to do with the little bit of moisture i see under the screen because before i started seeing that, it used to work. But the screen works just fine when WinMobile is running so i dont know

If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?

arrrghhh said:
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
Click to expand...
Click to collapse
No, in both. This problem originated from the fact I was never able to start up a blazin android. It started booting, but for some reason never finished it. With the previous editions I never had any problems.
arrrghhh said:
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
Click to expand...
Click to collapse
I know you are replying on another user, but I still want to respond
Yesterday my screen was responding for a short moment. I have replaced the WinMo rom after that several times, no success. Also deleted android and reinstalled it again. (I've been trying trial and error for a while now, without any success.)
My WinMo rom btw was an energy build. Any similarities with other users experiencing this issue?
Is there some internal memory where these type of settings (keyboard layout and such) are stored and what not always change if you upgrade roms?
Perhaps I should go back to the original T-mobile rom.

Just upgraded to the original tmobile rom, but I'm stuck at the WinMo startscreen (tap the screen to start using it for the first time) I noticed that if you slide the phone open (keyboard visible) the display of the screen is correct. If I flip it back I'm missing parts of the screen.

dwaaz said:
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Click to expand...
Click to collapse
I'm sorry for spamming this topic, but isn't it really weird that only for entering your pincode the numbers are correct, but afterwards the layout is all messed up?
6_7_8 = 123
Y_U_I = 456
H_J_K = 789
N=0
I have the feeling my phone is using system files (after login) of a completely different phone (and no.. I did use the right rom's ) This goes for the keyboard as well as the screen issue.

any bright ideas?
Just to bring it under the attention again, because I'm on the edge of sending it back to t-mobile. (I hope they are not going to charge me because I have a diamond 2 that also needs repairing, touchscreen doesn't work as well, and I'm seeing some costs coming up there. For some reason I always manage to wreck my phones in the first 2 years. )
Any bright ideas?

I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slighty and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App

It worked!
trotmanc said:
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slightly and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
Click to expand...
Click to collapse
I was kind of skeptic here of this solution, because my phone looked quit clean. But there I was, on visit with my parents, fiddling with my phone, thought; let's put my nails between the lines next to the touchscreen..... and wtf.. it worked My screen is back up. Very surprising but good.
No I only have my keyboard to worry about. Any thoughts on that?