Fix Memory Leak problem in 1.35 ROM - Touch Diamond, MDA Compact IV General

This is probably a stupid question, but is there any way to fix the TF3D memory leak problem in ROM 1.35 without flashing 1.37 - in general terms, I love my new toy and not being conversant with things like Hard SPL etc. I am nervous of trying to flash the new ROM in case I brick my device.
Any suggestions most welcome!

It would appear that 1.37 has the problem too - ref this post:
"I have Install Europe 1.37.405.1 Yesterday now I had a problem my memory gets full ( %80 - 85 ) without using any program or any function. When I softreset the device its around %50 - 55 but in 1 hour without using it reaches full.
Whats the problem ? Does anybody could have a solution or any idea for reason ?"
Any ideas?

I had the 1.35 ROM and the leak problem was so bad that I could not run Youtube at one point in time as the storage memory went to about 5mb only. I had to hard-reset to get back the memory. Thereafter, the storage memory would be on average about 30+mb.
I've just upgraded to 1.37.707.1 and it seems the leakage stopped. My storage memory started off with 60+mb. Now it hovers around 51mb.

I have rom 1.37.405.1 WWE and my memory is at 36.65MB free from being left on last night.

Related

READ ME before you start posting questions (FAQ, SimLock)

Hi all and thanks for viewing this post before you start asking questions that have been answered several times before.
For Sim(Un)Lock tool GO
Many questions can be found on the WIKI.
WIKI main page.
WIKI page for the Blue Angel
The WIKI is a website connected to this forum, and all information on the WIKI is posted by users of this Forum.
SO CHECK OUT THE WIKI, and read it.
GENERAL FAQ GO
Index of WIKI
How to upgrade to the latest rom GO
Bluetooth upgrades GO
CAB files GO
Extended Rom GO
Radio ROM GO
Upgrading the Blue Angel GO
****
More will be added later[/url]
Nice post, Bosjo....great idea....now let's hope people read this, so I can stop referring to the links in my signature...!
bosjo, add the new 1.40 Tutorial I added to wiki, it makes the seperate Bluetooth and Radio ones obsolete (largely) as 1.40 include 1.12.00 and 1.0.0.3900
The noob finally did it
I want to thank Brazillian Joefor helping me out with my ineptness to READ THE WHOLE WIKI first- I finally upgraded to WM2k5 flawlessly after nearly 6 hours and despite sctatching a bald spot into my head everything is great.
I also want to thank Helmi and everyone else that made this all possible this site is a real asset keep up the great work.
Siemens Sx66 Model ph20b1
Used the unlock on 12/07/2006 on referenced Cingular phone purchased somewhere around April 2005. Worked like a charm, phone now works great on T-Mobile.
I failed to download MaUpgradeUt_noID file from the ftp site for resolving the country code error problem. For tha I am requesting you please upload the file in rapidshare.com (or arrange to upload).
It will be a great help for me.
Thanks
I installed WM6 with a simple PIN last night. This morning I switched SIMs and when switching on I entered the normal PIN and it says "incorrect password".
I haven't changing the PIN and it worked last night. Of course now it goes into longer and longer gaps before you can do anything! and now i must wait for 34minutes before i can try my "lucky" PIN..
No problem I thought, I'll just do a hard reset... but BIG problem. It appears that WM6 won't let you do a hard reset from the unlock screen.
Does anyone know if they have changed the hard reset procedure in WM6?
From the device being powered on I am pressing an holding the power button, pressing the reset and then letting both go simultaneously - is this correct?
It is nice to know if someone steals your 'phone that they can't use it - not at all good when a bug in WM6 makes it happen to the owner!
I have a completely useless brick at the moment...
need your help guys..
Links for wiki don't work, any idea where to get these info from?
in the top bar there is also a link to the wiki, or take this one: http://wiki.xda-developers.com/
EDIT: sorry, apparently i misunderstood, the wiki is apparently experiencing problems and is currently down.
turning off alone.
I upgraded my BA to d-two's WM6.5.5 Build 23529, and now when the battery is on 30%, he turn of or reset and keep doing aftera a while when i turn on again. Chief tony, you know this error?
you should always make sure that your battery is completely full when upgrading. there's been people before, reporting that their battery meter is screwed up after upgrading. so, i guess the 30% are just not an accurate value and the battery is in fact empty. you should load up the battery up to 100% and re-flash the rom. the values will be more accurate
then.
another reason could be that your battery is really starting to go bad and maybe should be replaced.
Hi Chief
Hey chief tony, i reflashed my BA with full charge, and instaled the Wm 6.1 manilla 2d final from D-two, and i've got what realy happens, everytime i used the wifi conection, is doesnt take long and Ba turn of, and when i turn on where it must have the radio version, it appears 'none', so i soft reset and gets ok. you know whats happening?
ps: sorry for the bad english
the fact, that it turns off quickly again, points to the battery having lost most of its capacity. maybe you should have a look at ebay for a replacement.
it shows R NONE G NONE, because unplanned switch-offs or soft resets, that are not triggered by the reset pin cause the phone to boot without radio, some roms start without the radio then, some don't boot at all. it happens with all custom roms and soft resetting is the only way to avoid it.
Chef_Tony said:
the fact, that it turns off quickly again, points to the battery having lost most of its capacity. maybe you should have a look at ebay for a replacement.
it shows R NONE G NONE, because unplanned switch-offs or soft resets, that are not triggered by the reset pin cause the phone to boot without radio, some roms start without the radio then, some don't boot at all. it happens with all custom roms and soft resetting is the only way to avoid it.
Click to expand...
Click to collapse
I wouldn't blame the battery so fast on this one (although entirely possible). There are a few roms (not sure about d-two's 6.1 since I have not tried it) that will become unresponsive once you activate Wifi (not sure why), and eventually resets the device... He could try a different rom and see if that helps.
Hi,
I am trying to get the "For Sim(Un)Lock tool GO" but when I click on GO it returns "No input file specified."
Any other links that I can get this tool to unlock my Blue Angel...
Jay
this tutorial is quite outdated, the one linked in my signature is new and all links are working there. in the 2nd post, you will find the tool needed for the sim unlock and many more
Re-detecting my 1gb sd card!
Hi, Chef.
I initially had some issues with my 1gb sd card after upgrading to m 6.1 & then 6.5.3. But, after a vista laptop detected an removed a virus (autorun file), I was able to access again.
Now, after upgrading using sun dream's latest rom (6.5.5), my sd-card issue has re-appeared. I have just formatted the card (tried either fat or fat32) and still no progress.
Other Issues: Activisync's complaint about my having to increase the size of my mailbox & delete one or two other files is becoming too frequent.
my ba now trips up (or shuts down completely) when d battery is around 50%.
What next?
MDi
Idiake MD said:
Hi, Chef.
I initially had some issues with my 1gb sd card after upgrading to m 6.1 & then 6.5.3. But, after a vista laptop detected an removed a virus (autorun file), I was able to access again.
Now, after upgrading using sun dream's latest rom (6.5.5), my sd-card issue has re-appeared. I have just formatted the card (tried either fat or fat32) and still no progress.
Other Issues: Activisync's complaint about my having to increase the size of my mailbox & delete one or two other files is becoming too frequent.
my ba now trips up (or shuts down completely) when d battery is around 50%.
What next?
MDi
Click to expand...
Click to collapse
What Rom do you have?
ROM: sun_dream's WM6.5.5 Build 23569 CHS WWE
Radio: 1.15

