New BuildOS - Report Bugs Here

[jdombeck]

Originally Posted by gguruusa

Which OEM were you right clicking on? (looks like 2 different ones?)

I get the same alert when I click on any of the OEMs in the kitchen.

[gguruusa]

Thanks. Replicated, Resolved. I'll release the fix once I put a few other things back together.

[sshearer]

Hi, I tried creating my first build with the WM6 kitchen a little while ago and ran into the 'ROM too big' issue (so I'd like to add my voice to the chorus about wanting to see some sort of Current Build Size indicator as items are selected & de-selected).

But as a result of the above, I de-selected (among other things) my choices for JVM & .Net CE - and was able to get past the size issue.

However, in testing individual applications later, I ran into an error message for many of them (eg. WiFiFoFum) which indicated an error in the application. Sorry, I didn't write down the actual text, but for purposes of this posting, it doesn't matter anyway. At first, I just wrote it off as a WM5 vs WM6 application issue.

But then, I did another build where I included the .Net package, and the above run-time error (for WiFiFoFum anyway) no longer occurred. At which point I realized that there was a dependency.

In hindsight, DUHH !

But, it would be great if when selecting individual OEMs, BuildOS could tell the user that one or more other packages (eg. .Net, Java, ...) are required. I know that's already in place for some things, so hopefully adding these additional dependencies won't be too hard. I don't think the dependent packages should be automatically selected because there may be times when there are multiple choices (eg. .Net 2 & .Net 3.5).


Also, FYI, in trying to flash my ROM, I initially kept getting INVALID COUNTRY_ID (120). After some reading of postings & some experimentation, I changed by RUU selection to No ID, and then it flashed fine.

Then I realized that my issue was trying to flash a used (& imported from USA) Sprint 6700 when having selected Telus as my (Canadian) carrier. So, it might be helpful if the description of error 120 could be updated to include this scenario as an example.


Lastly, to be accurate, the carrier 'Telus' should be changed to 'Telus Mobility'. They are actually 2 separate companies ('Telus' controlling 'Telus Mobility'), and 'Telus' is all about land-line service.

[bobonit]

Originally Posted by gguruusa

Which OEM were you right clicking on? (looks like 2 different ones?)

Gguruusa, I get the same error, doesn't really matter which OEM I right click on to get OEM Info. But to give you a specific instance, I right click on "1-Calc Lite" then left click on "OEM Info" and get the error.

Edit - DOH, never mind, just noticed your last post.

[lennysh]

Originally Posted by bobonit

Gguruusa, I get the same error, doesn't really matter which OEM I right click on to get OEM Info. But to give you a specific instance, I right click on "1-Calc Lite" then left click on "OEM Info" and get the error.

Yes GGuru, you really should join the chat from time to time... I know ur a busy bee and all but sheesh man!! lol GGuruUSA, I have also had this issue...on alot of OEMs.

[gguruusa]

Originally Posted by lennysh

Yes GGuru, you really should join the chat from time to time... I know ur a busy bee and all but sheesh man!! lol GGuruUSA, I have also had this issue...on alot of OEMs.

Yeah, it'll happen on all of them. Sorry about that - it was adding one of your feature requests that broke it

(ok, it was my shoddy implementation that broke it - damn typos)

[guitardoc64]

Originally Posted by jdombeck

I get the same alert when I click on any of the OEMs in the kitchen.

Same here. My 2 examples were first an oem then a non-.nb bootscreen.

[guitardoc64]

Originally Posted by gguruusa

Yeah, it'll happen on all of them. Sorry about that - it was adding one of your feature requests that broke it

(ok, it was my shoddy implementation that broke it - damn typos)

That's what we're here for GG, to find the bugs and report them. Considering the scope of Build OS and how hard you've been working on it, not a big deal. I'd assume it still works and the info feature's all that's wrong but when I finish this post I'll flash a test ROM to see.

[guitardoc64]

Test Rom completed with no problems. I figured it would, but wanted to check it out. The errors don't seem to affect the performance or the build.

[lennysh]

Originally Posted by gguruusa

Yeah, it'll happen on all of them. Sorry about that - it was adding one of your feature requests that broke it

(ok, it was my shoddy implementation that broke it - damn typos)

You know you da man GGuru!!

I hate typos... Really hate typos....