Develop Bugs

? Very slow speech recognition.

Sometimes my Moto will recognize my voice as I'm saying it an execute the command quick, like I think it should all the time.
Sometimes I'll say something and it'll take forever, and sometimes completely fail. I can then open my phone and do a voice command with immediate results, so it's not my connection.
I removed commander and autovoice which seemed to help some at first, but I'm not sure it made a long term improvement. Removing some apps I didn't use from the watch also seemed to help some, freeing up RAM.
Is too much of the voice processing happening on the watch instead of the phone? Or is there a bluetooth issue? My S4 processes voice very quick almost always.
Anyone else experiencing this? I can't seem to find any time this does it more than others. Quit or loud room, doesn't seem to matter.
Any suggestions would be a great help. I use the moto for voice commands a lot and it defeats the purpose of not pulling my phone out when it takes so long.

ThePublisher said:
Or is there a bluetooth issue?
Click to expand...
Click to collapse
That one.
My old, decrepit galaxy s2 has what you describe but worse, sometimes phone bluetooth just turns off and can't turn back on... but mine is probably broken and dying.
Try re-pairing, cycling bluetooth on phone, or changing roms to one with a better bluetooth stack

If your S4 processes it fine, then it certainly is the connection between it and the watch. If cycling the antenna doesn't work try resetting either device, and if you're running a custom ROM check its dev thread for any BT related issues.

Going to try flashing an updated ROM. Currently on GoldenEye NB1 and going to update. I will let you know if this fixes the issue. Thank you two for your help.

Problem fixed
So I deleted the 360 from my phone's bluetooth. Then reset the 360. Upon reconnecting this time it worked great and has been excellent in recognition for a couple days now. Not sure what the difference is now, but it kept me from flashing my phone.

Bluetooth turning off since NMF26U

Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.

I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.

nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk

thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).

I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.

millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.

I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.

Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.

Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk

I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently

I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.

I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!

Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!

t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!

Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.

BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.

I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.

Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.

I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol

Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.

Verizon S8+ Bugs and Issues

