Yeah there's a major bug.
USB just won't see the internal but sees external memory.
This is a deal breaker don't know why people are so tolernace to these things!
First attempt to connect to PC to restore data from some apps didn't see either memeory locations.
Second time both int & ext were viewable from PC w/64bit W7 OS.
Managad to get my data loaded but no longer see's interal memory.
I've seen many versions of this same problem on other forums.
This by no means is anything short of a huge bug.
My droid one synched to my PC with no problems. I moved all the folders to an external HDD so i can start restoring app data to Bionic and it simply can't be done because it sees it it doesn't see it see's one it doesn't see the other...
Also tried synch to laptop w/V64bit Vista...Droid one no problem...Bionic it might as well be 1972!
This is a rudimentoary function that should work flawlessly...this is rediculous!
Found a possible reason this is happening...It seems that if you have your phone in USB debugging, every once in a while your phone's internal storage space won't show up properly. I hadn't even noticed that I had my phone was in USB debugging until last night; why would I? No phone you get retail comes defaulted in in debug...unless the Verizon sales person takes your phone in the back to back up your contacts up through Verizon's Backup Assistant.
I was able to solve the issue by ejecting the phone from my computer, turn off USB debugging, restarting the phone, and reconnecting it.
Also note; if you turn off USB debugging or switch the USB connection mode (charge only, USB mass storage, PC mode, Windows Media Sync) while the phone is still connected to your computer it pretty much guarantees your phones internal memory won't get recognized. I think this has to do with the fact that whenever you switch modes/disable USB debugging, the phone disconnects itself during the transition and the fact that the Bionic seems to have a lot of issues re-mounting its internal storage, taking unusually long to do so, and in many cases, not even being able to do so. Basically, if the phone isn't able to re-mount during that short period that it's disconnected between switching modes or disabling/enabling debugging, it won't get recognized as it can't mount the memory while it's in use by the computer.
Or at least that's what I'm thinking...I'm certainly no expert on this stuff; I'm really just going off of what I've noticed through experience.
1.) not everyone has unlimited data
2.) sometimes 3g just isn't enough to stream that movie
3.) even in the 4g fortified greatest city on earth there is no signal in the subway (as per Vihzel)
4.) because it's nice to have some music and movies on the phone just in case.
5.) I'm sure some fix will come out to make it more usable with apps
Yeah, I forgot Verizon dropped unlimited data...and your other points are valid; but none of it explains why we can't put our apps on the physical SD. And I'm sure a fix will eventually be implemented, but my argument is that we all waited months for this phone to come out under the guise that they were adding improvements to it, yet here we are with a device that can't properly utilize it's own features. Connecting devices to USB is something that's been around since...well since USB was created, at this point, I'm sorry, but I expect this to work properly, especially considering no other Droid device seems to be having these problems, at least not to this extent, the same goes for the app moving issues.
Don't get me wrong, I still am enjoying the phone a ton, and even with all these problems, I'll probably never switch to another phone during this contract period, but I think we're all in the right when it comes to being frustrated and upset about all this.