Related
Following a couple of previous spontaneous hard-resets, my SPV2000's now developed a liking for it, and I've got a completely repeatable hard-reset issue...
All I need do is press the telephone "Green" button!
What's odd is that if, following the hard reset, I hit the green button after the PDA's started up, but before all the Orange McGuffery installs, the phone just pops up fine. Soon as the Orange stuff's installed, it's back to green=hard reset.
WTF? Anybody else had anything similar?
If that is the case, it would seem that something in your EXtRom is the cause.
I suggest you try updating your rom, or just generally cooking your Extended rom.
Instructions on working with your extended rom are here:
http://wiki.xda-developers.com/index.php?pagename=BA_RomKitchen
TheLastOne said:
I suggest you try updating your rom, or just generally cooking your Extended rom.
Click to expand...
Click to collapse
Is that as scary as it sounds?
BTW - I've just tried to demonstrate this utterly-repeatable behaviour and... it's working as it should. <cries, bangs head on table>
I had a problem with my first M2000 in that it wouldn't soft reset. Whenever I tried it would just stall and would take over an hour with the sim card out before it would work again.
Finally get a replacement and I found the rom was insanely old. After a couple of questions in the upgrade folder I *just* flashed the phone with the latest rom and a slightly modified extended rom. While it does look tricky, its not.
Look here for more...
http://forum.xda-developers.com/viewtopic.php?t=19354
xyon said:
I had a problem with my first M2000...
I found the rom was insanely old.
Click to expand...
Click to collapse
Thanks - I seem to be fairly recent, though :-
Operator 5.31.1.124
ROM Version 1.31.00 WWE
ROM Date 12/13/04
Radio Version 1.06.02
Protocol Version 1337.38
ExtRom Version 1.31.124 WWE
AdrianC said:
BTW - I've just tried to demonstrate this utterly-repeatable behaviour and... it's working as it should. <cries, bangs head on table>
Click to expand...
Click to collapse
And it's back at it.
The phone was ringing, I pressed "Green" to answer it, and got a hard reset. Restored the backup, pressed "Green", and got a hard reset.
This is getting VERY depressing.
Has nobody ever experienced similar? <whimper>
<UPDATE>
It gets worse! The f**king thing's now wiped my contacts and calendar in Outlook.
Excuse me, I'm just off to take to drink.
It would be worth you trying to upgrade the radio to v1.08.00.
My SPV had the audio problem and it seems to have cured that (tho I haven't re-installed much of the 3rd party s/w I had on there yet) so maybe it will help you too.
I upgraded to v1.10.00 initially (from v1.06.00), but couldn't get my wifi link to work properly. I then tried v1.08.00 and everything seems fine.
Me too, just started this week
I am also having spontaneous hard reset problems with my pda2k. I have been using it for about 6 months and for at least two months with all the sw I now have on it. When I press the power button to bring it back from sleeping it starts the "time to align your touch screen" crap. I am fairly sure it is NOT my ROM but in case anyone needs to know that:
ROM: 1.22.00 WWE
Radio 1.06.00
Ext ROM: 1.22.162 WWE
The only other remote possibility I can think of it some combination of the aftermarket 2200 mAh battery combined with the very high side seat bolsters in my new car. Perhaps I am twisting or stressing my unit in my front pocket when getting into or out of my car and that causes a momentary loss of contact with the battery contacts. I have tried to duplicate that with my hands but have not been able to. I guess I will not put it in my pocket for a while to continue testing. To the fellow who lost all of their contacts. I sympathize! That is why I set my ActiveSync to NOT actually perform any updates. I know many like the features of AS but it is not transparent, bidirectional enough nor stable enough for me to embrace. I use Sprite for backups instead and keep the data on my pda2k as "primary". Any more insight on such new and random hard resets is appreciated.
Good info on Himalaya forums also
http://forum.xda-developers.com/viewtopic.php?t=12802
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!
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
iluvgillgill said:
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
Click to expand...
Click to collapse
I use this rom with 1.51 radio till the rom is issued. I never had to soft reset because the rom crashed. The only really annoying issue i had is the bluetooth's one (Time to time, it is impossible to reactivate bluetooth without SR. This is why i do not desactivate it anymore ). We can always argue on choices, taste and colors but this rom is quite stable and fast enough for what i do.
EDIT: BTW check also which applications you have loaded. Did you reinstall a backup done with SPB after coming from another rom? I experienced many problems with that. Even if not pretty, i always reinstall now all my applications after installing a new rom (and i use pimbackup for calendar, contacts,... infos)
I have same problem too, thx
Post in Schaps 3.60 thread...
Not so as you think
I don't agree with that the ROM issue after call. Your deveice may be has some problem. What about bluetooth yes, there is some interesting moment that you select open bluetooth, it doesn't open, as soon as you mark to open you should restart your deveice, then it starts with opened bluetooth. BUt when you are going to turn the bluetooth off there is no problem.
I'm sure, Schap as a great moderator will solve this problems in next generation of his ROMs. The variation 3.60a (has posted), may be 3.60b, then 3.60c may be. Or he will post something interesting like Iphone platform.(I want him to do it)
iluvgillgill said:
it happen to me several times as i finish a phone call and go back to the Today screen but on the left top corner still display the title "phone".and i cant press it to open the start menu when im at the Today screen not even the start key works.try hold down the power button to shut down but no luck.but everything still works at the Today screen (weather,music plug-in etc)
had to soft reset it.anyone have this problem as well?or is it a radio problem?
Click to expand...
Click to collapse
I have the same problem too, what I have discover is that during the call and the screen is off (either it off automatically after a time or you press the power button) then anytime you power on the screen again in between the call or after the call in a short time the problem tiggered.
the only way you can 'fix' it is to wait until call end then off and on your screen once then the 'start menu' back or wait for an amount of time until the phone lock tigger (that one with number pad)
I said 'fix' (with quote) because this definitely a temporary solution to deal with this problem
hope schaps can get more idea in how to trigger the problem and can fix this soon
other than this issue, the rom is really very great
cheers.
To the OP,
If you are using a Hermes I suggest you reflash from scratch ie Schaps ver 3.6 rom, then use radio rom version 1.47.10..
Install ALL your applications from scratch, manually. DO NOT restore from a previous backup using, say SPB Backup; that will screw your installation. Make sure all your apps are the latest versions, capable of running under WM6.
Preferably install one app at a time, as you would anyway, then test the phone and make sure it is working before installing another app, and so on.
Don't install a theme changer or other similar software until you are absolutely sure your installation works. Leave the performance parameter settings as they are, ie at default.
If all else fails use the ROM combination in my signature below. Rock solid installation, no problems or crashes.
Let us know how you get on.
Cheers
WB
have same problem also has anybody found that if you use internet shearing and recive a call you cant hear anyone and phone searches for network
thankz,
jdc21
no crashing for me..
the rom is really stable.
apart from the bluetooth issue its really good..
really stable and fast enough..
works really great for me..
Thanks Schaps for such a great rom.
waiting for 3.60b
Take care that Phone Dialer Skin could cause this kind of problem
wacky.banana Is maybe right
I have Schap's 3.60a along with my trusty Radio 1.47.10
No BT Issue till now
I use BT also with DrYAR-Bluetooth 1.6 (Whoopy!) No Issues at all either starting or Stopping BT
I'm using It for two days now It's OK
Did I mention that this rom Is even FASTER than the previous 3.5x?
i hav the same problem
When did this problem start?
I didnt have the bluetooth turn on just using it normally.and all application i install is fresh onto the phone memory.never install any program on the SD card.about the dialer skin i use Schen Kaiser 3G dialer.
Anyone got fix yet?
Same issue, not just Schap 3.60a
massimo729 said:
When did this problem start?
Click to expand...
Click to collapse
I've had this same issue for weeks now, ever since the newer ROMs have come out for the official releases (i'll have to track back the build numbers). I had it with Sleuth's last release, the vp3G 3.0 release, and now Schap's 3.60. I've done what other posters have said and hard reset, not loaded any apps, and still have the issue.
I believe I have tracked it down to do with X-button, as that's one of the few apps that is installed without customizations in both Sleuth and vp3G (and I run it in Schap 3.60a). My next step is to run vp3G 3.60 lite, without X-button, and see if that really solves my problem.
edwinyuen said:
I've had this same issue for weeks now, ever since the newer ROMs have come out for the official releases (i'll have to track back the build numbers). I had it with Sleuth's last release, the vp3G 3.0 release, and now Schap's 3.60. I've done what other posters have said and hard reset, not loaded any apps, and still have the issue.
I believe I have tracked it down to do with X-button, as that's one of the few apps that is installed without customizations in both Sleuth and vp3G (and I run it in Schap 3.60a). My next step is to run vp3G 3.60 lite, without X-button, and see if that really solves my problem.
Click to expand...
Click to collapse
As a follow-up, I went to VP3G 3.60.1 install, ran the base install with nothing else installed and still had the problem. Still, the workaround suggested by others (putting the phone in standby and coming out) fixes the issue for me.
Hey guys,
First of all, thanks to all the cooks, etc. on this forum - you've made my phone into a fantastic gadget instead of just a good one...
Unfortunately, I'm now having issues with my Orbit.
I've flashed various ROM's to the device over the last year, B&B, Bepe, Meschle ROM's all without a problem (few bugs as others have reported but nothing odd).
Recently my Orbit started crashing (frozen, no reaction to touchscreen or buttons), seemingly when I twist the case slightly or squeeze it slightly (the sort of thing which happens when the phone is in a jeans pocket etc.) Anyway, what appears to be a physical fault...
Sent back to O2 for warranty repair. When it came back to me, it looked like nothing had been done except to flash it back to WM5. (I left the official O2 WM6 on it when I sent it to O2)
Now I cannot get it to crash under WM5, but as soon as I flash ANY WM6 ROM to it, the crashes reappear. I've tried downgrading the Radio ROM to see if it's that, but no luck.
Any ideas what this could be guys?
If physical movement causes a crash it has to be hadware related. The fact it does it with WM6 is just a red herring.
I have the same problem after upgrading my P3300
pnyg
I would agree with you Danny that it's hardware-related, but I CANNOT get it to fail under WM5...!
Is there some part of the hardware which WM6 uses but isn't used in WM5?
I was also wondering whether it has anything to do with the SDHC as the first set of WM6 ROMs I flashed to the device worked perfectly well.
I've also noticed that my friend's Orbit has a white-coloured Rollerball but mine is a darker colour. Do I perhaps have an early model? Which perhaps can't handle SDHC?
Yeah, yeah, i know, have a lot of it on the forum, but, until now, i didn't find any real answer about it.
Sometimes i read that isn't hardware problem, sometimes i read that is.
Sometimes i read that need to change some keys on registry, but what keys?
The problem is the same of other users: the green and red key, videocall, Windows, Ok, "the left and right software buttons", the IE and Message buttons doesn't work. And the diretional buttons, the first time i press when i turn on the Hermes open the browser.
I don't know what to do anymore. That phone already stayed at the HTC Support for 3 months, and came back with the same problem. BTW, the HTC Support is a @#&ยจ%$$!!!!!
OK, atleast try a different ROM first, ie schaps or pandora naked???
IF it works on the newer ROMs then theres your answer.
Is the device a Tytn, Vario II, 8525 etc..?? ie let us know which brand it is.
I've tried a lot of ROM's, but not the newer ones. I'll try today. I'll try Pandora Naked and Schaps, in this order, and will post the results.
My device is a TyTN.
Tried the both ROM's (Schap's and Pandora) and still have problems with the buttons.
Hardware issue, suggest a 3rd party repair facility??
mrvanx, i've read something about the registry. Changing some keys in the registry i can solve this problem? Is there anyway to be something like that? I think, in a hard reset or a ROM change, the registry goes to the original situation. Therefore, if was a registry problem it'll be solve doing that HR. Am i right?
Like i said, it already stayed on the HTC Support for almost 3 months and they do NOTHING about it.
Anyway, thanx Mrvanx, i think that will be the solution.
Sounds like you're out of luck. I'm using an AT&T 8525 with WM6 and excluding the d-pad, all of the front buttons do not respond. The bug appears to be in the software since I, along with many of the other with this trouble, have attempted the hard reset are able to do so successfully (which requires holding down both of the soft menu buttons under the screen). I have also tried the hardware solution posted by another user and it was not successful with my device. Thanks for the remarks regarding HTC. I'll avoid sending my device to them.
Scg033, good luck. I'm trying to take my friend's TyTN and checking the registry. The seller insists that my problem is not a hardware problem. This is my last chance to try something. I'll try today and will post the results, anyway.
Well, i've tried to look into another TyTN's registry and made mine exacly like that one and... Nothing Happens. Still having problems. I think it's not a software problem.