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

[redd214]

Originally Posted by impudent1

I apologize, but I'd rather spend the night in a cell with Bubba than tackle that problem. Hopefully Scott will be back soon and with a healthy donation, he may be able to hook you right on up.

**EDIT** or yeah, what Bob said.

lol, thanx anyways man. i have been ripping my hair out for 3 days trying to figure this out!!!

[redd214]

Originally Posted by impudent1

I apologize, but I'd rather spend the night in a cell with Bubba than tackle that problem. Hopefully Scott will be back soon and with a healthy donation, he may be able to hook you right on up.

**EDIT** or yeah, what Bob said.

lol, thanx anyways man. i have been ripping my hair out for 3 days trying to figure this out!!!

[impudent1]

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.

[gman4471]

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

[oldman]

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

[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.

[redd214]

Originally Posted by oldman

Before any of the "smart" (not me) guys can help, they need a bunch more of info from you. Is it a Sprint or Verizon Phone? What type of app was it?
Did it require NetCF 3.5, sqeMobile, etc....What type of error messages were you getting? I'm not sure, because I'm just a user, not a hacker but i think that those different versions are newer MS ones that might appear on different phones and the "smart" guys figure out how to make them work with the Sprint or Verizon phones. The ROM you chose 21015 has been reported to have a few quirks that Scott will probably fix when he returns. The ones that have been reported as the most "reliable" are 20764 and 20931. But without more info, nobody can even guess why your app doesn't work.

Bob
Edit: SQL, not SQE.

its a verizon tp. the app itself wasnt just a regular cab like everything else, it has conduits and could only be installed thru syncing if that makes sense. it actually didnt require netcf 3.5 just 2.0. i know 21015 was kinda quirky but i tried 20764 and 20931 as well and those didnt work either.

forgot sorry, the error message said that the "windows turboapp (name of the application) conduit cannot communicate with your device, please press ok to attempt again"

[impudent1]

Originally Posted by redd214

its a verizon tp. the app itself wasnt just a regular cab like everything else, it has conduits and could only be installed thru syncing if that makes sense. it actually didnt require netcf 3.5 just 2.0. i know 21015 was kinda quirky but i tried 20764 and 20931 as well and those didnt work either.

I've read that apps with netcf 2.0 have backward compatability issues. Now I can't seem to find the link since it wasn't what I was looking for before.... go figure. I did run across it with a google search though.

[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?

[RONMAC]

Originally Posted by redd214

its a verizon tp. the app itself wasnt just a regular cab like everything else, it has conduits and could only be installed thru syncing if that makes sense. it actually didnt require netcf 3.5 just 2.0. i know 21015 was kinda quirky but i tried 20764 and 20931 as well and those didnt work either.

forgot sorry, the error message said that the "windows turboapp (name of the application) conduit cannot communicate with your device, please press ok any attempt again"

Did you go back to the insanely laggy stock ROM? I remember Scott had set up one of his ROMs using the stock build but had cleaned it up significantly.

You might want to reach out to him when he gets back and check to see if the ROM is still around.

Was the Stock build 20764? If so, try the R4R ROM as it is the same build.

Anything to get away from the VZW LAG WARE!!!