Brand new OnePlus, unlocked and rooted. I am unable to get the Android share/bump to work with LG G3 or Samsung S4.
Have researched around quite a bit.
Have tried File Beam, so it will send a file (bluetooth), but will not receive.
Any known fix for this NFC bump bug? My searches have turned up nada.
Thanks.
Well, SuperBeam works, but still no direct luck with NC Beam, even OnePlus to Oneplus, seems to 'beam' the file, until at then end, says unsuccessful at the end. The NFC beam, though saying NFC, turns on the bluetooth on both OnePlus'es, and at the end of the beam, turns off the bluetooth. Just having the bluetooth on, despite the NFC Beam, does not change the success.
I like the SuperBeam success, but it is a menu selection/more user active process.
Any help to solve the simple NFC 'bump' would be appreciated.
We now have 3 OPO's. I can NFC from any of them to a G3, but not between the OPO's themselves!
Anyone with similar issues or it's working well for you?
Please, does anyone have an idea on how to fix this?
I've tried nfc beam from opo to nexus 5 and it works OK. Don't have other devices to test though. Are you on stock ROM ? Did you try a clean wipe and reflash?
Yes, have tried full reset. All 3 phone on 44s. All rooted and all other systems working well.
what is odd is that I can NFC to other non-OPO phones. Just not to another OPO. I can Bluetooth bump share between them, it's just more cumbersome, and WI-fi bump share as well.
I think the NFC bump outta work straight forward. All three phone work great with other, non-OPO phones.
Is there anyway to track down this issue?
So what seems to happen is that with the NFC bump, with no bluetooth, the OPOs, with each other, fail the transfer. If I turn on bluetooth, and then NFC transfer, I am able to transfer.
OPO to other makes of phone, no need for bluetooth.
Is this all making any common sense about how this should/does operate?
Related
Hey everyone, was hoping someone might be able to shed some light as to what's going on with my phone/headset.
I've had this bluetooth samsung headset for a while, it's always worked on my old Galaxy I. It worked for a couple days on my Galaxy II, and then stopped. The phone will find it, and it will pair, but it will not connect.
So I tried my wife's headset. Same thing happened, worked for a couple days, and then all of a sudden it won't work. Same thing, it will pair, but not connect.
What in the world could cause this? Is there a file or directory I can delete that will purge the bluetooth settings on the phone maybe?
Thanks everyone.
I had this happen with my handsfree speakerphone and my Bluetooth ODB sensor recently. What I did was go into Settings>Wireless and network>Bluetooth Settings and unpair and re-pair the devices (long press on them from the list until the menu pops up to un-pair)
I did try that and rescanned for them. It finds then again but it's the same problem it just won't connect with them. Very strange.
Would a custom rom have any effect on something like this? I was thinking maybe switch over to something else and try that maybe?
Sent from my SAMSUNG-SGH-I727 using XDA
i have this trouble with my bt all the time. i usually have to turn my bluetooth off on the settings and keep restarting then turning it back on. after doing this three or four times it seems to start working right. if u find a faster way would be helpfull
I've found that BT (with and without custom Roms) seems to work whenever it feels like it. To be fair my phone usually seems to be willing to work, but more than a couple of times it has decided to not work for no good reason other than apparently enjoying watching me be mad.
Hello. Recently I was trying to use Wi-Fi direct to transmit data to my Lg g2. I manually paired the devices from Settings menu then I selected a file-share-wifidirect and.... nothing! It showed me an empty screen with a Search For Devices button and in a few seconds responded with a message popup "Data transmission via Wi-Direct must be performed with another huawei device at the moment". WTF? Why? Is Wi-fi direct something huawei specific? I do not think so. The odd thing is that LG also allows to pair devices but does not give you a possibility to send data via Wi-Fi Direct forcing you to use SmartShare Beam which is LG-only technology. Why manufacturers are so stupid, they state their product has some technolohy but it's actually unusable! I do not wan't 2 huawei devices and I do not want 2 LG devices! On the other hand my old samsung s3 hanles it in a proper way, I was able to send files from it to both aforementioned devices using Wi-Fi Direct.
I know I can install SuperBeam to deal with my problem but it's inconvenient to install it on every device you want to transmit data to. So I just wanted to know if anyone else had this problem. Also my ROM is a bit old, something like b121(I have MT7-L10 version) so I wonder maybe they have already fixed it in some newer ROM especially the lates ones with Lolipop. If so I will try to install that rom. Thank you.
For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
I'm so glad someone else also has this issue!
I was about to start a similar thread.
I have a lot of issues scanning my libre and it hardly ever works!
Can anyone help locate the exact location of the NFC sensor. I have watched Jerry rigs everything teardown but he did not mention where exactly it is located.
If someone could give me the exact grid number from this grid I've created I'd be very grateful!
CheopsChefren said:
For my diabetes I use the Freestyle Libre system to measure my glucose levels. It works using NFC, it should work using NFC. Sadly it only works a few times out of every 10 times I try. Sometimes the Oppo reads my glucose levels with no problem but usually it is just a miss and miss scenario.
Sometimes turning NFC off and on resolves the issue, sometimes powering the Oppo off completely resolves the issue, but several times the seemingly only option was to do a factory reset , reinstalling everything again, whereafter it works a few days, when the same problem reappears again.
As you can imagine, not something that makes me happy. Anyone out here who recognizes these NFC problems, and has a solution, or a way to make it work more reliable. Every other NFC operations seem to work okay, but this one is really bugging me, especially as it is important with regards to my wellbeing. i am using a fully updated Oppo Find X2 Pro.
On my previous phone, a Samsung S9+, i had no issues at all.
Click to expand...
Click to collapse
Is this issue still present on Android 11 for you? My issue still persists even on a factory reset
Have you found solution. I have the Same problem with OPPO reno 4 z
I have bought an Oppo Find X3 Lite this weekend. Same issue. Anybody has a solution already for the above? I imagined only NFC would be enough but why is it that the Oppo phone does not connect with the scanner? Any idea anybody?
I got the Android 11 update for Oppo Reno 10x Zoom, and my Freestyle Libre 2 Sensors stopped working with the phone. When I try to scan, the NFC service hangs and NFC will not work anymore untill phone restart.
Oppo told me it is a known problem and they will try to fix it in a new firmware update. God knows when.
THANX A LOT, OPPO! Now I have to carry around the ****ty Freestyle reader all the time!
Hi Everyone. I had this issue and called ABBOT. Got a fix which now works. In your phone settings go to the libre link app and clear the cache data. Restart your phone and voila it works!
Hi, All
So, I'm trying to run custom ROMs as I want to set my HID_DEV_MTU_SIZE to 512 for amiibos, but every time I boot up the phone or manually turn Bluetooth on, it just says "turning on" and then turns itself off again, then back on, then off, then back on, then off... I can't get it to see any nearby bluetooth devices and the about section doesn't even show a Bluetooth address. It isn't an issue when I have stock OTA Android 10 installed, though...
I've reinstalled both Lineage 17 and Bliss more times than I can count, tried adding qcom.bluetooth.soc=smd to build.prop, disabling A2DP hardware offload; nothing works.
I've done a logcat several times, and it always comes up with bluetooth has died, not sure if that's of any help, though.
I know there have been other threads about this, but none of the solutions on those have helped, so apologies for starting another one.
I'm really lost at this point, any input would be greatly appreciated!
Thanks!!
Update: I installed Pixel experience and bluetooth works fine on there!
trainingtoothpaste said:
Update: I installed Pixel experience and bluetooth works fine on there!
Click to expand...
Click to collapse
Well i have in installed and its still troubleshooting... My device is Huawei p20 lite and Pixel Experience v13 installed
Does anyone else have this problem? I just got the Galaxy 4 smart watch (bluetooth, not lte version) a few days ago. When I initiate a call from the watch it dial and says "See phone" and the call is now coming through the phone. I can click a button on the phone to send the call back to the watch but obviously this defeats the convenience of not needing to have the phone in arms reach.
My husband figured out that its some kind of interference with other connected bluetooth devices (even though they are off), like my car and handsfree earpiece. If I unpair each of those items, calls work as they should. As soon as I re-pair another bluetooth device the problem resurfaces. I'd rather not have to pick one or the other to work if I can help it. Samsung support hasn't been able to fix it. Any ideas?
I should have clarified, I'm wondering both who does and who doesn't have this issue. Please comment even if yours works perfectly.
Samsung support seemed to suggest it was a software issue thar might be able to be fixed in a future update but I'm not sure if its an issue for anyone other than me.
Maybe you should take a look at this topic https://forum.xda-developers.com/t/...hange-default-behavior.4369423/#post-86031957