people who have tried roms with 30meg free space

Just a quick poll... wanting to know how to take the direction of future roms
wow, 130ish views and only 10 votes... there has to be more than 10 people that have tried the new roms...
Love to try it.
Would try it but I don't want to reinstall all my appz and contacts for the new rom. Very time consuming and my build is pretty stable, have no complains for it. Unless anyone can tell me a easiler way to upgrade and have all my setting and stuff back be great.
Heard spiritbackup has the upgrade function but I don't like to use spirit backup always run into problems and it's slow. Spb backup seem so much faster and user friendly, but it doesn't have upgrade function I believe so ..?
Molski 30 MB WWE ROM
I installed this ROM yesterday, until now it works very well. I was using the KTAMAS AKU 3.2 ROM for 3 weeks, no really problem, once I did nor receive a call, and I had mybe 3 softreset.
using 2.26 tmobile rom with 20mb free after paging pool reduced. no problem so far. even restored backup seeing is similar 2.26 rom jus reduced paging pool. and now updated radio rom to 2.45. same speed as before. not fast but not slow either.
Although it's my own Rom, I don't see any difference with my previous 2.26.10.2 Rom, only difference is that I have more free RAM space!
Regards,
Molski
p.s. And I don't know how it comes that some people have trouble installing it, that it hangs at 98%, 99% or 100%. It is exact the same Rom as my other ones, only 2 numbers are edited in a .nb file with a hex-editor, nothing more, nothing less.
molski said:
Although it's my own Rom, I don't see any difference with my previous 2.26.10.2 Rom, only difference is that I have more free RAM space!
Regards,
Molski
p.s. And I don't know how it comes that some people have trouble installing it, that it hangs at 98%, 99% or 100%. It is exact the same Rom as my other ones, only 2 numbers are edited in a .nb file with a hex-editor, nothing more, nothing less.
Click to expand...
Click to collapse
i have issues with my own roms doing that sometimes also... even without editing anything, just normal roms hang at different spots... its weird, it could be the pc thats hanging or waiting for the device to catch up... something

