8 APR 09 - UPD 25: Mods please lock this thread! - Page 76

oldman · #1 (**permalink**) 03-05-2009, 11:32 PM

Quote:

Originally Posted by impudent1

I apologize, but I'd rather spend the night in a cell with Bubba than tackle that problem. .

Bubba's comin....get ready

gman4471 · #2 (**permalink**) 03-05-2009, 11:32 PM

Quote:

Originally Posted by redd214

i have a pretty unique question hopefully someone can help me out and i apoligize for the length of my post...

backstory: the reason i got a winmo phone is because of my work. we used to use palm software for our mobile applications but we just switched to winmo 6.1 to do the same thing

now they just released the new software for us and i have been having a VERRY tough time getting it to work with my ssk 1.5 rom. the help desk couldnt help me so i tried everything, deleting apps, hard resets, etc and still couldnt get it to work. i was using build 21015.

i decided that maybe the build of winmo might have been the problem and guess what, it was so i reflased with the stock build and low and behold it FINALLY worked. i alos tried every other build and the only one that worked was the stock one.

now the question i have is what is so diff. between the build numbers that would cause this?

i am still somewhat of a newb so i hope this isnt a dumb question and hopefully my story makes sense. if anyone could assist me or if you need more details any help would be appreciated cuz the stock build.... well it sux lol. i would much rather use the newer ones.

thanx in advance!!

Are you able to share what application you are having these problems with?

Does your company automatically provision your phone with SCMDM by chance? (Microsoft Systems Center Mobile Device Manager) I have been having issues when mixing together domain enrollment and certain applications that were not present in the stock rom

jucytec · #3 (**permalink**) 03-06-2009, 01:11 AM

Quote:

Originally Posted by redd214

i have a pretty unique question hopefully someone can help me out and i apoligize for the length of my post...

backstory: the reason i got a winmo phone is because of my work. we used to use palm software for our mobile applications but we just switched to winmo 6.1 to do the same thing

now they just released the new software for us and i have been having a VERRY tough time getting it to work with my ssk 1.5 rom. the help desk couldnt help me so i tried everything, deleting apps, hard resets, etc and still couldnt get it to work. i was using build 21015.

i decided that maybe the build of winmo might have been the problem and guess what, it was so i reflased with the stock build and low and behold it FINALLY worked. i alos tried every other build and the only one that worked was the stock one.

now the question i have is what is so diff. between the build numbers that would cause this?

i am still somewhat of a newb so i hope this isnt a dumb question and hopefully my story makes sense. if anyone could assist me or if you need more details any help would be appreciated cuz the stock build.... well it sux lol. i would much rather use the newer ones.

thanx in advance!!

Red welcome to the forum..

I think I know why your special app might be crashing...

.NET compact framework 2.0 and 3.5 are separate packages, but... 3.5 UPGRADEs some of the 2.0 Packages with Service Packs. Having said that, the Original SYS included with Vz's stock ROM has just .NET 2.0. Scott's ROM and many other cooked ROMs already pack 3.5 in the SYS or the OEM package.

Your solution may be as simple as getting a SYS version of 2.0 .NET and replacing the 3.5 folder entirely (if you are cooking that is...). You special App just might not support the Service Packs included in the 3.5 package.

gman4471 · #4 (**permalink**) 03-05-2009, 11:24 PM

Quote:

Originally Posted by impudent1

When it says select only "one" that doesn't mean go ahead and select nothing. SELECT ONE, you will have a much better outcome.

That would of course make sense, however I was just following your suggestion:

Quote:

Originally Posted by impudent1

...make sure that BOTH battery icon options were not selected...

With the stock battery icon selected I get inaccurate readings. Oddly enough, when I do not select any option for battery icons I get the cab error that I mentioned above (which makes sense) but other than that the battery icon works fine.

Which is why I was wondering if this error was preventing the customize app form installing anything past this point or if would simply continue going about its business even though that exception was thrown.

Where is the customize app and config files located? Would I be able to manually edit this file after build os runs to remove the battery.cab entry?

Thanks!

impudent1 · #5 (**permalink**) 03-05-2009, 11:32 PM

Quote:

Originally Posted by gman4471

That would of course make sense, however I was just following your suggestion:

With the stock battery icon selected I get inaccurate readings. Oddly enough, when I do not select any option for battery icons I get the cab error that I mentioned above (which makes sense) but other than that the battery icon works fine.

Which is why I was wondering if this error was preventing the customize app form installing anything past this point or if would simply continue going about its business even though that exception was thrown.

Where is the customize app and config files located? Would I be able to manually edit this file after build os runs to remove the battery.cab entry?

Thanks!

uh oh... I sent you a PM with a link to my documentation didn't I? I have not encountered this error, so as bob says "one of the smart guys" might just have to help. I'm going back to read your previous posts, so I can get myself up to speed on this issue. If I have any suggestions that I think may be beneficial I'll put in an edit on this post. If not, then we are in the same boat.

impudent1 · #6 (**permalink**) 03-06-2009, 12:04 AM

for the 2 guys with 21015 battery issues, I'm attaching my buildOS screenshots, just so you can see what I'm running on a working build without issues. No promises that it will work, just a good starting point.

gman4471 · #7 (**permalink**) 03-06-2009, 01:03 AM

Quote:

Originally Posted by impudent1

for the 2 guys with 21015 battery issues, I'm attaching my buildOS screenshots, just so you can see what I'm running on a working build without issues. No promises that it will work, just a good starting point.

The percent over battery icon seems to be working, its only the stock icon that's having issues.

impudent1 · #8 (**permalink**) 03-06-2009, 01:15 AM

Quote:

Originally Posted by gman4471

The percent over battery icon seems to be working, its only the stock icon that's having issues.

Glad I never tried it LOL!

**redd214** · #9 (**permalink**) 03-06-2009, 12:20 AM

sorry for my ignorance, but basically what ur saying is that i cant install 3.5 on my phone because itll prevent it from working? damn that would suck cuz i have a few apps that require it. thanx for your help

EDIT: i searched but i couldnt find an answer, but is it possible to have netcf 2.0 and 3.5 at the same time or will 3.5 automatically overwrite 2.0?

impudent1 · #10 (**permalink**) 03-06-2009, 12:36 AM

Quote:

Originally Posted by redd214

sorry for my ignorance, but basically what ur saying is that i cant install 3.5 on my phone because itll prevent it from working? damn that would suck cuz i have a few apps that require it. thanx for your help

EDIT: i searched but i couldnt find an answer, but is it possible to have netcf 2.0 and 3.5 at the same time or will 3.5 automatically overwrite 2.0?

Dude, the only difference between your ignorance and mine, is that I stumbled upon some info. I've can flash a rom and a few other things, thats it. I've been doing this for 2 weeks total

That said I found this link a little easier, and it may lead you down the path:
http://forum.xda-developers.com/showthread.php?t=390403