Hello there,
Since 7.0 (currently also on 7.1.1) got issue:
My phone is turning on Bluetooth randomly in a day by itself. When I turn it off it instantly turns on in 5 sec. I deselected Bluetooth searching under localisation, but still got this issue. Anyone know how to make phone to get Bluetooth enable only when I press Bluetooth button?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
I don't have this issue with 7.1.1 and I didn't with 7.0.
also, I never heard of that, so there has to be another problem. are you using a custom rom?
Original stock ROM. Scanning Bluetooth is turned off and still 5-10 times I get Bluetooth on per day
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Skimmed over too quick, if that specific toggle is off, have no idea. It's hidden pretty well, do not have this issue here.
Perhaps a factory reset, keep in mind all data will be lost.
scariola said:
Skimmed over too quick, if that specific toggle is off, have no idea. It's hidden pretty well, do not have this issue here.
Perhaps a factory reset, keep in mind all data will be lost.
Click to expand...
Click to collapse
Went factory reset, turned off bluettoth scanning, still bt goes turn on sometimes and immmediatly off but not always... and then stays and eats my battery.
JaCh0o said:
Went factory reset, turned off bluettoth scanning, still bt goes turn on sometimes and immmediatly off but not always... and then stays and eats my battery.
Click to expand...
Click to collapse
Tell me one thing.
Do you have Yanosik installed?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Domin_PL said:
Tell me one thing.
Do you have Yanosik installed?
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
Yes. But even if it's turned off it scans bt?
Wysłane z mojego Pixel przy użyciu Tapatalka
JaCh0o said:
Yes. But even if it's turned off it scans bt?
Wys?ane z mojego Pixel przy u?yciu Tapatalka
Click to expand...
Click to collapse
Yep that's it.
Go to settings and there should be something like turning Bluetooth (?) And disable it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Domin_PL said:
Yep that's it.
Go to settings and there should be something like turning Bluetooth (?) And disable it.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Click to expand...
Click to collapse
Gdzie dokładniej?
Wysłane z mojego Pixel przy użyciu Tapatalka
JaCh0o said:
Gdzie dok?adniej?
Wys?ane z mojego Pixel przy u?yciu Tapatalka
Click to expand...
Click to collapse
In settings of App (3 lines, left corner) Bluetooth section, there are something like automatically turn on Bluetooth when connected to headset, or something like this.
=
Zobacz w ustawieniach Yanosika w zakładce Bluetootha są takie pierdoły o włączaniu automatycznie Bluetootha czy coś takiego i spróbuj to poodznaczac, jak nie będzie działało to spróbuj w jakiś dzień odinstalować apke i zobaczyć czy to na pewno ona powoduje błąd.
Wysłane z mojego Nexus 5X przy użyciu Tapatalka
Related
Every time when I try to swype / roll down the notification bar / panel. It stops after 1cm and jumps back to the top. Than I try for the 2nd time and it rolls correctly. Very annoying to repeat the move every time... Anyone experienced the same? Any suggestions?
Thanks in advance!
Try to grab at the left side of bar or right side and on center. Maybe is touch issue
Wysłane z mojego GT-I9100 przy użyciu Tapatalka
mosespl said:
Try to grab at the left side of bar or right side and on center. Maybe is touch issue
Wysłane z mojego GT-I9100 przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, but I try to touch at exactly the same place and it works after the 2nd try...
what about if you are in app list or in settings or another part of menu and you want to pull down bar?
maybe factory reset will helps
i have the same bug
Send from my LT26i using tapatalk for Ipad
Which firmware are you on?
I cannot remember which, but one of the older FW had this bug.
It is gone with the latest .757 for me, so may be update, or do clean intall.
Have some hope, because I know what you are talking about. I had it for a while. But after rooting/upgrading the FW it is COMPLETELY GONE. So lets believe it is FW and not hardware for you too!
jewelkobayashi said:
Which firmware are you on?
I cannot remember which, but one of the older FW had this bug.
It is gone with the latest .757 for me, so may be update, or do clean intall.
Have some hope, because I know what you are talking about. I had it for a while. But after rooting/upgrading the FW it is COMPLETELY GONE. So lets believe it is FW and not hardware for you too!
Click to expand...
Click to collapse
it is .757
btw. just bought the phone and after unboxing it offered an update. so the phone is 1 week old and maybe with the latest FW.
only 2 bugs so far: that crack in every notification sound and this notifiaction bar bug...
I use an LG G2 and I didn't have ANY problems with that... so annoying that is Sony's nr.1 phone has bugs... VERY disappointing...
Mine did this as well with JB out of the box, and continued after both KK updates. It has become somewhat less frequent over time.
So im running fulmics 3.7 on d850 in the stock dialer next to the call button there is an icon with a phone and a little person simialar to the icon for contacts its always faded out slightly and i cannot use it just wkndering what it is
KitKat & Lollipop is the best Rom ever mate.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
adamzki2013 said:
KitKat & Lollipop is the best Rom ever mate.
Wysłane z mojego SM-N910C przy użyciu Tapatalka
Click to expand...
Click to collapse
I prefer kk over just about all other android release once all the bugs got fixed but a lot of the things i do with my phone are intag4ated into the system now such as like old drive droid i mount my phone on any pc as a usb recovery stick or live os and kk didnt nativly support it real well
TheMadScientist420 said:
So im running fulmics 3.7 on d850 in the stock dialer next to the call button there is an icon with a phone and a little person simialar to the icon for contacts its always faded out slightly and i cannot use it just wkndering what it is
Click to expand...
Click to collapse
You probably have a F400 device. It's for video calling. i think its only works in Korea
GTRanushka said:
You probably have a F400 device. It's for video calling. i think its only works in Korea
Click to expand...
Click to collapse
Garuntied d850
delete..
Work whit 6.0 deodex?
Inviato dal mio XT1635-02 utilizzando Tapatalk
Yes tutorial works in Android 6.0
Wysłane z mojego XT1635-02 przy użyciu Tapatalka
What is the function of this mod? I am sorry thanks
If you don't have a Moto with fingerprint scanner, than you won't understand.
It is super annoying on my Moto G4 Plus that the fingerprint scanner is not recognized after reboot, needing that first unlock to be pattern or pin.
In the United States, a fingerprint does not share the same legal protections that a password does (plausible deniability.) A fingerprint is not protected under the 5th amendment, but a password is. Just a warning. I believe Google has done this on purpose.
ryanbg said:
In the United States, a fingerprint does not share the same legal protections that a password does (plausible deniability.) A fingerprint is not protected under the 5th amendment, but a password is. Just a warning. I believe Google has done this on purpose.
Click to expand...
Click to collapse
It's for protection as well as fingerprint can be masked using current technology.
what this discussion?
you want to use!
You do not want to not install!
Hey guys, I really enjoy new Nougat on H815, it's all fast and fluid, battery life better, audio quality seems to have improved but there's one thing that kills me, KnockOn. Why? In MM it used to disable itself when in pocket or proximity sensors were covered, here it doesn't seem to work like that. I put my phone in pocked and it opened few apps, added new event to my agenda, almost called my last contact... Is it due I didn't flash bootloader? Can anyone confirm it doesn't work way it worked before or its caused by MM bootloader?
Wysłane z mojego LG-H815 przy użyciu Tapatalka
For me, quickcircle was the cause for this problem, as I stopped using it, I don't have this problem anymore.
Hello,
As checked on two Xiaomi Mi-6 phones, since updating to Oreo the alarm clock does not ring at the specified time. The notification with elapsed time can be seen in the notification shade but when the time comes the phone remaains silent. Disabling MiUI enhancements as well as all battery saving features doesn't help.
Is that a known bug with the MiUI software and if yes, is there a working solution/workaround at the moment?
Thanks.
Wysłane z mojego PLK-AL10 przy użyciu Tapatalka
Piciok93 said:
Hello,
As checked on two Xiaomi Mi-6 phones, since updating to Oreo the alarm clock does not ring at the specified time. The notification with elapsed time can be seen in the notification shade but when the time comes the phone remaains silent. Disabling MiUI enhancements as well as all battery saving features doesn't help.
Is that a known bug with the MiUI software and if yes, is there a working solution/workaround at the moment?
Thanks.
Wysłane z mojego PLK-AL10 przy użyciu Tapatalka
Click to expand...
Click to collapse
I am on beta 8.3.15 and am woken by the alarm every morning. Which version are you referring to? Global stable 9.2.3.0? China Dev?
Yes, that is the version exactly. I mean stable 9.2.3.0.
Wysłane z mojego PLK-AL10 przy użyciu Tapatalka
Me to, I've overslept for work yesterday, but later I have tested it with another time and it worked. 1. One that didn't ring whenever I set it. So I deleted it. I have 9.5.3.0 stable. I have a feeling that it's got something to do with Doze.? Advice please?