Do I have a memory leak problem? - 8125, K-JAM, P4300, MDA Vario ROM Development

Can someone tell me if I have a memory leak problem? Here's what I'm seeing. When I do a soft boot, and load into WM6, batterystatus reports 25.8 MB of free program memory. I'm using pocket plus, so mostly I close applications when I'm done using them, thus nothing is usually left open. As time goes on, what I see is a constant, but slow decrease in available program memory. In about a 24 hr period, I can lose up to 5-7MB. Does that sound like a memory leak, or is that just how WM operates?

I had a similar problem running WeatherPanel. My device kept creating new files, instead of update the exisiting one, in Data folder, after applied an "updated" to correct the moon issue. This killed my device since the main memory would eventually run into almost 0.
I reinstalled the application to storage card and switched back to the original dll file. So far I have not get any problem yet.

Related

6.1 ROMs have SD Issues - anyone find a fix?

All of them that I've tried, thus far.
You MAY NOT see this, by the way, depending on your access pattern, but it is DEFINITELY HAPPENING.
The problem is that its really, really ugly - your card's data is slowly being DESTROYED.
When it hits the "wrong" file, you will find out - the hard way.
This is NOT a "cooked ROM" problem - AT&T's base 6.1 load does the same thing (!)
The EASIEST way to find it is to use Advanced Config to move the IE cache to the card, then play a while. Suddenly the device will lock. You soft reset, and all "appears" well. Its not.
How do I know its damaging data? Because it has scrambled my TomTom map files "just enough" that TomTom comes up "No Maps" (!) - but the file names ARE THERE. The signatures are destroyed - it only takes ONE BYTE of change in the wrong place to do it.
Now what the ##$)! is PIE doing writing in that directory? Its not - on purpose.
The RSS reader will reliably do this too.
If you point them at main memory, no problems. Its SPECIFIC to the SD handler.
Its also SPECIFIC to 6.1 ROMs. 6.0 does NOT exhibit the problem, yet EVERY 6.1 load I've tried can be provoked into doing this.
The only fix is DON'T WRITE TO THE SD CARD via programs. Well.... that's not the WORST thing in the world on a Kaiser as it has a lot of internal memory, but....
Anyone know what the #@#$ is going on here - or have a fix for it?
PS: If you think you're not running into this, don't say I didn't warn you when you find one of your files destroyed without warning. I have run byte-wise compares of SD images and the corruption appears to be almost completely random. And yes, its across both SDHC and non-HC cards (2GB) - both are hit by it, and I've got three, all from different manufacturers. This is VERY reproducable and its not hardware either since 6.0 does NOT exhibit the problem.
Quite interesting... which rom build are you using ?
Have tried several - the most recent being the Hyperdragon 11/15 build.
The stock AT&T 6.1 build did the same thing as soon as I switched PIE's storage to the card. Its not instantaneous but if you browse for a significant length of time it WILL do it.
Flashed to 3.29 HardSPL to be able to load the various cooked ones here, all that I've tried so far do the same thing. Flash back to 6.0 AT&T, no problems.
VERY consistent.
I just put 3.28 HardSPL on to see if that changes anything. Can't imagine why it would, but....
Its pretty subtle if you don't browse heavily - if you get a "lockup" with PIE while its set to write to the card YOU ARE SCREWED. You may not know WHICH file got smashed but I guarantee one did. If it smashes the MFT then the fun really begins (the entire card's contents are gone), but I would prefer that to a RANDOM file getting destroyed!
I have run sector-by-sector compares and have found that where it "scribbles" when it happens appears to be completely random.
And again - 6.0 does NOT do it, and if you only READ from the card, its fine.
I suspect that its a "per-event" risk and so anything that runs from the card and writes data back there EVENTUALLY will screw you - its just a matter of time.
Genesis3 said:
The EASIEST way to find it is to use Advanced Config to move the IE cache to the card, then play a while. Suddenly the device will lock. You soft reset, and all "appears" well. Its not.
...
Click to expand...
Click to collapse
thats why it is strongly recommended NOT TO store ie cache to storage card. Keep it on device memory. There is no fix for this problem yet except keeping ie cache on device.
Sounds pretty easy to bypass the problem, eh? Don't store stuff to the card. No big deal. I mean, c'mon, it's not like we're going to run out of memory storing the IE cache on the device.
Beside that, it must only be IE as I've always used the card to store my email and attachments and have never had a problem. However, I am using a 16GB card...perhaps that makes a difference. I've been running various 6.1 ROMs (including some questionable betas) for almost a year now and have experienced ZERO corruption. Also, if it makes a difference, I perform so much data transfer with my card on a weekly basis. Pretty much filling and emptying about every third day.
It is NOT only IE.
The RSS reader that is in there (RSSHub) that HTC stuffed in the later roms does it too.
I managed to trigger it last night with RssHub; thinking IE was the only culprit cost me (another) reload of my SD card.
Be careful - if its per-event risk then ANYTHING you store on the card (e.g. pictures, etc) could cause it, and apps like TomTom that write places you set as destinations to as a cache can cause it too - its just that being data dependant the more often you write, the higher the risk.
BTW this is a 6.1 issue that does NOT affect the Wizard - I have had a custom (I cooked it) 6.1 ROM on my Wizard for six+ months without a single screwup. But I've yet to find a 6.1 ROM for the Kaiser that DOESN'T have this problem.
BTW, is there a 6.1 ROM around WITHOUT the new PIE? God I hate the new format on that thing...
I have been beating on PIE stored on the card, plus RSS stored on the card now for over an hour - after loading HardSPL 3.28 (was running 3.29) and SO FAR I haven't had it happen.
Now this doesn't mean much, but that I got a solid couple of hours in without it blowing up - when I was pretty reliably able to do it previously - might be significant.
Or maybe not.
I'll run this way for a week or so and see if I can get it to misbehave.... I have card backups
yah i have learnt to back up my sd all the time cause im CONSTANTLY getting corruption..but corruption i can see like messed uop names and folders which ive found more consistant when i have sd power settings set to enabled in advanced config..
I have also witnessed RSSHub destroying my card several times
I remember this problem when WM5 came out on the Artemis. It was linked to the power state and the device going into sleep mode. It never occured when you used the power button, only when it went into automatic sleep. I think there are options in schaps advanced config regarding this - might be worth a try.
Genesis3 said:
Have tried several - the most recent being the Hyperdragon 11/15 build.
Click to expand...
Click to collapse
I mean CE build number and aku. We have now many available builds from which to choose, and we could investigate whether it's a problem related to an HTC driver alone or if there's something in the SYS services too which has to be patched. I'm not talking about workarounds at all.
20931.1.5.0 (assuming the SYS and XIP were ported)
I don't have the numbers from the AT&T load handy.
Downgrading the SPL MAY have fixed it. I haven't had a lock/trash since last night when I changed the SPL. Hmmmm..... that "hotfix" may have been a "hotf$ck" instead.
Will update as/when I learn more.
This is NOT WM6.1 problem, if anything - it is WinMo's problem in general (all versions).
I have witnessed exactly same problem on WM 2003, WM2003SE, WM5, WM6 and WM6.1 - and I bet its the same on WM2002 and WM2000 (I just never had any of those ancient devices).
Solution is very simple:
DO NOT move IE cache to SD card, that's all.
Unless you have to (i.e. my iPAQ 6515 have literally no space left on Main Storage and I have to use SD for IE cache etc) then simply make at least weekly backups of your SD on your PC, its not a big deal, but it is annoying like hell (specially when it happens "on the road").
I have same problem several times!
Most offen it's happend in A***OS Smart Rom (don't remember full name), then i flash into wm6.1 off and it happends only one time. I use StorageTools to ix My Card after that (not data, only card)...
Is this heal????
Just use Opera browser. I dont have that problem in my tilt, although i did had problem with hermes, and scan and fix errors for the card made it go away. And i also a 2GB card, maybe it is an issue with higher storage capacity cards.
hi there, i have similar problem with my vario 3, i have installed all my application on sd card including tomtom. I have about 500 mp3 and pictures. i can listen to music all day at work but when turn my tomtom on, it says no maps found and then everything disappears on the sd card. it still shows in memory status that i have used 70% of my sd card but it doesn't show anything in win explorer.
i think it might have caused by installing tomtom on sd card.
can anyone help please?
mohsin_75 said:
hi there, i have similar problem with my vario 3, i have installed all my application on sd card including tomtom. I have about 500 mp3 and pictures. i can listen to music all day at work but when turn my tomtom on, it says no maps found and then everything disappears on the sd card. it still shows in memory status that i have used 70% of my sd card but it doesn't show anything in win explorer.
i think it might have caused by installing tomtom on sd card.
can anyone help please?
Click to expand...
Click to collapse
To recover that files you can use de windows tool error checking that will recover your files but to the found.000 folder (hidden), but the files are useless because is will be on the wrong extension and name
you have now 2 solutions:
1 - is guest the extension of that files and rename it
or
2- use the program named "getbackdata for fat" and it will correct the name and the file extension but not the correct name of the folder where it was. but better than nothing.
hope i could help
I saw this many times with RSSHUB - finally moved to main mem and have not seen it since. I also don't use PIE. It will be interesting to see if its 3.59 causing the issue, please keep us posted. I went a bought a new card thinking that it was a bad card:
If you're running 3.29 get it off your device - in fact, there should be a WARNING on the page for the various HardSPL versions. This may be device version specific (are there multiple hardware versions of the Kaiser as there are with the MDA?) but on MINE, 3.29 does this repeatedly.
I have now been running 3.28 for a week with ALL power management enabled, RSSHub and PIE caching to the storage card, and all my user-loaded apps running from the storage card, and I have been intentionally pounding the everloving hell out of it to try to get it to misbehave.
ZERO ISSUES.
The ONLY thing I changed was the SPL. I didn't even reflash the ROM (just the SPL) when I changed it - just used Jump to get back into the "superCID" mode and flashed 3.29 down to 3.28.
If you're running something other than 3.28, try 3.28.
So far, one week in, it has completely fixed this problem on my Kaiser.
Genesis3 said:
If you're running 3.29 get it off your device - in fact, there should be a WARNING on the page for the various HardSPL versions. This may be device version specific (are there multiple hardware versions of the Kaiser as there are with the MDA?) but on MINE, 3.29 does this repeatedly.
I have now been running 3.28 for a week with ALL power management enabled, RSSHub and PIE caching to the storage card, and all my user-loaded apps running from the storage card, and I have been intentionally pounding the everloving hell out of it to try to get it to misbehave.
ZERO ISSUES.
The ONLY thing I changed was the SPL. I didn't even reflash the ROM (just the SPL) when I changed it - just used Jump to get back into the "superCID" mode and flashed 3.29 down to 3.28.
If you're running something other than 3.28, try 3.28.
So far, one week in, it has completely fixed this problem on my Kaiser.
Click to expand...
Click to collapse
Does this happen with both cmonex’s & jockeyw2001’s HardSPL 3.29?
It happens with the ORIGINAL REAL 3.29 SPL that AT&T is shipping with their STOCK 6.1 ROMs!
That's not one of the hacked ones - that's OEM. I was able to REPEATEDLY lock the device and scramble the card by sticking PIE's cache on the card with the stock AT&T ROM.
I'm near 100% convinced its the 3.29 SPL that is FUBAR'd and not the hacking on it. I don't know why it should matter (its just a boot loader) but perhaps its doing something funky with the SD interface and whatever it does survives ROM initialization during the boot process.
In any event with 3.28 on my Kaiser I have had ZERO ISSUES with SD corruption or freezes of any kind, going on a week now. I've had no reason to reset it - at all - during that time.
I won't call this "conclusive" for another week or two, but given that with my usual usage I wouldn't survive ONE HOUR on 3.29, well, you tell me.

