Hey ,

Was enlightening reading about the bugs everyone has highlighted. I have experienced similar over my usage of 4 months.

  1. Earbud not connecting with phone despite taking it out of the case
  2. Flaky behavior on the app, doesn’t always show battery precentage
  3. Doesn’t allow mapping to voice assistant of choice

I will try and be active here on a daily basis 🙂

Hey all,

was really interesting to see everyone’s bugs with the earbuds. I’ve had the buds for around 4 months or so and they’ve been fine up until the last month or so where I’ve started to experience 2 main issues.

  1. The right earbud never wants to connect right away. If I put the right one in first and wait a few seconds sometimes it will but sometimes I have to put it back in the case and then in my ear for it to connect. If I put the left earbud in first the right one will never connect on the first try.
  2. Noise cancellation randomly turns off after putting the buds in the case. This is occasional, sometimes it will sometimes it won’t.
    5 days later

    Hello!

    I´ve been using the Ear 1’s since I got them at the HBX release in August.
    I have loved them and I think that it’s such a cool product. Definitely the best looking earbuds on the market.
    However there is a bug that doesn’t seem to get fixed and a new one that has come up with the new firmware update.

    1. At times, the right earbud just seems to stop working. I have to put both buds back in the case and close the case. Then re-open it and sometimes this does the job. Other times it just doesn’t work. The right earbud doesn’t show up in the app at any time. Either I just put them away for a couple of minutes and then it works perfectly or I do a full reconnect with the pairing button. A lot of people are talking about this issue (reddit) and I haven’t found a real response or acknowledgment of it yet.

    2. This bug came with the new firmware update in my experience. When listening to music it just sometimes cuts out for 1 second. Not a big issue but kind of annoying because I instinctively think that I’m getting a call.

    Besides these bugs still in love with them and I look forward to the future of Nothing as a company! 😀

    Cheers!

    Probably just a personal issue, though my ear canals itch a bit after using for a while. I’ve ordered some Spinfit silicone eartips to avoid that. Otherwise, super happy with Nothing ear 1 Black Edition.

    shahidmukadam its not difficult…just to make the earphone sound right, pick the bud other than the right because that is the right approach 😛

    2 months later

    hi guys. I report the feedback of a visually impaired friend about ear1. He use an iphone. When “voice over” is ON sometimes comands on the buds doesn’t work properly. For example when calls are coming the double tap doesn’t work first try, and need 3 or 4 times to double tap to answer the call. Same thing about triple tap for “next song” and other stuff. But if voice over is off, everything well, works first time.

      I have been using Ear(1) since last September and recently a couple of issues has been popping up very frequently, one of which is very annoying.

      1. When audio is playing it cuts out once uh a while on one or both earbuds for a about 15-30s leading me to think there’s a call incoming or some other issue. Has been popping up very frequently, say about 10 times in a 30 minutes usage session.
      2. The ear(1) widget on android 10 (OnePlus 5T) is unresponsive half the time. And everytime I’ll have to remove the existing instance and add a new widget for it work.

      If any of you face the same issues and have been able to find a workaround, please let me know. Thanks in advance.

        6 days later

        Hi another thing from my friend already quoted: wen iPhone (se2) + ear1 + voiceover ON the phone read 1 touch as “read input” + “click input” .

        Normally 1 touch = read; 2 touches = click

        This is a big problem because for example he make a lot of calls or send messages unwillingly. Bye

        10 days later

        Is there any way to get the updates for our Ears(1), by a server for example.

        I’m not sure if it’s possible to get a way to get the updates for our Ears(1), as the last update was almost 15 days later than a large majority of members.

          Sib64 it’s currently being carried out OTA, Sib. But we’re working on ways to improve the process and the app itself. I also get my update a bit later. It’s a gradual rollout to ensure there are no problems and everyone can get it. 👍️

            Rudi
            Thank you for your reply Rudi.

            It wasn’t for me (I’m patient), and for the Ears(1) updates it’s not heavy to download via OTA. But I was mainly thinking about the future updates that will come for the Phone(1) and the rest to follow.
            But I know that everything is already well underway and that the whole Nothing team has already thought about it.

            8 days later

            From last 8 months I am using Ear(1) and found it good but there are bugs which keep on irritating. Lists are.

            1. It changes ANC mode automatically specially when single bud is being used.
            2. Battery drain rate is different for both buds wen used simultaneously
            3. It is horrible to watch TV usng it on Samsung 4K TV. Every 15-20 sec its sound stops and resume. Not able to use it on TV.
            4. Case hinge feels shaky. Always have fear of breaking it by mistake.
            5. It takes time to reconnect on previous device. And if I open and immediately pulls one bud than case will connect to phon but that bud will not connect to phone. I have to place it again in case and have to take out it after 2 second to connect it.

            If worked upon these feedback, it will definitely affect Masses.

            lokeshkalwar
            But as far as the Ears(1) are concerned, don’t forget that they are not multipoint!
            About the other inconveniences, I think you already reported them on Discord?
            And if so, the SoftwareDevs have taken into account these problems already pointed out