[tsells]

Update 4:

Hour 3 complete and battery is at 80%. Device Analyzer claiming my drain is 5.78%/hour, meaning, in the math on RIM's planet 5.78x3 = 19+ as opposed to the 17.34 it equals on my planet. Under version .342, the math always added-up perfectly.

And, to top it all off, my Facebook notifications are suddenly dinging my phone again, even though I've already double-checked, just to make sure I'm not crazy, and all of that is turned off in the FB app options. Had this same problem when running 7.0, but it stopped under 7.1.xx.342.

I have no choice but to give this build until, at least, tomorrow before I nook it, because I gotta hit the sack (full day tomorrow -- gonna be real fun with a craptastic half-dead phone! ). Hopefully, tsells' advice about giving it time to settle-in will bear fruit; if not, me and .428 are parting ways. Honestly, even if the battery crap does get better, the Facebook dinging alone will cause me to dump this build if it doesn't stop as well.

Patience is needed. Rebooting your device uses up the battery. It takes a day and a few battery pulls for your phone to "settle in".
Most people will get a full day of charge for this device. Even 6%/hour will get you through a 17 hour day, but you should be able to get from 2.5%-4.25%/hour on most of the .3xx and .4xx builds (depending on your usage).
I am not too familiar with the facebook app but I highly doubt that an OS is causing a problem with the notifications. It's either a wrong setting or a bad install of the app. Double check all settings and if you are positive that it is correct I would uninstall and then re-install the facebook app.

[WBSnow]

Hello everyone. I am not too worried about battery life as I am people hearing me on my Blackberry. Since installing, and making & receiving phone calls, no one is able to hear me. I have done several battery pulls without avail. I have pulled the battery, and plugged my Blackberry in to my computer and it is updating again.

[tsells]

Hello everyone. I am not too worried about battery life as I am people hearing me on my Blackberry. Since installing, and making & receiving phone calls, no one is able to hear me. I have done several battery pulls without avail. I have pulled the battery, and plugged my Blackberry in to my computer and it is updating again.

You have the dreaded "mic issue" that some users have reported having on .402. You're probably going to have to go back to .391 which did not have any mic issue reports.
FYI, I'm on .428 for half a day with no mic issues at all.

[WBSnow]

You have the dreaded "mic issue" that some users have reported having on .402. You're probably going to have to go back to .391 which did not have any mic issue reports.
FYI, I'm on .428 for half a day with no mic issues at all.

Is there a fix, other than downgrading?

[sedalia066]

Since installing, and making & receiving phone calls, no one is able to hear me. I have done several battery pulls without avail. I have pulled the battery, and plugged my Blackberry in to my computer and it is updating again.

Looks like another OS with the muting issue confirmed. You are not alone.

[tsells]

Installed this OS last night. Battery drain today is at 2.8%/hr with low usage today.
Everything else seems really good with no problems at all.

[jeremycrews]

I am not too familiar with the facebook app but I highly doubt that an OS is causing a problem with the notifications. It's either a wrong setting or a bad install of the app. Double check all settings and if you are positive that it is correct I would uninstall and then re-install the facebook app.

I did dump and reinstall the Facebook app first thing this morning, and it seem to have helped. Apparently, if you select yes on the notifications when you first install it, then it couldn't care less about you changing your mind and trying to turn the notifications off later; they show as being off, but still ding through. If you say no right off the bat, though, it's all good -- or, at least, seems to be.

Installed this OS last night. Battery drain today is at 2.8%/hr with low usage today.

I would choke a stranger if it got me 2.8%.

Patience is needed. Rebooting your device uses up the battery. It takes a day and a few battery pulls for your phone to "settle in".
Most people will get a full day of charge for this device. Even 6%/hour will get you through a 17 hour day, but you should be able to get from 2.5%-4.25%/hour on most of the .3xx and .4xx builds (depending on your usage).

6%/hour isn't at all excessive with moderate usage, but to be getting that without ever touching the phone other than to check the time twice during each hour seems like a lot to me.

