Howzit?

I wanted to post my finding while using PDAnet with fw 2.1 on my 3G iphone. Prior to fw 2.1 I was able to maintain solid battery charge while using PDAnet. Since the 2.1 update, I've found that there seems to be some sort of bug that causes intermittent loss of charging ability when PDAnet is in use.

If you keep your screen on and unlocked while using PDAnet, you'll notice your battery indicator on the task bar (not the numeric readout within PDAnet) will change from the "charging" lightning bolt icon to the "charged" plug icon. It does this dispite being far from fully charged (I will post screenshots soon). When this happens, PDAnet just keeps draining the battery (easily tracked with the PDAnet numeric battery display). Sometimes I can initate charging again by unplug/replugging in the phone, but this is short lived and doesn't always work. Incidently, the lock screen battery icon correctly displays battery charge.

I have no idea what causes this and I think this is new since the 2.1 firmware update. My battery drain is actually worse than under 2.0, dispite all of the upgrades to PDAnet's efficiency. If anyone can shed some light on this, PLEASE post whatever information you have...and maybe share it with PDAnet developers!

FYI - the same issue is occuring with Netshare...something to do with 3G and wireless being active at the same time...the pessimist in me wonders if it wasn't purposely introduced by apple in an effort to get everyone onboard with the pending "official" tethering options from apple/att.

In case anyone out there is following this, I thought I'd update with this response from the Junefabrics guys:

"This seems to be a known issue, not caused by PdaNet in particular but have something to do with a firmware bug that got triggered when using PdaNet. We still don't have the exact detail but it could be caused by usage of both of the Wifi and the 3G data. We are not sure if it is from the OS firmware or just the jailbreak firmware or if there is anything we could do at the software end to avoid triggering this issue. Hopefully we would be able to get more information and a solution on this in near future."

So...if anyone out there has any more detailed info about the potential cause of this, please chime in so we can get this fixed!

Thanks