Related
Hey guys,
First post on the forum, so I hope I don't offend/irritate with my dumbass questions,
I successfully flashed to the Black Shadow IV rom yesterday. I installed all th e helpful cab files to restore my settings to the orange standard and got the skdcert fix for the voicemail quirk. All seems (seemed) to be running smoothly but I then stumble upon a problem.
I have found that I am resetting the device more than I should due to the fact that whenever I try to make a call, 5 times out of 10 the phone just crashes, all the buttons freeze up and the touch screen doesn't respond. On the odd occassion the buttons freeze but the screen still responds butr there's no way to drop the call. It just wont have it.
I upgraded to the Black IV shadow rom, but did not upgrade the radio which was out of the box at version 1.38.00.01. Could this be the root of the problem? I am running SPL- 2.10 Olipro.
Any ideas guys, you're the experts, I'm just a squirrel trying to get a nut.
Thanks in advance.
Gav
The 1.38 radio is pretty stable. However, if you are in the US, you might want to try upgrading it to the 1.40 radio which is AT&T optimized.
That ROM was released and is supported here: http://www.4winmobile.com/forums/htc-hermes/
Same happend to me too, I used Black Shadow IV for a week and now removed it, It is not stable.
My Jasjam hangs all the time and when conncting to PC.
Regards
Yeah, same. I used it for 3 days or so and crashed frequently. No additional programs installed either. BAD ROM
i've had nothing but a good experience with Shadow IV. ::shrug:: seems stable enough to me. it's never locked up on me and i've never had to reset except when i chose to to clear out the old memory once in a while.
as i mentioned in another thread, i have not installed any spb apps since they seem to have problems w/ WM6. i've had problems on a couple of different ROMs w/ the Spb apps.
could it be something that you've got installed and not the ROM itself? i had to do a little process of elimiation by installing basically one or two apps a day and seeing how it ran. things started going badly when the Spb apps were on there (Mobiel Shell, Time, Weather, Diary) so I haven't reinstalled them.
anyway, it could be something other than the ROM that is causing the instability.
regards,
mark
having multiple problems as well. cannot send text messages on cingular even after trying multiple fixes, frequent slowdowns, have had to soft reset at least once daily and also having problems with random lockups when charging. Going to reflash another rom.
having multiple problems as well. cannot send text messages on cingular even after trying multiple fixes, frequent slowdowns, have had to soft reset at least once daily and also having problems with random lockups when charging. Going to reflash another rom.
Am on Orange UK, and after running Black shadow for a while now I would rate it as the most stable ROM I have used. Admittedly I have only dabbled with some of the others, but have not felt the need to do more as am happy with what I have.
I did have an issue with SPB weather that others did not seem to have, but after romoving it, everything seems to be running fine. I soft reset every few days etc but I am happy with that.
Tis a bit strong to write BAD ROM with such certainty based on an individual experience, given that it works well for so many. Perhaps "This ROM did not work well for me" would be better.
Just a thought.
Sleuth255 said:
The 1.38 radio is pretty stable. However, if you are in the US, you might want to try upgrading it to the 1.40 radio which is AT&T optimized.
Click to expand...
Click to collapse
May be it is the radio rom, I have now installed radio 1.38 then Black Shadow IV and will try it for a few days and see how it works.
Also crash
Also crash and then back to Black 3.5 rom is Stable!
Still the same even with Radio 1.38, Crash when connected to PC and deep sleep in standby.
Use to have same problems while running CE-Star. Virtually permanently freezing on making/receiving calls, sending SMS and simple operations with the device.
After manualy setting chinese character set (thanks to XDA-Devs WIKI ) the ROM is extremely stable. Even trying to "destroy" the system with multiple operations (calls, internet browsing, sync, installing new soft, etc.) do not freezes it - very stable.
Suspect in your case you are using software which makes some changes to the system, consequently destabilizes the ROM
marttin said:
Use to have same problems while running CE-Star. Virtually permanently freezing on making/receiving calls, sending SMS and simple operations with the device.
After manualy setting chinese character set (thanks to XDA-Devs WIKI ) the ROM is extremely stable. Even trying to "destroy" the system with multiple operations (calls, internet browsing, sync, installing new soft, etc.) do not freezes it - very stable.
Suspect in your case you are using software which makes some changes to the system, consequently destabilizes the ROM
Click to expand...
Click to collapse
Hi,i am runing Black 3.0.1 and ce-star,like ou said freezing ,and my problem is when i use CE-STAR keyboard,it is Freezing too.where i can find the setting chinese charscter set?
thanks
Been running Black Shadow for 5 days, alongwith Radio 1.43, without any problem...
I've been running Black Shadow on T-mo US w/1.43 rom and I've had no problems.
I have been running Black Shadow since it was released and no problems so far.
chg1282002 said:
Hi,i am runing Black 3.0.1 and ce-star,like ou said freezing ,and my problem is when i use CE-STAR keyboard,it is Freezing too.where i can find the setting chinese charscter set?
thanks
Click to expand...
Click to collapse
Use WIKI and SEARCH funstion
You can go first to http://wiki.xda-developers.com/ and click on Hermes. After that use SEARCH function with keyword "chinese". Should get the following page:
http://wiki.xda-developers.com/index.php?pagename=WM5_Tweak_Language_Chinese
I am using for few days Black Shadow with 1.43 Radio, able to read Chinese Characters thanks to the described in WIKI method and no problems. Personaly I installed A4 input method as it serves me at best. I didn't change the registry manualy, but used the cab, it works perfect. Simply follow the instructions.
The only issue is that when serving internet with IE Chinese sites do not apear properly. Suppose it is needed additional fixing of the fonts in IE. Do not have time at present to explore the issue, but suppose to deal with it next week. In case you find a solution for IE please share the method on this thread-- Thanks
PS. Have tested Micrsoft Input -- simply do not works. Causes a lot of problems and destroys totaly the standard inputs
All,
I have been running this ROM for just under a week and the thing has been 100% solid - not a single problem.
I also agree with a previous statement in this thread, that to refer to the ROM as "BAD" based on a single attempt is somewhat unfair! Maybe it is this sort of thing that has forced some of the more senior Hermes developers away from this site and on to another location. Ever thought about it that way?
It is just my opinion, but we (all forum users) should do one of two things if we "chose" to use someone elses development. They are,
Acknowledge (privately or publically) the time and effort that has gone into producing something. The best way to do that is by constructive feedback even if the experience hasn't been as you expected
Say nothing if you can't make it constructive!
To place a one liner in a response with a "throw away" comment is about as useful to either the developer or the other forum users as.........well,..................no I won't go any further because it's not constructive
For the record - this version of the Black release has rectified a localised issue I was having with my WLAN that other version had not resolved.
If you chose to use it - great, join in. If not, equally great. Good luck with your chosen selection of ROM.
Rant end
marttin said:
Use WIKI and SEARCH funstion
You can go first to http://wiki.xda-developers.com/ and click on Hermes. After that use SEARCH function with keyword "chinese". Should get the following page:
http://wiki.xda-developers.com/index.php?pagename=WM5_Tweak_Language_Chinese
I am using for few days Black Shadow with 1.43 Radio, able to read Chinese Characters thanks to the described in WIKI method and no problems. Personaly I installed A4 input method as it serves me at best. I didn't change the registry manualy, but used the cab, it works perfect. Simply follow the instructions.
The only issue is that when serving internet with IE Chinese sites do not apear properly. Suppose it is needed additional fixing of the fonts in IE. Do not have time at present to explore the issue, but suppose to deal with it next week. In case you find a solution for IE please share the method on this thread-- Thanks
PS. Have tested Micrsoft Input -- simply do not works. Causes a lot of problems and destroys totaly the standard inputs
Click to expand...
Click to collapse
thanks a lot
Has anyone else had any issues with Tomtom Navigator 6 since upgrading to WM6 (offical SEA ROM)?
Under my old buggy WM5 ROM, it was perfect. As part of the WM6 upgrade I reinstalled it, and not it is unusably slow. It takes about 5 seconds between screen refreshes etc... you miss your turns by the time they are announced.
Does anyone know the cause or fixes? I've done a forum search and the problem has been reported on a couple of threads, but no real solution.
Some initial questions:
Under WM6, are people using the GPS manager in system settings? Or just pointing TT6 at the COM port directly? (What should the baud rate be set to?)
Is tngpseng.exe still required (never been entirely sure what this does exactly)
Does running it from the storage card (SanDisk 4GB) cause any performance hit? (I'm hoping not as my device memory is full)
The other chance I made is upgrading to the latest Australian maps. (Sinsis v675?) Are these known to be worse performance wise?
Does anyone else have Hermes, WM6 (official), TTN6, latest Australia maps working? can you post your settings?
Any help greatly appreciated!
Zilch said:
Has anyone else had any issues with Tomtom Navigator 6 since upgrading to WM6 (offical SEA ROM)?
Under my old buggy WM5 ROM, it was perfect. As part of the WM6 upgrade I reinstalled it, and not it is unusably slow. It takes about 5 seconds between screen refreshes etc... you miss your turns by the time they are announced.
Does anyone know the cause or fixes? I've done a forum search and the problem has been reported on a couple of threads, but no real solution.
Some initial questions:
Under WM6, are people using the GPS manager in system settings? Or just pointing TT6 at the COM port directly? (What should the baud rate be set to?)
Is tngpseng.exe still required (never been entirely sure what this does exactly)
Does running it from the storage card (SanDisk 4GB) cause any performance hit? (I'm hoping not as my device memory is full)
The other chance I made is upgrading to the latest Australian maps. (Sinsis v675?) Are these known to be worse performance wise?
Does anyone else have Hermes, WM6 (official), TTN6, latest Australia maps working? can you post your settings?
Any help greatly appreciated!
Click to expand...
Click to collapse
MrVanx's BT Receiver Setup
Works fine with me.
TT v6.201 (Build 7160)
OZ Map v675.1431
Zilch said:
Has anyone else had any issues with Tomtom Navigator 6 since upgrading to WM6 (offical SEA ROM)?
Under my old buggy WM5 ROM, it was perfect. As part of the WM6 upgrade I reinstalled it, and not it is unusably slow. It takes about 5 seconds between screen refreshes etc... you miss your turns by the time they are announced.
Does anyone know the cause or fixes? I've done a forum search and the problem has been reported on a couple of threads, but no real solution.
Some initial questions:
Under WM6, ....
Any help greatly appreciated!
Click to expand...
Click to collapse
Not related to WM6 but have you checked the number of Points of Interest that TT6 is trying to display. I use TT6 and have noticed no problems with WM6 so far - but regardless of ROM I found that unless I turned off the POIs that TT6 slowed right down and kept freezing.
Regards
tony.wheeler said:
Not related to WM6 but have you checked the number of Points of Interest that TT6 is trying to display. I use TT6 and have noticed no problems with WM6 so far - but regardless of ROM I found that unless I turned off the POIs that TT6 slowed right down and kept freezing.
Click to expand...
Click to collapse
Thanks Tony. I've turned them all off except the speed/red-light cameras and it does seem to have helped. (I won't know 100% until I take it out in the car, but it seems much faster at home on my balcony!)
The strange thing is I many POIs enabled on the previous install under WM6/older maps. Maybe the newer map is larger or something.
Does anyone know if custom POIs are more performance intensive than the build in ones?
I've had some kind of issue with TomTom since upgrading from Black Dymond (first to Magik and now to Satin). On the first upgrade I had to reregister my unit with my account to get access to my plus content (device ID change).
Now, I intermittently get a warning that it cannot find some file. I can't replicate it reliably and haven't had a chance to note the missing file. I suspect it has something with how TomTom is accessing info on the card.
My problem only presents itself when shutting down, so it's not a real issue for me. If it was, like yours is, I would first try increasing your caches. If that doesn't work, try going into the TomTom manager console when synced with the computer and remove everything (program, maps, voices, etc.) from your device/card and then reinstall it (make sure you have your disk or a backup, plus your registration code). If it has anything to do with lost file links, this should solve it theoretically.
I suspect your issues are due to either caching or lost links in TomTom itself, or both.
Tomtom has some problems with some wm6 roms not all.
My experience:
It worked fine with black dymond. No slowdown. No Problem.
It was painfully slow with black majik
It was OK with VP3g's v2.0 but after I added HTC home plug it slowed down considerably
Currently I am running latest Black Satin and TomTom runs just fine, stable, superfast, no freezes. This time I am going to stay away from HTC home plug.
You do not have shut down all of the 'nice to haves' (POI's) in such unnecessary and draconian fashion, quote "have you checked the number of Points of Interest that TT6 is trying to display".
Like Quist, I beleive the build of the ROM is much more at issue.
From my observations - Dopod / Black Satin / Sleuth's and Black Dymond are not at a problem.
I have noted significant refresh delays when using Schaps and Black Majik.
Good luck.
I've never seen TomTom run as fast as it does on my phone with vp3G's 3.0 WM6 rom.
I'm running TomTom version 6.100 (8330)
Im using Schaps 3.57a with TT6. So fast. Cold boot around 10s to 20s. Thanks
I'm finding I tend to have to do a soft-rest on my MDAC III about once a day, because although the phone continues to function fine, the radio (i.e. the GPRS/phone, not the FM radio) crashes. All appears fine, the device still works and has a signal showing on the bar, but I won't get any incoming calls, I can't make outgoing ones, and when I look at Activesync, instead of saying "Exchange: Connected", it says "Exchange: Last synchronised at 10:48am", which I guess is when the thing crashed. It's very frustrating because the only way I realise this has happened is when I notice that I haven't had any e-mails for a while.
One thing I have noticed is, working in London, I use the tube, and on my normal tube journey the train goes above and below ground, so the signal frequently comes and goes. The times it shows me I lost my ActiveSync Exchange connection usually corresponds to these times, so I think it seems to be that the phone loses the signal, but then never picks it up again (even though the top bar shows it's got a signal).
I'm currently using a WM6 ROM (3.7), but I also had this with an earlier WM6 ROM and the original WM5 ROM.
Anyone else have problems like this?
Yep, had exactly the same thing with the SEA Dopod Rom, had to soft reset to get it working again. The problem seems to be more of an O/S thing as the radio update (2.95.90) didn't make a difference.
The worst I have seen it is on the Dopod Rom where I had to soft reset, I didn't have any issues with the O2 WWE rom (except that it was rubbish!). I am now on Tom's B&B 4 Rom which does have this issue but I am able to recover by simply restarting the phone side of things via the comm manager.
Its a bit annoying but I'm happy to live with it for now and I'm keeping my fingers crossesd that Tom can cobble together a 4.1 rom out of the Kaiser extract he's got his hands on.
Cheers
Alex
Yeah it's the SEA Dopod I'm running at the moment, and although I've always had this problem, it seems a lot worse with this ROM, and like you said, with the others I could just restart with Comm Manager.
I'm not a big fan of the B&B interface, so I guess I need to either roll back to WWE v3.5 or find an alternative v3.7
I have an interesting situation with my Orbit. This never occurred with WM5, but only since WM6.
Description:
After a fresh boot, the device works perfect, and connects to GPRS when needed, and I am able to direct push my email all day long. Now, if I go into Comm Manager, and stop the phone radio, and then start it again, I am no longer able to connect to GPRS, and neither are any other applications. ActiveSync and DP don't work anymore, neither does IE.
The only solution to the above is to soft reset the device again, and things go back to normal.
Troubleshooting:
I've tried the regkey to keep GPRS always on. I've also tried to disable any today plugins that could be causing this issue. I've even tried a hard reset, but the same behaviour occurs. Oddly enough, this problem also occurs on a WM6 based Hermes device, and never did before when using WM5.
Something weird is going on with GPRS and WM6 in general. Sometimes, I will be on the train without reception, and when my phone gets signal again, GPRS will say it is connected, but it is not. I have to soft reset.
Needless to say this is annoying. Can somebody confirm that this issue exists with the base O2 WM6 rom? What about some of the other ROMs here that you guys/girls have? Does the same behaviour occur? My ROM and radio are just the defaults, no upgrades, etc.
N.
Hi There,
I am well aware of the problem, I currently work in a telecoms company and the main device we ship out is the XDA Orbit (Artemis).
Currently we are downgrading all devices so as to ignore the problem, but a permanent solution is being worked upon.
The HTC Touch's radio is identical to that of the Artemis, this problem does NOT exist on the Touch (Thanks for testing Pof!) So I atleast have ground to work upon, it is not related to the radio itself but the RIL (Radio Interface Layer) driver.
I'll let you all know if (or rather WHEN) I find a solution.
i've had loads of trouble with this issue and here are my findings:
the dopod sea 3.7 rom and and anything else based on it are the worst affected.
the o2 wm6 rom isn't too bad
tom and meschle's roms are both pretty much fine
I do a 20 minute tube journey every day so i have tested this quite well!
cheers
alex
I'm having the same issue in the Artemis Touch 2.1 Rom.
I found that when I disabled the Phone option, the Flightmode-option would enable. Now, when I want to enable the phone, I tab the Flightmode option to disable Flightmode. It then enables the phone automatically and successfully opens the GPRS connection.
Just done this a couple of times but for now this seems to be a workaround.
Read 'seems'
GuyBrush1978 said:
I'm having the same issue in the Artemis Touch 2.1 Rom.
I found that when I disabled the Phone option, the Flightmode-option would enable. Now, when I want to enable the phone, I tab the Flightmode option to disable Flightmode. It then enables the phone automatically and successfully opens the GPRS connection.
Just done this a couple of times but for now this seems to be a workaround.
Read 'seems'
Click to expand...
Click to collapse
The times I have had the issue with the O2 rom and the v.occasional times I have it with Tom/Meschle roms restarting the radio via flight mode always fixes it. With the Dopod and other 3.7 roms the whole radio seems to crash and you can't even get it into flight mode so soft reset is the only option.
This has been tested on all versions of the Artemis radio that are available.
same problem here on prophet. can connect. if i go ffline due to no signal, i cannot connect. after i switch to flightmode and activate phone again gpry works again. any patch?!.
holzzelt said:
any patch?!.
Click to expand...
Click to collapse
No patch, just better roms.
I have serious problems with Touch 4.01 and even Vanilla 4.01 reported as stable. It is fare away to be stable at all. Continuous freezing the mobile phone functionality. Telephone looks like everything is fine, but SMSes are not delivered and calls are in my voice mailbox. To find out the problem, I have downloaded Bepe's Artemis kitchen 2.1, what was (my feeling) the source of this ROM. And possibly recognized the problem. The Bepe issued two versions, second is fixed. But it seems that this Vanilla and Touch (4.01) has been generated by the first one. I have checked the size, date and time of OEMDrivers and they are different. Meschle, is it possible to generate your ROM by this fixed version? Thanks in advance.
josef.bilek said:
I have serious problems with Touch 4.01 and even Vanilla 4.01 reported as stable. It is fare away to be stable at all. Continuous freezing the mobile phone functionality. Telephone looks like everything is fine, but SMSes are not delivered and calls are in my voice mailbox. To find out the problem, I have downloaded Bepe's Artemis kitchen 2.1, what was (my feeling) the source of this ROM. And possibly recognized the problem. The Bepe issued two versions, second is fixed. But it seems that this Vanilla and Touch (4.01) has been generated by the first one. I have checked the size, date and time of OEMDrivers and they are different. Meschle, is it possible to generate your ROM by this fixed version? Thanks in advance.
Click to expand...
Click to collapse
Hi, how long do u have such problems and who is ur mobile operator. according to ur name I suppose that u r from Czech Rep.
I'm asking b'cause during last weekend I had also problem with my phone which leaded to reflashing of my phone but it was problem of operator.
I'm by O2 and have O2 XDA Orbit. I wasn't able to get any sms or report of delivery, i could send them only. and now i have bit different problem, sometimes sms from me is delivered, is shown in phone but it is something what i sended already before and then it dissapears from phone reciever's phone.
Such serious problems with ROM are strange, b'cuause those ROMs are out more then month and as I know, nobody had the same problem as u. I'm using Touch 4.01 without cube from first day when it was published here with no problem. i'm not couting problem with memory leaking which is probably problem of wm6.1 rom in general then Touch 4.01.
No, I am not only one who referring this problem. Look at this thread: http://forum.xda-developers.com/showthread.php?t=375930
Correct, I am from CZ and using T-Mobile, but in roaming quite often. But it happens independently on network. Touch Full 4.01 was more or less horrible, Vanilla 4.01 is better, but still time to time is freezing the radio part. To avoid discussion about radios, I have tried last 3 versions with the same result (3.08,2.98,2.97). But I really believe that problem is with OEMDrivers in Bepe's Kitchen. What Bepe even highlighted, that these drivers in first version are for different type of phone. The most stable version, what I had, it was B&B4.2 for more than 1/2 year. But of course WM6.1 is much faster. It was my reason for upgrade.
ok, then i cannot help, this is up on guys which r cooking ROMs.
will cross my fingers for u to solve this problem. it is nice from guys that they provided new ROMs based od WM 6.1 two months earlier than Macro**** but such serious problem takes us back to prehistory, b'cause having phone with which u r scared to call b'cause of freezing has no point.
Same problem here, flashed a lot of different roms to my device but only having these freeze problems since touch 4.01.
Right now it's only once per week. But it's been much worse: reboot, lock after 30 secs, freeze 5 secs later, repeat. Had to reflash my device. (And i always flash twice with a new rom).
I hope the fix is as easy as just building the rom with a newer version kitchen.
same problem for me.
i am running 4.01 Touch with full cube, operator is orange netherlands.
sometimes i have to reset the phone 3 times a day, after that i get a whole lot of sms (normal) and the calls i missed.
going to try 4.02 now, hope that's one's better
doesnt matter what version do you use - but always flash twice(one by one) and make a hard reset after flashing. Result is - much more stable work.
@d3ton4tor
I'm on dutch orange too, but haven't had a problem with touch lite 4.01. I'm using touch vanilla 4.02 now and still no probs.. I've got a MDA Compact tho..
I never had any problems with 4.01, or any of the previous roms, but since using 4.02 i have had several lockups now, about once a week. So maybe i better reflash it again see if that cures it ?
It is interesting. I have made update for Touch Vanilla 4.02 and everything works perfect. Sometime the less is more. I would never go for all Cube staff, it is only the memory eater from my perspective. I have realized that I can remove from StartUp folder WiFi link (I have T-Mobile ARTE110 - WiFi missing) and it is better. Under more or less conditions above 20 MB and it is very valuable especially for navigation SW like iGO.
Try PagePool 8M
Try PagePool 8M.
Pagepool
My English is so bad.
Or try the 4.02 it works fine here in my HTC 3300 also t-mobile client ;-).
Flashed it yesterday and works fine no freeze or what ever, even gps and radio works fine.
Greetz THeM
Destinator n maps
hey i just installed destinator 7 on my o2 orbit it doesnt detect the map infact no map at all
can any1 help me with this???
Hi,
You need to ensure that the maps folder is included in the destinator apps folder. That is when your destinator would be able to detect the maps.
By the way can you share your Destinator 7 (Mumbai Map) with me ??
Regards,
kailash
I too have problems with the Touch 4.1 vanilla rom but my issues manifested themselves after I had been using the rom for a while without any problems. Now I run out of memory quicker when using PIE and have to reset a lot more. Also sometimes am unable to connect to GPRS/EDGE without a reset. I will be trying any new roms that come out but its becoming clear to me that I need to upgrade.