Do not enable Battery Status tray icons in B&B 4.1 - P3300, MDA Compact III ROM Development

I 've seen the same question in a lot of threads so I open a new thread for everyone to know.
Do not enable Battery Status tray icons in B&B 4.1 because it causes to crash WM6 on Windows Mobile screen while boot.
I think there is the same problem in every WM6 rom with BS v 1.04.203 beta4.
It cause me to reflash my P3300 twice to find out.

Newest build versions of Battery Status solve this problem.

athanaso77 said:
Newest build versions of Battery Status solve this problem.
Click to expand...
Click to collapse
could you please point the way to such a version?!
thanx

http://forum.xda-developers.com/showthread.php?p=975639#post975639 , no problems!

As I understand, in last build loading sequences were moved to be lounched after device starts.
In my case counters turned on are crushes the device. There is no changes in new build.

Related

AKU3.2 Rom for Universal (until 21.12.06)

New thread
Look here:
http://forum.xda-developers.com/showthread.php?p=1082908
Old versions which are good but not the newest
Look here:
http://forum.xda-developers.com/showthread.php?p=1082908
Look here:
http://forum.xda-developers.com/showthread.php?p=1082908
Ahhh... new ROMs are so exciting! How much free RAM after install?
I do the upgrade it's ok
This is the first time I tried your ROM. So far I have no complaints. Speed is comparable to Indra's Beta 5 without anything installed. Both your ROM (Ivan) and Indra feels a little faster than JWright's 1.90.96. What I like about your ROM is the clean look it has, like an official Microsoft released ROM. Thank you for this ROM.
thank you
my very first upgrade
works perfect
Thanks, I'll try it later this week (currently running your beta14)
One Question: you mention
'No Extended Rom needed anymore'
in your changelog. Does this means I no longer have to unlock the Ext_Rom manually? Is it available for use right after flashing, or am I misunderstanding something here?
thanks, very very good work, but this is a transitory rom... well.. when the great change?
Some screen shots plz
Lt.Cmdr.Ivan said:
This is a AKU3.2 Rom.
If you have questions what AKU is about, read this:
http://www.mobile-review.com/pda/articles/wm-aku-en.shtml
Some features from AKU3 on Modaco:
http://www.modaco.com/index.php?showtopic=246614
OS 5.1.342
Build 15605.3.2.0
SP AKU 3.2
newest Beta 15
Very Special thanks to Mamaich because without him the rom wouldn't be as good as it is.
Thanks to venusforu for the plugin pack the should put the Audio/Video files into a working state again.
Old beta14 for reference testing (Speed stability etc.)
ftp://xda:[email protected]_AKU3_WWE/Ivan/UNI_AKU3_2_WWE_IVAN_beta14.rar
NEW AKU3.2 beta15 is on the FTP:
ftp://xda:[email protected]_AKU3_WWE/Ivan/UNI_AKU3_2_WWE_IVAN_beta15.rar
-------------------
Beta15 changes/additions/features List:
CompactFramework 2.0 SP1
Removed Battery icon on top
Pocket MSN works with "non hotmail"(for example [email protected]) adresses
No Extended Rom needed anymore
New MMS Client 3.5.1.5
IA Zip upgedatet
PagePool increased to 6MB
New Ringtone Plugin
New WlanManager
Pocket MSN works with non hotmail adresses
Phonepad included
Pushmail should work
Vista B1 Theme
Added New Battery Icon at bottom (this time it works)
New Camera 3.00 22864
Video Call Support enabled Options screen available now
Smartdialing with options tab
I forgot to mention
USB_HDD function supported
Credits for this go to Jwrightmcps and his rom where i took it from.
Voice Speed Dial Cab from Conchas included in the rar, so you can choose to use it
Autorun function is mapped to autorun.exe again.
Added Improvements from Jwrightmcps BT Stack stuff
Changed Paging settings for speed
----------------------------------------------------------------------------
Please check and verify the programs which function. Especially tests are welcome in this departments:
BB client functionality status unknown
----------------------------------------------------------------------------
As this rom is work in progress it may contain bugs which were removed previously, but not removed from this version. Please check and report bugs and solutions (if you find them).
Bugs: (1 known)
WIFI error1
Universal goes to standby mode with Wi-Fi turned on, then I switch the
device on, and it starts trying to register in Wi-Fi net forever
(shows "tower" but without circle and rays)
Only syncs if you do it manually
Click to expand...
Click to collapse
HI,
CLD ANYONE attach screenshots plz...Excited to look VISTA theme
Thnks
Still Rom date is 09/20/06 and it appers on the startup screen again.
WLan settings are no more accessible after installing German MUI. (Crash)
But that happened on beta 14, too. Seems to be an MUI issue.
melino said:
WLan settings are no more accessible after installing German MUI. (Crash)
But that happened on beta 14, too. Seems to be an MUI issue.
Click to expand...
Click to collapse
Sorry, what is "German MUI issue"?
Thank you...
I do not have the issue of the disconnecting Wifi (the reported "bug")?. So for me an excellent ROM.
Great job once again!!
When I reset the Qtek 9000 I received the message
" sddaemon.exe not present!! "??
Many Thanks
I have installed this rom, after some hour of use the memory ram comes down under 15 mb and must make a soft reset ,but this is normal? someone of you has tried wisbar?for me qtek9000 it is a fantastic device if I resolve the problem of ram ((
babak said:
I have installed this rom, after some hour of use the memory ram comes down under 15 mb and must make a soft reset ,but this is normal? someone of you has tried wisbar?for me qtek9000 it is a fantastic device if I resolve the problem of ram ((
Click to expand...
Click to collapse
Hehe... Don't sweat it. My RAM virtually never goes higher than 12 MB and I have no problems running any applications at all. Cheers!
Camera
Thanks for the update. I'm just wondering how come "New Camera 3.00 still says 22844 instead of 22864 for beta 15? Please let me know. Thanks!
Report on the new ROM (upgrading from O2 UK 1.30.162 ROM):
Booting seems much faster (after installing several apps and having rebooted it a few times). I guess this is due to RAM disk.
True VGA mode is waaay much better than 1.30.162 ROM - system fonts are properly aligned and the only problem I found so far is battery settings and dial pad (the latter is fixable with vinay's application).
Speed and responsiveness seems to be better than my previous O2 AKU2 ROM.
There are a few problems though:
there are some compatibility problems - like InterKey virtual keyboard causes hangs every now and then and it was working perfectly well with AKU2
Battery life seems to be worse than AKU2 - before I had my device on standby with blootooth enabled for the whole working day (8:00-18:00) with an hour of reading with Haali reader and it was hardly below 80% (75 or around). Now it was down to 70 % in the first few hours. And for the curious - I did checked all the usual stuff (receive all beams - off and so on)
Other than that - great
I have installed this ROM, it seems perfect.

WM6 issue: Locked out by Device-PIN (password incorrect)

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.

Artemis Touch 4.01 Vanilla call problem

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 !

Anyone else having serious crash problems with WM6.1 ROMs?

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!

How to stop memory leak?

Hi All
The Diamond is almost perferct phone. But still there is one major most annying issue: memory leak.
What do we know about it? Is it WM6.1 related issue or is it based on HTC softwate? Do we have any idea how to fix the problem? Does it exist only on Diamond or is it common problem for Windows mobiles?
Thank you for your information.
Br,
Illodin
question
have you tryed a cooked rom?
Cooked Rom tested
Yes Sir,
I have tested them almost all:TLR, Elite, shipped, Diamond project... All the tweaks is checked also.
No matter which Rom, it is necessary to boot device on the daily bases. Without booting operating sytem get sticky.
Br,
Illodin
Illodin said:
Yes Sir,
I have tested them almost all:TLR, Elite, shipped, Diamond project... All the tweaks is checked also.
No matter which Rom, it is necessary to boot device on the daily bases. Without booting operating sytem get sticky.
Br,
Illodin
Click to expand...
Click to collapse
in that case, have you tried the following:
1) disable tf3d
2) disable ezisip
then monitor your memory usage. it should be alot better.
lastly, do not over increase your file cache and graphic cache. i believe these tweaks will reduce your free memory.
How to stop the memory leak?
stop using your device
(couldn't resist..)
Hello,
I am afraid there is not much you can do. The problem is related to windows 6, not the touch flo...
I had the same problem with my Eten X500+, more than 1 year ago...
The fix has to come from Microsoft...
Philippe
I am using Panosha Light 5 and I have to say that it has the best memory management I tried so far,before this my memory went to around 30 in a few hours no matter what I did and with no apps running ,now I have 3 programs running and ActiveSync and the memory is 43,the last soft reset I did was ..havnt done any yet I upgraded to this rom Saturday morning.

Categories

Resources