Official HTC 6.5 ROM Issues - Touch Pro2, Tilt 2 Windows Mobile ROM Development

A few things guys...
On the old 6.1 ROM, when the TP2 was locked it automatically unlocked itself when you opened the keyboard (like it does with the stylus) but for some reason that option no longer works in 6.5. It unlocks if you take out the stylus still, but it doesn't unlock when you slide open the keyboard so any idea if there's a registry hack available?
Also, on 6.1, when the device was locked it returned to the TF3D home page whilst locking, but now it remains on the last viewed tab rather than returning home, so again, do you know if this can be rectified?
It does appear to be a lot slower than 6.1 now - using 73% resources on start-up which seems awfully high.

yes and when you get a sms when phone is locked then in 6.1 you get a red flashing led in winmobile 6.5 not.
Batterytime reduced from 2 days with 6.1 to 12 hours in winmob6.5
sometimes phone is locked at night the next morning phone is of !
when the phone is doing nothing how can the battery empty in few hours ?

oops hard reset did the job

Please use the Official 6.5 ROM thread : http://forum.xda-developers.com/showthread.php?t=570366

Related

** HELP!! ** My Diamond is inoperable!

Hello,
I know you're all very knowledgeable, so I need your help!
I turned off my diamond last night when the battery was running out and since I put it back on charge whatever I do I can't get into it.
Edit: It's actually the T-Mobile version MDA Compact IV but with Manila TF3D and skin.
It starts up, says windows mobile etc. then it gets to the phone lock screen (which is always a bit laggy) but I can only manage a few digits before it locks up and completely freezes, then I have to do a soft reset or remove the battery to even turn it off.
I've tried everything, even typing the password as fast as I can, but I entered the wrong password too many times and now it's asking me enter a series of letters and numbers before I try again (which would be ok if it didn't lock up by then).
What can I do!?
Daveraven
Panic over - read some posts and figured out how to do a hard reset - all sorted now, thanks anyway!
That'll teach me for setting registry cache tweaks to maximum!
glad all is well
now theres...tweaking and there is tweaking
Yeah.. I think I'll stick to the tweaking for now and avoid the tweaking..
daveraven said:
Hello,
I know you're all very knowledgeable, so I need your help!
I turned off my diamond last night when the battery was running out and since I put it back on charge whatever I do I can't get into it.
Edit: It's actually the T-Mobile version MDA Compact IV but with Manila TF3D and skin.
It starts up, says windows mobile etc. then it gets to the phone lock screen (which is always a bit laggy) but I can only manage a few digits before it locks up and completely freezes, then I have to do a soft reset or remove the battery to even turn it off.
I've tried everything, even typing the password as fast as I can, but I entered the wrong password too many times and now it's asking me enter a series of letters and numbers before I try again (which would be ok if it didn't lock up by then).
What can I do!?
Daveraven
Click to expand...
Click to collapse
I had a similar thing and had to remove the SIM and refit....I got mine replaced and have since flashed SwiftBLs rom on the replacement to get rid of all the horrible t-mobile, slow and buggy 1.37.x.x rom......even though they claim everyone is happy with the device.
Ahh .. right - may have to try that SwiftBL ROM then, haven't tried flashing a new ROM yet, will have to read all the instructions etc.
Apart from the pinkness, the original one doesn't bother me too much, I find it pretty fast - especially compared to when I installed the Manila TF3D - it was really slow after that!
** By the way - I've just noticed that since my Hard Reset the weather cannot update it says it cannot connect! What is wrong here? I can get onto the internet but not download the weather!? **
Daveraven

Tilt unresponsive to anything (not just touch)

I have searched and found some thread's about this sort of this but not exactly the same problem. I am using GARMIN'S FINAL ROM which I must say it awesome. Stable and the fastest I have seen yet but I am still have one problem, at certain point's my phone doesn't respond to touch, clicking of the front key's and even sometime I have to press button's on the keyboard 3 or 4 time's just to get it to type. I thought it could just be lag but even when I give the phone a few second's to do it's thing (load fully) it doesn't work properly? I mean even sometime's when I press the end key the friggin button's don't even light up.
I hope there is some help because I just got the Tilt and it seem's like a great phone but this is just getting to be stupid.
Thank's ahead of time.
i have the same issue with hyper dragon rom. and no, im not running any programs, memory usage is 48% (running nothing) however the screen wont respond to touchs, the keyboard wont respond etc but the cursor still blinks, animations still play etc.
ive already tried all of the "keyboard" fix's, adjusted the settings manually etc yes i calibrated the screen multiple times *waits for somebody to reflash even though i did that *
I was having that problem and I found the only way to workaround it was to re-align The screen in the Start>Settings>System>Screen menu. But, I have not had it since installing SJ's 15 November 08] HyperDragon III Raphael version here
http://forum.xda-developers.com/showthread.php?t=397121
I strongly recommend it. All you need to do is remember to install Opera 9 last per Notes at the top of the post.
Hope that helps.
I am going to try that out, it look's cool but it look's like there is way to much stuff for it to run fast? Also if I don't use Opera I don't need to install it correct?
bump! Any other idea's?
I have the same problem but mostly notice it when the phone comes out of sleep. The phone will work right then slow to a stop and not allow any input via the screen or keys. 10 seconds later it's good to go.
Edit
OK the fix I can confirm that woks is that you have to sim unlock your phone with the newer 6.1 roms. I did it and it completely fixed my lag problem. Use the kaiser unlocker to do it and it can be found with a simple search. Make sure you have a the right SPL and newer radio to make sure everything is compatible.

Slow boot up : 1min48

Hi guys,
I always found that the diamond was very slow to boot up... and I just considered it a lost cause....
Just to be sure, can you confirm to me that you have the same timing during the startup ?
Once I switch on the phone, and I feel the vibration, it takes 12 seconds to go from the "HTC Diamond screen" to the "HTC Diamond w/ firmware;radio version screen", then I have to wait for 20 sec to get the Windows mobile startup animation.
So I loose 32sec at each bootup just seeing this damn black HTC Diamond screen.....
Then at around 1min10sec I can see the Start menu
and finally, at 1min48 : SPB Mobile Shell appears and I can use my phone !
(Maybe my phone is slow down a bit by fingermenu and fingermsgbox... but it is still long, don't you think ?)
Thanks for your feedback.
Btw, I had a Touch Diamond 2 in my hands yesterday, and it was much more faster (for the first screen and to reach WinMo). I've also seen he has a kind of fingermenu/fingermsgbox integrated, it is only with the new manilla or is it system wide ? (i.e. even for the WinMo menus).
My Rom is Dutty rom 5.2.20764.1.4.3_V4
my hardspl is SPL-1.40.OliNex (it is maybe because of the hardspl that I have to wait so long at the first Diamond screen).
mine is slow too, I think it's normal !
HardSPL 1.90, rom netDrg 2.8
A startup : showcase, X menu and PocketShield
but I reboot my phone only about once per week, so time to boot it's not important for me
I measured mine. Startup time is important for me as I shutdown my phone every night.
0s Start ("Vibration")
~11s Boot Loader Screen
23s htc
33s WinMo animated
38s WinMo start and a bit later "TouchFlo 3D getting started"
53s Phone is usable
For ROM version see my sig. I disabled the dialer skin and the one or other service. I'm using pBar as "task manager".
I think I'll go first with the 1.93HSPL instead of the 1.90. Based on your timing, it should help a bit.
fwmone said:
I measured mine. Startup time is important for me as I shutdown my phone every night.
0s Start ("Vibration")
~11s Boot Loader Screen
23s htc
33s WinMo animated
38s WinMo start and a bit later "TouchFlo 3D getting started"
53s Phone is usable
For ROM version see my sig. I disabled the dialer skin and the one or other service. I'm using pBar as "task manager".
Click to expand...
Click to collapse
uh oh... 1.93 is faster, that's the good news !
the bad news is : WinMo reinstalled by itself !!! Wtf ?? I thought it was just the loader !! Oo
Is it always like that when you change the hardspl ??? didn't know :|
megosu said:
I think I'll go first with the 1.93HSPL instead of the 1.90. Based on your timing, it should help a bit.
Click to expand...
Click to collapse
I absolutely don't know but when thinking about it, I had the same. After flashing 1.93, my original ROM restarted from the beginning.

Solutions to charging and standby freeze?

Hi! For a while I've been searching for a reason why my phone seems to freeze almost daily while charging or before / after I snooze a morning alarm. And sometimes during the night, maybe it's random. By freeze I mean the phone is sleeping and when I push the power button nothing happens. The only way to restart it is to take off the cover and either remove the battery or press the little reset button.
I use itje's ROM with standard WM6.5 and Manila 2.1. I tried diferent builds and newer Leo ROMs, but I always get the same problem. It didn't happen some time ago when I was using WM6.1 + Manila 2.0.
While searching in the forums for solutions, I noticed there are some users with the same random freezes using various ROMs from different chefs. But most of the users don't seem to have this problem, which is weird. I guess the hardware should be the same, so does anyone have any idea why this freezing happens only to some of us?
I tried different methods and ROMs, countless hard resets and re-flashes, even additonal Stock-SPL and Hard-SPL, but nothing seems to work. It even happens if I install no other programs and don't have the SD inserted into the phone, only my SIM card. So it's not from external programs (like G-Alarm) either.
Well, any helpful information or advice? Thanks!
I am experiencing the same problem. If anyone got a solution for this, please share.
Regards, Eduardo.
i have the same problem to but only with the cooked wm 6.5 roms and higher not with the rom that came with my x1
i get the same problem. i'm using itje's Touch I-T Xperience 15 6.5
Now I flashed a WM6.1 ROM with Manila 2.1 to see if I still get the problem. Do you think our phones have a problem with the Windows 6.5 builds or maybe the problem is with Manila?
Did anyone try to live with one of these ROMS for a few days with Manila disabled to see if you still get the freeze? Maybe I'll try this also after I finish my 6.1 test. It's very annoying that we don't even know the cause for this freeze yet...
have the same problem when using 6.5 but when on 6.1 nothing of the kind...
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Well, I can confirm that on various itje 6.5 ROMs I get the standby of death without installing any alarm program. I didn't install ANY programs, for what it's worth. And others can use G-Alarm 2.3 and don't get this freeze.
Didn't use Valkyrie ROMs yet. I'm testing now Touch X 10.8.2 and I have G-Alarm 2.3 installed. Let's see if it dies in the next 48 hours while on a 6.1 build...
Here is my experience...
I never got standby freeze issue(never used G-alarm/Klaxon), but i do get black screen or garbled screen issue randomly while receiving call irrespective of the ROMS(wm 6.5/6.5.1).
Only one time almost a week i didnt face this issue, then later problem repeated. So i realized that week i've used COM4 build. So for testing it i tried again same one for a week and problem didnt exists. Since the ROM which i used has default X1 dialer which i didnt like at all.. so got updated to other ROM and started face the same issue
Maybe some of us have a slightly different harware in our X1 that triggers this freeze, but only in WM 6.5?
So far the WM6.1 + Manila 2.1 is working fine, lots of customizations made by me after flashing too. G-Alarm managed to wake me up OK.
Darkchaser said:
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Click to expand...
Click to collapse
Well you can count Valkyrie 4.5.502 out because i installed it yesterday and this morning after my alarm went off about 20mins later the phone frooze. I have been experiencing this for the past months and i REALLY hate this phone now. I have tried all sorts of tricks from reseting the phone around 9pm to just not running ANY program and it still freezes. I have tried all sorts of roms with the exception of Touch X 10.8.2. I guess i might as well give that one a try. I will keep an eye on this thread for a solution.
On an older Valkyrie TR build I was getting the problem and I fixed it by doing a soft reset with the SD card out, waiting for everything to load up and run nicely, then inserting the card again. Went to the music tab and waited for it to load all my tunes and the same with photos. Didn't have the problem after that, but I was only on that ROM for about a week.
I thought it may be related to usb port driver issues in WM6.5, but it could also be the audiomanager in manila or some conflict between a WM6.5 process and a manila process.
Anyway, will be trying 4.4.81TR Valkyrie and see...
But the biggest question is why some (most) people never have this problem...
Never seen this problem on WCX 22001 Pure wm6.5 rom and I'm using it for about one month. I've installed many apps and my X1 works great with battery about 2-3 days using WIFI, BT, and all other stuff. No Manila - no problem in this case. It's an older build of WM6.5 but with newer builds WCX Rom users didn't complain about freezing problem or alarm issues.
So maybe it's Manila?
Today I wanted to flash Itjes newest ROM but I'll wait for solution couse my phone should wake me up today
Can program your phone Lockscreen has frozen the rechargeable device. Best before charging you restart your phone and not run any programs.
yes i get this problem too.. every morning my phone is off.... so it really needs to be looked into.. it seems to occur from more recent builds of 6.5..
i was previously using a wild child pure rom from about 3-4 months ago (6.5 early build)... this issue never happened...
then recently i upgraded to the V11 Unoff series and now it occurs.. and is obviously occuring for a lot of people with other recent builds of 6.5...
if the solution is ever found please let us know....
I might be completely off here... but I used to have this problem often, in addition to having slide to unlock malfunction on me, even with the newer rom builds.
When I unchecked the boxes that said display owner information/notes when device is turned on, both problems were gone - it might just be a coincidence though and I've only been testing it for 2 days.
Hey guys,
I've been having the same problem, only that this are the situations in which I faced the issue with my X1i (and managed to replicate the freeze):
-Receiving SMS while charging (no pc conection)
-Charging while alarm goes off (again no pc)
-When task or appointment announcement sets itself to sleep (i.e: you ignore it) while charging. (go figure, no PC)
-When after ignoring (not hitting dismissed button) task or appointment screen shuts off (Running on battery)
I've also gotten the problem in other situations, but i couldn't replicate them. The only Thing I did notice was that there is a growth in the rate this happens over a span of 3 days after flashing/hard reseting. In my case, it was one increment per day (ie: 1st day, happened once; 2nd day, twice; 3times the 3rd day.. then, i reseted or replicated, so my statistics went down the pipe )
Other thoughs: what radio are you guys using? maybe we can narrow it down to a radio as well. Thus far I've seen it narrowed it down to Manila 2.5, but then others do not have this (and then there me, with Manila 2.1, that has it ). I changed my radio y-day and hasn't happened yet (xing fingers though...) wil try to replicate tomorrow after my alarm wakes me up
My info:
X1i Black (came with R3 generic UK ROM, Radio. 1.14...)
Issues happened with: Radio 1.10.25.18 (Installed with NRG's ROM vOCT 28)
ROM info: (see signature..)
Manila: v2.1.191...
Current radio: 1.14...
Carrier: AT&T US
I tried to contribute as much info I could get about this issue... hope we can get it solved.
I'll try to flash again a WM6.5 version to see what radio will be installed. This week I needed my phone WORKING , so I used a 6.1 ROM.
I didn't find a pattern for my freezes, but I think it mostly happened while charging from the outlet, or in the morning before the alarm went off (very bad thing to happen), or after I snoozed the alarm (again, very bad).
I read somewhere that it's useful to format your SD card before flashing. I don't see how this could help, but I'll try to flash via USB or from another newly-formated SD card. I always flashed with kovsimg.nbh on the SD root and I only formatted it when I got the phone, 9 months ago...
Also, some say it's good to flash first an original ROM, hard reset, then install the custom ROM again. I tried that, even stock-SPL and hard-SPL again, but didn't seem to work. Maybe I had 48 hours without freeze, but then it started again.
@8SE8 - I never had those options checked, so we can rule that out I guess.
I have been reading about this issue here and in another forum - mainly
because I had seen it only one single time. It actually occured when I was
loading the device during the night. I do not remember which ROM it was
exactly, except that it was an itje ROM with Manila 2.5.
Then, I went back to Manila 2.1 and WinMo 6.1, Touch_X 10.X.X. Must say,
that is still my fallback ROM, it feels extremely fast, it is stable, memory
usage is low - what else to wish?
Next, I went to the multilanguage Rhodium based Manila 2.1 and WinMo 6.5
from itje in my own language. After installing FM Tuner, a correct dialer and
some tweaks, it is also very fast and stable, memory usage at 50%. No more
soft resets since almost a week now, no "stand-by of death".
The difference to others is maybe: I do not flash using the SD card, always
with the USB connection. Is this provoking the difference? I cannot imagine,
but this is what I can contribute here.

WM6.5 Manila 2.5 Roms & Lockups

Hi Guys,
I suppose one good thing to come out of me constantly finding my HD dead after it being on standby for a few hours (it seems intermittent) is that it seems many others are having similar issues.
Can people post their findings to the following question so we can help the community at large narrow down the issue:
When your device hangs/freezes, is it in standby or in use?
If the unit is in Standby, are you using Manila 2.5 or an earlier version?
Which WM version are you using? (6.1 of 6.5)
Have you unticked the "Today timeout" on the Today Settings screen?
My experiences are as follows:
I have only seen this since I have been using a 6.5 ROM
I have only seen this since I have been using Manila 2.5 (i think)
I install only a small number of applications
I have used both MyPhone and PIM Backup to restore info
oh and finally, it's bloody annoying!!!
If anyone has any information as to what could be causing this please post. I'm sure we'd all give our left nut to get this fixed?
This does seem to be an issue that effects some and not others, I had it happen a few times but after flashing back to an official ROM then back to custom (including SPL) I have using custom ROMs for a while now without this occuring again.
Flashmore, thanks for your input. Can you state what steps you followed for others?
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
xboxhalo said:
Glad to hear someone else is also having the same problem, and that it doesn't sould like a hardware issue.
I have recently been trying to figure out what is causing the lock-ups.
It doesn't happen with WM 6.1 roms.
Always happens is standby, with screen off I think. Nearly always when charging and power off then on using power buttin.
Seems to be happening to me wth WM 6.5 Manila 2.5 or earlier.
Nothing changed for the today timeout.
Using apps that come with rom, nothing extra.
Going back to WM 6.1 until a cure is found.
Click to expand...
Click to collapse
I'm attempting to systematically find out what the problem is by installing the same programs each flash with the exception of one. The first attempt was to move back to Manila 2.1 - so far so good but I'm expecting the same to happen at some point.
I want a good ROM, but I'm more bothered about not missing an emergency phone call because my phone is dead!
Hi all.
I'm not sure if this is actually related since when I experienced these so called "lock ups" my phone hard reset and corrupted the SD card as well. This happened two times with HD and once with Diamond2. Both phones with WM6.5.
I'm using corporate exchange and get enforced a device lock policy. I noticed that each time the device froze it was displaying the "classic" device lock number keyboard although the "default" (the new wm6.5) lock was selected.
Anyway, both phones have been working perfectly with WM6.5 and manilla 2.5 after I have started to use the ugly "classic" lock screen.
E
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
gallegus said:
i think this is a conflict about the option ''turn off the backlight'' if you disabled it (on battery power and on external power) the problem disappear. i don´t know why it happes but this is my solution (since the revision 9...)
Click to expand...
Click to collapse
That's interesting. I might try that.
I have been on Manila 2.1 for a few days and so far so good though.
I'm on WM 6.5 w/ Manila 2.1 for a couple of days and it has happened to me too.
I just tried disabling the options for turning off backlight and turning off phone. Hopefully this "fixes" the problem.
Check this thread, same subject, more details !
K
As said by Kostas66 above me. I guess this thread will soon get a lock...
As per post#10 & 11, please use this thread for future posts
Thread closed

Categories

Resources