Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
shashankkp12 said:
Hi,
I have started to get this weired issue after the 8.1 update.
Whenever I receive a call, after picking up the speaker phone turns on automatically. I have to manually turn off the speakerphone, also it does not indicate that the speakerphone is turned on.
Click to expand...
Click to collapse
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
TeddyBeers said:
Solution is mostly the same for all of the problems.
Do full factory reset.
Setup Google account
Don't install any apps just yet.
Try if problem still exists
In most cases this will help.
What I've learned since my first android device, all of the custom ROMs etc, is that the updates are causing loads of problems.
Once in a while, especially after version upgrade, is worth doing full reset just after updating.
This doesn't apply not only to android, but pretty much every single device on the market.
Click to expand...
Click to collapse
Thanks for the suggestion, But by full factory reset do you mean the hard reset from the recovery menu or just the factory reset from settings menu -> factory reset..?
facing same issue please help
i am facign the same issue please help me out
Still no solution for the problem...I have made an habit to turn speaker phone on and off immediately after calling .
Try Macrodroid app to set an automatic task, to turn speaker off 1 or to seconds after receiving call.
I am also facing Same issue, can any one give suggestions
Somehow that happened to me when I just got the phone a few months ago. I think that was still on 8.0.
But tapping the speaker phone button 2 times everytime I have a call became nature for me and eventually after a few days, I no longer have that issue.
Are you still having that speaker phone issue now?
Yes...but while it was consistent on 8.0 it has become a random occurrence after 8.1 update
same issue
factory reset solution is not acceptable.
Related
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Andy.WP7 said:
Hi all,
for the last 5 or 6 days, my phone has crashed every single night. :-(
When I go to bed, I just leave it on the table, not charging, but with enough battery left to easily last for the night. The next morning, the phone is switched off and I cannot switch it back on, because the battery is completey drained.
When I charge and then turn the phone back on, it has done a "partial reset", meaning that all settings are back to factory defaults, contacts are gone, ... All accounts, apps, ... are still there, though. The worst part is that I cannot receive calls anymore either, in this case. Callers are immediately redirected to my mailbox, even though the phone has a signal and I can make outgoing calls without problems. The only way to fix this is a factory reset.
The next night, the same happens again.
Has anybody had a similar problem? Does anybody have an idea how to fix it?
Thanks and regards,
Andy
Click to expand...
Click to collapse
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
What firmware/ROM are you using?
What firmware/ROM are you using?
Click to expand...
Click to collapse
I am still using the stock Froyo ROM that the phone came with. The phone is rooted and I've installed a SpeedMod Kernel. However, both (rooting and new kernel) have happened months ago, so I doubt that they have anything to do with the problem.
(partial) solution found
Since a phone that crashes every night, using all settings in the process, is fairly useless, I decided that I might just as well trash it completely by trying (and maybe failling ) to install a custom firmware. So I downloaded Darky 10.1 and thanks to an excellent installation guide, I actually managed to install it.
Since then, my phone does no longer crash every night - it now reboots a couple of times a day The good thing is, though that after the reboot, the phone is back "in action" after maybe two minutes and it does not lose any data, setting or anything. So, it's not ideal, but much better than before ...
I was going to recommend trying a new ROM, but I found that as a workaround rather than a solution to your problem.
Did you perform a wipe or no-wipe install?
Kops said:
Did you perform a wipe or no-wipe install?
Click to expand...
Click to collapse
As I had pointed out in my first post, the crash that happens every night breaks something so that I can no longer receive calls and have to do a factory reset. Thus, the phone was basically wiped, already, before I did the installation and I then did a no-wipe install.
You are right, of course that this is more of a work around than a solution, but since I was thinking about putting on a new ROM for a while, already, anyways, it is a fairly good work around for me - and I really like Gingerbread and DarkyROM so far.
Kops said:
I'm sorry that I have no advice for you Andy, but I'm interested in hearing any solutions you may find.
Click to expand...
Click to collapse
In the end it turned out to be a hardware problem and I needed to get the phone replaced.
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
hmmm
carlosmeldano said:
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
Click to expand...
Click to collapse
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
really?
madhukarmohan said:
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
Click to expand...
Click to collapse
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
yes
carlosmeldano said:
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
Click to expand...
Click to collapse
Yeah, few r experiencing that. i hv seen complaints in sony blog and here too. I asked this question few days back. but, I didnt get reply.
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
thx
UltraWelfare said:
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
Click to expand...
Click to collapse
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
carlosmeldano said:
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
Click to expand...
Click to collapse
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
UltraWelfare said:
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
Click to expand...
Click to collapse
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
carlosmeldano said:
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
Click to expand...
Click to collapse
I hope everything goes fine
no success
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
carlosmeldano said:
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
Click to expand...
Click to collapse
Bring it to a sony service(or how's it called to your country)
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
carlosmeldano said:
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services are just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
Click to expand...
Click to collapse
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
UltraWelfare said:
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
Click to expand...
Click to collapse
yes, that's another option. the other option is to cry off from purchase (I can do it within a week), they return the money, and I buy another one. I'll see as this is not that disturbing problem and I have no other problems with the phone like wifi bug or anything else.
someone said it's a bug so I hope 4.3 next month will solve it.
I'm hoping someone has experienced the same situation as I.
For some reason after making a phone call I get stuck on the screen that says the redial or message for like 30 seconds to a minute before I can make another call or back to home screen.
This Issue has happened On Rapture and Hyperdrive Tom. So that's telling me most likely an App is the cause of this issue. The weird thing is I haven't installed nor updates any apps for a couple days.(Auto update turned off in google Play. Everything was normal then out of no where this issue started.
Any help/ ideas/ fix will be appreciated and thanked
Any xposed mods that might cause this installed???
Also was this a clean install??
Which includes wiping the internal?
Flash.
Part of the Solution
Well I updated my Moto X XT1092 to 5.1 yesterday. Since then, the ear speaker has stopped working during both incoming calls and outgoing calls. I can hear everything clearly while on loud speaker, however i can't hear a thing while enabling the ear speaker. The person I am talking to can hear everything though. After the update, i cleaned the device using clean master. I haven't done a factory reset yet and haven't done anything in the recovery either, hoping there is an easier fix to it. Can anybody help me fix it?
I am having the exact same issue. But in my case the earpiece worked initially and suddenly stopped working from yesterday. I tried rebooting the phone as well as rebooting in safe mode. Both didnt help. I also tried to clear the cache and data for the phone and dialer app, which didnt help either? I am planning to do a factory reset. Will that have any impact? I was on 5.0 pure edition when i sideloaded the 5.1 soak LPE23.32-14.
I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.
rectifyy said:
I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.
Click to expand...
Click to collapse
The factory reset didnt help too. Still having the same issue after factory reset
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.
rectifyy said:
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.
Click to expand...
Click to collapse
This didnt help either, Still the issue persists even after following every steps on that tutorial. Let me know if you have any luck with that
UPDATE:Finally got it working after updating to the latest build 23.16.3 posted in the general section
Nothing has worked for me so far. Is your phone xt1905? Well mine is xt1902 and I had updated it through ota before the entire issue started, and the build is 23.16.1. So I guess I'm already on the latest build. Do you have any suggestion regarding what i should do?
Hi,
I am also facing the same problem. I just updated my phone to 5.1 and now my ear speaker is not working one thing i noticed is if i connect a headphone, i am able to hear the sound, but the internal ear speaker of the phone is not working
Have anyone found any solution for it ?
Ear Speaker stop working after 5.1 update
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks
Ravneet Lohchab said:
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks
Click to expand...
Click to collapse
Someone over in the Motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.
Resolution for earpiece not working after 5.1 upgrade on moto x 2nd gen
walrusmonarch said:
someone over in the motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.
Click to expand...
Click to collapse
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset
I haven't updated to 5.1 and hearing aid isn't enabled.. Only thing I can think of is the dictionary update wifi required notification being the last thing that was done before losing sound in the ear piece. To remove dictionary updates is there a specific app I can clear data from?
owaismomin said:
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset
Click to expand...
Click to collapse
You legend, this worked! I've been trying everything. How the hell did they get enabled during the 5.1 update?
I found it a bit weird that it was working after factory reset and then suddenly stopped.
found this thread because my earpiece stopped working today. stock android 5.1 att moto x 2014. tried a bunch of stuff (hearing aid, wipe cache, reboot,..) didnt work. What did work for me was as simple as it gets. in my settings i turned everything off except cell signal (wifi, blutooth, location, screen rotate...) tried a call it worked. Dont know why or how but it did. havent tried turning everything back on yet. a bit scared to. Hope this helps someone.
!!UPDATE!! I do not think that helped . went out again and turning everything off didnt work.... So i back tracked to what I did before turning everything off. that step got my speaker back again for now at least. What that step was is i called my voicemail and inserted headphones in and out a couple times. I am thinking that the dialer thinks there are headphones plugged in so no speaker. I also believe it has to do with the dialer software since all other sounds and apps come out loudspeaker. using internal speaker test app internal speaker does not work when it is out. If it goes out again i will try headphones in that app to see if that resets it.
on I side note i just realized all my homescreen apps and widgets are gone. they are still installed just not on homescreen
So did anyone reach an effective solution regarding this issue or determined the root cause? It just happened to me today and i have been trying everything i have read online but nothing worked. Any help would be greatly appreciated.
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Tried doing that as well, didn't work.
Did anyone else find any solution?
I have wiped cache, cleaned the headphone jack, did the hearing aid thing.
Nothing has worked.
affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Found the solution, it was water damage actually.
My mom forgot to tell me that water went in through the headphone jack.
And as water conducts electricity the phone thought headphones were plugged in. Cleaning it with a cloth and a toothpick and then shaking the phone a few times fixed it.
I think that's why cleaning your headphone jack fixed it as well affiatic, water went in probably.
My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Click to expand...
Click to collapse
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3
Moriarty82 said:
My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3
Click to expand...
Click to collapse
Have you ever tried to make or receive a call on your Moto X and you hear nothing on the other side, almost as if there isn’t even a connection made? Then when you try to call again, for some reason it works?
If you have experienced this, you also understand how frustrating it can be when you have to hang up and dial again, just to make a simple call. This problem plagued me for months of owning my 2014 Moto X, searching everywhere for a resolution to this hugely annoying problem. It wasn’t only me who was experiencing this issue either. A friend with the same phone was having the exact same problem as I, however it was impacting them even more, since it was used for their business. At this point, I figured that it wasn’t only the both of us experiencing the issue, but potentially many others owners as well. After much more searching, I came across a similar issue on a different phone, which listed some ideas to fix the issue. To my surprise, when I completed the process, the problem was fixed and has yet to return. Here is what I did…
Fix Inability to Hear Calls on Moto X
I had tried many different things to fix this issue, such as switching from Dalvik to Art, then back to Dalvik again. Rebooting the phone also didn’t seem to help much at all. Now for what fixed the error (scroll below for the steps).
First, I wanted to clear all cache, as that can sometimes fix simple issues. After I had entered the Recovery menu and cleared the cache, I noticed the problem had stayed away for a bit longer than a reboot, but eventually it came back again. Next, I put the phone into Safe Mode. Once the phone rebooted into Safe Mode, I shut down the device and plugged it in to my wall charger for two hours. To my surprise, after two hours when I turned my phone back on and tried making a call, I could hear the other side. The problem was gone and has yet to return, months later.
Anybody that has experienced this same issue, should try the steps below. It may just make your phone much less frustrating to operate.
Putting the Moto X into Recovery Mode to Delete Cache:
1. Power off your phone, by pressing down the power button until the power menu pops up and selecting*Power Off.
[http://salloiacono]
2. Wait a few seconds, then proceed to next step.
3. Hold down the*Volume Down*for a second, the while still holding down the*Volume Downbutton, also hold down the*Power Button*for about 3 seconds, then let go of*Power Button. If you did this correctly, you will see the*Boot Menu.
[http://salloiacono]4. Press the*Volume Down*button, until you have*Recovery*highlighted. Then pressVolume Up*to select*Recovery.
5. Your phone will appear to reboot and you should see this little guy.
[http://salloiacono]
Don’t worry, you didn’t break anything.
6. Now you must enter the*Recovery Menu.
– For Android 4.4.4: Hold down the*Volume Up*button for about 10-15 seconds and while holding that down, press the*Power Button.You should see a new menu pop up.
– For Android 5.0: Hold down the*Power Button*for a few seconds and while holding that down, press the*Volume Up*key. You should see a new menu pop up.
[http://salloiacono]
7. Press*Volume Down*until you have*Wipe Cache Partition*highlighted, then press thePower Button.*Your phone will now reboot. It is time for the next step.
Putting your Moto X into Safe Mode
1. Once your phone has fully rebooted, you are now ready to put your phone into*Safe Mode. Hold down the*Power Button*until thePower Menu*pops up. Now press and hold thePower Off*button.
[http://salloiacono]
2. After a few seconds, you should see a new window pop up warning about*Safe Mode. Press*OK. Your phone will now reboot intoSafe Mode.
[http://salloiacono]
3. Once your phone reboots into*Safe Mode,Power Off*your phone.
4. With your phone powered off, plug it into your wall charger for 2 hours.
5. After 2 hours, you may unplug your phone and turn it back on. Now you should be able to make and receive calls without the issues you were experiencing before!
Hope this works as well for you as it did for me!
Verstuurd vanaf mijn XT1092 met Tapatalk
I have this annoying problem with my 2 month old p9!
The bluetooth keeps turning off by its self! I got my LG G Watch R a month ago, and sometimes it happened that it lost its connection, but it came back by its self...
But lately the bluetooth icon in the notification bar just turns off! Randomly....
EMUI 4.1.1. EVA-L09
The only solution google keeps finding is reset your phone... but i don't want to! Its a pain to reinstall everything to my needs...
Is this perhaps a power saving thing that i can turn off?
try to wipe cache partition by turning on the device while holding power and volume up button together, from there choose wipe cache partition,it will solve most of the problems
I tried it, unfortunately it didn't help
Any other ideas?
Another problem with the Bluetooth.
I bought a gamesir g3s gamepad.
After I connected it, I tried a few games.
I noticed a 1sec delay when I pressed the XYAB buttons. The direction pad or the analog sticks worked with no problem, no delay. At first I thought I had a defective gamepad, but after connecting it to my gf note 4, it worked flawlessly.
I paired it again with my p9, and it worked normally.... For a few minutes... Then the delay came back... If I reset the developers option to defaults (I didn't change anything, I just reset it) the delay disappears for a minute, but it comes back...
My question is, is the Bluetooth so bad in this phone or did I get a faulty device?
try update to nougat,if still u have problem after updating so i think u have faulty device.i don't have any problem using Bluetooth in nougat ,before in MM i had some problem but fix by doing wipe cache partition,but still on nougat more stable
OK, but I still didn't receive the update.
I guess I will have to wait a bit...
It is annoying though...
Mic-E said:
OK, but I still didn't receive the update.
I guess I will have to wait a bit...
It is annoying though...
Click to expand...
Click to collapse
manual update ,most of them not receive official update,so we use manual update
spring80 said:
manual update
Click to expand...
Click to collapse
Yea... I just figured it out Downloading the update atm
So after the update everything works ok now. Second day without a disconnect ?
I'm happy :laugh:
Hi there i am having the same problem how did you manually update your system?
You should be able to basically reinstall your system software using the OTA software update app already installed on your phone. Basically it'll reinstall the same OS again on itself without wiping data.
Superdees said:
Hi there i am having the same problem how did you manually update your system?
Click to expand...
Click to collapse
I fund the solution here on this forum. In hicare you need to go under service, and select os early adopters...
Look out up ☺
True, I am on EMUI 5 and Android 7 and no issues.
I have the same issue and I'm on Nougat. Sometimes I find the Bluetooh turned off with no explanation. Wipe of cache partition and data didn't help. Someone else with this problem?
When updated to 7, did you factory rest the phone? If not, you should. It will almost 100% fix the problem.
I am complainig about heating protection showing everi time reach temprature 104fht on my devise p9