This afternoon, I attended a little reunion/get-together at a local restaurant with some college friends: over a 5 hour period, I averaged a drain of 5.36%/hour, yet the phone is telling me I have 66% of my battery remaining. 3% of that drop is due to a reboot I did a few minutes ago to get the foursquare app out of my task manager (so it wouldn't just keep running in the background), therefore, it's fair to say I used 30+% during my outing.

I had WiFi and Bluetooth turned-off the whole time, and I killed the Wireless Network as well when I was passing through a large dead area (turned it back on once I had signal and it showed H+ with full bars the whole time at the restaurant). From the time I left my house until I returned, my 30+% bought me 1 quick voice call (2 minutes, at most) via the speakerphone, 1 text sent -2 texts received, 2 foursquare check-ins, took 7 high-quality pics w/ the flash, and used Blackberry Traffic's turn-by-turn voice GPS for about 10 minutes (just to test it out -- BTW, it works really well, even in my rural area).

Interestingly, leaving the restaurant at about the 4 hour - 20 minute mark (the venue is about a 45 minute drive from my home), the battery was still showing 81%. The remaining 12% bleed was the result of only 1 of the foursquare check-ins and 10 minutes using the GPS. Therefore, it seems that first 4.33 hours was being drained at only 4.39%/hour, according to my math; so much better, considering I was getting far worse drain yesterday evening with it sitting mostly on standby. We'll see how it does now that I'm back home now with it being barely used again.

Update: 1st full hour since returning home. Battery reading 59%. As I said above, it dropped 3% due to a reboot, but then it went from 66% down to 59% over the remainder of the hour. Sat idle the entire time that add'l 7% was bleeding away into the ether, except for answering a single call that lasted less than a minute. The Analyzer puts my average drain at 6.05%. 6.05x6 (hours) = 36.3, so if that number were accurate I should still have 63%-64%, not 59%. Also, that's with WiFi and Bluetooth both still turned-off.

Update 2: 2nd full hour since returning home (7th off-charge). Battery reading 51%. Enabled WiFi during the hour, in order to email the 7 large pics I took today to myself, so I could save and edit them on my PC. The Analyzer now says my average drain is 6.52%.

Update 3: 8th hour overall. Battery reading 46%. Average battery drain 6.85%. That part, at least seems to be leveling-out i.e. 6.85x8 = 54.8 -- 100%-54.8% = 45.2%, so now it's within 0.8% of the 46% the phone is reporting. I can deal with that, as I assume there's a margin of error involved. WiFi still on.

Update 4: 9th hour overall. Battery reading 42%. Average battery drain 6.61%. Seems to be getting better, but, then again the 4% drop during this hour occurred without the phone even being touched. I read somewhere on here that people were saying that having WiFi switched on and continuously connected to a network improves battery life on the 9900; maybe true of the 9810 as well?

[tsells]

Open Battery Analyzer and click on DETAILS. Scroll down to Total CPU and advise what the percentage is. Also scroll down and you'll see what's been running on your device and it's percentage. You'll most likely find what is running and causing the battery drain.
Again, the battery drain is most likely caused by user error (caused by a constantly running app or apps) or an incompatible app that is draining the battery.
EDIT: I just read that you have FourSquare. Isn't that a location-based app? Don't know too much about it but I have a feeling that could be the culprit. You might want to disable it and see how your battery goes.

[WBSnow]

I am not too worried about the battery drain as I am about the mic issue. I know some of you have not had an issue but I have, I downgraded back to .391 and will patiently wait until the issue is fixed or another official release comes out.

[jeremycrews]

Open Battery Analyzer and click on DETAILS. Scroll down to Total CPU and advise what the percentage is. Also scroll down and you'll see what's been running on your device and it's percentage. You'll most likely find what is running and causing the battery drain.
Again, the battery drain is most likely caused by user error (caused by a constantly running app or apps) or an incompatible app that is draining the battery.
EDIT: I just read that you have FourSquare. Isn't that a location-based app? Don't know too much about it but I have a feeling that could be the culprit. You might want to disable it and see how your battery goes.

Update 5: 10th hour overall. Battery reading 38%; another 4% drop but that includes receiving/responding to 4-5 text messages. Average battery drain 6.21%; so, still falling. Still getting better.

Total CPU% = 9.64%.

As for apps:

Foursquare is location-based, but I've closed it down. It isn't showing under under task manager or under Battery drain trends ---> Details. Slider Lock is, however, but only as 3.74% over 10 hours. Honestly, I have no idea how even to interpret that number. Is 3.74% bad? If so, that could be my culprit. I don't know, though. Is it saying, basically, that Slider Lock has been munching 0.374%/hour on average or is it, literally, accounting for 3.74%/hour in battery bleed? I added-up all the task percentages, including Slider Lock, and they don't add-up to anywhere near the 9.64% CPU, so I'm a bit lost. Everything listed, other than Slider Lock, begins with net_rim_blah blah blah, so those are system stuff, rather than apps, yes?

[tsells]

Foursquare is location-based, but I've closed it down. It isn't showing under under task manager or under Battery drain trends ---> Details. Slider Lock is, however, but only as 3.74% over 10 hours. Honestly, I have no idea how even to interpret that number. Is 3.74% bad? If so, that could be my culprit. I don't know, though. Is it saying, basically, that Slider Lock has been munching 0.374%/hour on average or is it, literally, accounting for 3.74%/hour in battery bleed?

Locking apps have been notorious for using the battery. I don't use one so can't help you with this, but that would be a good place to start.
I would close FourSquare and disable SliderLock, then re-boot the phone, and charge it over night. Then check your battery usage tomorrow with those apps not running vs. today.

[jeremycrews]

Locking apps have been notorious for using the battery. I don't use one so can't help you with this, but that would be a good place to start.
I would close FourSquare and disable SliderLock, then re-boot the phone, and charge it over night. Then check your battery usage tomorrow with those apps not running vs. today.

I'll definitely do that. Thanks!

[tsells]

I'll definitely do that. Thanks!

One more question:
By any chance, do you have any of the so-called "battery-saving" apps installed? If so, you should delete it because they are "snake-oil" and actually use more battery.

[jeremycrews]

One more question:
By any chance, do you have any of the so-called "battery-saving" apps installed? If so, you should delete it because they are "snake-oil" and actually use more battery.

I did for a long time, but dumped them a month or so ago.

[mickael_m]

Knowing where the folder is, isn't necessary. The next step in the process is making sure you have the latest version of Blackberry Desktop Manager 7, or the DM 7.1 beta, and Vendelete.exe. Links to both pc applications can be found in the forum threads. Use Vendelete.exe on any RIM OS titled "official", because there's a vendor file attached to some of these OS that prevent them from being recognized by the vendor code assigned to your mode phone. Once that program has cleared out the vendor file, connect your phone to your computer, via usb - yes, I typed that, because someone will ask - and start Desktop Manager. You should see a "star", denoting an available update for your device. Agree to the install, and wait for the all clear from DM before removing your phone from your computer.

I have down loaded the new OS I have deleted the vendor file, but the new OS will still not show when i open my DM, it says there are no new updates for my devicewhat do i do???

Thanking you in advance

[tsells]

I have down loaded the new OS I have deleted the vendor file, but the new OS will still not show when i open my DM, it says there are no new updates for my devicewhat do i do???

Thanking you in advance

Have you searched for a 2nd (hidden) vendor file?
Located on your computer at:
C:\Users\<your user id>\Appdata\Roaming\RIM\Blackberry\Loader.xml

You might have to turn on hidden files to find it:
Folder options>view>advance settings>show hidden files>save

[Lendo78]

What exactly happens when you delete the vendor file?

[the brother]

Magic happens, Lendo!!!! DM will recognize that your non-Telstra BB requires an os update!!!!!

[mr_chaela]

What exactly happens when you delete the vendor file?

It probably goes in the recycle bin where you can delete it permanently.

The vendor.xml file is carrier specific and is there to stop you loading the OS on another carriers phone. If you delete it/them then the upgrade is treated as a generic upgrade and can be loaded on any carriers phone. Doing this would only be a problem if the carrier supplying the upgrade had modified the OS to suit there particular needs. Generally speaking this rarely happens so it is quite safe to load the upgrade.

hth

[jeremycrews]

Why even bother with DM? I guess so you can update without wiping? If so, maybe I'll try that route next time; it's be much less hassle. I wiped mine using BBSAK, manually deleted the single vendor.xml file from the Apploader folder (didn't even know about the hidden one), then ran loader.exe, and it went off without a hitch.

[TerribleTim68]

... Doing this would only be a problem if the carrier supplying the upgrade had modified the OS to suit there particular needs. Generally speaking this rarely happens so it is quite safe to load the upgrade.

hth

"Generally Speaking", AT&T will modify the OS every time to block/tweak certain things they want you to pay extra for. Using a different carriers OS and killing the vendro file will give you an OS AT&T hasn't "played with". I'm not saying it's better or different, just is what it is.

[tsells]

Why even bother with DM? I guess so you can update without wiping? If so, maybe I'll try that route next time; it's be much less hassle. I wiped mine using BBSAK, manually deleted the single vendor.xml file from the Apploader folder (didn't even know about the hidden one), then ran loader.exe, and it went off without a hitch.

In the future, there's absolutely no need to wipe your device using BBSAK. Loader.exe does everything for you.
And the hidden vendor file does not apply to everyone. For some reason, there is a need to delete the second file when the computer does not recognize the new OS. I have done numerous OS updates and only once did I need to delete the second vendor file.

[tsells]

This thread has gotten off-topic. Day two with this OS and all is perfect. Fast browser, no touchscreen issues, good reception (no dropped calls), and no mic issues. Battery drain today is 3.3%/hr with moderate to heavy use.
Hard to tell if this OS is any better than .391 or Gamma Prime (hybrid), but it is certainly as good as those.

[jeremycrews]

In the future, there's absolutely no need to wipe your device using BBSAK. Loader.exe does everything for you.
And the hidden vendor file does not apply to everyone. For some reason, there is a need to delete the second file when the computer does not recognize the new OS. I have done numerous OS updates and only once did I need to delete the second vendor file.

Good to know, because I really would rather never do that mess again!

This thread has gotten off-topic. Day two with this OS and all is perfect. Fast browser, no touchscreen issues, good reception (no dropped calls), and no mic issues. Battery drain today is 3.3%/hr with moderate to heavy use.
Hard to tell if this OS is any better than .391 or Gamma Prime (hybrid), but it is certainly as good as those.

Mine is running phenomenally better today. The Slider Lock app was my battery-thieving culprit; sad, because I really liked it.

So far, I'm 3 hours in and showing only 2.36%/hour drain. It was actually only 1.34% over the first 2 hours when it was on standby; but, in hour 3, I did a battery pull (probably the last one I'll do for a while, since the OS seems to be settling-in nicely now), and I texted back-and-forth with a friend for pretty much the entire hour.

Needless to say, I'm much happier today than I was the previous few days.

[MT56]

would be interested to see what the +/ - are of.428 versus the .391......