Related
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
i had a similar problem but with my car's bluetooth. i cleared up my contact listed and the problem was resolved.
here is where i found the solution: http://forum.xda-developers.com/showthread.php?t=2646592&page=2
hope you come right.
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
...
onurcandan said:
Please help, after 4.4.2 with my note 2, bluetooth headset connection quality got crappy. I cant walk away from my phone more than 1 meter. Anyone experiencing this problem????
Click to expand...
Click to collapse
I did not find a solution yet! You yeah?
Jackal107 said:
I did not find a solution yet! You yeah?
Click to expand...
Click to collapse
I have the same issue with my headset. Hope someone will find a solution soon.
I too have same problem!!
Whats wrong with samsung!!, sometime Wifi problem and sometime bluetooth.:silly::silly:
earlier I was on 4.1.2 and it was working good with my jabra clipper bluetooth headset, after updating to 4.4.2 it sucks!.
according to my observation,
The OS is trying to save battery by limiting the bluetooth signal strength!, and the same problem with wifi also.:silly:
Looking for a workaround. If i find any will post for sure.
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
Found some others having the same issue e.g. here
http://androidforums.com/samsung-ga...nge-extremely-dropped-after-4-4-2-update.html
Click to expand...
Click to collapse
Yepp, I know that threat. But on my N7100 nothing works. In the meantime I'm on Paranoid ROM with 4.4.4 and it's a little better, but not much.
Frank67 said:
I have the same issue with my Note 2 after update to 4.4.2..
It seems to be a distance problem with my headset, every distance more than 50 cm creates
sound break up´s .. In my car the phone has a fixed place, it happens too, but not this much.
Maybe it is caused by a lower power managment for BT after update ?!
Click to expand...
Click to collapse
Hi
and have the same problem with the bluetooth, the phone in my pocket, Samsung headphones on the head and lose the music signal, conclusion .... android version
Before to upgrade I had 4.3 and works very well and now I upgraded to 4.4.2 my Note 2 with Phantom_V7.0 and work awesome but has a minus....... the bluetooth signal gets lost and it's not about the power,for ex i have battery with 4200 mAh
I will continue to keep looking this problem and I will return
There is no way to get better connection. The only way is using a 4.3 ROM
Seems like the problem is solved.
Hey guys!
It seems to me I’ve found the solution!
But firstly, a few words about the problems I’ve got…
I have Samsung Galaxy Note 2 and, when I decided to replace my old Plantronics Discovery 975 with their Voyager Edge, it had installed Android 4.3.
Both events, start using the new Bluetooth devise and upgrading to KitKat (4.4.2) occurred almost simultaneously, so it was pretty difficult to recognize what was the source of the problems that I run into – hardware/firmware issues of Voyager Edge or KitKat’s quirks. The problems were the following:
- Poor Bluetooth connection that resulted in distorted sound (not always, but often) thru the headset.
- Regularly losing the ability to use various Edge’s features, such as calling back to the last number, checking the battery status, recognizing who's calling, etc.
- Note’s battery drained badly – instead of 50-60% left at the end of the day, I got 10%...
I spoke several times with Plantronics support, but they ended advising me to replace the headset. I have neither found the specific solution in the internet and it was even reported that the factory reset would hardly help. So, that was almost the dead-end. But there was one pretty weird solution that helped to some people – deleting the duplicates in the phone’s contact list. But, since I had NO duplicates, it didn’t seem to be helpful. But then, I noticed one very strange detail – during the moments when Edge worked properly it correctly pronounced the names from my phone book, even tho some of them were quite unusual for English speaking "robot". All of them, but one – my mother’s record, which was a simple “Mom”, but when she called me, the Edge’s notification was definitely not “calling from mom”…
So, I just renamed “mom” to “mother”!
Guys, can you believe that, but ALL the problems (both phone’s and headset’s) have just gone! I’ve been using it for almost a week already and it’s OK. So, you may check your contact list, whether it sounds correctly.
Well, one issue left – weird/funny bug of the Edge’s firmware – start playing music when you take it off the cradle. (2 latest firmware updates didn’t cure that…). I just long press the voice button on the Edge to pause it. Not a big deal, to be honest.
Oh, just one last note – since Voyager Edge cannot be rebooted you can do the following if/when you neither hear the music (!), nor the report that the headset is connected when you take it off the cradle. Just long press the Call button on the headset (in my case it runs Note’s S-voice) and then everything works just fine. (Checked twice.)
Hope that this will help you too.
Cheers,
Max
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
harvey186 said:
Hi Max,
nice story, but I can't belive that this entry or change of entry will make the BT signal better.
cheers
Harvey
Click to expand...
Click to collapse
Hi Harvey,
Absolutely the same reaction was mine, when I read the comment by dawolverune (see page 1 of this thread). How deleting duplicate contacts might help…
Well, if assume that I tell the truth (and I actually do! ), then the solution may be explained in 2 ways: a) logical – I’ve been hammering with all this stuff for almost a week and nothing helped until I renamed that single contact and then, it just start working and b) technical – since Voyager Edge pronounced the wrong name it means that it took it from somewhere, but definitely from the wrong place and this might require extra “efforts” from the Bluetooth receiver/transmitter, etc. This indeed may result in abnormal behavior of the devise and “eating” the battery. If re-phrase the title of S. Coppola’s movie – here we had “Lost in Bluetooth” case.
Cheers,
Max
hack fix
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
ivan_109 said:
Am guessing someone has a fix to this issue by now, if so let everyone know
if not i just tried a hack that seems to work. when facing crackling/distortion of audio on Note2 just switch on the WiFi hotspot and range seems to improve
hope it helps......plzz educate about downsides of this hack
Click to expand...
Click to collapse
cool, it seems, that this hack is working
Thx
Jackal107 said:
4.4.2 ROM bluetooth does not work well!
Phone connected to the bluetooth headset is not working well. Sometimes the connection is lost!
4.3 ROM is not such a problem.
Does anyone have a similar problem?
Can anyone help?
Click to expand...
Click to collapse
I have the Exact Problem, and no one seems to have a solution to this. Did u find any by any chance ??
Thanks
SOLUTION OF BLUETOOTH DROPPING after 4.4.2 update
Yo !
I found the solution. No one has to downgrade Note 2 (N7100) to Jelly-bean in order to fix the Bluetooth range and WiFi dropping issue.
The fault is with the latest update from Samsung itself, May be it is a tactic to make people shift to the newer phones.(who knows) !
Anyway the solution to this problem is to Flash it with Odin it a previous release of 4.4.2.
In my case which is from the INU (India) region the release of August that is 29.08.2014 is a faulty update.
So i downloaded the older one and flashed it.. then everything worked perfectly as if the phone was new
Here is how to do it:- [BACKUP YOUR PHONE WITH KIES 3]
1. Check your version from *#1234#, Compare the version with Near August version of your Region. If it is same you better change it to get a way better performance.
2. Look up the earlier ROM version released from samsung-updated .com , http://samsung-updates.com/device/?id=GT-N7100&details=Galaxy_Note_2__International , I personally flashed it with the first version of Kit-Kat that came for note 2 in INU region. on the 8th April (08.04.2014).
3. Download ODIN http://www.mediafire.com/download/mbvtjub21ehsxrl/Note+2+Odin.zip
4. Install Samsung USB drivers http://www.mediafire.com/download/9qaqkld45387lzi/Skyrocket_GSII_ADB_Drivers.zip
[IF THE LINKS DON'T WORK then GOOGLE THEM AND INSTALL]
5. Power off your Samsung Note 2.
6. Hold Volume Down, Power, and Home Buttons at the same time. You will enter the ODIN DOWNLOAD MODE on your phone.
7. Press Volume up to Continue. It will Show "Downloading" "do not power off"
8. Connect your device to the PC where you have put ODIN and the md5 file (Firmware you want to flash with)
9. It will show connected to your device name on the top left of ODIN which means that it recognizes your device.
Click on PDA and select the firmware that u downloaded to flash Note 2 with.
It will lag for a few seconds but let it take its time.
When it is done. [Refer Image attached]
10. Press Start [It will take around 5 minutes, 3 minutes give or take]
11. It will Automatically Reboot your phone. Do not disconnect the USB cable.
After the boot is Complete ODIN will show a PASS on the left Side. Which means that the Flashing Process has been a Success.
If it shows fail then Repeat the process from STEP 6 all the way till STEP 11.
{ RECOVERY STEPS:- this will wipe all your data}
[Also, If device is Stuck at setup connection or on any other process, then disconnect your Note 2 from PC, close Odin, remove phone’s battery and put it back inside AFTER 5 seconds, press Volume up, Home key and Power key at the same time, When the Logo comes then Leave the Power button but keep pressing the other 2. Wait for it to show MANUAL MODE. Select Wide Data and Factory reset with Volume down and press power to continue, Then again wipe Cache.
Select Reboot . Now it should work perfectly.
CAUTION :- DO THIS AT UR OWN RISK.
Is this problem appears in official update? Want to update, but dont want any probs)
Yes the problem is with the official update. Better not update it till there is another update of it available.
I'm thinking this might have to do with Samsung dropping the Bluetooth version from 4.0 back to 2.0. I have no idea why they would do that but I've been wondering why my phone listed version 2.0 when the specs for this phone always said version 4.0. As you can see my debug screen shows it as version 2 and not 4.0. My Edge shows 4.0 on that same screen. I can't recall if older builds for the Note 2 had 4.0 listed but I believe they did and kitkat lowered it. Guess that's their trick to get people to upgrade, break things on our phones quietly...
Sent from my SM-N915P using XDA Free mobile app
I am running the AOSP sSmooth rom, and everything was working fine for a couple of weeks until recently when the mic stopped working.
I can receive and make calls, but no one can hear me on the other end. I can hear them though.
I was wondering how to access the diagnostic pages to check the phone. I tapped on the android version repeatedly but it just takes me to a lollipop screen that changes color the more I tap it.
Also if I reflash the rom, will I lose all my other settings? I was just going to flash the rom file again and hopefully it fixes what ever file is corrupted. I was hoping to keep all my other apps and info as is. I have a feeling it might be related to the "Wakie" app. I tried it out , it sucked and uninstalled it. The problem showed up after that.
To enter the menu download from Play Store Mediatek engineering mode
Some days ago in my Note2 the main mic switched with the noise reduction mic, so to talk I had to speak near the Noise reduction mic. After a reboot it was OK...
hi! recently found, yes found freebuds , someone lost them. so unable to give them back, i decided to nurture them myself?
I myself have a samsung galaxy s9+, and have connected them to it.
I have a few issues with it even though I have updated them to the latest firmware.
my issues include:
the freebuds just disconnect every now and then, they get out of sync with one another, get interrupted when in a busy street full of cars and on top of all that, there is a massive, 1.5 second lag between the video and audio when I try to watch videos.
I earlier saw earlier people tried to switch the codec either from AAC to SBC vice versa.
though myself, I don't know what any of that means, but if it helps.... ??
does anyone have any information or tips and tricks on this?
You might have a bad batch. TL;DR version, Russian users on 4pda mentioned that with earlier batches there were problems and they got a replacement which fixed the issues such as drop outs.
Since you're not the purchasing owner but a finders keepers type of owner, you're SOL.
Hi, I'm having issues too. Were working fine but suddenly only the right one is working. I tried to pair them many times, restore the freebuds... but apparently only one is pairing my pixel 2 XL.
germao said:
Hi, I'm having issues too. Were working fine but suddenly only the right one is working. I tried to pair them many times, restore the freebuds... but apparently only one is pairing my pixel 2 XL.
Click to expand...
Click to collapse
did you solved it?
same problem here but with Galaxy s9 plus
Nope, my freedbuds are now in a drawer
polotdi said:
did you solved it?
same problem here but with Galaxy s9 plus
Click to expand...
Click to collapse
Enviado desde mi Pixel 2 XL mediante Tapatalk
Freebuds not connecting
After depleting the battery. My freebuds no longer connect by Bluetooth, instead it gives 3 different devices (box, left and right bud). I have no idea how to solve this
Reset Procedure for not pairing left or right side
Hello Friends,
If you have a huawei FreeBuds and some issues to pairing or connecting Bluetooth, then sure you are not the first one!
You can try the follow steps:
1. Put the left or right one in the case and follow the factory reset.
2 after you reset one of the pair you take out the reset one, put back the other one, and follow again the reset factory.
When you done with the second one. You take him out.
3. Close the empty case. Close your Bluetooth on your devices.
4. Open the case, put them (pair) back in the case, close case
5. Open case and follow the factory procedure.
6. Close case and start a New pairing with your phone and the free buds, but remember delete first our free buds in your phone before you pairing again your buds!
After you successfully connected, you can try a software update. Download the freebud app in google.
The old firmware is 16x, the new firmware is 19x.
The best way to update the firmware is without you have pared the freebuds in your Bluetooth list.
So delete first your pairing. Or use a other android phone.
When you follow the update, he ask to open the case and the green light go on. Press directly on update on the app. Because there is a short time the app can search the buds.
Hold your phone and buds case together. Less then 5cm.
I updated them with a Xiaomi A2 Android 8.1.0 device with the freebud app from google App Store.
Have many luck because the firmware update can stopped many times, if that happens do a factory reset with the buds inside the case. And retry a firmware update.
Don’t pairing the buds!
Good luck!
left bud issue
From the last update , initially my left bud didn't work at all, after some reset and re-pair it works but at a very low volume. In contrast the right bud works perfectly. I don't totally know how to fix this annoying problem. I tried in 100 ways also re-pairing the buds one at times but nothing works.
Someone who can help me?
I have a problem, partizlly solved.
Maybe It can help some of you.
My problem is that the noise quality is horrible.
I update, and nothing to do. It's like an old headphone, horrible !
I discover that when I go on bluetooth parameters, and parameters of the freebuds, when I take off "phone calls'' ("appels telephoniques'' in french menu), the quality instantly switch to an HD sound perfect !
The problem is that I can only use It for multimedia, and can't make a call !
If it can helps some of you !?
But is there someone who can solve entirely my problem ?
Use a Oneplus 5t.
xstu25 said:
I have a problem, partizlly solved.
Maybe It can help some of you.
My problem is that the noise quality is horrible.
I update, and nothing to do. It's like an old headphone, horrible !
I discover that when I go on bluetooth parameters, and parameters of the freebuds, when I take off "phone calls'' ("appels telephoniques'' in french menu), the quality instantly switch to an HD sound perfect !
Use a Oneplus 5t.
Click to expand...
Click to collapse
check which codec (AAC or SBC) used now. I switched off the calls, but this doesn't makes any changes, codec still SBC
It didn't work.
deefit said:
Hello Friends,
If you have a huawei FreeBuds and some issues to pairing or connecting Bluetooth, then sure you are not the first one!
You can try the follow steps:
1. Put the left or right one in the case and follow the factory reset.
2 after you reset one of the pair you take out the reset one, put back the other one, and follow again the reset factory.
When you done with the second one. You take him out.
3. Close the empty case. Close your Bluetooth on your devices.
4. Open the case, put them (pair) back in the case, close case
5. Open case and follow the factory procedure.
6. Close case and start a New pairing with your phone and the free buds, but remember delete first our free buds in your phone before you pairing again your buds!
After you successfully connected, you can try a software update. Download the freebud app in google.
The old firmware is 16x, the new firmware is 19x.
The best way to update the firmware is without you have pared the freebuds in your Bluetooth list.
So delete first your pairing. Or use a other android phone.
When you follow the update, he ask to open the case and the green light go on. Press directly on update on the app. Because there is a short time the app can search the buds.
Hold your phone and buds case together. Less then 5cm.
I updated them with a Xiaomi A2 Android 8.1.0 device with the freebud app from google App Store.
Have many luck because the firmware update can stopped many times, if that happens do a factory reset with the buds inside the case. And retry a firmware update.
Don’t pairing the buds!
Good luck!
Click to expand...
Click to collapse
Soud glitch
I ve got something like scratches or sand sound from the left Budd. I'm using One plus6
Also I cannot change the Bluetooth codec because it's always changes to the SBS
I ve just installed the latest update and it didnt make sense
i have a huawei FreeBuds and some issues to pairing or connecting Bluetooth.i tried all the above instruction still not connecting.
I have problem with my freebuds.the left buds only last 25 minutes while right is more or less 3 hours. what should I do with the left?
Just wondering if other people who own the Freebuds 3 have the same issue I have with the ANC.
So when you turn it on it does its thing, and then after a minute or so it suddenly sounds different. Like the ANC resets itself and then starts using other parameters to decide what sounds it will cancel. And it keeps doing that every couple of minutes. When it does I hear a small "plopping" noise (a bit the same as when you turn ANC on).
Just to be clear: the source of the sound I'm listening to (video, music, ...) doesn't change at all. It's purely the ANC that does something different.
And yes I'm on the latest software update and I use a Huawei Mate 20 X.
i had the same problem as you as well. i managed to do it by few steps i tried below and it work both on my pc and my huawei P20
1. Ensure the box is fully charged
2. remove the right hand side on the freebuds from the box
3.press the back button for more than 3 seconds and the blue light blinking
4.turn on your bluetooth and search
5 the blinking blue light will be faster than previous meaning other device (PC or P20) detected the freebuds
6. connect it up until successful
7.do not close the lid of the charging case.
8.insert the right hand side into the box freebuds
9.press the back button for more than 3 seconds and the blue light blinking
10. the blinking blue light will be faster than previous meaning other device (PC or P20) detected the freebuds
11 . connect it until successful
12. remove the previous freebuds from your bluetooth list
13. download freebuds assistant
14. update.
i just Performed these all steps like 10 mins ago and it works twice. hope it helps.
REPLY
deefit said:
Reset Procedure for not pairing left or right side
Hello Friends,
If you have a huawei FreeBuds and some issues to pairing or connecting Bluetooth, then sure you are not the first one!
You can try the follow steps:
1. Put the left or right one in the case and follow the factory reset.
2 after you reset one of the pair you take out the reset one, put back the other one, and follow again the reset factory.
When you done with the second one. You take him out.
3. Close the empty case. Close your Bluetooth on your devices.
4. Open the case, put them (pair) back in the case, close case
5. Open case and follow the factory procedure.
6. Close case and start a New pairing with your phone and the free buds, but remember delete first our free buds in your phone before you pairing again your buds!
After you successfully connected, you can try a software update. Download the freebud app in google.
The old firmware is 16x, the new firmware is 19x.
The best way to update the firmware is without you have pared the freebuds in your Bluetooth list.
So delete first your pairing. Or use a other android phone.
When you follow the update, he ask to open the case and the green light go on. Press directly on update on the app. Because there is a short time the app can search the buds.
Hold your phone and buds case together. Less then 5cm.
I updated them with a Xiaomi A2 Android 8.1.0 device with the freebud app from google App Store.
Have many luck because the firmware update can stopped many times, if that happens do a factory reset with the buds inside the case. And retry a firmware update.
Don’t pairing the buds!
Good luck!
Click to expand...
Click to collapse
Hi i know this is an old tread, but followed your steps, the left one has been successful factory reset, but when i do the same for the right one it doesnt work, any solution please ?
Hello,
I got this phone since my former one died without notice (coming from a 5 year old oneplus one), it's my god daughter's previous one.
Working good smooth and all on stock rom (seems to be carrier customed, bundled with carrier apps) : Sony XPeria X F5121 / android 8.0, build 34.4.A.2.118 Sept 1 2018 / kernel 3.10.84 Aug 24 2018
I have a slight problem : whenever I'm calling, I have to put the "hands free" mode with speakers otherwise nobody can hear me. I don't think the microphone is broken and I am thinking of a "bug" in the rom.
Before re-installing my apps, i could call and people could hear me. The phone app is the stock one.
If I speak right in front of the microphone, but like shouting, people can hear me but at very low level.
Searched a bit on the internet, but didn't find anything about this, some people say it is because other apps are conflicting, I tried to remove every app I can think of using the microphone (whatsapp, line, etc), but didn't changed a thing, tried to tune the "noise reduction" in google voice search, but didn't worked either.
If I try to audio call with whatsapp, facebook messenger lite or line, people can't hear me. Using google voice search works without flaws.
Before going for a reset factory or flashing the phone with custom rom, is there anything else I can try to solve the problem ?
problem still not fixed : looking for a replacement microphone. Anyone know how to replace the part ? If defective and I dreamt that it was working with factory reset, I will replace it.
Found this piece, but don't know where it can fit ? Do I have to solder it on the mainboard ???
Ok update :
1- the microphone part sold in the link is not correct, I don't think it fits.
2- I teared up the phone, to find some little "pearl" blocking the microphone ... after removing the pearl, microphone works flawlessly.
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
its nokia that pushed the update they did not make the rom right
Same here I told nokia about it and they told me to wait for a bug fix. I told them I wanted to downgrade since your firmware bug broke my phone.
Just wait for a bug fix? So use a Phone that cant make calls right?
So payed a guy to unlock my boot loader to try to flash a rom so i can just make the phone usable.
I spend about 6 hours try to get the rom to work. With little to no luck I was able to get into twrp a few times.
So ya Im in the same boat. I just got this phone back 3 weeks ago from a rma due to a bad chargeing port. Now Im forced to pay some one to unlock the boot loader and try to get a custom rom Just to be able to call
If I cant get the rom working Im going to have to go spend like $200 on a new phone today just sucks
fisterkev said:
Got the update last night. Tried to check voicemail morning and was greeted with Alvin & The Chipmunks blabbing at me. It's like the speed of the call is x20 speed or something. It's completely unusable. Phone sluggish as hell, too.
Anyone know what's going on with the voice speed? I've never heard of anything like this.
I'm supposed to get a callback for a job interview I had yesterday. Pretty crappy timing. How is Google going to push an update that breaks calls like this? Absurd.
Click to expand...
Click to collapse
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
gumbyx84 said:
Have you guys modified the phone in any way like unlocking the bootloader or rooting?
Click to expand...
Click to collapse
I haven't. Just using whatever over the air OS Nokia pushes to the phone.
yes I did pay to unlock the boot loader I used linage from the rom section
it has all the bugs of the stock rom. Cant call out or with out the loud noise bug and no voip apps work
I did get the Android 9 based rom to work. it has a few bugs but its usable.
I more or less gave up im looking at a iphone now.
I spend 20 hours or more trying to get this phone to work
first the usb port goes out and I cant charge.
2 weeks after having the phone back I got a magnetic cable so the usb port would not brake any more cable. That was like $20
After 2 weeks android 10 more or less bricks the phone (a phone that cant make calls)
Then I have to spend like $15 to pay the poor guy to unlock my boot-loader (he did a great job)
I spend a lot more time loading the linage android 10 rom for it to have the same bugs ( in no way is it the devs fault im sure he did not know).
... can unlock your bootloader for a small fee.
I would say all android 10 based rom will have those kind of problems. I can only confirm it on the android 10 linage one
When I flash twrp most of the time the twrp would just freeze if booting form the phone.
I had no problem loading it with fastboot works evey time. So I would only use it install the rom and just boot it when you need it. I would not suggesting flashing it to recovery as it only worked some of the time for me.
Hope all that info helps
QUOTE=gumbyx84;81261583]Have you guys modified the phone in any way like unlocking the bootloader or rooting?[/QUOTE]
---------- Post added at 06:48 PM ---------- Previous post was at 06:44 PM ----------
The calling problem goes in and out. Some times it works some times it dose not. Facebook message outgoing calls the mic will not work, Same with google voice.
if i make calls with out google voice it works 1/2 the time. all the people have the same problem
https://community.phones.nokia.com/discussion/54374/android-10-after-update-on-nokia-7-1
diggeryo said:
Same thing happened to me with the sped up chipmunk-y sound. It happened during the dial and after someone picks up. Though it didn't seem to happen every time. Also, I didn't notice it on any incoming calls, just outgoing.
I tried a few things to fix it--rebooting, clearing some app caches, etc. Nothing seemed to work.
My next step was to try a factory reset, but then all of a sudden the issue disappeared. No new update was released/installed, so I just assumed the issue had been on my provider's end (T-Mobile), and they fixed whatever the problem was.
As for sluggishness of the phone after the update: I agree. It seems a little sluggish to me too. Not anything that is making the phone unusable. But it is noticeably more sluggish than when 9.0 was installed.
Click to expand...
Click to collapse
How to fix the phone call problems
To everyone having calling issues (distortion / squealing, or other people can't hear them), try this: Turn off Voice over LTE. You go to Settings -> Wireless and Networks -> Mobile Networks -> VoLTE, and turn that setting off. This fixed the problem for all 3 Nokia 7.1 phones in our family, when nothing else seemed to work.
Turning off VoLTE and wifi calling works, but VoLTE is important in my area with TMobile. Without it, too many dropped and missed calls. I actually downgraded from an Xperia XZ1 just to get VoLTE, now this happens.
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
In addition to disabling VoLTE, I also changed the 'preferred network type' (see posting from author 'fiumaxx' on nokia's user forum, search there using android-10-after-update-on-nokia-7-1 as search string). I changed it to LTE/CDMA which works well for me.
Normal call sound is back to normal but 3rd party calling still not working.
Click to expand...
Click to collapse
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Thank you so much for sharing! Works like a charm
Unfortunately denying microphone for the Google app did not work for me. I also noticed no one can hear me when making videos calls (Hangouts, Duo, Facebook messenger).
I then decided to factory reset, but did not help. Both VoLTE and video calling still not working.
Anyone else with video calling mic issues?
zhou68000 said:
I have TA-1085 running Android 10 that was pushed OTA on 12/25, while I do not have calling issues (from native call app) initially, calling from all 3rd party app (e.g. Messenger or Wechat) are not working: I can hear other side, while the other side can not hear me.
Click to expand...
Click to collapse
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
ikijibiki said:
This worked for me:
Go to Settings/Apps and Notifications and then tap on where it says See All xx Apps. Scroll down until you see the Google app and tap on that. On the next screen you see, tap on Permissions and then tap on Microphone. A small window will pop up, and you must change the setting from Allow to Deny.
After changing this setting, Google Assistant won't work (no Hey Google), but the fix is persistent after reboots. This makes me think the real problem may be with the Google app. We'll see.
Click to expand...
Click to collapse
Confirm this recipe works for my TA-1085. Thanks much.
I solved my random voice problems (others can't hear me on Duo video call, duplex voice on the other side etc.) with the voice match assistant workaround until hopefully gets fixed in a next update. Don't know for sure if the thing is only on Nokia's side or Google app's as well on Android 10, since disabling Hey Google solves all issues
Will have to try/catch on future google app updates as well to find out
Sly_North said:
I had the same symptom on normal phone call (other side could not hear me). In my case, it was the Google Assistant not releasing the microphone, and here what worked: open the system settings, go to Google (service&preferences)/Account services/Search, Assistant&Voice/Voice/Voice Match. Them make sure Access With Voice Match is ticked off.
Or try opening settings, searching at the top for "Voice" and open "Voice Match", and tick off "Access with Voice Match".
Click to expand...
Click to collapse
Under "Voice Match" I don't see any "Access With Voice Match" setting. What I do see is "Hey Google," which says "Access your Assistant any time you say "Hey Google" when your screen is on." Perhaps this is what your mean?
I tried this solution and it works, too. I think it also has the advantage of not completely shutting down Assistant's access to the microphone. Just waking up Assistant by voice. Much less of a price. Thanks!
Has anyone heard anything about a real fix for this issue? I've gotten two Android updates since the upgrade to Android 10, but this issue has not been fixed yet.
After extensive talks and inside info on Nokia's community forums, seems like a Maintenance update (MR) is on the way for May, which they say fixes -among others- both voice bugs. That is, the echo on calls plus sound distortion in some games (e..g Monument Valley 2 for me)
Cross your fingers everyone for a quick release and confirmation of the fixes!
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
dbal said:
Today was the day at last....! MR update showed up rolling out globally and echo during calls plus crackling sounds in games are finally gone
Better late than never NOKIA
Click to expand...
Click to collapse
Yes, they seem to have fixed the voice call problems with Whatapp, Wechat, Hangouts and etc since the Android 10 update.