Related
I have a weird situation and not sure if I may have done something to cause it (most likely). My rezound cannot see any Bluetooth devices when it does a scan. I've tried using most of the ICS and GB images out there and even went back to the stock ROM at scottsroms.com to see if I could get it to work again. I know Bluetooth works, because it will pair with a device if that device can scan my phone and start the pairing process.
Can anyone think of what would be causing my phone to not see BT devices?
My phone is HTCDev unlocked and I have the anan ra 3.14 on it for the recovery image.
Any help would be appreciated.
Thank you,
The assumption is that you have put the device that you want to scan into discover mode..... If so, then you may have a problem with the hardware.
If you haven't, the phone will only see devices which are in discover mode.
This may sound like an obvious thing, but I ran into a user the other day that didn't know that.
Completely understand the need to clarify. Yes, I put both the devices in discover mode and I press the scan for new devices continually.
I'm hoping it's a software issue since it works if another device handles all the pairing. That doesn't work with headsets though.
For instance, if I have my laptop search for devices, it will see my phone, pair with it and stream music from it. So it appears the hardware works, just doesn't scan, which I'm hoping (losing hope quickly) that it's a software issue.
Also, I have tried a few different ROMs on this phone, so I'm not sure if one of the kernel images may have messed it up or if the initial root software I used broke it.
Hello there.
I am using the X since a few weeks. It is a damm nice phone. perfect size, brilliant display and the rest of the specs is cool too.
But:
I can connect it with my car. I can get calls in the car using the audio + mic from the car. But I cant use the phonebook. And so I cant see who is calling or even use the carphonebook for dialing a number or use favs.
BT itself is working: I already transfered e.g. contacts via BT from my old phone. The UP MOVE is synching.
I also tried it on an BMW F20 - same problems.
In other forums ( e.g. oneplus ) I found some other persons with the same problem. They "solved" it by buying an app calles "Bluetooth Phonebook". It seems that the app will add/replace/change some BT Profiles.... It seems that there is an profile missing: PBA, PBAP Phonebook Access Profile.
If this is so, it will mean that OnePlus is not finished with the Oxygen 2.2.0.
The offical support can´t answer this question to me
Questions:
Can someone tell me how to check if this profile is on my phone?
If not present - how can I add it by myself?
Any other helpfull ideas?
Bluetooth Phonebook app is the easiest option.
Or i believe BT works with cyanogenmod
http://forum.xda-developers.com/one.../rom-cyanogenmod-13-x-oneplus-x-onyx-t3279784
I would not rely on Oneplus to fix it as the problem still exists in the Oneplus 2 and thats been out even longer than the Oneplus X.
Workaround
I also have the exact same issue with my 2015 BMW. BT connection for calls work stable but contacts are only synced partially. My solution was to again and again delete and re-connect my OPX until in one instance all contacts were available in the cars phonebook. I then stored all important contacts into the cars phonebook so that they are always present independently from the connected phone. Not ideal but a workaround.
The issue for the OP2 was solved with the latest OTA update. So hopes are that OPX will receive the same fix...
I also have the same problem with Seat Léon St.
According to OnePlus community on Google+, this issue has been solved with the last update of OnePlus 2.
I already contacted OnePlus Support on Twitter but they cannot confirm.
Envoyé de mon ONE E1003 en utilisant Tapatalk
I had a similar problems. With my OPT and OPX with My 208 GTi. Using Bluetooth Phone book from the play store was the easiest option.
Sent from my OnePlus X USO g Tapatalk
+1 BMW e71 2012 / Ford Kuga 2015. Bluetooth phone book solved both, although Ford sync took a couple of attempts.
Something that oneplus needs to sort. Shouldn't need to pay to get this basic functionality
That's a known bug on OxygenOS from loooooonnnggg time ago, it was finally solved on OP2 in the last update so, it must also be fixed on OPX in the nest update...
On CM12 \ CM13, etc, it works great with all car bluetooth systems...
at the moment i am still in contact with the OP Support Team.
They are still NOT commenting the missing BT profile in Oxygen.
The App "BT Phonebook" is realy working. So imho its a missing basic feature of OP and has to be fixed.
Yesterday I got an OS update on my OPx but in the readme was nothing mentioned about BT
This is probably not what you guys are looking for but i had the same problem with my sony headunit no contact names would display just the phone numbers. I have since installed custom rom CM13 by ashwin and everything is working contacts display names and i can search people to call through the stereo settings etc.
Indeed. I don't really want to flash but my wife was connected to my car with her OnePlus One within the minute and streamed Spotify... So yes, this is not we really want but at the end, OxygenOS is a bit bugged
I have the same problem with my 2011 Mazda 6. Bluetooth Phonebook did NOT solve this issue for me...
jevgeje said:
I have the same problem with my 2011 Mazda 6. Bluetooth Phonebook did NOT solve this issue for me...
Click to expand...
Click to collapse
yesterday the support was contacting me: They know about the issue and are working on an fix. No date
Hi all,
Recently got myself a Ulefone Armor 2. The device is not too bad so far. I switched to it after cracking my Power2's screen multiple times. It comes with a stupidly basic Android 7. So I just wanted to start a thread to see if anyone's got their hands on it and started hacking around. See the bookmarks below for all things customisation.
I've edited this first post multiple times to reflect the recent developments. Some people got root & Magisk working see links after my first remarks:
About the latest Software Update (aka 20180224_s21v57c2k_gq_fp or S21 GQ3037LF2 Ulefone V12 20171009-Update 20180224):
alpsayin said:
Nope, it's not the same. Something is fundamentally off with this ROM. Accessibility services get turned off automatically every time screen goes off. Half the background apps are killed every time screen stays off for a minute too. I've already reverted back to what I had before. I suggest stay away from this build.
Click to expand...
Click to collapse
If you've updated your phone to latest ROM use the below instructions to revert back but use https://www.needrom.com/wp-content/uploads/2017/11/S21_GQ3037LF2_Ulefone_V12_20171009.zip instead of the latest one:
[/U]https://forum.xda-developers.com/showpost.php?p=74294320&postcount=31
First remarks:
-Some people and I are having problems with USB-C headphone adapter (https://forum.xda-developers.com/android/help/ulefone-armor-2-t3684566/post74367962#post74367962)
-Device bluetooth volume level is separate from the headset's volume. (EDIT: fixed with recent ROM update)
-Adaptive brightness might be a tad bit aggressive in my opinion so I switched it off. (EDIT: less aggressive with recent ROM update)
-Android Pay does NOT work. It says device is not verified (which is sad, I really wanted this to work). (EDIT: works now with also recent ROM update).
-Camera button launches a camera app if you press for 5 seconds only. Useful to trigger underwater.
-SOS button needs 5 seconds push to start calling emergency contacts, but even then it causes a lot of pocket dialling.
-PTT button only works inside the Zello app. Kinda wish these buttons could be reassigned for other things (EDIT: see this reply https://forum.xda-developers.com/showpost.php?p=74451451&postcount=78).
-Generally buttons are easy to push, i change the volume every time I put the phone in my pocket, then again i might just need to get used to having a brick with 4g.
-Speakers are not great, but it's indeed waterproof. Took it into shower and gave it a good abuse.
-Fingerprint sensor is a bit annoying at times but I believe this might be because I was sent a phone with improperly attached screen protector. (EDIT: it was the badly aligned screen protector)
-Power menu doesn't have the shortcut to the power saving mode that I like so much
-Be gentle with your USB-C cap, mine broke. It's still waterproof, but now it's pretty easy to lose the cap.
-If you wanna save some serious battery, disable Google App data backup (App backup&restore).
-Sports mode in battery settings will make the phone "snappier" probably at the expense of battery life.
BOOKMARKS:
ROM Stuff (some need TWRP)
See this reply for instructions to update to recent ROM:
https://forum.xda-developers.com/showpost.php?p=74294320&postcount=31
TWRP Flashable Stock ROM with Magisk Root (Android Pay working, Buttons disabled, needs opengapps)
https://forum.xda-developers.com/showpost.php?p=74749806&postcount=174
Restore or write IMEI numbers:
https://forum.xda-developers.com/showpost.php?p=74450547&postcount=76
TWRP
See these replies for root and TWRP (v1, legacy):
https://forum.xda-developers.com/showpost.php?p=74399450&postcount=60
https://forum.xda-developers.com/showpost.php?p=74429860&postcount=68
See these replies for TWRP without OTG and root (v2, now also legacy):
https://forum.xda-developers.com/showpost.php?p=74488885&postcount=96
https://forum.xda-developers.com/showpost.php?p=74490010&postcount=97
English TWRP in zip and img formats, also something about Forced Encryption (v3, but also follow instructions from v2)
https://forum.xda-developers.com/showpost.php?p=75544568&postcount=281
Magisk and Root
Summary of SuperSU, Magisk, Xposed and Android Pay compatibilities:
https://forum.xda-developers.com/showpost.php?p=74580626&postcount=135
Magisk Installation (legacy, but use it for instructions):
https://forum.xda-developers.com/showpost.php?p=74472235&postcount=89
Latest Magisk (permissive, hidelist persists, allowing module installation, yay!):
https://forum.xda-developers.com/showpost.php?p=75803660&postcount=299
Re-flashing STOCK ROM and/or updating Magisk while keeping data (requires TWRP)
https://forum.xda-developers.com/showpost.php?p=75064226&postcount=223
Audio Issues
Fix for Armor 2 Bluetooth Disconnect Issue
https://forum.xda-developers.com/showpost.php?p=75461843&postcount=279
Audio not routing through or unstable USB-C headphone jack?
https://forum.xda-developers.com/android/help/ulefone-armor-2-t3684566/post74621805#post74621805
Tweaks (Buttons, Persistent Notifications)
How to disable default PTT & SOS functions and replace functionalities (requires ROOT):
https://forum.xda-developers.com/showpost.php?p=74445439&postcount=72
How to get rid of Persistent NFC notification
https://forum.xda-developers.com/showpost.php?p=75049379&postcount=216
Fingerprint scanner is NOT SECURE
https://forum.xda-developers.com/showpost.php?p=75796254&postcount=297
Credits: @sumec100 @djvinniev77 @enzovic @Sebastl @jemmini (? from 4pda.ru) @TuksOID @sargon__
Have you had any software issues and can you assign anything else other than emergency contacts to the SOS button? I have an LG X Power with a cracked screen and have been looking into this phone because the doogee s60 and bv8000 pro both show problems and I don't feel like spending 600 for a cat s60 or s41
Sent from my LG-K450 using XDA-Developers Legacy app
Wish there was a way I could disable the sos button on my doogee s60
Hi,
i got mine a week ago, and i think this phone is really great so far. Only thing i'm missing is a way to root it, i have tried everything i could find, but nothing has worked so far.
Tommy
I really wanted to like this phone, but Bluetooth is essencial to me, and I cant keep a Bluetooth audio connection constant with out disconnects and connects randomly, is very frustrating, I was expecting a better quality of the audio of the internal speaker when making calls, the holes of the back speaker one is a dummy the is no sound from it, and battery is good but not so good for the capacity, I was expecting more, and the camera is really sub par with a slow auto focus. I why didn't they make the screws of the sim compartment flush with case, was so simple.
fluis70 said:
I really wanted to like this phone, but Bluetooth is essencial to me, and I cant keep a Bluetooth audio connection constant with out disconnects and connects randomly, is very frustrating, I was expecting a better quality of the audio of the internal speaker when making calls, the holes of the back speaker one is a dummy the is no sound from it, and battery is good but not so good for the capacity, I was expecting more, and the camera is really sub par with a slow auto focus. I why didn't they make the screws of the sim compartment flush with case, was so simple.
Click to expand...
Click to collapse
I just tested the Bluetooth on a speaker, i had no issues with it. As for the battery, there is a lot of settings you can tweak, and turn off all of the Google draining apps. I have installed Greenify too.
Camera is not the best, but it does the job. We get what we pay for, and for that price i cannot expect to get a better phone, that probably would survive a nuclear war lol
tmiland said:
I just tested the Bluetooth on a speaker, i had no issues with it. As for the battery, there is a lot of settings you can tweak, and turn off all of the Google draining apps. I have installed Greenify too.
Camera is not the best, but it does the job. We get what we pay for, and for that price i cannot expect to get a better phone, that probably would survive a nuclear war lol
Click to expand...
Click to collapse
I'm glad that you having a better experience with Bluetooth, I do hope that I can solve my problems with it.
I also just bought an Armor 2, and I also want to be able to configure the ptt and sos buttons in a better way. I hope people who know about this give us a hand. regards
I can assign emergency contacts to SOS button. Multiple ones in fact; if first person doesn't answer automatically calls the next one and so on. I was just curious to give them other functionalities, such as launching apps.
tony442 said:
Have you had any software issues and can you assign anything else other than emergency contacts to the SOS button? I have an LG X Power with a cracked screen and have been looking into this phone because the doogee s60 and bv8000 pro both show problems and I don't feel like spending 600 for a cat s60 or s41
Sent from my LG-K450 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Did anyone manage to get Android Pay working? Android Pay doesn't verify the android, I was really looking forward to being able to use it...
I just got mine, love it for the price but unfortunately didn't read about android pay. I just tried and yep, no good to add payment cards. If you have a banking app that accepts card integration, it works that way, so it's just android pay/Google security.
Now, has anyone tried downloading the latest official ROM from needrom? They cite one from 10/9, I tried to install after ensuring the device is properly detected and the process fails. Something about Brom incompatible.
Not sure if anyone here has had successes with flashing MediaTek based devices, any tips?
djvinniev77 said:
I just got mine, love it for the price but unfortunately didn't read about android pay. I just tried and yep, no good to add payment cards. If you have a banking app that accepts card integration, it works that way, so it's just android pay/Google security.
Now, has anyone tried downloading the latest official ROM from needrom? They cite one from 10/9, I tried to install after ensuring the device is properly detected and the process fails. Something about Brom incompatible.
Not sure if anyone here has had successes with flashing MediaTek based devices, any tips?
Click to expand...
Click to collapse
Well, I was using a ulefone power 2 before this one. SP Flash tool version >5 works great. You just need to make sure device is fully powered off and connect usb cable. It might get into a bootloop, but if you start the flashing process while it's off it will get off of the bootloop and flash it. Hopefully at least.
I am using TSB, Santander, and nationwide. I guess none of them has card integration?
I'm searching a custom-Rom (lineageOS) for Armor 2. This Link ( rootmygalaxy[dot]net/lineage-os-15-for-ulefone-armor-2/) says "download it", but I can't found the Rom.
If I would self-compile it. Where I can find the driver for Armor 2?
With regards to android pay, I emailed ulefone support and they noted that they are working on it, need to get the keys to fix. They asked for device IMEI and will try to make the update via OTA. You can email them from their website. Looking at 3 weeks but I'm not counting on it. At least someone replied right away.
djvinniev77 said:
I just got mine, love it for the price but unfortunately didn't read about android pay. I just tried and yep, no good to add payment cards. If you have a banking app that accepts card integration, it works that way, so it's just android pay/Google security.
Now, has anyone tried downloading the latest official ROM from needrom? They cite one from 10/9, I tried to install after ensuring the device is properly detected and the process fails. Something about Brom incompatible.
Not sure if anyone here has had successes with flashing MediaTek based devices, any tips?
Click to expand...
Click to collapse
i installed the last room (nedroom) yesterday and was ok ok, i had a problem with connecting the usb (did not want to run the download process), helped "volume up" ON , the phone off, and then connect the usb to the pc and when I started process the "volume up" OFF , it started Mint 18.2 cinnamon 64-bit, SP_Flash_Tool_v5.1728_Linux - run as root , the MTKxxxx driver setting, for linux is here on XDA.
I would also be happy for recovery and root for armor 2.
with greetings of sumec.
sumec100 said:
i installed the last room (nedroom) yesterday and was ok ok, i had a problem with connecting the usb (did not want to run the download process), helped "volume up" ON , the phone off, and then connect the usb to the pc and when I started process the "volume up" OFF , it started Mint 18.2 cinnamon 64-bit, SP_Flash_Tool_v5.1728_Linux - run as root , the MTKxxxx driver setting, for linux is here on XDA.
I would also be happy for recovery and root for armor 2.
with greetings of sumec.
Click to expand...
Click to collapse
Nice. Did you wipe everything or was it an in place update that retained your data?
djvinniev77 said:
Nice. Did you wipe everything or was it an in place update that retained your data?
Click to expand...
Click to collapse
I deleted everything like a new phone. If you have a backup date so when you start offering a recovery from a backup or as a new phone. Every update to rom through flashtool makes full wipe data, so it's a good root and recovery.
Is there any way of disabling that wretched camera button ? I am fed up with clicking noises from my pocket as it takes shots, and deleting them all afterwards....
Gnubi said:
Wish there was a way I could disable the sos button on my doogee s60
Click to expand...
Click to collapse
I use the APP "Button Mapper" Ver: 0.54 Free
You can reconfigure PTT and SOS buttons to open your desired Apps.
You can also disable operation with the Lock-screen
My actual configuration for PTT button is:
Short press: Nothing,
Long press WhatsApp,
Double press: switch between DND, Vibrate and Outdoor sound mode
and for SOS:
Short press: Nothing,
Long press: PayPal
Double press: Shazam
wilkofife said:
Is there any way of disabling that wretched camera button ? I am fed up with clicking noises from my pocket as it takes shots, and deleting them all afterwards....
Click to expand...
Click to collapse
Camera button requires pro version, but I can live without it :good:
I noticed today that my USB-C to headphone jack cable is not working. Anyone else had that problem?
Also, ButtonMapper works great but sometimes it causes a soft reboot...
I have just purchased a Xiaomi mi 8 lite and went through the process of unlocking the bootloader but it says I have to wait 360 hours which is an absolute joke. does anyone know a website that unlocks Xiaomi smartphones as I cant wait that long. many thanks.
Hello guys, after succesfull Bootloader unlock and flashing new os i have no Sound at all, no phone call etc, fp isnt working too, any sugestions?
Just wait. Everyone had to wait.
I got rid of the phone in the end only had it a few days, hated the retarded process of having to wait to unlock the bootloader and the even more crazy process of unlocking it. Got myself a Xiaomi Mi A2 with stock Android pie 9 so much better than the overbloated Miui software.
I read somewhere else (do not recall exactly where), the reason for the long wait is they want you to get two weeks of MIUI advertising. Once the phone has been activated for at least 2 weeks, it will unlock instantly using their unlocking software, no wait required. Can anyone confirm this?
lexridge said:
I read somewhere else (do not recall exactly where), the reason for the long wait is they want you to get two weeks of MIUI advertising. Once the phone has been activated for at least 2 weeks, it will unlock instantly using their unlocking software, no wait required. Can anyone confirm this?
Click to expand...
Click to collapse
You have to enable developer options to bind the phone to your miui account to start the unlock countdown of 360 hrs (better than the 720 it was). During the wait period you must not logout of miui account (factory reset, change from stable to beta or vice versa) or you will no longer be able to use that miui account to unlock ever! You will have to create a new account and start over at 360hrs again. Once all the requirements are meet then unlock software will work without issue.
cidxtc said:
You have to enable developer options to bind the phone to your miui account to start the unlock countdown of 360 hrs (better than the 720 it was). During the wait period you must not logout of miui account (factory reset, change from stable to beta or vice versa) or you will no longer be able to use that miui account to unlock ever! You will have to create a new account and start over at 360hrs again. Once all the requirements are meet then unlock software will work without issue.
Click to expand...
Click to collapse
I have been trying to make it happen, but it keeps telling me that my account is not associated with my phone number, which it is.
Developer options have been enabled since within 10 minutes of owning this phone. However something I missed, you have to link your account within Developer options by entering the "Mi Unlock Status" item and clicking "Add Account and Device". Anyway, I did this but still no love. Still says there is no phone number associated with my account. Grrrrr. Any ideas anyone? I really love this phone so far, but may still exchange it for the Pocophone. F1.
Also, on a side note. Once the bootloader is unlocked, is it possible to re-lock it?
I read on the MIUI forum that if you launch the unlock process with a chines IP address and with your email, not the phone number, with a VPN, you could unlook in less than an hour
I discovered the information too late, I'm in the 360h waiting list ...
ljvd said:
I read on the MIUI forum that if you launch the unlock process with a chines IP address and with your email, not the phone number, with a VPN, you could unlook in less than an hour
I discovered the information too late, I'm in the 360h waiting list ...
Click to expand...
Click to collapse
I read this somewhere too, using a VPN will do the trick. However when you register your phone with your account in the Dev Opts, it makes you turn off WIFI and register via 4G/LTE (probably for GPS location data). That doesn't necessarily mean it would still not unlock if the PC unlocking tool is connected to a Chinese VPN, just casts my doubts.
Anyway, I finally got it to take....after I created a new Mi account and got the phone number registered. However the message the Unlock tool gives upon successfully starting the unlock process is very uninformative. It says something like "Couldn't unlock device after 360 hours of trying". I have not even owned this phone for 360 hours!! After googling for this crazy error, I found it is "Engrish" for "Must wait 360 hours to unlock your device". JEEZE!! Go figure!!
I really can understand making one wait for a certain amount of time to unlock it, just to give the owner enough time to erase the data on a potentially stolen or lost phone. Nobody, I mean NOBODY, is going to wait 15 days before remotely erasing their phone. But then again, when the BL is unlocked, it will automatically erase all the data anyway, so perhaps my point is moot.
Hello,
since I purchased my Redmi Note 10 (which came with MIUI Global 13.0.7, Android 12) I experienced some bluetooth issues which I hadn't with my previous phone (Redmi Note 7 with Android 10).
E.g.: I'm wearing a device (Dexcom G6) which sends every 5 minutes my blood glucose value to my phone via bluetooth; if I'm away for a while, the device doesn't reconnect automatically but asks for pairing again... and until I confirm I don't get new values. This could happen several times per day.
I've read a lot of people complaining about this behaviour (that seems related to Android 12); several workaround are suggested but nothing really solved the problem. I can provide more details if needed
Btw, the connection with Miband 6 is unstable too.
These issues are quite annoying and, as I said, I didn't experience them with my previous phone, so I'm wondering if switching to a custom rom can help me on this!
Hello,
Changing ROM can help, if the problem is software and related to MIUI for example.
As a last resort, I think it doesn't cost anything to try custom ROM, it is always possible to go back to the initial MIUI, if necessary.
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
spider1163 said:
It would be interesting to list the attempts you have already made to avoid making unnecessary suggestions.
If you haven't already done so, I'm thinking in particular of disabling battery optimization for the application used with Bluetooth.
Click to expand...
Click to collapse
Thanks for your reply!
Bascially, there are several apps well known in the diabetics community that can be used to read values from the device: xDrip+, Dexcom etc.
They all worked flawlessy on my old phone but with the Redmi Note 10:
- xDrip+ disconnects for 20 minutes after each reading (it should be 5)
- Dexcom asks for BT pairing now and then, sometimes even when I'm near my phone
Of course I disabled battery optimization.
These issues have been reported by users since Android 12 and not only on Redmi phones...
I tried to follow some suggestions:
- disable BT battery optimization: this was possible on Redmi Note 7 but I can't find such option on my Redmi Note 10;
- use apps like "Blue Car Tethering" that force BT tethering with paired devices; this improves the situation but doesn't solve it (with Dexcom I get fewer BT pairing requests, and with xDrip+ I get readings every 10 minutes);
- on "developer options": change "ACRCP Bluetooth" and "MAP Bluetooth" versions, but it didn't work even trying all possible combinations.
I'm experiencing problems with my Miband 6 too, that sometimes disconnects from its app; this didn't happen on my previos phone but it could be related to some bugs with the app itself.
My feeling is that, generally speaking, BT is more unstable.
Important: there are also users claiming not having issues with Android 12 at all, so maybe they are related to some manifacturer customizations; that's why I'm wondering if using a custom rom can help.
Sorry if I was too long but I tried to give more details.