Results 1 to 6 of 6
  1. #1
    james
    Guest
    Hi all,

    Now keep in mind that I'm very happy with my SCP-6400...I used to have
    the SCP-6200 and both phones satisfied my needs extremely well...but I
    wanted to post these issues to see if other people have had them, and
    if there are any solutions I'm not aware of. (Google search indicates
    that they've not been mentioned before.)

    Interestingly, all of these issues were also issues on my 6200.

    1.) The most annoying for me...I have the phone set so that it won't
    ring at all on phone calls that are private/unknown. However, if the
    phone is set to ring level "vibrate" or "high+vibrate", the phone will
    vibrate for a private/unknown call anyway (but won't ring.) And it
    does just as it's instructed if the phone is set to any other ring
    level...it won't ring at all.

    2. Battery consumption on talk seems a touch higher than on the 6200
    (an annoyance, since one of the reasons I got the 6400 was so that I
    could get a new battery, the 6200's battery was staring to go.) But
    here's the really weird one...the battery meter could be fully filled
    in (all the hash marks there) and then I'll start up the browser...and
    suddely two hash marks will disappear. While the broswer uses up a lot
    of battery, it seems that just starting up the web decimates the
    battery, and it happens almost always without fail, and I had the same
    problem on the 6200 (though I didn't do much browsing on it.)

    3. Another irritation is the fact that the phone stops displaying the
    time if it has lost the digital signal. I don't see why Sanyo couldn't
    have added a simple counter to keep the time showing under most
    circumstances. As a side note, I would also love to have the time
    showing while I'm on the phone (it's got the room to display both time
    and length of call.)

    4. Not a big irritation, but a curiosity. With key block on, all the
    keys are blocked (a little message pops up saying that key block is
    on, if any are pressed.) Except for the 9, * and # keys. So why not
    block out those keys?

    5. Finally, just another curiosity. Occasionally I can hear the party
    calling me be connected into my phone (so I can hear them) for about
    half a second before the phone actually rings. This seems to happen
    with other phones...I've called someone, and heard them for about half
    a second before I start to hear the phone ring. Can anyone explain
    this?



    See More: SCP-6400 irritating issues




  2. #2
    hatoncat
    Guest

    Re: SCP-6400 irritating issues


    james wrote:
    > *Hi all,
    >
    > Now keep in mind that I'm very happy with my SCP-6400...I used to
    > have
    > the SCP-6200 and both phones satisfied my needs extremely well...but
    > I
    > wanted to post these issues to see if other people have had them,
    > and
    > if there are any solutions I'm not aware of. (Google search
    > indicates
    > that they've not been mentioned before.)
    >
    > Interestingly, all of these issues were also issues on my 6200.
    >
    > 1.) The most annoying for me...I have the phone set so that it won't
    > ring at all on phone calls that are private/unknown. However, if the
    > phone is set to ring level "vibrate" or "high+vibrate", the phone
    > will
    > vibrate for a private/unknown call anyway (but won't ring.) And it
    > does just as it's instructed if the phone is set to any other ring
    > level...it won't ring at all.
    >
    > 2. Battery consumption on talk seems a touch higher than on the 6200
    > (an annoyance, since one of the reasons I got the 6400 was so that I
    > could get a new battery, the 6200's battery was staring to go.) But
    > here's the really weird one...the battery meter could be fully
    > filled
    > in (all the hash marks there) and then I'll start up the
    > browser...and
    > suddely two hash marks will disappear. While the broswer uses up a
    > lot
    > of battery, it seems that just starting up the web decimates the
    > battery, and it happens almost always without fail, and I had the
    > same
    > problem on the 6200 (though I didn't do much browsing on it.)
    >
    > 3. Another irritation is the fact that the phone stops displaying
    > the
    > time if it has lost the digital signal. I don't see why Sanyo
    > couldn't
    > have added a simple counter to keep the time showing under most
    > circumstances. As a side note, I would also love to have the time
    > showing while I'm on the phone (it's got the room to display both
    > time
    > and length of call.)
    >
    > 4. Not a big irritation, but a curiosity. With key block on, all the
    > keys are blocked (a little message pops up saying that key block is
    > on, if any are pressed.) Except for the 9, * and # keys. So why not
    > block out those keys?
    >
    > 5. Finally, just another curiosity. Occasionally I can hear the
    > party
    > calling me be connected into my phone (so I can hear them) for about
    > half a second before the phone actually rings. This seems to happen
    > with other phones...I've called someone, and heard them for about
    > half
    > a second before I start to hear the phone ring. Can anyone explain
    > this? *


    1) For some reason Sanyo doesn't let you independently control
    vibrating and ringing settings. It's really pathetic.

    2) The 6200 is a 2G phone, and has a different Qualcomm chipset than
    the 3G 6400. I would not be suprised at all to hear it has worse
    battery life.

    3) Yep, another Sanyo failure. The newer Samsung phones and Hitachi
    P300 keep track of the time, but Sanyo thinks you will always be in
    range of a Sprint signal.

    4) Bug in firmware. Sanyo & Sprint don't care enough to fix them...

    5) The phone is sending the command to Sprint to push up the bandwidth
    because you are taking the call. It's part of the CDMA EVRC codec,
    it's just the 6400 has such a slow processor that the delay is
    noticeable.

    ---
    www.sprintpcsinfo.com

    --
    Posted at SprintUsers.com - Your place for everything Sprint PCS
    Free wireless access @ www.SprintUsers.com/wap




  3. #3
    O/Siris
    Guest

    Re: SCP-6400 irritating issues

    In article <[email protected]>, [email protected]=20
    says...
    > 4) Bug in firmware. Sanyo & Sprint don't care enough to fix them...
    >=20


    911, *2, #ROAD

    I'm guessing that we assumed there are numbers customers would always=20
    want to contact, even with keypad lock.

    --=20
    -+-
    R=D8=DF
    O/Siris
    I work for SprintPCS
    I *don't* speak for them.



  4. #4
    Gr8 Oz
    Guest

    Re: SCP-6400 irritating issues

    Ok, wait a minute....I am REALLY confused by this
    given "reason".....Help me out here.....
    It was specifically stated:

    ALL THE
    > keys are blocked (a little message pops up saying that key block is
    > on, if any are pressed.) Except for the 9, * and # keys. So why not
    > block out those keys?



    AND THE RESPONSE WAS:

    > > 911, *2, #ROAD...


    Then this really ought to bake your noodle.....
    HOW ARE THOSE OPTIONS POSSIBLE???

    If 9 is enabled....11 are disabled,
    * is enabled....2 is disabled,
    # is enabled....ROAD are disabled ????

    Does pressing the 1st key in a specific sequence
    automatically temp. enable the remaing keys in that
    sequence.....ie: cant dial 11 unless you 1st dial 9
    cant dial 2 unless you first dial *
    As long as you press # 1st while being locked then you
    have the ability to dial ROAD and never unlock the keys?

    If it is an exclusive "Safety calling feature" while the
    phone is locked, where can I locate this feature for
    this specific device? I may be wrong, but that doesn't
    sound quite right to me. If it can in fact be done,
    what other devices offer this "Key Lock-Dialing" feature
    Any insight would be greatly
    appreciated.


    --
    Because there is a satisfied customer today...
    The company can open their doors
    tomorrow...


    O/Siris <[email protected]întpcs.côm> wrote in article
    <[email protected]>:
    > In article <[email protected]>, [email protected]=20
    > says...
    > > 4) Bug in firmware. Sanyo & Sprint don't care enough to fix them...
    > >=20

    >
    > 911, *2, #ROAD
    >
    > I'm guessing that we assumed there are numbers customers would always=20
    > want to contact, even with keypad lock.
    >
    > --=20
    > -+-
    > R=D8=DF
    > O/Siris
    > I work for SprintPCS
    > I *don't* speak for them.


    [posted via phonescoop.com]



  5. #5
    Hemant Shah
    Guest

    Re: SCP-6400 irritating issues

    While stranded on information super highway O/Siris wrote:
    In article <[email protected]>, [email protected]
    says...
    > Then this really ought to bake your noodle.....
    > HOW ARE THOSE OPTIONS POSSIBLE???
    >
    > If 9 is enabled....11 are disabled,

    If you press 9, 1 is disabled.

    > * is enabled....2 is disabled,
    > # is enabled....ROAD are disabled ????

    Press '*' or '#' then 9 is disabled, after 9 is pressed 1 is disabled.
    '2' and ROAD are still locked.

    I tried it on my 6200.

    >
    > Does pressing the 1st key in a specific sequence
    > automatically temp. enable the remaing keys in that
    > sequence.....ie: cant dial 11 unless you 1st dial 9
    > cant dial 2 unless you first dial *
    > As long as you press # 1st while being locked then you
    > have the ability to dial ROAD and never unlock the keys?
    >

    Not really. I'd have to try it out, but they have the lock codes set so
    we can't do that in the lab. I just noticed that each of the keys in
    question matched up with special needs numbers.

    --
    -+-
    R??
    O/Siris
    I work for SprintPCS
    I *don't* speak for them.

    --
    Hemant Shah /"\ ASCII ribbon campaign
    E-mail: [email protected] \ / ---------------------
    X against HTML mail
    TO REPLY, REMOVE NoJunkMail / \ and postings
    FROM MY E-MAIL ADDRESS.
    -----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
    I haven't lost my mind, Above opinions are mine only.
    it's backed up on tape somewhere. Others can have their own.



  6. #6
    james
    Guest

    Re: SCP-6400 irritating issues

    NNTP-Posting-Host: 69.47.60.248
    Content-Type: text/plain; charset=ISO-8859-1
    Content-Transfer-Encoding: 8bit
    X-Trace: posting.google.com 1064979739 29341 127.0.0.1 (1 Oct 2003 03:42:19 GMT)
    X-Complaints-To: [email protected]
    NNTP-Posting-Date: Wed, 1 Oct 2003 03:42:19 +0000 (UTC)
    Xref: news.newshosting.com alt.cellular.sprintpcs:116877

    On my 6400 I was able to do the following with keyblock on:

    911
    *911
    #911

    the 1 key does get enabled once a 9 has been typed. After a * or # has
    been typed, the only thing that can be typed is a 9, once 91 (or #91,
    *91) has been typed, I can only type another 1, and then it's all
    locked out.

    Still dunno what the purpose of the * and the # would be (since I
    can't do *2 or anything like that) but I do see the merits of being
    able to dial 911 with keyblock off.



  • Phones Discussed Above

    Sanyo SCP-6400 More Sanyo SCP-6400 topics Sanyo Forum Reviews
  • Similar Threads

    1. Sanyo Phone Reviews
    2. Sanyo
    3. Nokia
    4. alt.cellular.sprintpcs
    5. Games