SBH50 and LG Nexus 4

Hi,
I purchased the SBH50 in October 2013 and basically found it solid and working well ... until ...
Google updated me to 4.4.2 at which time I started experiencing troubles.  Specifically:
1. SBH50 app no longer runs in the Notifications Bar/Tab of Android and therefore no longer displays caller I.D., only the number on incoming calls.  This was working before the update.  Oddly, if I open Settings/Apps I can find the app "running" in background but it just  no longer runs in the drop down menu or Notifications Bar/Tab as before.
2. It drops calls.  Never a problem before the update.  Right in the middle of a call it will just beep and disconnect me and then in a few seconds reconnect.  This might happen 2-3 times in a row.  Very frustrating. 
3. People I am talking to report that it seems to be cutting out on them as well.  My sentences to them get chopped and therefore illegible.
Since getting this I have been dissapointed at the lack of voice dial support that many other more basic devices have had before.
On a positive note I have not noticed it cutting out or dropping when playing music.  That seems to work fine so far just as it always did.
I would appreciate any input.  Thanks in advance.

Same problem here! Music plays ok, phone calls drop, no extended functionality through the APPs on the SBH50.
The only difference is, I got the SBH50 only two days ago and my Nexus 4 had already been on 4.2.2 so it actually never worked for me. 
I'd very much appreciate a solution either from Google or Sony's end...Thanks!

