Related
I've bought lightly used T-MobileSDA II(US) -HTC Tornado!! It haven't any tracks of taking apart under the cover!! But when I take away battery even for a few seconds my time and date are missed to date of making the phone.....maybe someone knows what to do with my phone??? I think trouble in backup battery!! but what happened with it?
I'm not sure about the SDA, but the Cingular 2125 with WM5 did the same thing and I think that's normal behavior. If you flash up to a WM6 or WM61 that problem goes away as the date and time are set from the carrier.
tonyzoc said:
I'm not sure about the SDA, but the Cingular 2125 with WM5 did the same thing and I think that's normal behavior. If you flash up to a WM6 or WM61 that problem goes away as the date and time are set from the carrier.
Click to expand...
Click to collapse
... not for me! I had this issue with standard WM5 ROM. I then upgraded my ROM to WM6.1, but if I remove the battery, the time and date are still reset to original ROM date. So, no change from original ROM as far as resetting time and date is concerned.
I wouldn't call it a problem though. Sync your phone with your PC and within seconds, the time and date are set to the present, so it's no big issue... just a bit annoying!
I'm thinking your phone doesn't have a backup battery.
I know mine doesn't.
I don't think it has anything to do with the OS.
mikolopatamys said:
I've bought lightly used T-MobileSDA II(US) -HTC Tornado!! It haven't any tracks of taking apart under the cover!! But when I take away battery even for a few seconds my time and date are missed to date of making the phone.....maybe someone knows what to do with my phone??? I think trouble in backup battery!! but what happened with it?
Click to expand...
Click to collapse
Thats a known problem with Tornado's. When new, the backup battery keeps time for a few minutes after you remove battery, after some short period of time(in my case about 2 months) it stops doing that. However, its not a dead backup battery. Run Celetask, go to TOOLS... POWER STATUS... and notice that Backup Battery status is HIGH, 255% 0mV.
My personal conclusion is... WM6 on Nitro's ROM has some script that tracks and saves "last known time". When you remove battery and power up again, it reads and displays that "last known time". Notice that if you leave it w/o battery for a 10 minutes, time will be 10min off. However, if you enable the "Automatic Time Zone" under the time settings, it will sync time with service provider(if they have that feature).
Not sure if other 6.0Roms do that to, its why I'm asuming its a tweek or script by Nitro.
Now, going back to that Power Status... Shouldn't HIGH be 100%? 255% would be over charged? 0 mV = 0 power? lol Ok, someone pull out the backup battery and messure voltage on it ) I'm not responsible!
yeah! celeTask show that. if i wouldnt sell my Tornado ill try to upgrade it to WM 6
Replace back up battery
I think your SDA needs a new back up battery. But, you will have to dismantle whole SDA before you can see small, steel color flat battery right behind key pad. I remember seeing somewhere on the net on how to dismantle SDA to replace keypad/broken screen!!
The same thing happened to me. The first few months I had the phone, when I took out the battery, the time didn't reset. But after the few months, it would. I assume it is due to an internal battery gone dead.
There is a solution however, when I upgraded to a wm6 ROM, it fixed itself. It adds a feature where the time is automatically updated from the network, so I no longer have any problem with the time
That being said though, when I posted this before, someone else said it had to do with the tornado radio update, and not installing wm6 specificly. Anyways, if you update your ROM with the IPL, SPL (spelling?) and wm6, it should work beautifully again
I have a T-Mobile SDA too, I think it's name exactly "Tornado Tempo" (it has 3 media buttons and 1 button for Internet)
And I wonder if these buttons will work when I flash the ROM to WM 6.1, what kind of ROM should I use? Can I save the original ROM for backup (tell me what software to do it)? Thanks alot ?
Hey folks,
I have been having a lot of problems with my X7510 lately. The screen keeps locking up in standby mode. When the device is in standby I turn it on and it prompts me for my password. After putting in my password I just get a black screen with the word "password" at the top. While the device is in this state I can still sync (and see all of the files on it) when I connect to my computer. The screen on the device, however, is locked up. This problem has been happening several times a day lately and I cannot receive calls when it happens (nor do I get any indication of missed calls). The only way to get the X7510 to work is to do a soft reset.
At first I thought it might have something to do with the password manager, so I turned the password off today. A couple of hours later I found it locked up anyway. When I pressed the power button it did not come on at all, though the GSM and BT/WIFI lights continued to flash.
Is anyone having this issue? Were you able to figure out what was causing the problem? I am very frustrated right now. My device locks up so much that it is practically unusable since I have to do a reset 2-4 times a day.
Yes- I'm seeing the same issue from time to time. Haven't had time to investigate yet.
Last time it happened was yesterday- Green and Amber lights were flashing, but all buttons unresponsive, and had to do a soft reset.
Running PocketPlus 4.03 as a front end.
That is probably a software issue. Better enumerate your softwares and find out the common one causing it. Usually start with the last one you installed prior to having the problem.
cktlcmd said:
That is probably a software issue. Better enumerate your softwares and find out the common one causing it. Usually start with the last one you installed prior to having the problem.
Click to expand...
Click to collapse
I agree it's definitely a software issue. The only recent addition for me has been Spb Keyboard. PP4.03 has been on since day one, and did not initially seem to be associated with lockups.
When I have time, I'll try and narrow it down a bit.
I have not installed any new software in over six weeks. The only thing that has changed in the last week is an update to IM+. I have uninstalled it completely and will see what happens. If this fails I am not sure what to do.
LocoHarami said:
I have not installed any new software in over six weeks. The only thing that has changed in the last week is an update to IM+. I have uninstalled it completely and will see what happens. If this fails I am not sure what to do.
Click to expand...
Click to collapse
Just for the record, I don't use any sort of Instant Messaging!
With my Advantage on the ultra-extreme blinks I suffered the tortures of the damned, tortures of the damned. No less than once every couple of hours I'd find my device locked up. Upon direction from my kind forum mates, I decided to uninstall the last software change on the not-so trusty X7510. After removing the IM+ software the PDA still locked up two more times that day. I gave up hope and decided to do an hard reset.
The next day, however, it did not hang up at all. The same goes for today, so after locking up five times a day for a week I have not locked up once in the last 48 hours. No hard reset and all is viddy well, little brother, Viddy well.
Unsure if it was the IM+ update or not, since it locked up twice after the uninstall, but I will not be reinstalling the IM+ update. In the name of science, I will install the original version this afternoon and see what happens.
Most gracious thanks to all those who took time out to reply to this thread.
I can concur that 3rd party software running in the background is usually the culprit.
In my case, I'm having an on-going saga with Hebrew localization bought from P.D.A.C. If I put the device to "sleep", with the email program set to download every 15 minutes (via wifi - no SIM installed), I come back to find a device that will turn on when the power button is pressed (a bit longer than usual), but then no response from any hardware button or screen - a soft reset via the hole in the back is the only way out.
I can in general say that the localization has other problems, like slowing the device down, and generally causing unpredictable hangs, but I'll save that for another thread.
To their credit, PDAC have taken a stab at trying to fix it, but since they don't have (and apparently don't intend to purchase) an HTC 7510 for testing, it's become a slow, hit-or-miss proposition.
One of the problems for gadget fiends like me who are not programmers is choosing a device that isn't massively popular - the support by third-party developers is not adequate. So here I find myself trying to learn how to fix what should work properly out-of-the-box.....and being frustrated by lack of background/knowledge.
-avi
Had this lockup problem since i received the device.
The other week in an attempt to fix this i have flashed to the latest 3.29 Rom from cmonex (thanks!) with ExtRom 3.29. As i have a Chinese x7510 version this ExtRom has fixed Opera text block problem, but still had constant lockup after putting unit into sleep mode.
Yesterday, i tried option 'Do not lock buttons' in Key Lock under Settings. Since I have not had one single lockup! Even having in sleep overnight, hit power button and up pops today screen. Normally i would have to soft reset.
This is what i have done so far. I'll have to start installing apps and see how it goes...
G'day from LA
Hi AvantX,
Another Aussie here, but living in LA for the last 7 years.
I loaded cmonex's hard SPL on to my x7510 some time ago, but so far I've been loathe to load an other ROM on to my x7510 as I have been unclear on the return path to the stock rom in the evet of a mishap. I've been hoping to see some ROM development on this forum similar to Kaiser & TyTN but so far we have not seen too much, other than the promise of AP4 amd MichyPrima's ROM somewhen.
Can you show here some screen shots of the 3.29 ROM? Does it look the same as the stock ROM and how does it run compared to the stock ROM? The stock ROM is 3.27.405.3 - is 3.29 an improvement? Does loading 3.29 affect the radio - mine is 1.58.
Thanks mate in advance.
So I flashed my phone to the HyperDragon III ROM a few months ago. Everything works smoothly and I had no problems at all. Only small issue was the keyboard lag and that issue was addressed in a separate post.
After using the Keyboard Lag fix, my phone does not fully load. I get to the splash screen and everything and then the Start Bar loads as well as the bottom Calender and Contacts menu. The screen will display my background and it will say "Tap Here to launch TouchFlo". I tap there and nothing happens.
I've been patient and I let it sit there and nothing happens. I can get to my text messages but it runs unusually sluggish and will display an overview of all messages but when I try to open a specific message, it freezes up.
This is actually the second time this has happened. The first time I removed the Keyboard Lag CAB but the issue continued. I left the phone alone and reset it a few times and miraculously it started working fine.
I have since removed the Keyboard Lag CAB completely yet it has still happened. Anybody else have the same problem or have a solution? Any help would be great.
Never flashed HDIII rom's so I have no idea why you are having that problem. Have you already post this issue on the rom's threat?
not-available said:
Never flashed HDIII rom's so I have no idea why you are having that problem. Have you already post this issue on the rom's threat?
Click to expand...
Click to collapse
Not on the HDIII thread. I did originally post my problem on the Keyboard Lag thread. 10 minutes after posting the first time my phone went back to normal so I went back and edited the post.
So try it on the HDIII threat. That's the best where you can get help related with that rom.
Also, maybe some other user had already that problem and have some solution or is waiting for some. Ah, before post the question, that some time to read the full threat... your answer can be already there.
Thanks. I just figured I would post. I've been reading the thread for a while now. Its over 900 pages so I thought I would ask first
You can also try to do a search on that threat http://forum.xda-developers.com/showthread.php?p=3102963&nojs=1#goto_threadsearch
Happy New Year
So my phone just started working again. After about an hour or so of resetting and stuff it displayed Lauching TouchFlo and its normal again. I'm just afraid to ever turn it off again.
did anyone solve this problem?! cause mine just randomly stopped launching touchlo and I dont know how to get out of it?!
Closing thread
Please post issues with HyperDragon rom in the HyperDragon thread, instead of opening new ones.
Peace,
Joshua
My keyboard was working fine all this while until about 2 weeks ago it starts to act up. When I press the spacebar, sometimes it will create double spaces (instead of the usual one), and sometimes, it wouldn't work at all (meaning no space is created).
Does anyone else have this problem?
And just wondering, I have flashed my TP to ROMeOS, so if I were to claim warranty, does that mean I'll have to re-flash my TP back to the original firmware?
Bump - I really need some help.
Bump again! Mine is doing this at the moment. Stock ROM. UK Vodafone.
As far as going back to get it fixed by someone, yes, you would have to go back to stock SPL and stock ROM. It sounds like a pretty strange problem. The only thing I could think of is that you have some particles stuck underneath the space key since it's acting s erratically.
same problem here. I don't think that it is particles under the keyboard as that would not explain the double spacing issue.
I only noticed it on the R2A rom, don't remember it being there on the R1 so prob a rom issue.
I have this problem too
Figured I'd give this a good Ole Bump, because it seems that, although not widespread, it's still an issue. I'm running the Latest 6.5 ROMeOS on my Fuze and am having the SAME problems mentioned in the first post. I remember reading in Da_G's thread that there was something corrected in his ROM by using a custom xT9 dictionary? Anyone have any input? I'm (almost) positive this is not hardware related. It seems to be tied to the OS. Thanks in advance.
me too having the problem as well, i've it for more than 1.5 months i think, and no one having this in the earlier day which no one can help me out with it, but this few days i think i manage to solve this problem already, which i think it actually is a hardware issue, i used to use my right thumb to press spacebar and the problem occur, but since few days ago i try changing it to use my left thumb to press spacebar, who knows, the problem did not come to me since then... maybe you can try this, if not, i think you might gonna sent it back for warranty... hopes this helps...
I'm almost positive it has something to do with xT9. I just used a cab from my tilt days to disable xT9, and its happening FAR less than it was. But its still happening lol. Even with the regular stock non-finger-friendly keyboard set as the SIP. Back to the drawing board.
Well, I'm not sure if everyone else has read and figured out the problem, but it is now known what causes the spacing issue.
Apparently the newest builds have changes to the compime.dll file. These changes are what is causing the spacing problems, and (so far) can only be resolved by using the compime.dll from build 21731 or earlier. So how do we fix this
I know that Da_G has a package in his kitchen to change the dll back to an earlier one, but for the people that are using already cooked roms, what do we do?
djcaston said:
Well, I'm not sure if everyone else has read and figured out the problem, but it is now known what causes the spacing issue.
Apparently the newest builds have changes to the compime.dll file. These changes are what is causing the spacing problems, and (so far) can only be resolved by using the compime.dll from build 21731 or earlier. So how do we fix this
I know that Da_G has a package in his kitchen to change the dll back to an earlier one, but for the people that are using already cooked roms, what do we do?
Click to expand...
Click to collapse
If that's the problem, then this post might help you.
EDIT: But someone noted this problem with their stock ROM, which suggests a hardware issue, not a ROM problem.
I thought I'd post this since clearly I'm not the only one who suffers from this problem. After 6 months of living with this problem, I've decided to flash back to stock SPL and stock ROM and sent it to SiS for repair. They replaced the keyboard, and in just 2 days, I got my phone back (talk about a speedy repair!).
I don't know about you guys, but I'm almost positive mine is a hardware problem. I'm now using a WM6.5 TF3D2 ROM by shep211 and the keyboard seems to be working perfectly.
-accidentally double posted-
i got the same problem.
spacebar sometime can press sometime cant.
i think is hardware problem
anyone can guild me how to open n repair it?
my touch pro is not under sis. too bad.
Mine's been doing the same thing recently. I'm *hoping* this is an os issue, but I'm using stock original bloat free rom.
My has also been acting up tho (goofiness with Opera, rare and seemingly random shut offs and freezing) so I was hoping that a flash to a cooked rom would fix it.
I'm planning on doing it this weekend, if I get around to it I'll post here on my results.
I had the same problem. Went to the AT&T store and got a new phone
I too have been having this problem. I have been using NRG's roms for the past month (no blame on them) and the problem started to occur. Whenever I texted i would hardly ever get any spaces and it would double space when i did get it to work. I found that if i went slower and pressed harder it would work fine, however this is not a good solution. So i figured it was a hardware problem so i put everything back to default for ATT warranty purposes.
This is where it gets weird, the dumb thing starts to work again. I thought it was pure hardware failure because i had to press harder, but now that problem was gone.
So now I am running stock ATT rom but it is starting to double space ALOT. However this only occurs in the text message box. If i open word and type it is flawless. So is there a glitch in the text messaging program?
same problem here... happens when texting in my browser, in forums, in sms msging, all over...
I have a Samsung Omnia with a WM 6.5 build, and I noticed a similar problem, regardless of which onscreen keyboard I use. Basically whenever I type a dot (.) or press the spacebar, the previous letter would get selected (underlined) for a second, before the caret returns to the intended position. Typing the spacebar in a browser would indeed produce 2 spaces.
I assume it's related to the input/dictionary suggest feature, yet dis-/enabling this feature in the settings doesn't fix the problem. My guess is that the dictionary somehow thinks that a single spacebar press is a correct word, which is automatically expanded to the full word (1 space), followed by another space to put the following word.
This issue surfaced at some point (the rom initially worked fine after a hardreset).
same issue on my phone
Hello there,
I'm using PPC's since more than three years, but I never experienced such a problem like this! I'll try to reconstruct what happened:
I was coming home with my Diamond Pro in my pockets and playing music over A2DP like I do everyday. I laid switched off my headphones and BT on my Raphael. Then I connected the charging cable because battery was already low. I realized that the Raphael did'nt respond properly and made a SR (via the hole). While booting I did something else waiting for the screen for entering the PIN, but then I had to see that there was a notification like this (on a german Raphael, I just translated it to english):
audiobooster_remain.mscr
The file "audiobooster_remain" couldn't be opened. It is either not signed with a trustable security certificate or one of its components couldn't be found. If the problem keeps existing try to reinstall or restore the file.
Click to expand...
Click to collapse
I have to add that I have this script (Tip #20 from here) in my autorun folder. There was behind of it the same notification for AEButtons Plus and my other autorun-apps.
But what made me wonder was the following:
The whole screen looked like the green HTC-standard design and then there appeared this screen with introductions and display calibration as we know it from hardresetting.
After that I was stunned and of course I knew that the Extended ROM setup would shortly follow. So i quickly made a SR although the o2 installation hadn't shown up until that. But after rebooting it did show up and let it do his job.
Since that everything looks like the standard o2 design and the named notifications show up after every SR. But what makes all this really weird is not the fact that all this happened automaticly and suddenly, but the fact that the device hasn't really hardresettet (although it seemed so because of the calibration and introduction screen and the standard designs)!
All of my programs are still installed and my modifications on the TF3D (e.g. I had deactivated all tabs but the music tab because I use Mobile Shell) still remained. But strangely enough my programs aren't anymore registered. Well, this alone would'nt be so bad, but the programs don't work like they should: e.g. I can't run the Mobile Shell, GScroll isn't configured anymore (as in initial state) and all the other programs (e.g. Pocket Plus) too. For most of the programs I have to confirm first before I can run the exe (e.g. Resco Explorer, which also is in initial state).
But it seems that the internal storage has been flashed, becaue the My Documents folder is also in initial state, my files aren't there anymore (but that doesn't really matter because I had the most of them on my storage card). To sum up, the Raphael really acts weird.
Something I almost forgot: There several times appeared another notification in between which I've never seen before:
It was white text on a black background (it filled the whole screen) and there stood something (in english) about that my device couldn't boot properly and probably should be hardresetted by pushing SEND and I did, but nothing happend. BTW: It wasn't the screen you know from hardresetting!
I don't know what type of screen that was and what all this is supposed to mean, but it's definitely weird! Does anybody know why this happened or does anybody know similar cases?
Of course I'm aware of the fact that flashing the device would probably be not a bad option, it would be an opportunity to update. I don't have a backup because till today everything went fine since I bought this Diamond Pro as a new device almost a half year ago. I don't remeber the ROM Version but I think it probably would be the o2-Version from a half year ago.
I really would be grateful for any good advice... Best regards