[Azurelimits]

I guess I am one of the lucky few. I have been using .37 for a little bit and it restarted once but thats it. I have been able to get UMA to work and connect. I dont know what I did or if I did anything. It just worked.

[graphreak]

Empower Html Pro used to work perfectly with the .18 on my TMO curve.
Stopped working after .37 upgrade.
The auto-backup re-installed Empower from my .18, but did not work.
So I deleted it and then tried a fresh Empower OTA install.
Pulled battery and then checked, but no Empower.

As most have already noticed UMA does not work either.

Plus I noticed that the .37 seems to be much slower when I'm on a call
and hit the Menu button to say, Activate Speaker, or Activate headset etc.
Wonder if anyone else has this slowness issue?
But I do seem to have a lot more Free memory after the .37 upgrade.

Did not have these issues on .18 other than the memory leak thing.
Seriously considering reverting to .18.

[cschrage]

I did not have memory leak issues with .18
I was on .37 for 4 hours before downgrading to .18

[tdawg00]

Originally Posted by graphreak

Empower Html Pro used to work perfectly with the .18 on my TMO curve.
Stopped working after .37 upgrade.
The auto-backup re-installed Empower from my .18, but did not work.
So I deleted it and then tried a fresh Empower OTA install.
Pulled battery and then checked, but no Empower.

As most have already noticed UMA does not work either.

Plus I noticed that the .37 seems to be much slower when I'm on a call
and hit the Menu button to say, Activate Speaker, or Activate headset etc.
Wonder if anyone else has this slowness issue?
But I do seem to have a lot more Free memory after the .37 upgrade.

Did not have these issues on .18 other than the memory leak thing.
Seriously considering reverting to .18.

I couldnt get empowered to work on .18 hmmmm Maybe I should redownload it and see

[GentMAB]

I couldn't get empower to work form .10 to .18, haven't tried it on here but I guess it won't work either since I don't have the new BIS and I don't use the BES at all, the HTML I know was supposed to be a server upgrade, but one thing I did notice, m.youtube.com does work through wifi now and it previously didn't.

[John Clark]

Empower has nothing to do with the new BIS/BES and native HTML support. I haven't personally used Empower on any of the Beta OS's. There have been issues with 3rd party apps and some versions of 4.5.

[GentMAB]

Wirelessly posted (Blackberry Curve 8320)

Yeah I know it doesn't, jus saying it don't work cuz someone said it did for them, my uma still gives the same error, but I'm okay with .37 so far, mem leak there but not as bad, docs to go appears lil better than in .10 but no real change in my eyes, jus waitin on the true release

[GT5L]

Originally Posted by John Clark

HTML email has not been officially released yet. It requires OS 4.5 AND an upgrade to BES and BIS. You need both.

Thats going to be resolved soon
North America BIS 2.4 Server Upgrade/Outage June 7-8th

[DiabloZoe]

The WIFI does not even light up on my phone

[BIOHazard87]

Originally Posted by John Clark

.18 had wifi/uma issues for me so I actually use .18 with the rim8320g.sfi file (in the GPRS folder) from .10. Pretty good combination.

I just now got really confused, when you are saying .18 and .10, are meaning 4.5.18 / 4.5.10 or 4.2.2.18...

[John Clark]

I'm talking about 4.5.0.18 and 4.5.0.10.

[BIOHazard87]

Alright thanks for the clarification

[graphreak]

Originally Posted by GentMAB

I couldn't get empower to work form .10 to .18, haven't tried it on here but I guess it won't work either since I don't have the new BIS and I don't use the BES at all, the HTML I know was supposed to be a server upgrade, but one thing I did notice, m.youtube.com does work through wifi now and it previously didn't.

Empower (Pro) actually did work very well on .18 on my phone.
Stopped working after an upgrade to.37.
Though a BBSmart trial version worked OK.
I nearly went back to the .18 but, decided to hold off a few days.

Then just yesterday I tried a fresh OTA install from the getempower
site and they happen to have a version now for the
4.5 and Above OS that is working very well on the .37.

Worth a try .

[John Clark]

Hopefully, BIS 2.5 will come soon and html will be native to the OS. There is a network upgrade this weekend and we're all hoping.

[graphreak]

Originally Posted by John Clark

Hopefully, BIS 2.5 will come soon and html will be native to the OS. There is a network upgrade this weekend and we're all hoping.

Have to try & get my money's worth out of my investment in
the Empower Pro and enjoy the beta OS features too

No doubt those who want the HTML view by default on the ,
would be the lucky ones to avail the feature without shelling extra $$s.

Question(s) would be, how the feature would work along with
the 3rd party viewers installed on the phone.

[John Clark]

Good question. The viewers do some extra things that the native viewer probably won't do. I'm not knocking the viewers....just was posting some info.

[graphreak]

Oops, that thought never even occured to me.

Just my thoughts on how RIM would be approaching their native
HTML viewer feature given that existing 3rd party one's already in
the market have some pretty interesting points in them.

[Surfish]

we shall see

[DaveJL]

This worked for me...(for my T-mobile Curve)

Go into options, then security options then certificates.
delete the 2 t-mobile usa inc listings.
it will ask you to enter a password before removing keystores. (use password blackberry)

Go into options, then advanced options, then service books.
delete the 2 wifi tcp/ip entries.

Reboot the curve.

The 2 wifi tcp/ip entries in service book will reappear after the reboot.

Next go to mobile.blackberry.com with the bb browser and click on help.
click the hotspot@home(uma) is not working link and follow the instructions to install the root certificate and the trust certificate.

Reboot again and see if you should have UMA

[John Clark]

This didn't work for most with .37 on the TMo 8320. Tried it several times the first time I loaded it.