Hi,
I just bought True Wireless Earbuds (Audio-Technica ATH-CK3TW) to use with my Nokia 7+, but I just can't use them with it.
When I pair them the settings says they're connected (but not the way it should be, see screenshots) and then go to "Saved Earbuds".
When I say not the way it should be, it should show current battery state and have a toggle button to enable AptX codec (See screenshot took from Xiaomi Mi A2)
I tried to connect the earbuds with other devices, Computer, Laptop, other Android/Apple phone, that have or not Bluetooth 5/BLE and AptX Codecs, It works for all of theses.
I contacted Nokia support who tried multiple fixes but none of these worked, I even did a factory reset, it does not work.
This problem ever appeared before ? Someone can help me with it ?
Thanks in advance !
What does the reseller of both devices suggest?
Nokia just said to wait for an Android Update to see if it fixes the problem.
Audio-Technica didn't see any of this the past, so they didn't have any clue of what to, except reset the earbuds.
It would be great if I had the opportunity to try with another couple of 7+/Earbuds but both aren't really popular so it might be difficult...
I use sony neck bands with no problems.
I also use Bluetooth earbuds actually, Xiaomi Redmi Airdots, "cheapest TrueWireless" but I just wanted to change for a better sound.
So yes, I know that most Bluetooth devices works with the phone.
I have the same problem with Sabbath E12 Ultra
Its says Saved earbuds but not connected
I got it working I switch my system partition to oct 2019 patch, using fastboot
fastboot getvar current-slot
determine the slot then
fastboot --set-active=a/b
This may factory reset you're phone so do backup
Oh cool for you !
How did you find this solution ?
And how you can do this without bricking it ?
Hawiie13 said:
I got it working I switch my system partition to oct 2019 patch, using fastboot
fastboot getvar current-slot
determine the slot then
fastboot --set-active=a/b
This may factory reset you're phone so do backup
Click to expand...
Click to collapse
btw: switching to other slot NOT go to oct2019patch, but always go to previous installed patch
Can you be more explicit ? I didn't understand what you mean by switching to other slot.
k3dar7 said:
btw: switching to other slot NOT go to oct2019patch, but always go to previous installed patch
Click to expand...
Click to collapse
Assuming you are in the latest security patch its november 2019 as of now no december 2019 security patch maybe preparing year-end android q update
I just tested that the november 2019 patch is the update that this bt problem with my sabbat e12 ultra
So if i change slot its previous update is otcober 2019 patch
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
FirmYn said:
Oh cool for you !
How did you find this solution ?
And how you can do this without bricking it ?
Click to expand...
Click to collapse
Hi you may check other workarounds here tbis may help https://forum.xda-developers.com/nokia-7-plus/help/nokia-7-plus-ver-9-0-bluetooth-problem-t3898964
Hawiie13 said:
Assuming you are in the latest security patch its november 2019
Click to expand...
Click to collapse
yes, but i only clarify what is A/B slot (for others and future)... is always current and second and on every OTA update is switched...
example: if now i have installed nov2019 and have current=a then NOW in second=b is previous (actually oct2019patch), but after upgrade to december2019 is changed slot, current=b and second=a, in second keep previous system with november2019, is like dualboot with always actual and previous system(ota patch) version
k3dar7 said:
yes, but i only clarify what is A/B slot (for others and future)... is always current and second and on every OTA update is switched...
example: if now i have installed nov2019 and have current=a then NOW in second=b is previous (actually oct2019patch), but after upgrade to december2019 is changed slot, current=b and second=a, in second keep previous system with november2019, is like dualboot with always actual and previous system(ota patch) version
Click to expand...
Click to collapse
thanks for clarification,
Thats why its the time to go back to oct patch since nov is the latest as my workaround for this bt issue
if dec patch is out we hope this issue is fixed
i think its best to wait for Januray Android Q update , hopefully they will fix it , but if not , do we lose the October slot ?
GOOD NEWS EVERYONE , i got the android 10 update and headphones are working Perfectly now
Same for me ! So I bought them again
Related
Hey, all; Apologies, if this has been posted before, but I cannot seem to find this partilular issue. I had purchased my new T813, off a retailer on ebay, they indicated it was a store return, and had the google frp lock. I managed to easily bypass the frp in a Tab E, so I figured (quite incorrectly) that this would also be a no brainer... not so!
I have tried flashing several firmwares, (got one from Russia that seemed to work okay, but still had google frp. I put the earliest firmware I could find on it; "T813XXU1APD7_T813XAR1APD8_HOME.tar.md5" It failed, and I was stuck on download mode, and would only reset, using the Vol down/home/pwr buttons, only to reboot to a green screen, stating; "firmware update failed" (on the tablet, and the red failure in Odin). I could not get the flash to work, 4 times, and was worried about the tablet running out of battery, so I flashed (not knowing what the hell I was doing (how many readily admit that?) I flashed a 20mb file called; "BL_T813XXU2APK6_CL9829844_QB11715585_REV00_user_low_ship_MULTI_CERT.tar.md5" and the tablet was able to boot, past the Samsung flashscreen, but loaded up to a black screen stating; "enter password... to power on, or something like that" Does anyone know what the password is? I can't remember where I got this, there's so much scattered around the web, I was just reaching for anything... any help would be greatly appreciated.
Sounds like a stolen Tab, I'd say. ?
Niii4 said:
Sounds like a stolen Tab, I'd say.
Click to expand...
Click to collapse
That's what I'd say also. Return to seller.
In order to bypass FRP, you have to downgrade the firmware to the lowest possible build as it doesn't have any patch to fix security holes.
Like mine, SM-P580, I had to flash Hong Kong firmware to bypass FRP as it's older build than US version. As long as you can downgrade firmware, bypass FRP is easy. I have done it within 3 minutes.
Power + Volume Down will force your tablet to restart. When you can get to Download Mode, try to flash a new an older firmware again, regardless region . If you can downgrade firmware, your chance is 100%. A build that forces you to have internet connection in order to continue until it get Google account verification is a build that need to downgrade. Older build allows to continue setup after Software Update check failure due to disconnected internet. The latest builds will lock attempt to downgrade so don't flash any new builds . I experiment with the latest build of Android 6 and Android 7, they do the same thing: check software revision and lock downgrade if a lower one is detected. I can downgrade Android 7 to Android 6 as long as that build has security patches which lock FRP bypass.
This users did it by downgrade from T813XXU2APK6 to T813XXU1APF4
https://forum.xda-developers.com/showpost.php?p=72159888&postcount=25
The last 3 characters of a build is the date of release
PF4
P=16 or 2016
F= 6 or June
PF4 means version 4, released on June 2016
---------- Post added at 08:20 PM ---------- Previous post was at 07:59 PM ----------
Niii4 said:
Sounds like a stolen Tab, I'd say.
Click to expand...
Click to collapse
Not necessary to be stolen. I bought mine without password or PIN, but forgot to remove the owner's Google account when flashing new firmware.
It activated FRP but I was able to bypass it to use the tablet.
First thing to do when buying second hand: factory data reset.
Everything else is stolen goods.
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk
Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes
Stransky said:
Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Am on 8.1 global variant. How are you still on Feb?
Scarkinyua said:
Am on 8.1 global variant. How are you still on Feb?
Click to expand...
Click to collapse
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk
AchinPakhi said:
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes
Click to expand...
Click to collapse
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"
They've also removed the functionality in which you can navigate using the fingerprint sensor ?
After the may 2018 update I noticed some 4G connectivity issues: no more internet. By moments, the phone would switch to 3G and then internet would work.
I thought I did something bad, so I reset APNs, etc. no luck. I even completely wiped the phone, but that did not change anything.
Then I saw this thread on Nokia forum:
https://community.phones.nokia.com/support/discussions/topics/7000025066
For now, by forcing 3G, I can get internet all the time, but I hope this fix will be temporary.
Scarkinyua said:
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"
Click to expand...
Click to collapse
ah sorry for a super late reply.. if u have already set up trusted face then it's already been activated.. just lock the screen and turn on using the power button.. there will be a small face icon at the bottom middle of the screen .. when it recognized ur face it will show a unlocked lock(open lock) icon.. then just swipe up the screen...
TA-1062
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one
Stransky said:
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Much easier with the roll back firmware and sideload using ADB or straight from recovery.
Done the ADB and got 8.1 April version (no wipe and everything seem to work fine).
After that got OTA update to May security patch.
More here: https://forum.xda-developers.com/showpost.php?p=76546067&postcount=56
It may be working without enrollment to developer preview. Someone uploaded the zip.
Alfaroerik87 said:
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one
Click to expand...
Click to collapse
I'm also stuck on 8.0 1062.
Flameboy42 said:
I'm also stuck on 8.0 1062.
Click to expand...
Click to collapse
I'm on 8.1 :/
Alfaroerik87 said:
I'm on 8.1 :/
Click to expand...
Click to collapse
What's your location?
I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?
tkiafar said:
I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?
Click to expand...
Click to collapse
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
Flameboy42 said:
What's your location?
Click to expand...
Click to collapse
I'm from Chile
Alfaroerik87 said:
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
I'm from Chile
Click to expand...
Click to collapse
Main directory is the same directory you open first when you connect your device for file transfer, that contains "alarms , android, data" directories. I put the file there without renaming it, and dialed the code. There are posts on the same thread that cover file not found issue, check them out. In any case if it doesn't find the file the only option is ADB sideload.
Face unlock was added
Face unlock was added and security patch updated to may
Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse
I bought MIA2 in January, global version and update it to pie without problems and then, aI installed the January security update, then I had a bootloop problem, and since it was untouched the only option was warranty or test point. Since I didn't want to lose some pictures, I opened my brand new device, :crying: did the test point, and put the V10.0.2 rom with MiFlash. It worked but I couldn't recover mi pictures.
Now, phone is offering me to install the February security update, and I'm scared to have the same issue again. I have USB debbuging activated and also the option for the OEM unlock activated. But haven't touched anything else.
Should I try to install this update?
Are these options enough to recover the phone if I have a problem or should I do test point again in case of bootloop?
Thanks for your answers!!
marioandresl said:
I have USB debbuging activated and also the option for the OEM unlock activated. But haven't touched anything else.
Should I try to install this update?
Are these options enough to recover the phone if I have a problem or should I do test point again in case of bootloop?
Thanks for your answers!!
Click to expand...
Click to collapse
I have updated with the latest February patch without any issues. My bootloader is also unlocked.
bidhu said:
I have updated with the latest February patch without any issues. My bootloader is also unlocked.
Click to expand...
Click to collapse
Ok guys I just Updated to V10.0.4 Or February update without problems. Thanks!!
Hi dears
Usb preferences grayed out and I can not connect my phone to pc! pc doesn't recognize the phone at all!
i tried to check through fastboot but still the same also i tested 2 cables and 2 PCs still the same...
in addition, the contacts names doesn't appear when the phone call and in the recent calls, as well.
Please help me. ((((
is there any way to roll back the phone to the before update state (i mean I want to undo the update)?
same here
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
But I was able to unlock bootloader
---------- Post added at 12:15 PM ---------- Previous post was at 12:13 PM ----------
But then got unrecognised usb device error some error 43 in windows did u get the same?
hv2002 said:
same here
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
But I was able to unlock bootloader
---------- Post added at 12:15 PM ---------- Previous post was at 12:13 PM ----------
But then got unrecognised usb device error some error 43 in windows did u get the same?
Click to expand...
Click to collapse
thanks for your response...
I don't know how to unlock the bootloader! can you help me to doing that? what is the reason or goal of doing that?
hamed_isu said:
thanks for your response...
I don't know how to unlock the bootloader! can you help me to doing that? what is the reason or goal of doing that?
Click to expand...
Click to collapse
As of now we cannot unlock bootloader coz the update just messed with our device my laptop shows this device has malfunctiond failed to recognise...but it charges fine
If you unlock the bootloader you can install custom rom and do a bunch of cool tweeks in your phone totally worth it
hv2002 said:
As of now we cannot unlock bootloader coz the update just messed with our device my laptop shows this device has malfunctiond failed to recognise...but it charges fine
If you unlock the bootloader you can install custom rom and do a bunch of cool tweeks in your phone totally worth it
Click to expand...
Click to collapse
ok, thnx... but I didn't have good experience with installing custom rom on my previous phones... there are always some bugs in the custom roms ... aren't there?
what should we do now, except waiting for new update?!!
This issue is not hugely addressed in the forum's they might not fix it in the next update (maybe)
There is nothing much we can do
the best part is that the phone charges! xd
Same here since May update, still waiting for a fix.
I experienced the same issu since April
Now i failled to update twrp then my phone is bricked
Never othere Xiaomi Phone
Grayed only if not connected to PC. Connected to PC all working fine.
I had everything grayed out when I was using any other usb C cable than xiaomi
anryl said:
Grayed only if not connected to PC. Connected to PC all working fine.
Click to expand...
Click to collapse
Which security patch r u on?
hv2002 said:
Which security patch r u on?
Click to expand...
Click to collapse
5.6.2019 latest patch.
anryl said:
5.6.2019 latest patch.
Click to expand...
Click to collapse
And everything works fine adb fastboot?
Btw are u using the stock usb cable included with the device?
hv2002 said:
And everything works fine adb fastboot?
Btw are u using the stock usb cable included with the device?
Click to expand...
Click to collapse
Yes all (adb,fastboot) working fine. Original cable ok.
Any microusb cable with. SAMSUNG Adapter USB Type C do Micro USB working ok.
Android version: 9
Security patch level: June 5, 2019
Model: Mi A2
Model Name: M1804D2SG
Build number: PKQ1.180904.001.V10.0.10.0.PDIMIXM
Baseband version: MPSS.AT.3.1-00777-SDM660_GEN_PACK-1.198333.2.200425.1
Kernel version: 4.4.153-perf+
#1 Tue Jun 11 18:29:16 WIB 2019
I'm guessing yours isn't (Android One) "jasmine" Global ROM? Because mine's got no such problem... Last screenshot is with the device ejected and unplugged, after having transferred these files.
EDIT:
Dumb question, but have you factory-data-reset it? "Erase all data (factory reset)" on this phone, under System, Reset options.
kgbme said:
Android version: 9
Security patch level: June 5, 2019
Model: Mi A2
Model Name: M1804D2SG
Build number: PKQ1.180904.001.V10.0.10.0.PDIMIXM
Baseband version: MPSS.AT.3.1-00777-SDM660_GEN_PACK-1.198333.2.200425.1
Kernel version: 4.4.153-perf+
#1 Tue Jun 11 18:29:16 WIB 2019
I'm guessing yours isn't (Android One) "jasmine" Global ROM? Because mine's got no such problem... Last screenshot is with the device ejected and unplugged, after having transferred these files.
EDIT:
Dumb question, but have you factory-data-reset it? "Erase all data (factory reset)" on this phone, under System, Reset options.
Click to expand...
Click to collapse
i get same issue,too with latest update build v10.0.14, usb option only show grey. before that its working normaly. anyone have solution
I'm not on stock rom but i'm using HavocOS having the same issue
mark.dx said:
I'm not on stock rom but i'm using HavocOS having the same issue
Click to expand...
Click to collapse
its strange, my MIA2 before get this issue its working normaly, but u forget its auto update on when restart. so, its auto update with latest but the result is bug in usb, now i cant do anything like flash,fastboot etc. something like in "jail". Better from Xiaomi must respond this big issue, for XIA2 with send latest ota update with clean issue
xplancer99 said:
its strange, my MIA2 before get this issue its working normaly, but u forget its auto update on when restart. so, its auto update with latest but the result is bug in usb, now i cant do anything like flash,fastboot etc. something like in "jail". Better from Xiaomi must respond this big issue, for XIA2 with send latest ota update with clean issue
Click to expand...
Click to collapse
I can flash rom but I'm afraid if I flash rom and something happen I cannot recover from it as I cant connect my phone to PC. I will waiting until we have clear solution.
mark.dx said:
I can flash rom but I'm afraid if I flash rom and something happen I cannot recover from it as I cant connect my phone to PC. I will waiting until we have clear solution.
Click to expand...
Click to collapse
u can flash with usb cable? its seem u can access usb, in my condition any access to usb cant detect. This bug actualy from the ROM. i plan roleback to build v10.0.2 or must under v10.0.13 cause in this version issue coming
November 2019 security update is now available in India. Showing 93.9mb size for 4gb_64gb model.
Yes got in Malaysia also
also in iran but 88.4mb
Got it too(15=>17) 93,9 MB. Restart without any troubles.
Here in Brazil as well, everything went fine with magisk.
Got it here too. In the Netherlands. Size was about 93.6 MB.
I think that the biggest updates size are the ones that comes from version 15 (first October patch) and the smaller comes from version 16 (the last October patch)
pfss said:
I think that the biggest updates size are the ones that comes from version 15 (first October patch) and the smaller comes from version 16 (the last October patch)
Click to expand...
Click to collapse
Yeah, I think you're right
Any news about android 10 on Mi a2?
lucky_kuk said:
Any news about android 10 on Mi a2?
Click to expand...
Click to collapse
No. Just wait
Eu não vi nada de novo neste update [emoji36]
Enviado do meu Mi A2 através do Tapatalk
Bootloop after november update
kandarpjha said:
November 2019 security update is now available in India. Showing 93.9mb size for 4gb_64gb model.
Click to expand...
Click to collapse
My friend makes the update and the device (Xiaomi mi a2) now is in bootloop.
How can he recover the data?
Sorry if I'm in the wrong thread but the bootloop is caused by the newest update (november update).
lucky_kuk said:
Any news about android 10 on Mi a2?
Click to expand...
Click to collapse
Probably December to 1st quater nxt year
Edit: though custom is in the corner if you are impatient enough. . . Just sayin.
Hi guys. I'm actually on September patch V 10.0.14.0, unlocked bootloader and rooted with magisk. How can I update my device without losing root?
No new bugs discovered. Thank god for that.
Ema9901 said:
My friend makes the update and the device (Xiaomi mi a2) now is in bootloop.
How can he recover the data?
Sorry if I'm in the wrong thread but the bootloop is caused by the newest update (november update).
Click to expand...
Click to collapse
Well bootloop as i expierienced and got it working agian.
1. ..remove simcard
2. Plug in charger. Wait till u see screen of battery power then power on ( phone will start then ).. or u do not see this screen during power on u will see bootloop. Then power off and repeat,took me 10-20 times power on/off but this worked for me 4 successful times (restarts)...sim i pushed in after the phone started and loaded android since then always charged and never turned off until the latest ota to 10.0.0.17!
So rom 10.0.0.15 creates bootloops.. now the phone updated via ota to 10.0.0.17... no bootloops expierienced any more...now i can sleep again
If u get the phone restarted u can see the rom version at about screen. U can update through ota this solved bootloop issue for me.
P.s. without battery charger connected and bootloop problems u will see phone turn off immediatly with some vibration or small buzz. In short u need to this with charger connected
Goodluck.
Updated from September to November. No issues.
Sent from my Mi A2 using Tapatalk
Chrisdclsd said:
Well bootloop as i expierienced and got it working agian.
P.s. without battery charger connected and bootloop problems u will see phone turn off immediatly with some vibration or small buzz. In short u need to this with charger connected
Goodluck.
Click to expand...
Click to collapse
What do you mean? Do i have to charge the phone while updating? Or do i have to charge the phone when the phone bootloops?
Manually installed it (by pressing myself check for updates) No new problems until now.
Yay more bugs!!