WM6.5 build 21501 kitchen

[savior02]

Originally Posted by xd1936

I use Ageye's G-Alarm for alarms, and haven't noticed a problem. Try it: http://www.ageye.de/

i also have this problem and i also use galarm but still same results..i even checked to fix windows bug....i fixed it by adding 5 minute alarms quick and standard..some rang some didnt..but now after a few it works now..weird...

[GaryP2]

Originally Posted by xd1936

So... The Viigo Public Beta doesn't work with this build... I have no idea what the problem is, and Viigo tech support already knows about the issue and is unable to replicate it:

Has there been any progress toward gettng Viigo to work with 20931?

[xd1936]

There's something wrong with the compatability of the .NET version included in this ROM, and Viigo's codebase. The Tech Support I talked to went through the trouble of flashing a custom ROM with 6-on-6 and .NET 3.5 on it, and had no problems...

The only think I can think is different versions of .NET. Anybody??

[gguruusa]

Originally Posted by xd1936

There's something wrong with the compatability of the .NET version included in this ROM, and Viigo's codebase. The Tech Support I talked to went through the trouble of flashing a custom ROM with 6-on-6 and .NET 3.5 on it, and had no problems...

The only think I can think is different versions of .NET. Anybody??

First, it's not a rom, it's a kitchen. 2nd, what ROM did he flash? What did you flash? Only .Net 2.2 is built in by default.

[1loudsvt]

once you complete the kitchen it makes a rom and 3.5 is built in 2.2 is an option in the kitchen....

[gguruusa]

Originally Posted by 1loudsvt

once you complete the kitchen it makes a rom and 3.5 is built in 2.2 is an option in the kitchen....

lol - you're right!

[xd1936]

Originally Posted by gguruusa

First, it's not a rom, it's a kitchen. 2nd, what ROM did he flash? What did you flash? Only .Net 2.2 is built in by default.

1. Yes, I know the difference, however it is the ROMs on my device, not a kitchen, and that it was I was referring to. The ROMs that I have created. The .Net included in the ROMs made by this kitchen will all not work, however I haven't tried the .Net 2 option.

2. I am not sure, creating the chance that I was lied to and brushed off. It would be in the best interest, though, for them to test the latest Windows Mobile, so I believe I was told the truth. This is the email I got:

"Sorry it took a while to get back to you. I did spend some time today trying to simulate your problem. I was not able to reproduce the problem on my end. Viigo runs fine on WM 6.1 professional, CE OS 5.2 20757 and Internet Explorer 6. I tried to look in to installing the cooked version you are using, but it seems very time consuming. I will not be able to do this at the moment due to the other deadlines I have to meet at work. I will still try to reproduce the problem if things ever slow down here at Viigo Inc. Hopefully when Microsoft releases the official version you can get Viigo to work again on your device. "

I don't know if I'd say "time consuming"

The bottom line is, other people are reporting the problem as well on other cooked ROMs, and it is believed to be a problem with the .NET version. I have used this kitchen for over a year now, and have had no problems until the last two or three builds released

[gguruusa]

Have you tried installing .net35 after booting (from .cab)? It shouldn't change anything, but you never know.

[xd1936]

Are there different versions of .Net 3.5?

[xd1936]

Well, I can confirm that it's a problem with .Net. I have tried selecting 2.0 and upgrading with the CAB and it does not work. However, .Net 2.0 does. Guess we'll have to wait to figure out why certain apps have .NET 3.5 + This Kitchen's ROMs