Hi everyone,
I have 2 Galaxy S8+ from Verizon and here are my issues:
Past issues:
One of them did not come with the Galaxy Apps store (Not the plays store), and that phone also experienced the DQA issue
Current issues:
If I turn on Fingerprint gestures, the fingerprint sensor will stop working, this was an issue I had from the day I got the phone and has continued even through the updates. Here's a thread I made about it a while ago : https://forum.xda-developers.com/galaxy-s8+/help/fingerprint-sensor-t3595614
My internal speaker has detached, or at least I think that is the issue, as sometimes when I am in a phone call and shake the phone just a little bit, it will either start making a weird buzz sound or completely cut off the sound. Shaking it again will fix it, that's why I think it's a physical issue. I haven't dropped my phone and just in case I ever do, I have a case and a screen protector on it, and neither of them (phone, case, screen protector) have any damage marks on them.
The Biggest Issue: Currently this is the most annoying bug I am experiencing is that whenever I go to lock screen and security in the setting app, it crashes the settings app. I also can't use the search function in the settings app, as it crashes the app withing a few seconds. The lock screen and security is the only menu in which I experience this, I am 99% sure this is due to me turning on Secure startup. I had it turned on a few days after I got the phone and it worked great, I had to turn it off once, about a month ago in order to get a quicker boot. After that I was experiencing issues turning it back on (meaning I turned it on, rebooted the phone and it would not work) , after some persistence, I was able to get it to work and it has worked and still works.
One thing to mention is that I had done the most recent system update, I am not sure this issue was caused by at, since the inability so search in the setting menu has happened prior to the latest update.
I have tried everything other than a full factory reset (wiping all cache, wiping apps cache, reset setting, reset network settings), which I refuse to do, It is absolutely unacceptable for me to pay this much for this phone and have so many issues with it, I have factory resetted my phone (Samsung's recommendation) in order to fix the first issue listed above, multiple times and it did not work.
At this point I really don't know what to do, Samsung support has been useless in this, I don't wish to replace my phone right now as I need it to much to even give up for one day, If anyone has any advice/fix other than factory resetting, I'll happily try it.
Thank you,
GGgamer16

Sounds like a factory reset is needed. I just tried all you mentioned with zero problems on the newest update w/ navbar options and experienced none of that. Speaker problem is most likely hardware related.

Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?

*Hooligan* said:
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
Click to expand...
Click to collapse
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.

brandonc0526 said:
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
Click to expand...
Click to collapse
Yeah I have tried changing channels. It didn't matter. I'm on 2.4 GHz.

I found a possible fix from another forum. I changed my wifi encryption from wpa2 AES/tkip to wpa2 tkip only last night and was rock solid after that point. I didn't have any more wifi issues... Just wanted to mention this change for other people. I usually got 5+disconnects every night. I'm gonna try just the AES option tonight and see how it acts.

3 screen off issues

Hi everyone.
I have a note 10 + 256 go exynos from france.
SInce about last update one ui2.5, I have seen 3 issues which I think are related.
- AOD tap to show not working
- Double tap to wake not working
- When I remove the phone from the ear during a call the screen does not light up anymore whereas before yes.
I almost returned the phone in warranty a short time ago because my screen only registered two fingers,a few days later I received an update that fixed this problem.
For these 3 problems I tried 3 things :
- Update touch screen firmware via *#2663#
- Factory reset
- Reflash the stock firmware with odin and frija
I also have another problem a few times a day the screen freezes, I have to lock unlock the screen and it works again..
Do you think it's a software problem or a hardware problem (damaged screen, damaged sensor or other)?
Please help me thanks.

Lol, firmware and/or software; maybe a settings or permissions issue as there are many. Hardware rarely fails unless it receives severe abuse. You can perform some of the builtin hardware tests just to be sure.
Try using the factory load if the apk in question has been updated or wait for an update that fixes it. Be sure to check the Gallaxy Store for updates.
I'm still running on Pie because it's fast, stable and functional. No scope storage that I don't want or need.
Once you get an OS optimized and running well there's little advantage to upgrading many times unless the new OS is really worth it.
Many times it's not... I'm still running W7 too.
You invariably end up with new issues, hunting down all new glitches and worse, since it's new there not many online solutions.

Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares

Those are all system apks that run in the background.
Is Android System configured correctly?
Try clearing it's data and of course the system cache.
A hard reboot as well.
It's interesting you lost the proximity sensor.

Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.

cyroko said:
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Click to expand...
Click to collapse
cyroko said:
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
Click to expand...
Click to collapse
If it happened after the firmware update... it's in the firmware or software.
Bad firmware can sometimes blowout a cpu but doubt it damaged the hardware controlling just that one feature of the touchscreen.
If that was the case the touchscreen wouldn't work at all.
Maybe the firmware is ok but got corrupted during the download or flash.
A defective memory module could corrupt the load but again that rarely happens.
So back to the firmware/software/settings...
Maybe someone here has seen this before or has a better idea to sort it out.

Honestly I'm not sure it's exactly after an update.
It's just that it's not functions that I use very often. I don't call a lot of people and most of the time I use very little Aod and double tap2wake.
Usually when I grab my phone to use it I unlock it directly with the fingerprint.
when i mentioned the problem where my screen only recognized two fingers at this time , aod and dt2w were already weird as it only worked on the top half of the screen not on the bottom half ..the update solved the problem for the 2 fingers but not for the fact that aod and dt2w only works on the upper half.
Now for some time aod and dt2w no longer work at all no matter where I touch the screen.
I want to clarify that I use a screen protector with loca glue but that it is from the beginning and that it has never been a problem before.
I know this is a weird problem thanks for your patience

I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does

I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does

2x post

when i did the factory reset it was the first thing i tried before even resetting a password but it didn't work anyway.
For the screen protector I use the same brand from the beginning and it has never caused me a problem of this kind, but maybe this one is defective ..
I would have to remove it to try but I have lazy to change it again because I had to change it twice in a little while.
Hoping that by dint of applying the loca glue I haven't damaged anything.
Thanks

Nah the glue didn't hurt anything; it's well sealed.
The tap on AOD I never use but I double tap to turn the screen on/off. If I lost that I be witch hunting.
Try increasing the touch sensitivity if you haven't already... and make sure no other apps have accessibility permissions that could conflict. Same for device administrator permissions.
Try it in safe mode as well.

Question Xiaomi Smart Pen Failing and Shaky

Does anyone know how to solve the problem of the xiaomi smart pen? (it keeps failing and the writing is really shaky)

Perhaps there is a problem with the tip?

I already trade the tip and didn't work... The pen works fine on my pc (ideapad flex 5i)

Try updating the pen's firmware

It's updated
There is some driver that I have to download? Because in the settings of miui it's everything updated

Is it updated or is the update failing?
Try this to be sure: https://forum.xda-developers.com/t/xiaomi-smart-pen-firmware-update-error.4362203/post-85947797

It is updated

Only other thing I can think of is to unpair the pen from the Bluetooth, reboot the tablet, and reconnect
If that doesn't work, the pen is probably faulty. Take it back to the store you got it from, under warranty

is the problem in all apps or specifically system notes app?

Go to SETTING, on KERNEL version tap 4 times and CIT pages. Its kind of tester for your hardware. I had problems with the stylus too, until finally figured the work around. But at least, it stay on BT the longest by far after i tried this.
Been doing hook unhook god know how many times alredy too tired too frustrated. Hope it stays this time.
Peace Out