<> 11-2-2010 <> Medium Hill ROM's <>

[dibbson]

Hmm that seems odd. Your the first person to report problems like this on that build (did you flash stock before hand, sometimes i've heard flash stock and then clear storage, and then flash custom). An update is coming, I'm just trying to get my UC/Provisioning app i've built from the ground up perfect as i haven't found one i'm completely satisfied with. Made some progress on it today, and hopefully i can wrap it up tonight. If i do the updates will be uploaded directly after that.

[jas0nmack]

Originally Posted by eman

Did you go into the settings menu in Bing and change gps to comm 4?

Bing v5 doesn't have settings options like that. It also has an unsigned driver error when launching it.

[dibbson]

i will revert back to the older package then since it's having issues.

[razorloves]

Originally Posted by manekineko

Is the 2/2 build 2.5/23519 build freezing for anyone on the bootup after provisioning on install? I redownloaded and reflashed, trying both from USB and SD, and still have that happen. After I take out the battery, it starts normally from there.

i had the same problem with the 24001 test rom from a couple nights ago. It only happened once though, out of the 3 times that i hard reset and ran carrier provisioning. It was unresponsive and blank screen a couple seconds after the carrier provisioning finished installing. i had to pop the cover off and hit the reset button. Also, for some reason, each time that i ran the carrier provisioning, it took about 3 minutes to install. strange.

[dibbson]

Hence the reason i'm making my own UC/Provisioning, shouldn't have any issues once i get it finished going forward as this one is made off the 6.5 SDK. I'm tired of these random issues and whatnot. I would have stuck with tierautoinstall but it's 50/50 on 6.5.x whether it works or not. 6.5 it worked fine, but i didn't want to run one uc/provisioning on one set and another on the other set.

[manekineko]

Originally Posted by dibbson

Hmm that seems odd. Your the first person to report problems like this on that build (did you flash stock before hand, sometimes i've heard flash stock and then clear storage, and then flash custom). An update is coming, I'm just trying to get my UC/Provisioning app i've built from the ground up perfect as i haven't found one i'm completely satisfied with. Made some progress on it today, and hopefully i can wrap it up tonight. If i do the updates will be uploaded directly after that.

Yeah, I normally am not a big believer of the flash dance, but I did it anyway this time due to the troubles I was having, but it still happened. Flashed stock, and changed the method I was using the flash from SD to USB. Probably not a huge problem though if it was already at the loading Sense stage. I'm more worried about that random Manila crash I got.

[manekineko]

Originally Posted by dibbson

i will revert back to the older package then since it's having issues.

Unless there's a strong preference the other way, I would also recommend using the older Google Maps 3.2.1. The newer 3.3.1 is bugged on CDMA networks, causing the My Location feature not to work.

http://www.google.com/support/forum/...c2a7d2eb&hl=en

[dibbson]

3.3.1 works fine for me, my trick to get it to work for me, is i run quick gps before i start google maps.

[manekineko]

Heh, this is pretty minor, but it's pretty funny looking how there are two Settings icons that look exactly the same in the Start Menu, and one brings you to WinMo settings and one brings you to Manila settings. Seems like the Manila settings are pretty easy to access on the far right already without being in the Start Menu...

[manekineko]

Originally Posted by dibbson

3.3.1 works fine for me, my trick to get it to work for me, is i run quick gps before i start google maps.

Really? Without GPS active? What's the accuracy level you see? After running QuickGPS I see accurate to within 43000 meters, which is to say, it doesn't even know what state I'm in for sure!