[decibel]

Originally Posted by decibel

Ok... I finally found the problem for the "Ringtone is Corrupt" in 21502 on my Touch Pro. If I don't cook in "Widgets" or "WMWidgets" in the stock SYS, the problem does not occur. As soon as cook that in, boom, error. So something in here is causing issues with the Sounds & Notifications cpl and/or Phone cpl. I had it happen ONCE right after flash on the PHONE CPL, but as soon as I soft reset it goes away. However, it could stay gone for a day or so, then it might return. Soft resetting fixes it though. So, WMWidgets isn't the only package causing the issue. If someone wants to take the time to decipher a debug log to find the culprit in the Widget package, be my guest. I do not need that package, so I just won't include it from now on. But others might still want to include it, so a debug log should point to the culprit. Further, like I said, I still get the error every now and then (once a day, once every other day) and I have to soft reset. I have no clue where this might be occuring now. Since I can't produce it on flash/soft reset, it makes it very hard to find the package involved. I turned on debug and will have to wait for it to happen again. Like i said, as soon as you soft reset it goes away, so I just enabled debug (which requires the soft reset) and went to "cause the error" and low and behold it was gone again. So now I wait.

EDIT: Da_G and I are starting to think this might be a memory overlap issue. Something that Ervius is suppressing in the new bepe style kitchen. I am going to run another G'reloc to see if any overflows are happening I didn't catch. I am going to run it with WMWidgets built in, because really, nothing in that Package should cause this error. I'll post my results in a few.

And the results are in. Looks like there were overlaps in the Widgets package, as well as a couple others. I have now built a ROM (and am flashing as we speak) that completely passes G'Reloc. Here are the trouble files from my G'Reloc:

IEActiveX.dll - integer overflow (Found in AdobeFlashLite)
riplugin.dll - integer overflow  (Found in WMWidgets)

The files below I don't exactly know what the error is, but if G'Reloc is having
an issue with it, I don't know what/how Ervius/Bepe handle it, so I just 
collapsed them.

downloadservice.dll - I/O Error 105 (Found in FWUPDATE)
sqlcese30.sys.dll - I/O Error 105 (Found in SQLCE)
TraRecoEnu.dll - I/O Error 105 (Found in Transcriber)
uiserviceplugin.dll - I/O Error 105 (Found in FWUPDATE)

I am thinking we CDMA folk are having issues with these new sys' because they are starting to utilize the native 6.5 kernel. The native kernel has better (or support in general) support for the larger memory allocations. Where we are getting the integer overflows, GSM folk don't really have to worry about it (if using Da_G's xip/kernel/rom/kitchen) because their kernel can handle the larger memory sized files and alloc's. So I am thinking if we make sure to collapse what needs collapsed and make sure there are no memory overlaps, we should be fine. This is a major problem with WMReloc and bepe/ervius new. They both suppress the overlap warnings/errors and just continue on with the build. If you look at the log files, you will see these warnings and even the memory alloc's that are overlapping. This is bad. So making sure everything is clean and tidy with G'Reloc seems to be the fix/right way for now. Hopefully one day CDMA will get a native 6.5 kernel so we can have the stability found in the GSM world. Just my ideas.

Originally Posted by decibel

My only problem I still cannot figure out is my "Alarms". They will not play the specified alarm tone, period. They will play the reminder tone and vibrate and everything, but will not play the alarm tone at all. When you are setting the alarm tone, it sounds just fine, but when the event fires, no alarm tone. I have tried all 3 alarm slots, and no changes. I have tried turning off all options (vibrate, repeat, play, etc) and re-enabling just the play sound option and still nothing. This one is driving me batty. I have dumped everything out of the ROM except OEMDrivers/OEM_LANG_0409 (and used Stock ROM dumped OEMDrivers/OEM_LANG_0409) and the problem was still there. So it has to be in the SYS somewhere. Since the stock is 6.1 and the problem occurs in 6.5, comparing the 2 SYS's for differences is almost an impossible task. Anyone have any ideas on this?

Ok.. this is still eating my lunch. Anyone?