Similar Messages

  • FCoE and multiple Nexus 5000s and a 7000 core

    Hi
    I have a customer who is looking at four Nexus 5020s to start with and more in the future uplinked to a Nexus 7000 core.
    Am I right in thinking that whilst data traffic will be able to reach hosts ocnnected to a different Nexus 5002 via the 7000 core FCoE traffic will not ?
    If so what is teh recommended way of rolling out pods of 5020s for VMware servers with converged network adaptors so that they can all access the SAN ?
    Regards
    Pat

    Don't use corecenter for fan speed control.  Instead, use the BIOS:
    1) Open Corecenter from the administrator account or a user account that has admin privileges.  Click on the top center logo which should open the fan speed control window.  There should be two items, CoolnQuiet and User/Manual or something like.  Put it in manual and move the slider all the way to the right. Ignore the CoolnQuiet, it's misnamed here - MSI's corecenter does not control CoolnQuiet.  What MSI is calling CoolnQuiet is just fan speed control.  Anyway, put it in manual.  Close Corecenter and you should never have to open it again unless you want to monitor fan RPM's.
    2) Next, reboot and enter the BIOS.  Go to the H/W  Monitor settings.  Turn on Smart CPU Fan Speed.  Set to 40 C +/- 1.    This will allow the motherboard to control the fan speed.  On the other hand, if you want your fan always at maximum, then disable Smart Fan Speen control.   Don't worry about the Smart NB Fan speed, leave it disabled.
    Also, keep in mind that when you first open Corecenter, the immediate fan RPM's reported are not correct.  It takes it a few seconds to get the readings.  So wait until Corecenter minimizes itself to the system tray, then open it from there, and you will see the correct fan RPM's.

  • Adobe air and HTC Nexus 1

    Hi,
    I'm trying to test my game on my nexus 1. I understand that to be able to do that I first need to download and install Adobe Air for Android from the Android market.
    When I go go to the Air page on the market it says that the app is incompatible with my phone. I'm running OS 2.2 that should support the app and from what I saw nexus 1 should be able to run AIR.
    Did someone else had this problem and managed to solve it?
    Thanks,
    Oz

    Everything makes it look like Nexus One should work. Do you find that very few apps are available, or that a lot are, but not your own app? If it's just your own app, can you say how many devices the marketplace tells you will be able to use your app?
    If it's a low number, read through this thread, in case it applies to you:
    http://forums.adobe.com/message/3975735#3975735

  • VSM and Cisco nexus 1000v

    Hi,
    We are planning to install Cisco Nexus 1000v in our environment. Before we want to install we want to explore little bit about Cisco Nexus 1000v
    •  I know there is 2 elements for Cisco 1k, VEM and VSM. Does VSM is required? Can we configure VEM individually?
    •   How does Nexus 1k integrated with vCenter. Can we do all Nexus 1000v configuration from vCenter without going to VEM or VSM?
    •   In term of alarming and reporting, does we need to get SNMP trap and get from individual VEM or can be use VSM to do that. OR can we   get    Cisco Nexus 1000v alarming and reporting form VMware vCenter.
    •  Apart from using Nexus 1010 can what’s the recommended hosting location for VSM, (same Host as VEM, different VM, and different physical server)
    Foyez Ahammed

    Hi Foyez,
    Here is a brief on the Nexus1000v and I'll answer some of your questions in that:
    The Nexus1000v is a Virtual Distributed Switch (software based) from Cisco which integrated with the vSphere environment to provide uniform networking across your vmware environment for the host as well as the VMs. There are two components to the N1K infrastructure 1) VSM 2) VEM.
    VSM - Virtual supervisor module is the one which controls the entire N1K setup and is from where the configuration is done for the VEM modules, interfaces, security, monitoring etc. VSM is the one which interacts with the VC.
    VEM - Virtual ethernet module are simply the module or virtual linecards which provide the connectivity option or virtual ports for the VMs and other virtaul interfaces. Each ESX host today can only have one VEM. These VEMs recieve their configuration / programing from the VSM.
    If you are aware of any other switching products from Cisco like the Cat 6k switches, the n1k behaves the same way but in a software / virtual environment. Where the VSM are equal of a SUPs and the VEM are similar to the line cards. The control and the packet VLANs in the n1k provide the same kind of AIPC and Inband connectivity as the 6k backplane would for the communication between the modules and the SUP (VSM in this case).
    *The n1k configuration is done only from the VSM and is visible in the VC.However the port-profiles created from the VSM are pushed from the VSM to the VC and have to be assigned to the virtual / physical ports from the VC.
    *You can run the VSM either on the Nexus1010 as a Virtual service blade (VSB) or as a normal VM on any of the ESX/ESXi server. The VSM and the VEM on the same server are fully supported.
    You can refer the following deployment guide for some more details: http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9902/guide_c07-556626.html
    Hope this answers your queries!
    ./Abhinav

  • MLD limitations M2 and F2e Nexus linecards

    Dear all,
    According to Cisco's IPv6 MLD configuration guide, the following limitations and guidelines are applicable for Nexus M2 and F2e lincards.
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/nx-os/multicast/configuration/guide/b_multicast_chapter_0100.html
    Optimised-Multicast-Flooding must be disabled.
    Does anyone know whether these MLD limitations are also applicable for the recently manufactered/released F3 linecards?
    Many thanks in advance!
    Kind regards,
    Wim

    With current software, the only way for F2E to be in the same chassis with the M1/M2/F1 cards is for the F2E to be in a different vDC.  The only way to connect the F2E to get connected to different cards is to physically connect them either through copper or fibre.

  • FCoE using Brocade cards CNA1020 and Cisco Nexus 5548 switches

    All,
    I have the following configuration and problem that I am not sure how to fix:
    I  have three Dell R910 servers with 1TB of memory and each has two  brocade 1020 CNA cards dual port.  I am using distributed switches for  the VM network and a second distributed switch for VMotion.  I have two  of the 10G ports configured in each distributed switch using IP Hash.   The management network is configured using a standard switch with two 1G  ports.
    The  Nexus configuration is we have two nexus 5548 switch connected together  with a trunk.  We have two VPC's configured to each ESX hosts  consisting of two 10gig ports in each VPC with one port going to each  switch.  The VPC is configured for static LAG.
    What  I am seeing is that after a few hours the virtual machines will not be  accessible via network anymore.  So if you ping the VM it will not work  and if you get on the console of the VM then ping the gateway then  nothing as well but if you try to ping another virtual machine on the  same host on the same VLAN then it will work so traffic is going through  the ESX backplane.  If I reboot the ESX host then things will work  again for another few hours or so then the problem repeats.
    The version of vSphere I am using is ESXi4.1
    Please assist I am stuck.
    Thanks...

    Here is the link for Nexus and Brocade interoperability Matrix
    http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html#wp313498
    usually this table would show those models those have been tested and verified
    However I do not see  Brocade 5300 listed in the table . It could be, interoperability may have not been tested by both vendors perticularly to 5300 type Model.

  • Install and Configure Nexus 1000V

    Hi all !! Hope everyone is well !!
    I just purchase 2 Nexus 1000V's. Could someone give me some guidance on how to go about installing / configuring a Nexus 1000V switch ? This is my first time working with Nexus series switches. Thanks in advance !!!
    D.

    Hi,
    Here are some of the documents and video links that will help you to proceed futher with Nexus 1000v installation:
    http://www.cciemachine.com/en/US/products/ps9902/prod_installation_guides_list.html
    http://www.google.co.in/search?q=nexus+1000v+installation&hl=en&client=firefox-a&hs=Hnt&rls=org.mozilla:en-US:official&prmd=v&source=univ&tbs=vid:1&tbo=u&ei=WtloTI6hAc-rcbb98I8F&sa=X&oi=video_result_group&ct=title&resnum=4&ved=0CCwQqwQwAw

  • VPC / Cisco ACE and the Nexus 2K and 5K

    Hi all,
    So we have a test environment that looks like the following. We have 2 5K's switch 1 and switch 2. Switch 1 has two 10gb connections downstream to a 2K and switch 2 has two 10Gb connections downstream to the other 2K. We have a few servers that are multi-homed with LACP and VPC via the 2Ks and it works a treat.
    We have our Cisco ACE 01, ports 1 and 2 going to one of the 2K's and we have ports 3 and 4 going to the other 2K, ACE02 ports 1 and 2 going to one of the 2K's and we have ports 3 and 4 going to the other 2K. If i enable VPC and none LACP based etherchannel i cannot get the ACE's talking to each other, but looking at the VPC status its all healthy and up.
    Has anyone managed to multi-home the ACE between two 2K's with VPC successfully? 
    If I disable the links so each ACE only has links upstream in a traditional port-channel and not cross connected, the ACE's can see each other with no issues.
    Cheers

    Doh.. so we had a cable patching issue in the end. Let this be a lesson to all networking chaps - always check the basics first! Now we have patched the cables as per design the VPC has been established and works.
    Now we  have VPC is working we are simulating link failures. When we restore a shutdown physical port within the port-channel/VPC that sits between the 2K and ACE (simulating a port failure) the ACE's lose sight of each other for about 10 seconds and causes an short outage until the port is up and up. The logs on the ACE show 'the Peer x.x.x.x is not reachable. Error: Heartbeat stopped. No alternate interface configured' but the VLAN for the FT interface is carried over all four ACE NIC's that are multi-homed to two 2K's... very strange, i would not expect this, it's like the MAC addresses for the FT interface are waiting to be timed out on the 2K until they are switched on another interface within the port-channel and VPC.
    Anyone seen this before?

  • Connecting a Dell B22 FEX to Nexus 6001 and storage

    Hi Folks,
    We have a setup where we are running a Dell B22 FEX in Blade enviornment and want to connect the B22 FEX to a cisco Nexus 6001 switch. As per NX-OS release note, B22 FEX and 6001 Nexus connectivity is supported.
    Now after connecting to Nexus 6001, how do i get access to storage pool or SAN fabric ?  As per another thread of discussion, Nexus 6001 does not support direct fabric attachment at this point in time. So how do we bridge these two elements to a storage fabric ??
    As per 6.02 release note:
    "Support for DELL FEX
    Added support for the Cisco Nexus B22 Dell Fabric Extender for Cisco Nexus 6000 Series switches starting with the 6.0(2)N1(2) release."
    This is the exact reason we bought it. We have a enviornment where we are running Dell B22 FEX.  Idea is to connect the B22 FEX into Nexus 6001. We are confuse at this point. After connecting the Dell B22 FEX to Nexus 6001, how to access the storage network or storage fabric ??
    Thanks,

    Hi Rays,
    The function should be the same for all FEXs regardless of what parent switch they connect to. to.
    if you are referring to this comment:
    You can connect any edge switch that leverages a link redundancy mechanism not dependent on spanning tree such as Cisco FlexLink or vPC
    FelxLink is a different technology that does not use STP, but not every switch platform supports FelxLink. FlexLink is not used very often, as other technologies like VSS, VPC and stacking has emerged.
    HTH

  • Please tell me how to connect with FCoE UCS-mini and Nexus N5k (N5K-C5548UP-B-S32)

    I have UCS 5108 Blade Server Chassis (with two B200 M3 Blade Servers inside and two FI 6324) connected to Nexus N5k switch through 4x10GE links.
    I want to configure the two aggregated channels FCoE (vFC) from chassi to switch.
    All instructions I've been seen refer to the fact that UCS-mini must be in the FC end-host mode, but UCSM 3.0 version does not support this mode, what shoud I do?
    I set up following the instructions www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/116248-configure-fcoe-00.html
    But, after setup I have a fault on fabric: FCoE or FC uplink is down on Vsan 500;
    And in Nexus: Vsan 500 is down (waiting for flogi)
    When I do "show interface vfc 1" from Nexus CLI I see no 'Trunk vsans (up)', but
    'Trunk vsans (initializing)             (500)'
    Unfortunately, I can't find technical notes for UCS mini (with UCSM v. 3.0), so may be You can promt any guides or suggestion for this?
    Thank You in advance!

    The release notes of 3.0.1e, which is for UCS-mini,
    http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/ucs_3_0_rn.html
    says:
    Unsupported Features
    The following features are not supported in Cisco UCS Manager, Release 3.0:
    Features, defect fixes, and platforms introduced in Cisco UCS Manager, Release 2.2(2c) and newer that are not explicitly called out in New Features or Resolved Caveats sections of this document.
    Some features introduced in Cisco UCS Manager, Release 2.2(1b) and earlier releases:
    –Ethernet Switching Mode
    –FC End Host Mode
    – Private VLANs
    – Port Security
    – KVM Virtualization is not tested (although not explicitly disabled)

  • Ask the Expert: Configuration, Design, and Troubleshooting of Cisco Nexus 1000

    With Louis Watta
    Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about design, configuration, and troubleshooting of Cisco Nexus 1000V Series Switches operating inside VMware ESXi and Hyper-V with Cisco expert Louis Watta. Cisco Nexus 1000V Series Switches deliver highly secure, multitenant services by adding virtualization intelligence to the data center network. With Cisco Nexus 1000V Series Switches, you can have a consistent networking feature set and provisioning process all the way from the virtual machine access layer to the core of the data center network infrastructure.
    This is a continuation of the live Webcast.
    Louis Watta is a technical leader in the services organization for Cisco. Watta's primary background is in data center technologies: servers (UNIX, Windows, Linux), switches (MDS, Brocade), storage arrays (EMC, NetApp, HP), network switches (Cisco Catalyst and Cisco Nexus), and enterprise service hypervisors (VMware ESX, Hyper-V, KVM, XEN). As a Technical Leader in Technical Services, Louis currently supports beta and early field trials (EFTs) on new Cisco software and hardware. He has more than 15 years of experience in a wide variety of data center applications and is interested in data center technologies oriented toward data center virtualization and orchestration. Prior to Cisco, Louis was a system administrator for GTE Government Systems. He has a bachelor of science degree in computer science from North Carolina State University. .
    Remember to use the rating system to let Louis know if you have received an adequate response.
    Louis might not be able to answer each question because of the volume expected during this event. Remember that you can continue the conversation on the Data Center community Unified Computing shortly after the event.
    This event lasts through Friday, JUne 14, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.
    Webcast related links:
    Slides
    FAQ
    Webcast Video Recording

    Right now there is only a few features that are not supported on N1Kv on Hyper-V
    They are VXLAN and QOS Fair Weighted Queuing. We are currently demoing VXLAN functionality at Microsoft TechEd Conference this week in New Orleans. So VXLAN support should be coming soon. I can't give you a specific timeline.
    For Fair Weighted Queuing I'm not sure. In the VMware world we take advantage of NETIOC infrastructure. In the MS world they do not have a NETIOC infrastructure that we can use to create a similar feature.
    Code base parity (as in VMware and Hyper-V VSMs running NXOS 5.x) will happen with the next major N1KV release for ESX.
    Let me know if that doesn't answer your question.
    thanks
    louis

  • VN-Tag with Nexus 1000v and Blades

    Hi folks,
    A while ago there was a discussion on this forum regarding the use of Catalyst 3020/3120 blades switches in conjunction with VN-tag.  Specifically, you can't do VN-Tag with that Catalyst blade switch sitting inbetween the Nexus 1000V and the Nexus 5000.  I know there's a Blade switch for the IBM blade servers, but will there be a similar version for the HP C-class blades?  My guess is NO, since Cisco just kicked HP to the curb.  But if that's the case, what are my options?  Pass-through switches?  (ugh!)
    Previous thread:
    https://supportforums.cisco.com/message/469303#469303

    wondering the same...

  • Interoperability issues between Nexus 5k and HP storageworks (8/20q)

    Hello community,
    I am trying to get a VM host and a windows server to connect to their storage across a nexus and HP (Qlogic) fabric switch. This is currently having issues with the VM host unable to see the datastores, possibly due to interoperability between Cisco and HP (Qlogic)
    I have configured and tested the connectivity using only the cisco nexus and this worked, I then tested it using only the HP fabric switch (HP 8/20q) and this also worked.
    However, when using the HP and Cisco Nexus as shown in the attached diagram, things stop working.
    The connection is using Native Fibre channel, On the Cisco side I performed the following steps
    Configured the Nexus with Domain ID 10 and the HP with Domain ID 20.
    Connected the 2 fabric switches on fc1/48 (Cisco) and port 0 (HP) and confirmed that the ISL came up (E_port 8G), I confirmed connectivity using fcping both ways.
    I connected the SAN to the Nexus and the servers to the HP
    Configured VSAN 10
    Added interfaces fc1/41 to 48 in VSAN 10
    Created 2 zones ( ESXI and Windows)
    Added the PWWN for the ESXI server and the MSA2040 to the ESXI zone
    Added the PWWN for the Windows 2k8 server and MS2040 to the Windows zones
    Created zoneset (Fabric-A) and added both the above zones in it
    Activated the FABRIC-A zoneset
    The result is that the zones and zoneset are synchronised to the HP switch .I confirmed that I was able to see the servers and SAN WWN in the correct zones on the HP.
    From the 8/20q switch I am able to fcping the SAN, Nexus and servers, however the Nexus is only able to fcping the SAN and the HP, it returns a “no response from destination”  when pinging the servers.
    I have added the FCID for all the units in the same zones to see if it makes any difference to no avail the result seem to be the same. I have gone through various Nexus/MDS/HP/Qlogic user guides and forums; unfortunately I have not come across any that shows this specific topology.
    source for HP user guide is here: http://h20565.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c02256394
    I’m attaching the nexus config and partial view of the “show interface brief” showing the fibre channel port status
    Interface  Vsan   Admin  Admin   Status          SFP    Oper  Oper   Port
                      Mode   Trunk                          Mode  Speed  Channel
                             Mode                                 (Gbps)
    fc1/47     10     auto   on      up               swl    F       8    --
    fc1/48     10     auto   on      up               swl    E       8    --
    Any help and advice would be greatly appreciated. thanks in advance

    Hi all, after much reading, Walter Dey provided the hint to put me on the right track. 
    By default the Nexus 5k is in interop mode 1. However, one of the requirement for this to be "interoperable" with other vendor the FCDomain ID in the entire fabric needs to be between 97 and 127 as stated in the Cisco website.
    http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/interoperability/guide/ICG_test.html
    Another issue that had me and my colleague scratching our heads, was that we were seeing high level of CRC errors on the ISL interfaces. This was caused by ARBFF settings mismatch between the Nexus and the HP. This was resolved by ensuring that the ARBFF setting on the HP was set to false and the command "switchport fill-pattern ARBFF speed 8000" is configured on the ISL interface linking the 2 switches. (note that Cisco's default setting for the ports is IDLE, until this is changed the link will not stabilise)
    Thanks for all your help guys.

  • Cisco VSS Dual-active PAgP detection via Nexus and vPC

    Hi!
    We will soon implement Cisco nexus 5595 in our Datacenter.
    However we will still be using a pair of C6500 in a VSS in some part of the network.
    Today we are running dual-active detection via a PAgP Port-channel, but those Port-channels will be removed and the only Port-channel we will have is to a pair of Nexus 5596.
    Does anyone know if we can run PAgP dual-active detection via this MEC/vPC?
    Thank you for your time!
    //Olle

    Hi,
    The easies way is to connect both links from the 6500s to only one of the Nexus switches. Than create a portchannel on both the 6500 and the Nexus.
    The other option would be to connect the 6500s directly together via a gig link and use fast hello instead of epagp.
    I would use fast hello since it is supported on the 6500s.
    HTH

  • Cisco LAN Management Solution is required to support Cisco Nexus 5548P and 5596UP switches?

    Hi,
    Could someone help to know what Cisco LAN Management Solution is required to support Cisco Nexus 5548P switches and Cisco Nexus 5596UP switches?
    These new Cisco switches are being implementing on customer network and he ask us that he requires these equipments be supported on a LMS solution (customer currently is using LMS 3.2.1)
    Can someone help?
    Thanks in advanced,
    guruiz

    Some very limited Nexus support is present in LMS 3.2.1 - see the supported device table here.
    To get more complete support, including the 5596UP, they need to upgrade to LMS 4.x (e.g.  LMS 4.2.2 is the latest and is sold under the Cisco Prime Infrastructure 1.2 umbrella). The major upgrade from 3.x to 4.x requires purchasing an upgrade license.
    Some functions (namely User Tracking ) will not be available on the 5k due to non-support of the requisite MIB on the device. I believe LMS still doesn't let you do VLAN management on 5k's - you need to use DCNM for that if you want to do it from a GUI.
    See the table here for LMS 4.2 device support.

Maybe you are looking for