Related
Ok so off recent reading it seems that many people that have followed the steps in "Make your X01HT a WM6 Device (for Gaijins)" have unstable devices. Please complete this poll, and if you have a stable (one or less crash a week) please tell us how. It seem that many people here are Stuggling to get a stable WM6 that supports Japanese.
My Black Majik ROM and every other ROM before it crashes 4 or more times a day!
to stop crashing cook in Japanese support??
look at this (from Make youe x01ht a wm6 device) from my last post there.
I wish somebody could figure this out. Anyway, at the moment, the cooked lvsw with built in Japanese support works best. Although it is a little slow. It has not crashed for 2 days solid -- no matter how much I have thrashed it. Every single other English rom crashes.
Therefore, it is possible to make a stable wm6 with Japanese support -- just how!
-----------------
Yep I installed the Japanese input enabled version of LVSW. Some things I noticed were that it was modified to install the Japanese stuff (including character input, mslite, fonts, x02ht setting for softbank Japan, etc) following flashing, i.e installed these setting automactially from the extended rom. Now, I am wondering why the thing is so stable. It has not crashed ONCE in the 24 hours I have been trying to crash it.
Funny because every single other English WM6 rom, including the same version of the LVSW rom I have installed have all had terrible problems with random crashing etc; the only difference being that I followed instructions from the beginning of this thread to install the Japanese.
My question: how do we set up English roms so that they automatically install Japanese stuff (including x01ht settings for Japan) from extended rom following flashing?
Very strange that doing it this was could make it so stable. Unless of course, there are newer/more stable versions of a lot of the software links that appear in the original thread?
Ideas please! Would like to solve this enigma.
tora201, where do you download the Japanese input enabled version of LVSW ? I'm really tired of frequent crash and would like to have a really stable ROM.
rickywck said:
tora201, where do you download the Japanese input enabled version of LVSW ? I'm really tired of frequent crash and would like to have a really stable ROM.
Click to expand...
Click to collapse
http://rapidshare.com/files/39953635...WWE_3.30.3.zip
See #89 onwards of "make your x01ht a wm6 a wm6 device"
And, yeah, it is extremely stable. I have installed the HTC home plugin thing as well as the new touch dialer, etc. No problems at all! Cheers mate.
I use LVSW 3.30.3 English ROM with LetsJapan and JapaneseIME (both by Asukal) installed...
Generally, phone seems stable, but then after switching to any of Japanese IMEs (Tegaki, Romaji...) trouble starts... Worst problem is that sometimes SMS and MMS freezes the phone, for example, on message reception. It is even worse by the fact the incoming message is then lost forever!
For some people, switching to Japanese input everyday is essential, and of course, messaging too... these two things seems to clash on all ROMs (some seems to be much more stable than the others).
What we need here is more stable Japanese font & input method package to do things properly... We need Asukal
tora201 said:
http://rapidshare.com/files/39953635...WWE_3.30.3.zip
See #89 onwards of "make your x01ht a wm6 a wm6 device"
And, yeah, it is extremely stable. I have installed the HTC home plugin thing as well as the new touch dialer, etc. No problems at all! Cheers mate.
Click to expand...
Click to collapse
Thanks, but the link seems not working, could you post again ?
Stable CJK system
My experience :
1. Install Asukal's echinaNo5a to support Chinese, Japanese and Korean.
CJ fonts are included.
1.1 move&over write /Temp/wince.nls to /Windows
1.2 delete the startup menu's "usemynls?".
2. Install A4&Hanwan to input Chinese input and Atok to input Japanese.
3. Install other stuffs: Genocide Today, KPCapt, MMSLite265, JJ Pimp My Black 0.2,SQLCE 2.0, AozoraKoneko
I am using Elf_Edition_v2.1 based on LSVW 0519 ROM switching from Black 3.0.1.
It usually works several days for me and surely randomly locks too, but is mostly stable one ever
If anyone teaches me how to cook a ROM, I can make it.
I've tried it and it seems that it is quite stable, but I can't connect to the Internet via GRPS/3G. I've tried to delete the Softbank setting but it didn't seem to work.
http://rapidshare.com/files/40804243/RUU_signed.nbh.html
here you go! Just the nbh file.
Thanks for your replies and votes. Many others here seem to have crashing/freezing problems, just wondering why you all (except me and one other) said that your PDA is stable?
My Black Majik ROM has been better recently, but not what I call stable, recent crashes:
Thurs-0
Fri-4
Sat-0
Sun-0
but I don't know why.
I expect a phone to be completely stable, not mostly stable, not like old versions of Windows, like XP very rarely crashes, sure programs crash but I think it is a major programing/design error when the OS fails and the only way out is a reset.
People have all sorts of problems, quite often linked to the software they install(in this case Japanese support software), but I don't see how this software stops the OS from working, if there is a problem with SPB mobile or any other sotware then that software only should crash within the OS and leave everthing else alone, not take down the whole system, unbelievable!
pre-cook Japanese into the external rom in wm6 english??
rockyV said:
Thanks for your replies and votes. Many others here seem to have crashing/freezing problems, just wondering why you all (except me and one other) said that your PDA is stable?
My Black Majik ROM has been better recently, but not what I call stable, recent crashes:
Thurs-0
Fri-4
Sat-0
Sun-0
but I don't know why.
I expect a phone to be completely stable, not mostly stable, not like old versions of Windows, like XP very rarely crashes, sure programs crash but I think it is a major programing/design error when the OS fails and the only way out is a reset.
People have all sorts of problems, quite often linked to the software they install(in this case Japanese support software), but I don't see how this software stops the OS from working, if there is a problem with SPB mobile or any other sotware then that software only should crash within the OS and leave everthing else alone, not take down the whole system, unbelievable!
Click to expand...
Click to collapse
Mate, here is a sort of copy of my post in the "Make your X01HT a WM6 Device (for Gaijins)" (in wm6 hermes forum).
I have not heard anything back about my inquires, so I am posting it here with a few changes/comments. Note, I am using a x01ht and live in Japan, so I am using the softbank network.
I had the same problem as many others: when using WM6 (An English version) with Japanese language cabs/MMSlite etc installed AFTERWARDS using the guides on this board, they ALL crash, in one way or other.
This is strange because The Samurai build (beta 1/2) (Japanese cooked rom) worked perfectly! What is going on here? I wish there was away to convert it to English (I mean the GUI only). Then I would be in PDA heaven.
Overall, I have found that all Japanese language wm6 roms have worked better than with English ones installed with Japanese input/language support. Anway reasons/ideas why this would be would be most welcome......
Some typical crashes with English WM6 builds with Japanese language/fonts/mmslite 2.65 or 2.75 installed aftterward：
- MSSlite crashes A LOT (the whole thing freezes, then upon re-set, half the mail in the inbox is gone -- or the MSSlite programme itself is gone and needs a reinstall).
-crashes A LOT using explorer. No reason at all. Again, it just freezes. Freezes more with wifi.
-sometimes crashed on the comm manager screens, or in settings.
The point is, the thing crashes A LOT under WM6 with Japanese support installed later, following any of the guides here.
Anyway, in the end I went with Hermes_WWE_3.30.3.3_4_X01XT (Latest LVSW wm6 in English with Japanese support cooked in to install settings upon first boot via the external rom)
http://rapidshare.com/files/39953635/Hermes_WWE_3.30.3.zip
It works fine. Not one crash over a week! And believe me, I have tried to crash the thing. I even installed the touch HTC plugins.
Basically, the difference between this and other wm6 roms is that all the Japanese support was cooked in to install via the external rom upon the first boot. So, my question is:
Since somebody (A Japanese guy) made this, it should be possible to make a similar Black version (for example) with built in Japanese language/mms/softbank settings set up to install automatically via the external rom upon first boot. Anybody know how to do this?
If we can do this, or somebody post a guide, it would seem to solve all our problems.
I'm guessing that maybe we take a copy of the Ext_ROM from the one you're using, install another English ROM, and then copy the EXT_ROM over, and hard reset it to kickstart the auto setup process. What do you think?
I tried it in Black Majik, and had to run the Ext_ROM manually, but nothing changed, even after a reset! No connection, fonts, nothing!
You've got to edit a file in the Windows directory to enable it, I see. When I get time I'll have a go...
hamster0914 said:
I'm guessing that maybe we take a copy of the Ext_ROM from the one you're using, install another English ROM, and then copy the EXT_ROM over, and hard reset it to kickstart the auto setup process. What do you think?
Click to expand...
Click to collapse
Would that work?? Oh, my phone is locked so I can't do that! :-( its the post April softbank one. Damn you softbank! Can somebody else try that??
****! This ROM is Magic!! How made it?
Only problem is that it's slow, if compared with Black. Can anybody cook a black ROM with this incredible Softbank support?
Please!!!!!
hamster0914 said:
I tried it in Black Majik, and had to run the Ext_ROM manually, but nothing changed, even after a reset! No connection, fonts, nothing!
You've got to edit a file in the Windows directory to enable it, I see. When I get time I'll have a go...
Click to expand...
Click to collapse
You mena that if if you run all the .CAB of the extended ROM, 1 by 1, in the proper order; nothing changes?
Yes, that's right.
hamster0914 said:
Yes, that's right.
Click to expand...
Click to collapse
I checked the ROM carefully ... All the Japanese support is cooked into the ROM, not via Extended ROM.
Or that boy cook new ROM, or we can't do anything. Anyway ... I think that it's extremely slow for be WM6.
Saludos
Great! Kind of.
It is good to know that I am not the only person who has had chronic trouble with installing Japanese support in WM6. I have tried quite a few ROMs, Black 2.5 through Dymond, as well as a few LVSW, and have had random lock-ups and the SOD on all of them. I keep going back to my Japanese WM5 ROM for the stability. I've got a three-day weekend coming and will report back after flashing Hermes_WWE_3.30.3.3_4_X01XT with anything I find out about this baked-in Japanese support ROM.
To sesaru, I have noticed that LVSW is routinely slower than Black - even without any Japanese support issues.
the rom is slow, but it is completely stable. I wonder how it was made? It certainly shows it CAN BE DONE. I have not had a single lock-up since I installed it. So.... something going on here. Nobody can figure it out? Oh, and for the record, it installed all of the Japanese stuff from the external rom upon first boot (the 3 second thing). So, I wonder why does Japanese work without crashes if installed automactially upon first boot via external rom??
I've been searching the forum all over, cause i'm pretty sure i saw someone else report about this too somewhere on this forum, but i can't find it anywhere anymore... Here's the horrific problem...:
With WM6 (Official Dopod SEA, no SPL) i already encountered two times the horrifying message "Password Incorrect" when i want to login again after a reboot.... No matter how many times i fill in the CORRECT password (ie. Device-PIN), it just keeps me out... This is going to be the second time in 3 days i'm gonna have to do a hard reset (i guess it's time for a backup program), and this has pissed me off completely...
I don't dare using a PIN anymore now... cause it's my only (working) phone right now...and i rely on it.
These lockups happened everytime i made a change to the device like installing an appplication or tweaking something in the registry. After the reboot i'm locked out...
Anyone any ideas what causes this, and how to prevent/fix it ?
I have the same problem.
Just did ANOTHER hard reset. And the problem is gone. I'm still investigating.
Feeling that it might have to do with the programs being installed.
I have the same ROM as you.
Keep posting.
joymike123 said:
I have the same problem.
Just did ANOTHER hard reset. And the problem is gone. I'm still investigating.
Feeling that it might have to do with the programs being installed.
I have the same ROM as you.
Keep posting.
Click to expand...
Click to collapse
I'm still busy 'rebuilding' this sucker... But as for now can you confirm it didn't happen again even after editing something in registry or installing an app ? That's when it happened to me everytime (while the PIN was enabled during this)...
And the weird thing is that i'm running exactly the identical software-setup as on previous ROM's... like mUn's WM6, LVSW's, original WM5, GPS WM5 and then some... But never ever i had this problem before... i'm thinking more something like bug in new WM6, or maybe the HTC taskman...?
Edit: i added SpbBackup to todays setup....so hopefully when it happens again, i can recover of it more quickly... Also fiddled around the reg until i made sure i did ALL tweaks i want... I'll wait a few days with a PIN this time...
Locked out
Same thing with me, pin disabled until further developments of this weird bug.
I can confirm this bug. Happening to my friend with the latest PDAVIEt's ROM based on DPOD WM6 official.
When u flash your ROM and a PIN was setted, you'll be stuck at the boot with a message that tells you : Your mother F* password isn't correct...try again...and Again .. and again...
the only Sollution is to reflash.
Weired, not !!!!
I'm tired on updating & downgrading.
I'll cook my own ROM now
Ok...let's start summing up all that software in our devices... here i go for mine:
-Stowaway BT keyboard driver
-Saman WM5NewMenu
-David Andrs Sun'n'Moon
-Spb Backup (new this time )
-Spb PocketPlus 3.2
-Spb Weather
-Spb PhoneSuite
-Ilium Newsbreak
-Caywen Kevtris 2
-larna iContacts
-Google maps
-DeveloperOne AgendaOne and Codewallet 2006
-Coreplayer
-Chi-Tai Batterystatus ext
-ATIfix
-Resco Explorer2007 and Radio
-MS VoiceCommand 1.6
-TomTom 6.03
torpie13 said:
I can confirm this bug. Happening to my friend with the latest PDAVIEt's ROM based on DPOD WM6 official.
When u flash your ROM and a PIN was setted, you'll be stuck at the boot with a message that tells you : Your mother F* password isn't correct...try again...and Again .. and again...
the only Sollution is to reflash.
Weired, not !!!!
I'm tired on updating & downgrading.
I'll cook my own ROM now
Click to expand...
Click to collapse
I wonder if this is related to the problem with the DOPOD ROM (and its derivatives) changing the Device Code in TomTom Navigator? It doesn't happen with any other ROM, and has caused problems with TomTom refusing to issue a new activation code. The only solution to that is to regress the ROM to WM5, or flash a non-DOPOD one.
I don't see at all what TomTom has to do with the specific issue in this thread...
WM6 password bug
It is a known issue and it was WM6 bug. Was reported to MS. With PS turn on, when you take out the battery, WM6 will forget the password. Therefore cannot turn on.
Moaske said:
I don't see at all what TomTom has to do with the specific issue in this thread...
Click to expand...
Click to collapse
Probably nothing, but if the DOPOD ROM seems to be misinterpreting password information, it could be the same bug that misinterprets the Devcie Code. Strange thya both only seem to be occuring with DOPOD derivatives.
NeilM said:
Probably nothing, but if the DOPOD ROM seems to be misinterpreting password information, it could be the same bug that misinterprets the Devcie Code. Strange thya both only seem to be occuring with DOPOD derivatives.
Click to expand...
Click to collapse
Well, i think this has a lot more to do with the fact that you changed the OS image... Although i cannot explain why the cooked MW6 versions do not display this behaviour...
cptanz said:
It is a known issue and it was WM6 bug. Was reported to MS. With PS turn on, when you take out the battery, WM6 will forget the password. Therefore cannot turn on.
Click to expand...
Click to collapse
Correct! Taking out the battery also forces a reboot... So, every reboot makes it 'forget' the password so it seems...
Incredibly that M$ even dared to release this to OEM's....and even worse: they haven't fixed it yet!!!
Come to think of it....: i never had this issue with one of the cooked WM6 ROM's (though you get batterydrain problems and slower performance in return).... That's really strange...
Could it have something to doe with the fact that the Dopod ROM has "HTC_P3600i" in the 'About' screen ? (meaning it's for some forthcoming hardware, and NOT the standard P3600 ?)
I've got the same problem too and have tried several ROMS with the same problem. PdaViet 4.00.5, Gullum, etc with the same problem. Problem is, I cannot deal without a PIN as my company exchange server enforces a policy to set a PIN. I've gone back to WM5 now which is very very stable until a solution is found.
Moaske said:
Come to think of it....: i never had this issue with one of the cooked WM6 ROM's (though you get batterydrain problems and slower performance in return).... That's really strange...
Could it have something to doe with the fact that the Dopod ROM has "HTC_P3600i" in the 'About' screen ? (meaning it's for some forthcoming hardware, and NOT the standard P3600 ?)
Click to expand...
Click to collapse
Actually I'm using a modified PDAVIET Rom, but I didn't have any i in my about screen when I was using the official dopod.
I'm removing my battery now to have a cold start... I don't have any pin or password problem, even if I'm using a pin protected sim and a pin protected device (two pins at startup)
Ciao
wm6 password bug?
i've got the same problem, with an e-ten x500+....
Very strange
I just want to tell you that I never had this problem (which would be terrible for me, cause using Exchange Server you must enter a password unless you do a special registry hack).
I used mun_rus WM6 ROM and I am using Bepes German WM6 ROM and I never had any problems with the password... very strange.
*Bump*
So it seems to be narrowed down to pretty much all official WM6 rom's, but has anyone found out yet if there's a way to fix this ? Does M$ know ? Have any of the cooks here found what the difference between the WM builds is, that causes this terrible issue ?
I'm still on the Dopod WM6 rom, but my device is totally unprotected now.... unacceptable... (apart from having to deal with me to get your hands on my Trin)
I've been on the PVIET 10 rom for a week with PIN code activated without any problems.
Today I decided to change the dialpad, and as soon as that happens, after a reset, I can no longer enter my PIN.
Anyone having the similar problem?
Me too
I was PDAViet for over a week, I had issues with TOMTOM, when I re-installed and did a soft reset I got the device code error. I had no choice but to do a hard reset and start over again. I was using Ausdim prior to this for ages and never had this problem.
I meet the same problem with rom Faman 3.1 Fr
I read somwhere : a bug report about this is present on the Microsoft website. It is a know issue from Microsoft WM6.
Hi!
I've a trinity who works in faman 4.03 and rom radio 1.43.30.11.
I've got a bluetooth headphone : Motorola s705.
I've try to follow many tutorials and forums about this subject but i'm still not happy of my sound :
-the quality is horrible (like if i was listening a big compressed mp3 with a lot of crackles)
-the sound "cut" every 10sc during 1sc
I don't know what to do.
Thanks to anyone who can help me.
try flashing wm6.1 mary's new lite rom get the top link with the .1 at the end of the build number, all drivers are updated.... it works for me... hope this helps
also update your radio to the latest which is 1.50.08.11... this solves a lot of problems...
If the above two desn'y work (it should!) then its your headset...
Thanks but i'm french and even though I'm abble to comunicate on this forum i'd rather than having a french rom, it's more sure
the radio 1.50.08 is really better?
oh sorry didnt realise you were french, you have good english....lol
yes radio is much better... and its still GPS activated too.
ok let's try
wITH MY fAMAN 4.01 AND A jABRA bt620 and Radio 1.46? i VE GET THE SAME PROBLEM,
After installing A2DPFIX.cab,, , it's working Well !!!!
Where can i find ad2pfix? Cause i've already read that it's an important cab but i've never find it...
I've tried to udpate my radio rom at 1.50.08.11. and I still have the same problem
zitoun said:
Where can i find ad2pfix? Cause i've already read that it's an important cab but i've never find it...
I've tried to udpate my radio rom at 1.50.08.11. and I still have the same problem
Click to expand...
Click to collapse
For the cab fix, try here http://forum.xda-developers.com/atta...5&d=1165092579
However, I have read somewhere that even if you install the cab fix, it may not fix it much, as other things can affect A2DP performance as well. I'm not too sure about this, as I've been told that even background programs running or lots of today plug-ins can affect this.
ok thanks a lot but the link is dead... :-(
It's ok i've found AD2PFix and intalled it. But it does not work. I've always the same problem.
I have nearly the same problem....
I've passed to ROM faman 3.6 and Rom Radio 1.38.00.11. and the sound is really better. Still not perfect but pretty good. Enough to listen music without crying
There is another solution perhaps, try to install the following folder :http://www.mobinaute.com/61292-astu...oth-de-toshiba-sur-un-pdaphone-qtek-s100.html
Hi Everybody!I have SPV M650 Orange(Artemis).I update my ROM to Artemis Touch 4.01 Vanilla and now i have problem with calling.After night i try to call but... my phone not respond,others programs and function working normally.Restart(big battery drain 10% down after soft reset !!) and my Artemis working fine.Before im using Artemis 4.01 Vanilla ROM and problem will be the same!I update my radio to 03.08.90 but problem stay.Please help lads!
Sorry,bad english.
Regards.
the same
I have the same problem, but I have a FULL version of 4.02 ROM (ENG). The problem is exactly the same - after some time (one night for example) the "phone application" stops responding when I want to make a call. I think it's the ROMs fault. I thinking of going back to the original WM5 or original WM6 from HTC.
kosiara said:
I have the same problem, but I have a FULL version of 4.02 ROM (ENG). The problem is exactly the same - after some time (one night for example) the "phone application" stops responding when I want to make a call. I think it's the ROMs fault. I thinking of going back to the original WM5 or original WM6 from HTC.
Click to expand...
Click to collapse
I think the problem is from the OS ROM. I had same problem with vanilla 4.02.
Just try it another new build ROM.
Cheers
Same problem here
Zecanilis said:
I think the problem is from the OS ROM. I had same problem with vanilla 4.02.
Just try it another new build ROM.
Cheers
Click to expand...
Click to collapse
Hi Zecanilis,
I encounter the same problem that is described here by user kosiara an Novy
The GSM signal is excellent, but the phone does not work from time to time and when I try to make a call, I get the message "the operation failed". of course nobody can reach me neither... When I do a soft reset everything is back to normal...
This is very anoying and I do not know what to do.
I bought this PDA second hand, with the upgrades already done for me. Since I do not have any personal data or programs on it yet, I wouldn't mind doing a hard reset and installing everything from scratch.
What would you suggest as a stable system OS and ROM versions?
Any help would be much appreciated.
Here are my actual data:
XDA Orbit
IPL 1.25.0001
SPL 1.11.0000
GSM 03.08.90
OS 3.13.0.0
ROM version : Artemis Touch 4.02 WWE
ROM date 4/08/08
Protocol version 4.1.13.52
Model Nr : ARTE 200
WM 6.1 Professional
CE OS 5.2.19199 (Build 19199.1.0.0)
Regards
But, yet again, I don't understand...
Vanilla 4.01 and 4.02 seem to be very popular and appreciated roms.
How come we are the only ones to complain about phone not working properly?
Is it really the OS build? CE OS 5.2.19199 (Build 19199.1.0.0) I don't think so. I have seen it also a lot in Devices.
What could it be then?
I hope it is not a Gsm radio hardware pb......
Any suggestions?
Thanks
Zbootsom said:
But, yet again, I don't understand...
Vanilla 4.01 and 4.02 seem to be very popular and appreciated roms.
How come we are the only ones to complain about phone not working properly?
Is it really the OS build? CE OS 5.2.19199 (Build 19199.1.0.0) I don't think so. I have seen it also a lot in Devices.
What could it be then?
I hope it is not a Gsm radio hardware pb......
Any suggestions?
Thanks
Click to expand...
Click to collapse
I'm not "guessing". I had the same problem and i think my problem is solved after this new rom i have.
Just try one recent build of OS. My build is 19591.
Before upgrading, just turning off and on the phone in the "comm manager" whould give me that problem sometimes. Now i've allready tested it and all is ok.
Cheers
Zecanilis said:
I'm not "guessing". I had the same problem and i think my problem is solved after this new rom i have.
Just try one recent build of OS. My build is 19591.
Before upgrading, just turning off and on the phone in the "comm manager" whould give me that problem sometimes. Now i've allready tested it and all is ok.
Cheers
Click to expand...
Click to collapse
Hi, and thanks for your reply.
I am new to this and althought I read many post, I am not sure.
Can I just upgrade the OS Build without flashing a new ROM.?
If Yes, How do I do it...any tutorial?
Thanks
No.
You have to flash a complete new ROM.
Cheers
OK Thanks
Whish me good luck,,,
Good luck and good choose...
!Novy said:
Hi Everybody!I have SPV M650 Orange(Artemis).I update my ROM to Artemis Touch 4.01 Vanilla and now i have problem with calling.After night i try to call but... my phone not respond,others programs and function working normally.Restart(big battery drain 10% down after soft reset !!) and my Artemis working fine.Before im using Artemis 4.01 Vanilla ROM and problem will be the same!I update my radio to 03.08.90 but problem stay.Please help lads!
Sorry,bad english.
Regards.
Click to expand...
Click to collapse
I experienced that problem a few weeks ago and it's happening more often in the last days. My ROM is Artemis Touch 4.02 full.
Some people started complaining that they couldn't phone me while I didn't see any problem with my phone (as long as I didn't try to make a call myself).
Funny addition to that problem: Sometimes I find my phone (usually in the morning) with a blank white screen. I don't know why that keeps happening but I sure would appreciate any hints what's the root of all that evil.
I'm happy with the 4.02 ROM so I'd rather avoid some things if it keeps the ROM stable.
novy said:
I experienced that problem a few weeks ago and it's happening more often in the last days. My ROM is Artemis Touch 4.02 full.
Some people started complaining that they couldn't phone me while I didn't see any problem with my phone (as long as I didn't try to make a call myself).
Funny addition to that problem: Sometimes I find my phone (usually in the morning) with a blank white screen. I don't know why that keeps happening but I sure would appreciate any hints what's the root of all that evil.
I'm happy with the 4.02 ROM so I'd rather avoid some things if it keeps the ROM stable.
Click to expand...
Click to collapse
when you installed your new rom did you flash it twice ?
this will make sure that all system files are copied 100%.
its really important to do this on all new roms that you install.
neilhhardy said:
when you installed your new rom did you flash it twice ?
this will make sure that all system files are copied 100%.
its really important to do this on all new roms that you install.
Click to expand...
Click to collapse
Thanks for your answer. Yes, I flashed it twice and I even flashed a factory rom before that. All Artemis Touch roms were fine until 4.01 and 4.02.
So Zecanilis is probably right blaming the OS version for that malfunctions.
New Rom
I have flashed my device using USPL (took me 2 days to setup the program to work with vista drivers). Then I flashed the same ROM I had before (Artemis Touch 4.02 full Red and Black) but with a different OS build. (as Zicanillis advised)
I will use it for a while and let you know if the freezing phone problem has been corrected.
Cheers
One other change that is on my build is page pool.
My page pool is 6 MB, and some Touch and vanilla (included the 4.02 i had) is only 4MB.
In my opinion that could be another issue to test.
My PDA is working just fine now.
Cheers
For me the problem was the OS Build.
I flashed my device with the same 4.02 vanilla but with a different OS buid and the Phoneworks great. Been using for 2 weeks now, never freezes or looses signal.
Cool
Thanks to Zecanillis advice! obrigado !
After trying six or seven WM6.1-based ROMS from three different cookers (19199 and 19209), I'm starting to wonder if there's not something 'seriously' wrong with the WM6.1 base image.
I begins to strike me as some sort of duration-based memory degradation. My experience has been that runtime lasts between 2 and 48 hours before a hard reset is necessary. In my case, I pared my installs down to adding merely my password safe as the only add-on, and still it crashed.
The most interesting pre-crash was going to "Programs" and noticing the number of icon substantially reduced (...and reducing...), and the remaining icons as default program icons.
After about five days of fighting with these and trying different methods of extending runtime, I reloaded an older copy vp3G's 3.0.0 from last summer and haven't had a problem for the past 72 hours. In fact, I had no lock-ups with WM6-based, previously.
I'd be interested in other people's experiences with WM6.1-based ROMs on the Hermes...
- Marc
i may be wrong, but i think recall reading that flashing back to your stock rom, then flashin to 6.1 may fix some hard reset problems....
as for me, ive used 4 or 5 6.1 roms and havent experienced a hard reset.....my latest and favorite so far is faria's and dr.p's 6.1 rom, been running a week no hard reset...
im usin an at&t branded 8525
i was having a few issues with this but ended up changing radio versions from my standard 1.16 to 1.48.
havent had an issue since doing that.
i had the crash problem also, but after I not install htc cube in any of the wm6.1, everything ok and stable.
problem is with cube in wm6.1 i think.
Faria's is the best so far, but they all have problems to varying extents. Have you tried running Oxios Close apps? That will help you claim back memory and maybe help prevent the need for a hard reset. you can get it here: http://www.oxios.com/memory/
lupes5 said:
i may be wrong, but i think recall reading that flashing back to your stock rom, then flashin to 6.1 may fix some hard reset problems....
as for me, ive used 4 or 5 6.1 roms and havent experienced a hard reset.....my latest and favorite so far is faria's and dr.p's 6.1 rom, been running a week no hard reset...
im usin an at&t branded 8525
Click to expand...
Click to collapse
Interesting. I did notice that on some ROM flashes that boot screen retained a previous ROM's splash. That might mean that some ROMs are not including all facets (OS, Radio...Bootloader?) of the complete image. Will give that a shot now that I'm back to a stable WM6.
st3v3 said:
i was having a few issues with this but ended up changing radio versions from my standard 1.16 to 1.48.
havent had an issue since doing that.
Click to expand...
Click to collapse
Radio is 1.45 with vp3G 3.0.0. Will check again after a Faria re-flash and upgrade to 1.48 if it isn't included.
fizzy15 said:
i had the crash problem also, but after I not install htc cube in any of the wm6.1, everything ok and stable.
problem is with cube in wm6.1 i think.
Click to expand...
Click to collapse
I had that thought too, but my last ROM didn't include any of the HTC apps, at all, so I think it's some conflict or something lower level. The cube 'is' a resource hog, however...
hamster0914 said:
Faria's is the best so far, but they all have problems to varying extents. Have you tried running Oxios Close apps? That will help you claim back memory and maybe help prevent the need for a hard reset. you can get it here: http://www.oxios.com/memory/
Click to expand...
Click to collapse
The resets are always due to hard lockups, and they can be with only Activesync running as an application. I try to keep the number of running apps at a minimum for reasons that are probably fairly obvious to all here...
you are not alone...
http://forum.xda-developers.com/showthread.php?t=376211
Im also having the same problem .. all sorts of experiments has been done to test on why WM6.1 crash when I install them .. but 1 thing i noticed that it always hang before softreset that eventually lead to hardreset .. i thought hardware accelerations problem ... so what i do is .. every WM6.1 i changed to 8mbpp .. until now my machine ok.
My2Cents.
-/Abid.
Flash to stock rom then to wm 6.1... Apparently there is a problem if you flash from big storage rom to wm 6.1(not sure why this is so) but there have been a huge number of people who say this works for them, myself included.... I tried every wm6.1 rom that came out then doing something stupid eflashe stock os. No problems with wm 6.1 since. Also I believe that 19209 is somewhat more stable than versions 19199 or 19202... I'm using PDAViets 19209 rom,just changed to black edition, and have had NO trouble EVER since installing it when it first came out, no soft resets and more importantly, no hard resets... Cheers
milleniumbug89 said:
you are not alone...
http://forum.xda-developers.com/showthread.php?t=376211
Click to expand...
Click to collapse
Yep, sounds like the same behavior I'm seeing. Soft lock, reset, soft lock, reset, hard reset...lose data... (rinse and repeat)
fix
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
I have the same problem! Tell schaps so in his next rom he may fix this serious problem
Shadow CE 6.1
chronosxx said:
After trying six or seven WM6.1-based ROMS from three different cookers (19199 and 19209), I'm starting to wonder if there's not something 'seriously' wrong with the WM6.1 base image.
I begins to strike me as some sort of duration-based memory degradation. My experience has been that runtime lasts between 2 and 48 hours before a hard reset is necessary. In my case, I pared my installs down to adding merely my password safe as the only add-on, and still it crashed.
The most interesting pre-crash was going to "Programs" and noticing the number of icon substantially reduced (...and reducing...), and the remaining icons as default program icons.
After about five days of fighting with these and trying different methods of extending runtime, I reloaded an older copy vp3G's 3.0.0 from last summer and haven't had a problem for the past 72 hours. In fact, I had no lock-ups with WM6-based, previously.
I'd be interested in other people's experiences with WM6.1-based ROMs on the Hermes...
- Marc
Click to expand...
Click to collapse
Use Shadow CE 6.1's rom .. I have been using it for months, and it is near flawless. Do it, you won't regret it . I've tried everything else .
Fix works...
raidzx said:
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
Click to expand...
Click to collapse
After trying almost everything to get more than a few hours of runtime out of WM6.1, I followed the above instructions to the letter and WM6.1 has worked for 24 hours now (yes...a new record). I will update in a few days if the Hermes/Faria 6.1 combo continues to function.
One note: I was not able to use Vista to update to Hard-SPL after the Stock AT&T 6.0 ROM re-flash. Each attempt resulted in an updater error on the PC after the handheld entered bootloader mode. Did the same procedure on XP and it worked flawlessly.
Hey. Had the same problems but i solved it with flashing a AT&T Stock Rom first.
Now my Hermes with PDAVIET B&C WM6.1 Rom running like a flash
Without any freezes.
here is the link to my problem thread:
cu
poPY
raidzx said:
http://forum.xda-developers.com/showthread.php?t=381959
follow those instructions and your problems will be solved.
Click to expand...
Click to collapse
Sorry, but following those instructions does NOT solve my problem. It does for some, but not all.
What works for ME, is to turn off the Storage Card power saving.
gregma said:
Sorry, but following those instructions does NOT solve my problem. It does for some, but not all.
What works for ME, is to turn off the Storage Card power saving.
Click to expand...
Click to collapse
I will update the thread with your information, thanks!