Hello all,
I'm a new user, and quite new to PDA's and Smart Phones.
I found this forum while looking to see if the Trinity would be releasing WM6.
I've looked at the LVSW_Trinity_WM6_v2.0.1.1 sticky thread at the top of this page and I downloaded the following from that thread;
HARD-SPL
GSM_1.41.00.11
20070527_Trinity_WM6_v2.0.1.1
I did them in order, the first two without any issues.
When I came to install the 20070527_Trinity_WM6_v2.0.1.1,
I get to where the progress bar is and activesync turns off as the device switches to the multi-coloured lines screen, an error pops up saying that it could not find the device. Although it clearly has because I had to answer yes (on the device a few steps ago) to install the ROM.
As soon as it kicks in to start installing and the screen goes coloured it just disconnects every time.
Any help would be greatly appreciated!
If you need any more information please let me know and I'll endevour to find the correct info for you. (still learning my way around the phone).
ps. before I started this I all ready had the latest WM5 ROM from HTC on the device as I have only just bought it, when I checked at HTC and went to install their latest version it turned out that version was all ready installed. (don't know if that helps).
This sounds like regular behaviour to me.
Do you let it stay in the multicoloured screen (bootloader mode this is) and run the romupdate again? That's what I need to do with mine.
RaindancerAU said:
This sounds like regular behaviour to me.
Do you let it stay in the multicoloured screen (bootloader mode this is) and run the romupdate again? That's what I need to do with mine.
Click to expand...
Click to collapse
Weird, I thought it needed an Activesync connection to do this, but I took your advice and it worked great, thanks allot!
Hello again,
So, I've been running WM6 for a few days now and I've noticed a few issues on my device.
I've installed the following;
HARD-SPL
GSM_1.41.00.11
20070527_Trinity_WM6_v2.0.1.1
My issues are/were;
Camera would not initilize - FIXED - Found thread on forum about removing battery, this cured it for me.
Battery drains quicker - UNRESOLVED
Media player sounds allot quieter - UNRESOLVED
Appart from these three issues (one of which I found a fix for) everything is great.
Are there any fixes for the above issues? Or is it something only I am experiancing.
Thanks allot for the help and a good release.
There is a fix for the battery drain in one of the threads in this WM6 forum and there is also the bass fix somewhere around here. If I wasn't a tad busy atm I'd have another look for them but IIRR they're easily found with a search
Hi, I found both of these, but for the mon_rus version, can I use those on this version?
Many Thanks
Well I found the transcriber, but no fix for the rubbish sound on my trinity and wm6.
Is it possible to go back to wm5? I hope so as I use it's mp3 allot!
Hi everybody,
This is my first post. This forum has been very helpful with issues with all the smartphones I've had in the past, so I'm throwing in this piece of information that might help someone with the same issue I had with my T-Mobile Wing/ HTC S730 (same as the Hermes).
PROBLEM: touchscreen is not responding and after a hard reset (recommended by T-Mobile not so saavy techs) I got stucked in the "TAP THE SCREEN TO SETUP YOUR WINDOWS MOBILE DEVICE" and since there is no "ESCAPE" button to skip this screen, I had a pretty much useless phone, I could only receive calls but not able to place any calls or have access to the start menu or any other function pretty much.
SOLUTION: after hours searching all over the internet, I found a very nice - FREE! - application designed for blind people to "SKIP" the align process, http://www.codefactory.es/en/ by CodeFactory. The application is called "REMOTE SCREEN ALIGNMENT" it is very easy and a quick way to skip the screen alignment process.
CONCLUSION: although it will not fix the unresponsive touch screen, it will at least let you access your phone through the buttons and slide out keyboard.
P.S.: there are many other tools and free apps there for a lot other phones.
ENJOY!
~~~~ FREEDOM OF INFORMATION IS THE BASIS OF LIBERTY ~~~~
JR
sx66_fl said:
SOLUTION: after hours searching all over the internet, I found a very nice - FREE! - application designed for blind people to "SKIP" the align process, http://www.codefactory.es/en/ by CodeFactory. The application is called "REMOTE SCREEN ALIGNMENT" it is very easy and a quick way to skip the screen alignment process.
JR
Click to expand...
Click to collapse
Hi - a word to the wise. Search here before the the internet in general.
http://forum.xda-developers.com/showthread.php?p=1985256
http://forum.xda-developers.com/showthread.php?t=331451
http://forum.xda-developers.com/showthread.php?p=1983932
http://forum.xda-developers.com/showthread.php?t=351999
http://forum.xda-developers.com/showthread.php?t=337698
Good to see you here on XDA-Dev. Keep up the good work. We like folk who post solutions and contribute back to the community.
Mike
May not work on WinMo 6.5
(warning: problem on Kaiser, not Hermes, though sounds as if it may be relevant here also- mods, feel free to remove the post if it is not relevant in this thread).
Had a similar problem, though was on WinMo 6.5 (Anryl's 21725 for Kaiser).
Unfortunately, this solution does not seem to work on 6.5- everytime the RSA executed successfully, and the phone restarted, but went back to the "Tap to setup device screen".
Went back to stock HTC 6.1 ROM, and the RSA works fine, and was able to start using the phone again.
===============UPDATE==============
The application was the SPB Fullscreen Keyboard v4.11 that was the culprit, verified over 3 hard resets that this is the offending program.
I hope this saves anyone else from going through the grief I have suffered. I completely forgot to include it on my list below so I am glad I had the patience to test one more time. (I ussualy forget to install it, then go to txt message or something and install it).
==================================
I am pretty much at wits end here and am preparing to return this huge lump of crap to the store. It seems that if I install "pretty much anything" and NOT use the touch-flo garbage... the phone will work great.... until i need or want to soft-reset it....
then the logo comes up, the ROM/RADIO numbers, and then the screen turns black, to never come on again.
Having worked for Sprint for 5 years, and moreover having built my own custom roms at PPCGeeks for 2 years I feel that I have a pretty good grip on the ins & outs of windows mobile.
I have NO clue what is going on with this phone.
I have three of them in my possession. It happens on all three.
I install each application, ONE-AT-A-TIME, soft reset after every single install, its fine. I wait a day or so, soft reset... SURPRISE you gotta redo your phone.
I have narrowed it down to a few programs that *may* be the cause of my irritation...
-Phonealarm (overrides the notifications...???)
-Ptravelalarm (and three other alarm programs) notification flaw???
-Memmaid (deals with notifications...???)
I dont expect anyone to know the answer, maybe someone else is having this issue (i hate Touch-Flo) and is trying to install programs to make the handset usable from the today-screen.
I am going to list my installed programs, and maybe, just maybe, someone smarter than myself can pinpoint the culprit.
-batti 2.4
-calendar plus
-sbp fullscreen keyboard 4.11
-google maps 3.21 (never GPS locks btw)
-iContact 95
-phonealarm 2.30
-pTravelalarm 2.81
-Resco File Explorer 7.05
-rlToday v22b
Thats it, thats all i use on my phone, im a creature of simplicity. On the todayscreen i have phonealarm, rltoday, ptravelalarm, calander+
I went to the forums for both phonealarm & memmaid, and there doesnt seem to be any threads with my issue. ptravelalarm has no support, but I have tried g-alarm, gsalarm & poweralarm, and they all seem to fail as well.
Again I cant narrow it down to a single application because after an install and reset it works fine. Its like "after the program simmers" that it wants to "Black-Screen" the phone.
I am 100% sure that a custom ROM will alleviate all of my issues as I am using all of those programs on a 6800 and a 6900, with WM 6.1 & WM 6.5 respectively.
They even work on the stock roms for both handsets....
Any ideas? How far out is the HARD-SPL? I have about 3 weeks left before I have to return these things.
Thank you for reading, and any help that may be forthcoming.
I'm having the exact same issue, it's very frustrating to pay $400+ for a phone only to have it blackscreen of death you every time you try to boot it up. Touchflo seems nice but it just adds extra button presses to what should be straightforward tasks. I hope things turn around but right now I'm not impressed.
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.
I had a strange reset of my phone last night, through what I think was no real action on my part, but I wanted to defer to the experts and see if anyone can help me make sense of this...
Also, as you'll see at the end of my post—if you make it through my rambling—I could find some of the info I seek elsewhere on this, and other forums, but the combination of data would be a difficult scavenger hunt and I thought this thread may help other lite (or lazy) power users with similar issues or info searches in the future...
So I was changing my battery out last night and when I was pulling the dead one out I had accidentally turned the phone on, but was talking to someone at the time and, being distracted, continued pulling the battery.
I got the new one in and turned the phone on to be greeted by what I think is called, and excuse my ignorance on terms as I have had no real interest in rooting to date, the debug screen—white background, cute little android rascals on the bottom, several restart options, etc. I believe I selected 'fast boot', as I think I have done when some random serious of events have greeted me with the 'debug' screen in the past.
All seemed fine and the device started up but it lagged on a black screen with an icon I interpreted as an 'update' icon and a progress bar. When I got to the OS, my settings, screens, apps, etc were reverted to stock conditions. My SD card retained all its contents and I used AppBrain so I was able to get things back to some semblance of normalcy rather quickly, but I am left with so many questions...
I've come up with 3 possible explanations...I made an error on the 'debug' screen, my device had a huge and random hiccup, or there was some strange update last night that, despite my best efforts, I cannot find mention of here or on any other forums.
Some additional info...
-on App Brain site, after linking the reset device back up to my E-mail/account, I have a totally new list named, not by the former 'ADR6300', but by 'HTC Droid Incredible'. This leads me to believe either AppBrain has changed its naming convention for this device since I originally set the app/account up, or there was some strange mystery update.
-I have always updated when prompted so I believe I was running the newest OS and am still on 2.2 now.
I'm not really looking for a solution to the reset, more looking for answers/theories and some preventative measures for reducing possible distress should something similar occur in the future.
-back-up methods...I use Launcher Pro Plus - paid, and just realized I can back-up home screens and settings through the launcher but is there anything else I should be doing?
-break down on that 'debug' screen, best option to choose for various issues, etc.
-has anyone heard of a similar story, update last night, or know the reason for AppBrain's new naming convention for my device?
Any other info, tips, or relevant advice would be much appreciated. As a Web/graphic designer and modern woman I am inquisitive and technical by nature but tend to subscribe to the 'if it aint broke, don't fix it' school of thought unless there is some new feature I hear about or want when it comes to my device. So I am not dense but I definitely don't know everything and I am looking to you, the 'experts' for answers
You held vol - and the pwr button when you turned on the phone. That is what made you go to the bootloader (debug). From there i'm guessing you had the phone do a factory reset, that is why everything went back to how it was when you first bought the phone.
2.2 is the "newest" build available without rooting your device.
Rooting and making a backup through Recovery is the best way (imo) to create a backup.
For what it's worth, I think g00s3y is spot-on
When you get to the hboot screen (the white screen with the Android dudes at the bottom), there should be 5 options:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
FACTORY RESET
Seems most likely that you mistakenly hit the last one rather than the first.