Related
ive had WM6 for about a week or so and i have noticed a few bugs but this volume strip one really bugs me. i recently put the jogbar app on my dash and it worked fine with WM6 beta but just recently my volume strip stopped working altogether. ive reset everything and i even deleted the jogbar program to no avail. any suggestions? maybe there is something in the registry that got messed up
adewey234 said:
ive had WM6 for about a week or so and i have noticed a few bugs but this volume strip one really bugs me. i recently put the jogbar app on my dash and it worked fine with WM6 beta but just recently my volume strip stopped working altogether. ive reset everything and i even deleted the jogbar program to no avail. any suggestions? maybe there is something in the registry that got messed up
Click to expand...
Click to collapse
That happened to me once when using the application. I just edit the registry now. I recommend you go to the Volume strip in the Settings and set it to default. If that does not work, ClearStorage (which will wip your device entirely) You will loose data so backup your information and apps before you do so.
JAmerican
I did all of that too, and it still didnt do anything, i even manually edited the registry and it still didn't do anything.
Is this a bad thing?
That thing was as useless anyways. I turned mine off the 2nd day of owning this gem. IMHO, I believe the touch strip is a gimmick. Stick with the scroll wheel. Don't fix what isn't broken.
Well unlike most people that have a dash, i actually liked the thing because i knew how to use it, and now that its not working, i can barely hear people on the phone because the volume isn't loud enough.
I don't understand how the touch strip would take any kind of skill in using it. You touch it and it is supposed to behave a certain way. Obviously, that was not the case for most users, such as myself.
It's either a love or hate relationship with the touch strip. Mine stopped working and it was different trying to navigate. But i got it back and i'm good.
lol...
Thats what I thought too, you actually have to rub your thumb from top to bottom or bottom to top as if it were an actual scroll wheel. I felt stupid after complaining about it, but thats all it is.
Well lucky for u guys, ur volume strip still works. Mine just stopped working randomly, and even after getting wm6 it still doesnt work...
Hey, you're lucky. I had to disable mine. That volume strip is probably the worst implemented "feature" I've seen on a smartphone yet. Thanks HTC!
It's fine for in-call volume -- and tapping it during an incoming call was the only way to mute the ringer without forwarding to voicemail -- that doesn't work anymore. Does anyone know if there's a way in the WM6-Dash to mute an incoming call?
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
1) Bluetooth sound quality - we each use Bluetooth headsets and have noticed lots of crackling unless the phone is turned with the back facing the headset. This didn't happen with our previous phones (same headsets) unless we got 15-20 feet away from the phone.
2) Dropped calls - I've noticed a ton of dropped calls when I'm talking on the phone and driving along my normal work commute. There are 1-2 holes along the route where my previous phone would drop, but this one drops 5-6 times. I found these radio updates in the ROM forum. Would that help?
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
As for #4: Not all programs have a landscape mode natively.
jlczl said:
As for #4: Not all programs have a landscape mode natively.
Click to expand...
Click to collapse
Thanks. I figured that she might be using an app that doesn't work in landscape since I haven't come across it yet.
Also, regarding #2, I should have mentioned that I have 4.48.25.20 as my current radio.
1) I use Jabra 2nd gen and mine is working great. A little crackling sound but nothing major.
2) Depend on the area you live and coverage, you might want to try different radio. I have stock radio and mine is working great. Better than my fuze was actually. I can get 1 or more bar than Fuze and call quality is super clear. No drop calls yet while I had like 2-3 drop calls with my fuze.
3) I am still running on stock rom and yes indeed it's slow and sluggish. I have to reset the phone physically sometimes. I am not too happy about moving the battery cover just to reset as well. With custom rom, the phone will be snappy since some people are running custom rom with their Tilt2 already. I am in the same boat as you. Waiting for the complete stock rom dump. Until then.
4) Not all the landscape work as you have already found out.
I use a BlueAnt and my BT reception is good.
I thought mine was slow at first but as I tweaked it a bit, turning off alerts and pop ups, it SEEMS to be more of what I expected.
Haven't had a dropped call issue.
But, I am thinking that I will flash the ROM when something comes along.
Thanks for the replies.
FWIW, my wife uses a Jawbone 2 and the crackling is noticable on both ends of the call. I use a first-gen Jawbone and have nocticed the crackling as well. It seems that it works better when the phone is on the same side of my body as the headset. I did not notice this crackling on my Dash and Blackjack 2 nor her Dash.
I think the dropped calls problem is definitely area related. My wife is currently out of town and it hasn't dropped her calls at all that I know of. And when I'm at home, it's no problem. It's just that on my regular commute, it drops 5-6 times where my previous Dash and Blackjack 2 only dropped once or twice occasionally. I've only made my commute once since I got the Tilt2, so maybe there were some coincidental network issues. That said, call quality has been very good.
I just turned off the new SMS notifications. I've also removed a couple of tabs that I know I'm never going to use (stocks, AT&T, and music) at that seems to have made things a little snappier too.
HAH! Not more than 1-2 minutes after I posted my last message (from my laptop), I went to use the internet connection on my Tilt2 and it locked up. A message appeared asking if I wanted to send error details to MS and then my phone turned off.
Another thing I've noticed is that Opera takes a *really* long time to switch from landscape to portrait. And it seems to be significantly slower than Opera Mini was on my Dash and Blackjack 2. Maybe because Opera Mini is Java-based on those platforms?
My wife is now reporting that her Tilt2 won't unlock unless she slides open the keyboard. Her Exchange connection requires the phone to automatically lock and require a PIN entry. I suggested tapping the power button but that doesn't wake it up, either.
Any suggestions? I'm thinking she might have a bum unit since mine isn't having nearly the trouble hers is.
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
SoapDoctor said:
As far as the lockups, I think there was a thread somewhere about that. Mine doesn't actually lock up but it hangs horribly. Give it 5min or so and it figures itself out, usually involves opening the keyboard at the same time it is launching something, sms in my case.
Suggestion? Hard reset hers and if it continues swap it out.
Click to expand...
Click to collapse
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
e_dogg said:
Thanks for the tip. Unfortunately, she's out of town right now so I actually haven't seen the things she's complaining about first-hand (except for a couple of things that have happened on mine too).
I'll send her instructions for a hard reset and see if she's adventurous enough to try it on her own. The AT&T store near where she's at is exceptionally good - they really know Windows Mobile there and were a big help in getting the phone initially set up. So, worst case, she can go there and have them do it.
Click to expand...
Click to collapse
Don't run to fast with my advice, I'm a complete noob but hard reset would be the first thing I would try. It is a microsoft product after all and I'm pretty dman lazy to run to the store first.
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
e_dogg said:
My wife and I each purchased Tilt2's earlier this week. We both come from Windows Mobile 6.1 phones and are generally happy with WinMo products and comfortable with tweaking them.
We're both having some trouble with the Tilt2 and I'm hoping that someone here might be able to help.
3) General performance - The phone seems a little bit laggy and slow to react. Nothing like what we saw in demo videos on sites like wmexperts.com. My wife even reports that hers has completely locked up on her before. And I've noticed a severe lag waiting for the phone to come back after I've flipped the keyboard out. I assume that installing a custom ROM would help with this as it's helped on previous phones we've owned. However, there isn't a 100% working AT&T ROM to revert to yet (only one that appears to work is missing radio and bootsplash at this point) in case the custom ROM doesn't perform better, so I'm a little leary of doing it. Should I be worried? Or will the custom ROMs here help get rid of the lagginess.
4) Switching to landscape mode - My wife told me that her phone isn't always switching to landscape mode. She doesn't have any apps installed yet so I'm assuming it's in all of the default screens. Should everything work in landscape mode?
Thanks in advance!
Click to expand...
Click to collapse
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
I can't really help you out too much, but I haven't been experiencing many of these problems at all, and I'm still on the stock rom, just cleaned it up a bit. Spend some time on the forums and you'll find some good quick hacks to try before you try a new rom.
superrrguy said:
I'd like to add that I'm also having some issues with sound and response time.
My phone starts fresh with about 65% of resources used up. After regular phone/contacts usage for an hour I'm at around 70% and after Opera, the phone is done. I can browse or use file explorer or music but there goes the multi-tasking.
I haven't flashed a ROM yet. I just wanted to see what AT&T did with this thing 1st.
One more thing, why did they switch the FN and Shift keys? My brain is having a hard time getting used to it, especially when the shortcuts that require the Fn key are on the bottom row.
Click to expand...
Click to collapse
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Linear2202 said:
FWIW- I have a Jawbone 2 and have cracking in the audio. Had it with my Fuze also and have always wondered if it was the headset or phone. I don't think I could keep my fuze in the holster because of the crackling.
I have some slight performance issues, but it's not to bad. Seems mostly relating to minimizing a program and starting a new one.
I have a strange problem with the TF3D photo tab. It's slow to get the image clear. I select an image and then try to scroll through them. It hangs on one, then flips it's orientation (I haven't moved the phone though). Anyone else have issues with the photo tab?
Click to expand...
Click to collapse
Good info about your Jawbone issues. I have an old Plantronics headset that I'm not really using anymore. Maybe I'll give that one a try to see if it's just that Jawbones don't like these new versions of HTC phones (it worked great on her Dash).
As for the photos tab, it seems to work ok. Though the first "flip" through the pictures seems to be slower than subsequent flips.
I found that hiding tabs I won't be using like the "AT&T" tab seems to help speed things up. I think I have 3 or 4 hidden.
amurch said:
#3 I am running NRG ROM Photon date 10/17 and it is insane on my tilt 2. No radio change either. Stupid fast, eye candy, and never a dropped call or sluggish issues. Link below (5k plus thread, really read the first page to see the versions and Faq's)
http://forum.xda-developers.com/showthread.php?t=553506
Click to expand...
Click to collapse
Thanks - good to hear of your sucess with the NRG ROM. That's the one I'm planning on trying since I really like the 6.5.1 changes.
redpoint73 said:
Touch FLO 3D uses up quite a bit of RAM. I unloaded it and restarted, and my phone is down from 65% to 49%. Unfortunately, I'm kind of liking Touch FLO 3D
Click to expand...
Click to collapse
Yeah, Touch FLO 3D sure is purty. And, now that I have the tabs sorted and hidden the way I like, it's very easy to use.
Just an update...the Energy ROM seems to have cured the dropped calls. With the stock AT&T ROM, calls dropped about 5-6 times on my regular commute. With the Energy ROM, not a single one!
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Linear2202 said:
Something that has happened to me now a few times...I get a call on the phone. Caller ID and picture show up fine. Screen turns off..later i turn the screen on and the phone number is not accurate any longer and the picture is gone..
Anyone had this happen to them?
Click to expand...
Click to collapse
Yep - happened quite often with the stock AT&T ROM. I don't recall seeing it after switching to the Energy ROM.
Hiya.
Im using my TP2 for two month and Im really satisfied with this phone (as I did with TyTnII (thanks for tab and ok keys there ;-).
But few things bother me so Im trying to ask here:
1) Default action in email is reply all. Is it possible to change it to reply?
2) incomming SMS have long vibration time. Where can I to make it shorter?
3) When Im calling someone and he pick it up, it vibrate. But too short, can it be longer?
4) there is possible to set phone to switch to external microphone when its faced down. But in spite of the fact that I have it checked, it doesnt work :-(
5) row, where is battery, time and notification pole is everything extept battery notification filed. It means that anywhere I click Notifications is opened. What bother me the most is, that there is for example new email and when I click on it nothing happened ;-(. Rhodium Pack should solve this problem, but its not avaible anymore because of some licence problem.
6) I was always using another than original rom. In TP1 I was using song recognize program, TCPMP, etc. Can someone give me advice, what ROM is now the best? What ROMs are you using and why? Can someone explain me what are shortcuts in the names (WWE etc)? Im in Western Europe, but why its so important?
Thanks a lot!!
John
I don't know the answers to everything, but I know that there are places in the registry that can be removed (named OutlookEnhancement) to remove the reply all. Here is one area to look:
[HKLM\Services\OutlookEnhancement]
"DLL"="OutlookEnhancement.dll"
Remove the OutlookEnhancement.dll field. I'm sure if you searched for something like remove reply all, you will find hits on it explaining how to do it.
I've seen the long vibrate on text, and haven't felt the need to change it but every now and then a bug happens where it vibrates REALLY long, like over a minute, and then I just hit a button to stop it.
I've never seen a Vibrate on Connect modification to let it vibrate longer.
Mine usually switches to external mic when I flip it upside down. I've had it not to it once or twice. Does your G-Sensor work in applications? Maybe Calibrate it? And try it on a level non moving surface (like a table).
WWE means World Wide English. Best ROM questions usually go unanswered here. Everyone's preferences for a favorite rom are different. Line up and sample the Chef's selections and see which one tastes best to you
I installed the Android OS on my phone that was found on this post:
http://forum.xda-developers.com/showpost.php?p=5480057&postcount=7353
I updated it and everything to what he has but occasionally my hard buttons at the bottom will either stay lit or not respond at all. Or it will even go crazy as if I were sitting there spinning my finger around the middle hard button thus making it highlight everything on my menu. That also causes trouble because then it thinks that when I press the home key it decides to bring up the call log screen.
Is there anyway to disable the "iPod Scroll" on the center hard key?
Dude. You should update to the newest build. And update Rootfs and zImages.
everything is in the XDAndroid thread in this forum.
I updated to the one found here:
http://forum.ppcgeeks.com/showthread.php?t=104276
And my scroll wheel and hard buttons still mess up from time to time.
What device do you have? RAPH100?
Sorry I don't know the developer names but its the HTC Fuze for AT&T so it's either the RAPH100 or just the RAPH. The start up config I'm using for Droid is the RAPH config.
Its best not to touch the capacitive DPAD and scroller during boot up. (safe time is when you can see a n d r o i d or the bootscreen.) This and having the pad clean is very crucial if you don't want it going crazy.
Try cleaning it with a wet cloth/tissue and try again.
I also had a screen protector which was massively scratched which caused problems. Ever since removing it the DPAD has been working great.
dude i totally have the same problem.
i ve tried wipe it clean but no luck.
sometimes everything work great but all of a sudden the buttons go wild and start flashing. after that, nothing will bring it back to normal. maybe after a few minutes if will stop blinking, lefting one or two LEDs on, and the button is then less responsive, though still works if you place your finger on the button you want for a few seconds before pressing.
I've seen a few people complaining about this but other says its because of our own device...
However everything works normally in WM... so i guess it might be about the sensitivity or something like that.
no matter it get fixed or not, I do want a method to disable the scrolling too, and maybe the left and right buttons, because they never work even under WM...
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
also getting the exact same problem a lot, with everything up to date, clean, and not touching on bootup. would it be difficult to implement a code where we could just disable the middle scroll wheel? thats the thing that causes the most problems, and its not really that useful anyway.
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
twiggy159 said:
@reverendkjr
This may be off topic but, you say you leave your phone running Droid all the time? How do you not drain your battery in like 4 hours unless you leave it charging all day?
But I'm pretty sure I'm as up to date as I can be and I still get this issue.
Click to expand...
Click to collapse
Its not off topic at all. I have been using Xandroid as my one and only OS for about a month now. I do charge it quite often, and I leave it on my desk at work on a charger. I also charge it at night as I sleep. I start off the day with 100% and can go 6 or so hours without issue. I continuously get 3-4 days in a row without a reboot or a failure. I find that it has become a suitable alternative to Winmo. The difficulty that I have is that there are primary functions which I miss a bit (camera mostly). But I feel that in order for me to fully understand and appreciate this, and to be able to contribute as a quasi beta tester, I must be willing to spend as much time with it as possible. I keep up with these forums on a regular basis , checking them sometimes 2-3 times a day. It is difficult to distinguish helpful info sometimes, since there are several versions floating around, and not everyone has the same setup & environment. I search as much as I can to find my own solutions, and for the most part, I'm relatively proud of myself. I usually only chime in when something is really bugging me, or I see something valuable that I can add to a conversation.
This issue was one that I had seen a few people talk about, and it had always been chalked up to being a dirty sensor type of thing, or someone touching the pad while it was booting. Having tried all of these solutions with no success, I had come to the determination that it was not constant, it could be ignored or dealt with, and eventually someone would fix it. It is most definitely not a "hot" item, so I never made a stink about it. Now that others have brought it forward, I decided to add my experiences.
I have loads of respect for the developers, and realize that they are not doing this for me. They are doing it for themselves, and fortunately, they share it with us. I am envious of their ability to make this project possible, and have no expectation or demands. I just take what they give us, and try to make it work for me.
Just my two sense, I'll step away from the pulpit now.
+1 for Navigation Wheel or capacitive D-pad issue
reverendkjr said:
Yeah, mine does that too. Its random, sometimes not happening for days, then all of the sudden it starts. And this is within the same boot. Very odd. BTW, I keep up on all builds, always update asap, and my pad is spotless. I can't really figure it out.
Click to expand...
Click to collapse
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
spideyngo said:
May I appeal to the developers to move Raph110 Navigation wheel to "Not working" so further development can occur. I do not touch the wheel during boot, but it still randomly flips out. My screen is clean. I did the clean cloth thing. The Navigation wheel not only flips out going all over the place. It actually rarely works the way it should in any application.
All I really need is to turn it off or disable the Navigation wheel if at all possible. Is it necessary to load the Nav-wheel capacitive drivers or can we disable them? Would it disrupt the function of the D-pad if disabled because all I need is the D-pad.
Chime in RAPH110 guys. Would you care if the Nav-wheel was disabled, because I actually think this is what is causing the issue.
I just want to make sure that I communicate to any developers that this is not a major issue. To me, I feel as though this is the only issue that I have at all. With the build I use, I honestly have no other issue which means that the Raph110 Android end product is 99% complete. To be direct, Thank you! I feel as though you purchased me a new phone, so this is no way a complaint. It is only the last 1% quality assurance analysis. ;-)
Edit: I just re-read this thread and the common denominator is HTC Fuze or RAPH110 users are having this minor issue. RAPH100 posting are saying "Just read the thread" or "use updated packages" or "clean the screen" which I think may all work and be valid for you RAPH100 users. I can indeed say without a doubt that this does not work for RAPH110.
In order for me to stop the random D-pad/Nav-wheel random scrolling, I have to screen lock it, let it go to sleep, then it might stop. It does stop mind you, but it is quite random how I am able to stop it.
Click to expand...
Click to collapse
I think mine is a RAPH100... i cant take out the battery and double check... but mine is a unbranded version fron 3 australia... which i remember is raph100. and i totally have the same issue so this is not only happening on raph110 i believe.
Hey guys,
I was having the same problem in wm6.5 using many different energyroms, i disabled the scrollwheel altogether within the registry, never used it anyway. I am now getting the same problem in Android. is there is a registry parallel in android?
btw using a RAPH100 (all above fixes did not work)
devs, is there no easy way to implement a disable scroll wheel setting?? i swear that wheel will drive me crazy at times
While this could be an issue with all Raph 110's (AT&T Fuze), I think it is just a subset due to hardware problems. For me, the problem only happens occasionally and it does not only occur in xdandroid, but also in WM. There is an HTC tool (for WM) named NavDbgTool.exe that will show you what is happening with the capacitive buttons/touch area on the Raph. For me, when I have issues it lights up all over and shows touches occurring that are not occurring. I know of at least one XDA member (Captain Throwback) who was able to get a replacement phone (a Tilt2) from the insurance carrier because of this issue.
Perhaps this is a problem that eventually happens with all Raph 110's due to a hardware flaw. If that is the case, maybe enough complaints to AT&T will cause them to replace all of the devices (similar to how Sprint is replacing all their Touch Pro's due to overheating issues). In the meantime, if you have insurance, you should be able to get a replacement phone, just use the NavDbgTool.exe to document the problem in WM.
Also, due to this issue, it would be nice to have the option to disable the capacitive touch area on the Raph 110 in xdandroid (while keeping the D-pad working). I don't use it for anything now that zooming doesn't work for recent versions of Opera in WM.
I'm starting to think that this is Winmo ROM related. I noticed that since I've used the ROM that I have installed right now, the amount of times this issue has affected me has been slim to none. I am currently running the an NRG rom from june 12 with sense 2.5.
link: http://hotfile.com/dl/47992175/ccd8b44/Energy.RAPHAEL.21905.Sense2.5.Jun.12.7z.html
I'm not guaranteeing anything, but its working for me.
Maybe it has something to do with a package that is built into certain roms. I have noticed a few times where the winmo ROM i have loaded will affect Android's performance as well. The ROM that I am currently running was also what provided me with the ability to get GPS working in Android.
I hope this helps some of you.
I don't think it has anything to do with WM. For me, it only happens in Android.
firstly i have a raph100 that has this issue too, so its not just raph110
secondly, for me, this happens in wm too but a lot less frequently and seems to repair itself. It happens in android 70% of time when i boot, the 30% else happens later...
newly released zimages seem to shutdown the capacitive panel when sleeping, and this solved my problem a little bit since every time it goes crazy I can put the device in sleep then resume it...
But when it goes asleep the two buttons on the right act as back, the two on the left act as home. I think there is only one physical button on both sides, the touch figures if you are pressing back or end.
Sent from my AOSP on XDANDROID MSM using XDA App
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.