Motorola V710
first off: jcrow78 is 100 % right
the 7000s were shipped prior to 6-25 but some stores jumped the gun.But everyone knew definitively about their release. Everything he said re matrix,dummy models etc is 100% true and the phone is a long way off. Supposedly some units were in some centers and warehouses but there were issues so they had to b sent back for flashing which after VZW re-checks it, is a 45 day period. SO if everything goes according to gameplan (and a lot of times it dont), the earliest the phone will b in actual VZW stores is late august, most likely september. 2 things to mention: 1, Moto has zero clue, zero idea about the release of this phone ( so calling them is futile) and 2, theres a chance, a teeny chance that VZW will (after all these issues/software/te...
(continues)
(continues)
...
Not to mention, look at the bugs Level2 noted for today's log of his testing. This is *so* typical of Motorola phones. That type of information is so much more valuable than release date speculation because it shows what we would be getting if the phone were sold right now. Who knows what other problems lurk in there.
I'm hoping that the phone, if/when released, isn't so buggy as to be unusable. But I've seen with Motorola CDMA phones in the past that when you go beyond the most basic usage, things often start to break. It's a little bit like they build and check the software to the extent they know VZW will use scripts to do QA, and nothing more. Good radio quality, but software that isn't solid enough to handle it.
I'm hoping that the phone, if/when released, isn't so buggy as to be unusable. But I've seen with Motorola CDMA phones in the past that when you go beyond the most basic usage, things often start to break. It's a little bit like they build and check the software to the extent they know VZW will use scripts to do QA, and nothing more. Good radio quality, but software that isn't solid enough to handle it.
...
haus said:
Not to mention, look at the bugs Level2 noted for today's log of his testing. This is *so* typical of Motorola phones.
The password bug certainly seems fairly significant. It wouldn't affect me at all, but I could see how it could.
The other bug doesn't seem like a bug at all. To me, that would be a benefit... being able to close my phone, without having to start all over in my GIN app. If I want to close my GIN app, all I have to do is push the button to do so. I would tend to believe that this is not a bug, but a change in functionality.
...
FireStryke said:
The other bug doesn't seem like a bug at all. To me, that would be a benefit... being able to close my phone, without having to start all over in my GIN app.
I agree.....kind oof like a boss key HEHE 😁
jcrow78, sorry if I came off as attacking you. It's hard to make a statement come off the way you want it to without the effect of the tone of your voice. I'm sure what you are saying is VZW policy, I was just saying that it has obviously been broken in the past by some stores.
...
no problem man..I fully understand the tonality issues of forum posting. I agree that policy can and probably has been broken before
...
I was referring more to the backlight bug, not to mention "call in progress?" Running an app on the phone doesn't use airtime, does it? I suppose some do (like POP mail, etc - but games?) Eh, I'll admit I don't know since I've never used a BREW/GIN phone. I did have some Java games on my T608, and they don't use airtime.
The backlight bug is serious IMHO. This phone will eat battery like cake - why give it anything to suck the juice even faster.
The only thing about the password I can think of (other than dismal, spaghetti code that makes my blood run cold) is that he *228'd and didn't mention doing so. This sometimes causes phones to reset the password to the last 4 of the phone number. At least I've seen it happen. So maybe it's not...
(continues)
The backlight bug is serious IMHO. This phone will eat battery like cake - why give it anything to suck the juice even faster.
The only thing about the password I can think of (other than dismal, spaghetti code that makes my blood run cold) is that he *228'd and didn't mention doing so. This sometimes causes phones to reset the password to the last 4 of the phone number. At least I've seen it happen. So maybe it's not...
(continues)
...
