ivoanjo

You seem to be Portuguese as well so I'll just point out that physical key layout is not the same as software layout. I'm writing this on my Pro1 and I can type é è à á ç ã etc without issue. I'm using the FinQwerty app with the US Intl layout btw.

interesting. That's definitely not my experience -- I turn BT off from time to time, and I do get a notification telling me that the Gear has disconnected, but when I turn it back on it reconnects happily and without friction. I actually quite like Samsung's line, it's a pity that they are deliberately and by design holding it back -- I have a full linux machine attached to my wrist but it does very little apart from notifications, some very simplistic sleep/health tracking, and tell the time.

Yes, I use a Samsung Gear Fit2 Pro watch and indeed I've noticed more quick status notifications (that show for a second and then hide again) in the latest weeks from their sync app for Android. Hadn't connected it with the update, but yeah, I guess they might've started at the same time.

Note that there's no usable write support for NTFS in the linux kernel; what you see on linux desktops is ntfs-3g, a full implementation of ntfs that works as an app and uses the kernel FUSE api.

Did anyone manage to use an SD card on the stock firmware using anything other than FAT32? I'm up for whatever, I just want to get rid of the crappy 4gb file limit. It's a bit bizarre to still need to put up with it on my multi-core phone with gigabytes of ram and a third of a terabyte in storage 😕

Not that I noticed. I was able to kill most processes (other than tasker, that even when disabled somehow kept a background process).

Thanks for the suggestions. I tried the long-press-to-force-reboot, as well as stopping almost all processes that are not system ones, and no dice. I'm not going to do the factory reset -- I only end up using the headphones more often during this... unusual times of staying at home, so it's not worth the reinstall.

Thanks everyone for your replies. Just to clarify, I've recorded a video with three different headphones (including the AKG headphones shipped with the Galaxy Note 8 ) all suffering from this issue: It's good that this seems something more specific to my device's software or (shudders) hardware, not a generic issue that affects everyone. Any suggestions on how to debug it, other than factory reset? I was trying to avoid needing to redo my entire setup just for this issue 😕

I've had this issue ever since I got my Pro1, but I finally got annoyed enough to ask about it. I'm running the latest version of the stock firmware (20200306), and every time I plug in my 3.5mm wired headphones (Sony MDR-E829V) the Pro1 takes around 8 seconds to recognize that they are plugged in and switch over the sound. This means that quite often I plug in my headphones, press play on something, and then awkwardly get sound over the loudspeakers for a few seconds until it's switched over. And since I never had a device that behaved like this (and I've used these kinds of Sony he

I've definitely felt the issues coming from a Galaxy Note 8 where it worked flawlessly. I use both an Echo dot "alexa" and a taotronics device (turns my 3.5mm headphones into Bluetooth ones) and I get issues very often -- devices are not able to connect, especially *after* previously connecting and disconnecting to the devices. Going to the Bluetooth settings and manually clicking to connect to the devices does nothing. What I've found that works a lot of the time is toggling the Bluetooth on the Pro1 off and on again. This usually restores functionality, and it can connect a

Website seems to be broken now -- could you take a look? (Have you considered mirroring somewhere, e.g. github or something?)