buggy wizard?

hello, im running underground wm6 on a 8125, with a sandisk 2gb card, and fairly little apps installed. as of latley, my device keeps locking up..like ill unsleep it, and itll be a half black screen...or sometimes its the main screen but nothing works...this usually happens when the phone has been idle for a while...
any suggestions?
Greets,
the rom u are using is quite old and buggy there are good roms out now check the wizard WM6 thread. This will solve your probs.

Solutions to charging and standby freeze?

Hi! For a while I've been searching for a reason why my phone seems to freeze almost daily while charging or before / after I snooze a morning alarm. And sometimes during the night, maybe it's random. By freeze I mean the phone is sleeping and when I push the power button nothing happens. The only way to restart it is to take off the cover and either remove the battery or press the little reset button.
I use itje's ROM with standard WM6.5 and Manila 2.1. I tried diferent builds and newer Leo ROMs, but I always get the same problem. It didn't happen some time ago when I was using WM6.1 + Manila 2.0.
While searching in the forums for solutions, I noticed there are some users with the same random freezes using various ROMs from different chefs. But most of the users don't seem to have this problem, which is weird. I guess the hardware should be the same, so does anyone have any idea why this freezing happens only to some of us?
I tried different methods and ROMs, countless hard resets and re-flashes, even additonal Stock-SPL and Hard-SPL, but nothing seems to work. It even happens if I install no other programs and don't have the SD inserted into the phone, only my SIM card. So it's not from external programs (like G-Alarm) either.
Well, any helpful information or advice? Thanks!
I am experiencing the same problem. If anyone got a solution for this, please share.
Regards, Eduardo.
i have the same problem to but only with the cooked wm 6.5 roms and higher not with the rom that came with my x1
i get the same problem. i'm using itje's Touch I-T Xperience 15 6.5
Now I flashed a WM6.1 ROM with Manila 2.1 to see if I still get the problem. Do you think our phones have a problem with the Windows 6.5 builds or maybe the problem is with Manila?
Did anyone try to live with one of these ROMS for a few days with Manila disabled to see if you still get the freeze? Maybe I'll try this also after I finish my 6.1 test. It's very annoying that we don't even know the cause for this freeze yet...
have the same problem when using 6.5 but when on 6.1 nothing of the kind...
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Well, I can confirm that on various itje 6.5 ROMs I get the standby of death without installing any alarm program. I didn't install ANY programs, for what it's worth. And others can use G-Alarm 2.3 and don't get this freeze.
Didn't use Valkyrie ROMs yet. I'm testing now Touch X 10.8.2 and I have G-Alarm 2.3 installed. Let's see if it dies in the next 48 hours while on a 6.1 build...
Here is my experience...
I never got standby freeze issue(never used G-alarm/Klaxon), but i do get black screen or garbled screen issue randomly while receiving call irrespective of the ROMS(wm 6.5/6.5.1).
Only one time almost a week i didnt face this issue, then later problem repeated. So i realized that week i've used COM4 build. So for testing it i tried again same one for a week and problem didnt exists. Since the ROM which i used has default X1 dialer which i didnt like at all.. so got updated to other ROM and started face the same issue
Maybe some of us have a slightly different harware in our X1 that triggers this freeze, but only in WM 6.5?
So far the WM6.1 + Manila 2.1 is working fine, lots of customizations made by me after flashing too. G-Alarm managed to wake me up OK.
Darkchaser said:
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Click to expand...
Click to collapse
Well you can count Valkyrie 4.5.502 out because i installed it yesterday and this morning after my alarm went off about 20mins later the phone frooze. I have been experiencing this for the past months and i REALLY hate this phone now. I have tried all sorts of tricks from reseting the phone around 9pm to just not running ANY program and it still freezes. I have tried all sorts of roms with the exception of Touch X 10.8.2. I guess i might as well give that one a try. I will keep an eye on this thread for a solution.
On an older Valkyrie TR build I was getting the problem and I fixed it by doing a soft reset with the SD card out, waiting for everything to load up and run nicely, then inserting the card again. Went to the music tab and waited for it to load all my tunes and the same with photos. Didn't have the problem after that, but I was only on that ROM for about a week.
I thought it may be related to usb port driver issues in WM6.5, but it could also be the audiomanager in manila or some conflict between a WM6.5 process and a manila process.
Anyway, will be trying 4.4.81TR Valkyrie and see...
But the biggest question is why some (most) people never have this problem...
Never seen this problem on WCX 22001 Pure wm6.5 rom and I'm using it for about one month. I've installed many apps and my X1 works great with battery about 2-3 days using WIFI, BT, and all other stuff. No Manila - no problem in this case. It's an older build of WM6.5 but with newer builds WCX Rom users didn't complain about freezing problem or alarm issues.
So maybe it's Manila?
Today I wanted to flash Itjes newest ROM but I'll wait for solution couse my phone should wake me up today
Can program your phone Lockscreen has frozen the rechargeable device. Best before charging you restart your phone and not run any programs.
yes i get this problem too.. every morning my phone is off.... so it really needs to be looked into.. it seems to occur from more recent builds of 6.5..
i was previously using a wild child pure rom from about 3-4 months ago (6.5 early build)... this issue never happened...
then recently i upgraded to the V11 Unoff series and now it occurs.. and is obviously occuring for a lot of people with other recent builds of 6.5...
if the solution is ever found please let us know....
I might be completely off here... but I used to have this problem often, in addition to having slide to unlock malfunction on me, even with the newer rom builds.
When I unchecked the boxes that said display owner information/notes when device is turned on, both problems were gone - it might just be a coincidence though and I've only been testing it for 2 days.
Hey guys,
I've been having the same problem, only that this are the situations in which I faced the issue with my X1i (and managed to replicate the freeze):
-Receiving SMS while charging (no pc conection)
-Charging while alarm goes off (again no pc)
-When task or appointment announcement sets itself to sleep (i.e: you ignore it) while charging. (go figure, no PC)
-When after ignoring (not hitting dismissed button) task or appointment screen shuts off (Running on battery)
I've also gotten the problem in other situations, but i couldn't replicate them. The only Thing I did notice was that there is a growth in the rate this happens over a span of 3 days after flashing/hard reseting. In my case, it was one increment per day (ie: 1st day, happened once; 2nd day, twice; 3times the 3rd day.. then, i reseted or replicated, so my statistics went down the pipe )
Other thoughs: what radio are you guys using? maybe we can narrow it down to a radio as well. Thus far I've seen it narrowed it down to Manila 2.5, but then others do not have this (and then there me, with Manila 2.1, that has it ). I changed my radio y-day and hasn't happened yet (xing fingers though...) wil try to replicate tomorrow after my alarm wakes me up
My info:
X1i Black (came with R3 generic UK ROM, Radio. 1.14...)
Issues happened with: Radio 1.10.25.18 (Installed with NRG's ROM vOCT 28)
ROM info: (see signature..)
Manila: v2.1.191...
Current radio: 1.14...
Carrier: AT&T US
I tried to contribute as much info I could get about this issue... hope we can get it solved.
I'll try to flash again a WM6.5 version to see what radio will be installed. This week I needed my phone WORKING , so I used a 6.1 ROM.
I didn't find a pattern for my freezes, but I think it mostly happened while charging from the outlet, or in the morning before the alarm went off (very bad thing to happen), or after I snoozed the alarm (again, very bad).
I read somewhere that it's useful to format your SD card before flashing. I don't see how this could help, but I'll try to flash via USB or from another newly-formated SD card. I always flashed with kovsimg.nbh on the SD root and I only formatted it when I got the phone, 9 months ago...
Also, some say it's good to flash first an original ROM, hard reset, then install the custom ROM again. I tried that, even stock-SPL and hard-SPL again, but didn't seem to work. Maybe I had 48 hours without freeze, but then it started again.
@8SE8 - I never had those options checked, so we can rule that out I guess.
I have been reading about this issue here and in another forum - mainly
because I had seen it only one single time. It actually occured when I was
loading the device during the night. I do not remember which ROM it was
exactly, except that it was an itje ROM with Manila 2.5.
Then, I went back to Manila 2.1 and WinMo 6.1, Touch_X 10.X.X. Must say,
that is still my fallback ROM, it feels extremely fast, it is stable, memory
usage is low - what else to wish?
Next, I went to the multilanguage Rhodium based Manila 2.1 and WinMo 6.5
from itje in my own language. After installing FM Tuner, a correct dialer and
some tweaks, it is also very fast and stable, memory usage at 50%. No more
soft resets since almost a week now, no "stand-by of death".
The difference to others is maybe: I do not flash using the SD card, always
with the USB connection. Is this provoking the difference? I cannot imagine,
but this is what I can contribute here.

SOD caused by Manilla (97% CPU)

Hello everyone,
Yesterday I installed the official upgrade from HTC for my Diamond 2. Besides my personal settings, I installed a task manager from this site. Now, my phone has continiously 'Sleeps of death'. Sometimes he wakes up after 5 minutes or more. I opened the taskmanager and I took a look to the processes and everything was ok, except Manilla, which had a CPU usage of 97%.
I have a WWE edition phone.
Can someone help me with this? I searched for 'Sleep of death', but those issues are from july 2009 and at that time there was no upgrade yet.
EDIT: I deïnstalled the Task manager already .
I have restarted the device once again and now I looked from the beginning to the processes. It seems that first services.exe uses a CPU from 90% and higher and after a few minutes, this decreases and then manilla goes to CPU usages of 95% and higher.
First question will be:
Did you hard reset after you flashed your new ROM?
O, I though that flashing a new ROM goes hand in hand with a hard reset. I didn't. Why is it necessary?
Reminence of the old ROM will remain as the RUU flash doesn't completely overwrite 100% of the blocks. A hard reset will almost always resolve any issues.
Issue still not solved
Ok,
I've just executed a hard reset. The problem is still there. After the first soft reset, required for some adjustements, he had again a SOD.
What is wrong?
I assume you are not HSPL'd as you are installing stock upgrades, correct?
Did you download the upgrade from HTC's site using your S/N?
There are a few things you can try.
You can reflash the upgrade. Always HR after.
You can download MTTY and perform a "task 29" which will wipe your flash drive and provide a clean platform to flash to.
or, reflash to your stock ROM, then try to reflash the upgrade.
Also, search on SOD as there may be other fixes that I am not aware of.
The typical cause is driver incompatability.
I always install the official upgrades after downloading them from the official HTC site with my serial number.
I'll try your method and after that I'm going to report it here if it was helpfull.
Thank you!
Possible solution
I just read the topic about the problems with the HTC sms application. Well, I discovered, that this app also causes my problems, becaus it loads all smses all at once, every time I have to use it. It just seems that this HTC app isn't made for such a large numbers of messages.
The solution can be found in this topic, I think: 631449
I'll try this...
EDIT:
Ok, I found the solution! It was indeed the HTC messaging app what caused my problem! I installed the 'Zenyee Disable HTC Messaging 1.2' application and now my smses at loaded within seconds! I hope that HTC will come with an update for this app soon. It was very nice, but I can't handle a 1000 messages.
My mum had 3k+ smses in her TD2, and was experiencing lag.
I upgraded the ROM to stock WM 6.5 2.53.707.4 (Manila 2.5.20113030.0), (no other programs installed)
and then restored the trimmed-down 1k+ smses via MyPhone
Sense was extremely sluggish. The phone started having the Sleep of Death - soft reset and power on, power off after 5 seconds, power on for 1 second, power off for 10 seconds - power on - SOD!
The problem was solved by turning off Sense (from Today), and disabled the HTC Messaging with "Disabling HTC Messaging in manila 2.5" by zenkinz. The cab didn't work, but edited the registry manually and is now running the SMS Patch - it works fine now. Snappy on and off, runs programs smoothly.
I think that Sense 2.5 was never meant to handle thousands of SMSes.

Categories

Resources