Wizard - low memory warning won't go away

I recently started getting a "Your phone is running low on free storage space. Delete old or unused items to create more space." warning on my HTC Wizard (Cingular 8125). Which seems odd since at the time I had 12MB of free storage space. I did some research on here and downloaded clear temp. I also removed 2 applications and cleaned, via the program, the caches for Opera 8.5 and PIE. I now have 20.99MB of storage space free but I am still getting the warning. I did a power off/on. A soft reset using the button on the side and a firmer reset by removing the battery and sim card. However, I am still getting this warning. Any suggestions as to what I should do next?
Thanks,
when you get this message, please run a task manager to check how much free memory you have both in storage and in ram..
you can report back and i'll try to help you
Just went away
For some reason it finally stopped showing up.
look at me.. solving problems telekenesisly

Raphael kills SD-Cards??

Hello everyone,
i own a Raphael since January and in this time it allready killed 2 SD-Cards.
The first one about 4 months ago.
Suddenly in the middle of usage the Raphael froze and i could not get it started again. even after a hardreset it was stuck in the bootscreen.
after a lot of trying and finally removing the sd card it bootet again without a problem.
the card was not readable anymore in any of my devices or windows boxes.
i thougth myself. well can happen even when a card is only half a year old got a new 8GB card and forgot about the incident.
yesterday while listening to some podcast suddenly the sound died. taking out the phone i found out it did not reacted to any power button presses or anything the screen stayed black.
after a softreset the phone worked again but took about 5 minutes to get in a usable state and the programms installed on the sd card where not aviable anymore.
taking a closer look i found that the card was not displayed in file explorer anymore.
gave it a try with my mp3 player. same result no card was found.
today in the morning i gave it a try on the pc with an sd-adabter. but also no result, wondows does not even recocnizes any device being plugged in. tryed a few data recover tools but non of them found the card.
someone has similiar experiances or any tips how i could get my data back from the card?
i guess the phone has to be send back for maintainance, but i doubt that they will find anything, if they accept it at all.
I have changed 4 sd cards because of similar problems. But the problem is most likely because of the fragility of high capacity microSDs, I wouldn't blame Raphael. Try other manufacturers (and try to find the ones that are not just rebranded)
I've had many issues with sd card corruption, but have solved some of the issues. Here's my advice (fwiw):
1. Get a card scanner, and regularly scan your catd. I do it everyday (takes 5 min). I use Wizcode Scandisk. It fixes errors and dumps out files that can be opened in notepad. It's worth looking at them, as it helped me find the multiple sources of corruption that I had.
2. Don't put your PIE cache on the card.
3. Change all 'save' paths (esp. the camera) to main memory.
4. Store any programs you use a lot on main memory.
5. Do NOT have any programs that run constantly on the sd card.
6. Do NOT put Fingerkeyboard on the sd card (major problem for me).
Basically, my advice is to use sd cards for storage. The Raphael has a lot of memory-use it for programs. I haven't had to format my card in about 4 months. I was doing it every couple of weeks for a while.
well basically i was using my sd card as a storage place for movies and podcast + podcastplayer prog.
and was using the player more or less the whole day.
i used the same card (and the other one before) also in my mp3 player when the raphael or the bt headset run out of power and there is no power outlet aviable to recharge. and twice the card failed in the rapahel.
when i got a new card, i also found that the card is working 100% on pc and mp3 player, but the raphael still can not see any sd card.
i really blame the phone and also assume that it now has a defective reader.
have to give it back to repairs as soon i have flashed the original firmware and make my way back to the store
You should scan the disk to find out the error sources. It may be something simple that causing them. Also, if your phone freezes when listening to music, you may want to either wait it out, or remove the card before soft resetting. You should do some searches on card corruption. There are lots of threads here that can be helpful.
many Sdcard and usbStick manufacturers got lowlevel format tools you can download and get cards not otherwise working in cardreaders on pc back to life
would love to get those cards working again. but i also would love to get the data back that was on them.
but the problem is the cards do not even appear on the pc, or any other device i have that can read/write them (usb card reader, digi cam, mp3 player)
its just as if nothing is ever inserted in the reader.
the low level format tools don't rely on windows driver model to detect cards
Flash Format (cnetx) has always been able to re-format my card, even when my pc couldn't recognize it and neither could my fuze. It has a free trial that works fine.
I haven't experienced any of these issues myself. But I'm sure I will now that I said that....
i gave that flash format a try, but it even failed to install. was one of those weird .exe installers. on the pc side it told me install was sucessfull, but on the ppc side was just a promt "installation failed".
a cab install would be nice, but without a working cardreader in the phone i guess would also not be of much help. i guess cuz of that that prog will not help me much. the reader in the phone is broken. cant read any cards, even brand new unused ones that are fine everywhere else just dont show up on the phone.
as for other "low level format tools" my search was quite unsecessful. i was looking at the sandisk and the transcend page (the suppliers of my 3 cards) but could not find anything.
google just found more request for this kind of program but not really somewhere where i could get it.
patlabor said:
i gave that flash format a try, but it even failed to install. was one of those weird .exe installers. on the pc side it told me install was sucessfull, but on the ppc side was just a promt "installation failed".
a cab install would be nice, but without a working cardreader in the phone i guess would also not be of much help. i guess cuz of that that prog will not help me much. the reader in the phone is broken. cant read any cards, even brand new unused ones that are fine everywhere else just dont show up on the phone.
as for other "low level format tools" my search was quite unsecessful. i was looking at the sandisk and the transcend page (the suppliers of my 3 cards) but could not find anything.
google just found more request for this kind of program but not really somewhere where i could get it.
Click to expand...
Click to collapse
Check C:\Program Files\Microsoft ActiveSync\CNETX-you'll find the cab in there. There will be several-you want the PPC-Arm one. It should install fine.
Card Freeze
Yeah I had the same thing happen. Raphael would not boot unless I removed the card and as soon as I placed the card back into the sd slot it would lock up. Unlike you I was able to get on of my PCs (either the XP Pro or the Vista Pro) to recognize it but all I could do was format it.
OK I like the idea of moving all the data to the main however I'm an old Windows CE guy (yeah I had a Jornado) and the memory used to be shared between program and storage. The device would allocate from the other when more was needed. If I place all the stuff I want into the Raphael main memory won't that lower the amount of RAM I have for running programs or vice versa? I really don't know if the memory is fluid since all I get when I look into the memory is one listing total storage and one total program, there is no slider bar like there used to be in windows ce.
webfrm said:
Yeah I had the same thing happen. Raphael would not boot unless I removed the card and as soon as I placed the card back into the sd slot it would lock up. Unlike you I was able to get on of my PCs (either the XP Pro or the Vista Pro) to recognize it but all I could do was format it.
OK I like the idea of moving all the data to the main however I'm an old Windows CE guy (yeah I had a Jornado) and the memory used to be shared between program and storage. The device would allocate from the other when more was needed. If I place all the stuff I want into the Raphael main memory won't that lower the amount of RAM I have for running programs or vice versa? I really don't know if the memory is fluid since all I get when I look into the memory is one listing total storage and one total program, there is no slider bar like there used to be in windows ce.
Click to expand...
Click to collapse
The storage memory on the device is flash, not ram, so you don't lose program memory changing the save paths to main memory (if that's what you meant by moving data to main memory).
I never had any issues with my storage cards (sd and cf) on my 2003 device. I don't think it was the device, but rather the cards. The big, 16 gb cards just seem to be less hardy than a 1-2 gb card. I had all my apps on the storage card (including stuff like magic button), and never had a problem. But, jeez, the 16 g microsd is sensitive as hell. It gets minor bits of corruption at least once a week. I scan it everyday to avoid it crashing, which has helped, because I've gone 4 months without formatting it. One thing that I've found screws it up royally is doing a lot of file/directory operations over active sync on a pc. I don't know why, but cutting and pasting files from one folder to another in the sd card frequently results in lost clusters. Renaming folders is also a bad idea.
OK Flash
Well I guess I didn't explain it correctly. According to HTC the RAM is 288MB with a ROM of 512MB. So I'm really confused since according to the start>settings>system>memory the total for my storage and my program = 549MB which is of course more than 288 and 512. So when I load applications into my device and get a choice of main or storage card when it was a large file (some apps I use were 14 megs or more) I would choose the storage card.
My old experience with Windows CE was whatever memory was on the device was shared with both the program and storage, so I would put as much as possible on my storage card. However in windows 6.1 or higher it lists two separate columns for Program and Storage with: Total, In Use, and Free. So when I install apps I presumed they went into the storage area. Am I mistaken? I figured Program on the device meant how much is currently in use. Kinda like opening multiple windows on a PC. I notice it's low when at once I have 4 applications open on my windows mobile device so that's what I thought Program memory was.
Therefore does installing to the Main, when given a choice during program installation. where does it get installed ROM, RAM? Why is my total memory higher than RAM or the ROM
Any insight would help me decide the best location for my program installation to not corrupt the data, or have the flash card screw me up either.
288 MB is the total amount of system ram. A large amount is not user-accessible, it's used by the kernel/OS/Page-pool, so you don't see it reported. It's still there, though. The rom memory is 512 MB, but the actual memory in rom is subtracted by the storage memory so you see the amount of user-available memory. With 2003 devices, if the battery ran down, you lost all of your data, because the storage memory was in RAM (except perhaps for a little flash disk space). But with a fuze, you can pull the battery out, and not lose your data.
Totally confused
OK your right about the 2003 devices which is why I placed most of my stuff on a storage card. However why is my total reported memory 549MB more than the 512 ROM? Also when I install stuff to the device where does it get stored, the 512 ROM? Are you saying that the 200mb of Program being shown is 288 RAM minus the 88 being used to run the OS?
So are you saying its safe to install all my apps onto the device and I won't lose anything if the battery runs out?
Yeah, I've been saying that for about 3 weeks, lol! They got rid of the volatile storage memory with winmo 5; we're onto 6.5 now, and it's a thing of the distant past. I you don't believe me, pull out your battery (there's no backup battery on the device) and see if it causes a hard reset.
This is not an uncommon problem with digital cameras, as well. It's complicated, but the bottom line is this: whenever you buy an SD/micro SDHC/etc. card, you should do a full format of it on your COMPUTER, then put it in your device.

Programs on memory card quit if phone is put to stand-by

Hi,
I use Windows Mobile phones for many years. Most time a HTC Wizard, but some other devices as well. Recently I got a new Eten M800 and came across a very bothersome problem that I cannot solve and that did not occur with any other of my older devices.
Each program I install on the memory card will quit itself if I put my phone in power safe mode. Don't know how that mode is called correctly. If I push the on-button shortly or leave it to rest for a short while. If I turn the phone on again the program has been quit. This is very uncomfortable and hasn't occurred on any other WM phone I used. It even occurs with different ROMs installed on it. I already tried toggling the power management options found in the tool AdvancedConfig but that didn't help as well. I thought it might be some problem where it will lose the handles to opened files if the card is put to power management mode. I have no idea what else to try but would be very thankful for any ideas or help. Programs I've tried and this occurs with: Cachemate, Opera Mini for WM, Tomeraider. Probably this happens with every program installed on the memory card. If I install the same program to the device's internal memory the programs do not quit!
Help appreciated
Tim
Edit: One last thing that might be worth mentioning: This is the first time I use a SDHC card. I didn't try yet if that would happen with a (smaller) normal micro SD card.
thats always been the case for the htc phones I had
sd interface is disabled to save power when suspented
resulting in apps being terminated
same reason why people don't put today screen programs and stuff on sdcards

[Q] task rpcrouter:15 blocked

I have a HTC Fuze (AT&T GSM). I followed the instruction on (http://forum.xda-developers.com/showthread.php?t=951981) for FRX06 but it keeps getting stuck at "task rpcrouter:15 blocked for more than 120 sec". It never gets to the calibration screen... I even tried downloading and using a pre-made ts-calib file but the results were the same.
I also tried numerous other posts ROMS (FRX03, FRX04, XDAndroid 2.2 (rel 1.6).cab, even tried XDAndroid 2.1 (rel 2.5a).cab) but I still get stuck at the "task rpcrouter:15 blocked for more than 120 sec" error.
I read in another post back in Feb 11 that it was an issue and someone acknowledging it is an issue but no solution stated in the 19 pages of forums. Another user states this is a "bootloop" but did not offer any solution.
In any case, I never got to any graphical screens - never got past the text screens (white text on black background).
Help!
Actually the fix was to delete the data.img but that would be the "quick fix". This WAS mentioned under the troubleshooting section of THIS post. If you really want to see the calibration screen, download an older kernel package as stated HERE.
BE SURE TO SAVE THE FILE CALLED ts-calibration THAT YOU JUST CREATED!​Additionally, I want you to format your microSD and start over from scratch. Just to flush out any other issues that you and may not encounter; such as the "waiting on SD card" issue some complain about. When I say format, I mean use something other than windows to format your microSD. I use the free version of partition wizard and it seems to do the trick. IF you want something a little less program intensive, I would suggest using SD Formatter. Again, not required but it might help solve other issues you may encounter on down the line.
All of that being said, I have a RAPH110 aka at&t Fuze, so I know this process works. If it doesn't work for you, YOU are doing something wrong!
Also, if you insist that you would rather skip the calibration screen, you may use my ts-calibration file. Make sure you place it where the file called haret.exe is.
CLICK HERE for your viewing pleasure!
Same problem with FRX06 even after FORMAT with OVERWRITE of the microSD. I included the ts-calib file. Got past "Creating a new Data Store" then got stuck at "mdp irq is already 4 4 and above mdp_dma: busy" where it would retry after getting stuck for 120 sec.
I then reformatted again and this time tried "XDAndroid 2.2 (rel 1.6).cab". Got to "Creating a new Data Store" and it is stuck there for over an hour - so I gave up.
I then tried deleting the files for "XDAndroid 2.2 (rel 1.6).cab" and this time tried "XDAndroid 2.1 (rel 2.5a).cab". Same issue.
Next, I tried loading Android on the Device instead of Storage Card. Stuck at the same point... I waited 5 min then quit.
I read elsewhere possibility of problems using micro SDHC cards... do you have a microSD card in your Fuze? My card is a Patriot microSDHC 8GB.
As always, there may be a bad batch but have had no such luck with buying PNY nor SanDisk. You did download 1231 as mentioned earlier, correct? So, if you want to try that first, you'll need to delete the existing modules-xxx and zImage file and extract the contents of the downloaded file till you see the modules-xxx and zImage_xxx. Rename the one called zImage_xxx to just zImage and be sure to place them with the file called haret.exe and launch haret once more. Keep in mind, downloading the kernel packages may not be required but in order to test things out and to see what works best, it is. Good luck my friend!
So I tried again and let the install run overnight (>4 hr). In the morning, it was still looping so I stopped it. Today, when I looked at the microSD, I see 171 FSCH0xxx files... most are 32K. 170 was 192K and 171 was 1.81M total of these files were about 158MB. Does this indicate anything?
Anyway, I reformatted my microSD card twice using the SDFormatter (Overwrite, Size Adjustment on), loaded FRX06, replaced the set with the 2 files you sent and renamed the zImage file. Booting up, goes into text screen, still get the timeout error. This time I noticed that there was a line that says "INFO: task dd:91 blocked for more than 120 seconds." My guess is that it's creating those FSCK files again... meaning SD card errors?
Have you another microSD to confirm whether it is a bad card? I just started from scratch (for the 50th time today) and I am NOT seeing what you are seeing(I don't see any FSCHxxx files)... I don't suggest trying anything older than FRX06. If anything, I'd suggest you see if you can find another microSD and probably only use that card for temporary storage.
OK, I'll have to go get another card this weekend then. I do think it seems like the card has some kind of compatibility problem... what brand are you using?
For tonight, I've formatted the card twice and then am trying the "XDAndroid 2.2 (rel 1.6).cab" now... It is stuck in the "Creating a New Data store" line for >20 minutes now... (FXR06 passes that but gets hung up trying to fix the file system). I'll wait a while longer and see if it will miraculously finish creating the new data store.
Thanks for your suggestions.
I have a PNY and SanDisk both 4GB class 4. I think bestbuy has the PNY one for like 30 bucks (maybe cheaper?)
I don't know what the problem is but I'm willing to help out how ever I can
I downloaded MiniTool Partition Wizard and deleted the microSD card's partition then recreated it. Then, I recopied the files into the root of the microSD, installed into my FUZE, and clicked on herat... this time it got into the Android graphical portion (no calibration needed since I included the ts-calibration file), stayed at the ANDROID screen for a while then went blank. I waited about 6 minutes then turned it off. When I went to see what's inside the microSD, I found the data.img file 256MB and also messed up file system again - since I shut it off prematurely.
With a lot more confidence this time, I repartitioned the microSD again, placed my Android files under its own folder. Crossing my fingers...
Ah, so you've been using the file path method then? If that is the case all one would need to do is put rel_path=FRX06 in the startup.txt file, between the quotation marks. Additionally, if you prefer more ogranization and plan to run more than one build at a time, it is best to have that command in your startup.txt file for each build. Keeping in mind, once you do this, it pretty much sets the default path for that build to that particular folder. I wasn't aware that you were starting one folder deep, my apologies . It's best to use the root folder for troublshooting and what not. I prefer to only use one build at a time because I find it easier to keep problems isolated and it helps me troubleshoot at the same time.
Additionally, if you want a more easier way to troubleshoot Android issues and you don't mind waiting for the data store (aka data.img) to be recreated at boot time, then one would only need to delete the data.img file (keep in mind if you have any settings or contacts, these may be deleted as well). What I usually do is once I get a good data.img, I make a backup and zip them up (or use your method of archiving). I also make a backup before I make any changes, like if I am testing out a new rootfs or kernel package. Most of this has been discussed and mentioned in the Android forums.
That did not work so I reformatted again and went back to using the root of the microSD for Android... FRX06 was stuck on GUI but blank screen all night - I turned it off in the morning. Back to the drawing board. At least I got the microSD issue figured out... on to the next mystery.
Update:
OK, partitioned my 8GB to 7GB FAT32, 512MB ext3, 512MB linux swap. Loaded FXR06 into the root folder, booted and it works this time. However, once into Android, it would lock up.
Case 1: Boot up android, clicked on Gmail, screen is android but nothing in the screen except background. Took out battery to turn off.
Case 2: Boot up android, left it alone, screen turned off - will not wake up. Took out battery to turn off.
Case 3: Boot up android, went to settings to set up wifi, froze. Took out battery to turn off.
Case 4: Boot up android, went to settings to set up wifi, entered WEP key, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing). Took out battery to turn off.
Case 5: Replaced the modules and zImage files to the new ones you sent me (12/31/2010)... booted up android, went to settings to set up wifi, entered WEP key, shows connected, Fuze froze (I know because the screen is non-responsive, back button remains lighted after I move my finger away, and the clock on screen is not advancing).
Seems my Fuze is locking up soon after Android boot. Tried numerous times... left alone, freeze. Tried calling, freeze. It seems to be time based. So close...
Strange, though, as the phone remains warm to the touch despite being frozen for some time.
Yeah, you lost me at partitioning your device as I don't even touch that stuff. I think you are using something different. Sorry but I can not help you, my friend!
Thanks anyway... the partitioning is just to make the partition "different". Probably no relevance unless it allowed me to exclude some bad sectors from use. As far as Froyo, I guess there is some kind of HW or SW problem with my phone. I may reflash my Fuze to another WM ROM - just to clean it up and isolate SW as the problem.
Let me clarify, I don't partition my microSD because XDAndroid builds simply do not require this. There are Neopeek variants that require partitioning of the microSD but I still think your method is slightly over exaggerated. I'm not sure why but I guess for some reason there may be an issue with your microSD and partitioning may be a way around this issue but I don't know enough about partitioning microSD/non-volatile flash. So, I couldn't say for sure...
Ok, so I installed Tael ROM (WM 6.5) then tried installing, it still freezes after 1-2 min of booting up (or during boot up). So it looks like it's a hardware (phone or microSD) issue for some reason. I guess hardware vs thinking kernel because the 2.1 installs also do not work.
On another note, it seems that the Android boot process corrupts my other files... I have folders for GPS and photo (DCIM) and it "corrects" those errors and kills my files.
Hmmm... I can't say for certain as I've never experienced that issue. All of my files remain intact before and after booting into Android and rebooting into winmo. Are you talking about the files on your phone or microSD. If you are talking about your microSD, you might be experiencing the hardware issue and the while you boot into Android, it is only attempting to "fix" these issues and in the process, kills the files contained with-in. Does this makes any sense?
Yes, the files are those I mentioned are in my microSD. So, yes, looks like some kind of interface issue causing Android to think the files are corrupt and then try to "fix" them. Strange though that WM does not try to fix the "errors".
I think it's kind of like the linux way to make sure there won't be any issues when you run the OS, since Android would run off the microSD and not from the phones storage. Currently, there is some development for this called NAND. Still really nothing solid as to whether it will work or not but always good to know, I guess?
Well, the thing is those files are pictures/videos/GPS maps... so I think WM is able to read them (so not an error) yet Android does during its pre-boot scan. Anyway, since upon successful scan and android actually loads, it would freeze in 1-2 min, so the problem may not be limited to the microSD. Yeah, perhaps the NAND will work better. I did get Warm Donut to run on my old Tilt, so I am still hopeful.
The issue that is stumping me is that I'm not experiencing the same issues you are with XDAndroid and I'm not sure how else to help aside from using another microSD to confirm an issue with your current microSD.. sorry

Categories

Resources