Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
malikons said:
Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
Click to expand...
Click to collapse
1. if by "the latest OTA" you mean cm-12.1-YOG4PAS3AJ (About phone: Kernel version 3.4.0-cyanogenmod-gef06bf8), then that is what I have, and double tap is working just fine.
2. although i am no engineer nor software developer, i feel i could say with fair confidence it is definitely a software issue. why? because i have used custom kernels that added such a feature to phones that didn't come with it.
3. you can try disabling Display & lights | Prevent accidental wake-up; use a task manager or Apps to look at your running processes and stop any that shouldn't be running then try again.
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Im on 3OH. Double tap to wake wasn't working straight after the update, but i did some fiddling like turning it on and off, played with settings and after a reboot it was working again.
Thank you sir. You just gave me a huge hope. I'll keep playing and will hopefully make it to work. Cheers,
Sent from my ONE A2003 using Tapatalk
malikons said:
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
indeed you have (supplied your version no.), please excuse my oversight.
yours would appear to be newer than mine and, no, just checked & not available for me yet. sorry i can't be of help. hope someone else could. cheers.
I'm on 3OH and it works for me
After power on or reboot, go to settings-display, disable DTTS, turn off the screen with power button, turn on the screen, enable DTTS and now the DTTS will work until next reboot or power off. This is the way I manage to make it works. I hope Cyanogen will solve this bug in next build.
I have also problems with double tap, happened already 2 times in 5 days, reboot solves the problem...
Not sure what I did but the double tap to wake feature has started to work again. I messed around quite a bit with the settings and also rebooted the phone a few times. Although, the response is quite slow, like there is some lag between double tap and when the screen wakes up. It seems to be improving in response time as I play with it more, not sure if its psychological though . Hopefully cyanogen guys will take care of it in the future update.
Stopped working for me too! Seems since the last 2 updates things have gotten bad! If it ain't broke, why fix it?
Sent from my Z1 using Tapatalk
Double tap to wake is working again! I think my phone has a mind of it's own lol!
Sent from my Z1 using Tapatalk
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Double tap to wake has stopped working again! Bloody updates.
Sent from my Z1 using Tapatalk
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Lol! Thanks will try that but shouldn't have to.
Sent from my Z1 using Tapatalk
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
malikons said:
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Thanks it worked! Lol
Sent from my Z1 using Tapatalk
Agree , we shouldn't have to but this phone isn't very stable at the moment. Sometimes I wonder why I'm even using it there's something in this phone I really like though and I believe in cyanogen
My phone was perfect when I bought it. The problem started with the countless updates I've had since then.
Sent from my Z1 using Tapatalk
malikons said:
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It also happens with CM nightlies
Thank you for saving me a lot of time and frustration
Related
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Burkettacb said:
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Wow this is happening to me as well. I'm running the optimus rom currently. I'm reverting to stock here shortly in hopes for the KK update soon so I'll see if that fixes it.
nope. up to date stock zva now and knock on doesnt work but knock off does work as you stated. well this is wierd.
Well thats ****ing depressing
Sent from my LG-LS980 using xda app-developers app
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
This could also be an issue with your proximity sensor. If something (screen protector, finger, dust, etc.) is blocking your proximity sensor, it could be reporting to the phone that it is in a pocket, and to keep the screen off. Try to clean that area, and avoid obstructing the sensors "view". As for the leaving it in the sun, you could have damaged the sensor? You could test it by making a call real quick and see if the screen turns on when you pull the phone away from your face.
Sent from my LG-LS980 using XDA Premium 4 mobile app
The sensor seems to be working fine. Just tested it.
DrZeuss said:
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
Click to expand...
Click to collapse
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
4NDR345 said:
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
Click to expand...
Click to collapse
My screen turns completely on and off when I use the button/knock-off feature. I'm going to take it to a technician today and see what they have to say about it.
First, What are you running on your device? Stock? Rooted...
Burkettacb said:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
That's odd, I have not seen much on this... if running stock
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Or againg, a ROM you may be using.
More detail would be helpful:good:
For me it happend on stock and rooted with aospa... Dont know What can cause this. I Sent it to my Carrier they found nothing....
Gesendet von meinem LG-D802 mit Tapatalk
running stock myself. Technician was useless and told me nothing.
DrZeuss said:
running stock myself. Technician was useless and told me nothing.
Click to expand...
Click to collapse
Same here
Gesendet von meinem LG-D802 mit Tapatalk
Did you try the Stop Having Sprint fix?
Sent from my LG-D800 using XDA Premium 4 mobile app
I got the d802...
Gesendet von meinem LG-D802 mit Tapatalk
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
ingoljosh said:
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
Click to expand...
Click to collapse
This^. For me I have to use my entire thumb or even palm, but it occasionally works.(still like 1/30 tries). This leads me to believe that it is software related. This one issue is killing me. I hate using the power button on the back so I only used knock on. Now that it's not working I'm hating this phone. Knock off works great and I know knock on is kernel based so maybe someone can create a kernel that fixes this issue.
This did work for me. Fixed the knock on feature on my D802.
Credit: Smith I Run (Thread from android central. Can't post link to thread)
There is a solution; (not sure about it, my friend had the same problem and he fixed it with this method)
Open dialer menu and type;
5689#*980# (Sprint)
3845#*801# (T-Mobile)
3845#*803# (AT&T Canada)
3845#*802# (International)
3845#*800# (At&T)
3845#*980# (Verizon)
And when hidden menu is showed up, go to "Settings"
and go to "Update Touch Firmware".
The touchscreen won't work until after 5 seconds, Wait for it and if touchscreen gets working, exit the menu.
Lock the phone and try knocking on the screen, It should be working :laugh:
Click to expand...
Click to collapse
Guys,
Today I got a real issue with new s5. When I try to slide the green answer button on screen, it doesn't respons.
I try 2 or 3 times after it works. It's really annoing problem. Anybody has same? Thanks...
zanbay said:
Guys,
Today I got a real issue with new s5. When I try to slide the green answer button on screen, it doesn't respons.
I try 2 or 3 times after it works. It's really annoing problem. Anybody has same? Thanks...
Click to expand...
Click to collapse
Hello,I have the same lag?
Anyone else have noticed this?
Yes, I've got the same problem. It took so long the other day that I missed the call completely.
Sent from my SM-G900R4 using Tapatalk
anyone have an solution?
First thing I would do is a hard reset - A pain I know, but doing so you can check whether it is potentially a Hardware issue with multitouch/touch etc.
Once you've done that, if it's still exhibiting the same behaviour check your screen behaviour on touch reactions on normal day-to-day use. There may actually be an app for it. (the Note 3 suffered some touch problems, not saying the S5 has them but have to check to be sure) .
If it is deemed a software glitch and a reset fixes it then you should be OK. - However if it's a touch screen bug I'd suggest returning/swapping it.
I'm more inclined to believe it's a software glitch, and a factory reset will indeed solve the problem.
Oke,thanks
Same issue! Did a factory reset but didn't help. Send it to local service center, they keep telling me there is no issue with the phone and that when it happens I should record a video as evidence of the problem. So much so Samsung warranty! Plus I have encountered ransom reboots when answering the phone.
Totally unhappy with S5. It is terrible. S4 and S3 were very stable.
vegerfrancois said:
Hello,I have the same lag?
Anyone else have noticed this?
Click to expand...
Click to collapse
i did noticed that too..
on mine if you put directly your finger in the circle and drag it works 1st try..
i still didnt have time to hard reset to be sure..
I noticed this too. I find that you have to hold your finger on the green answer and slide slowly. It's definitely a software problem that will hopefully be fixed in an update.
Factory reset makes no difference as done this for another problem I was having.
Sent from my SM-G900F using Tapatalk
Don't suppose anyone has found a solution to this yet? Or any alternatives to the stock dialer that might perform better?
I also get a lag between selecting a text field and the keyboard popping up which is very frustrating. Had expected more from a brand new phone
I had this problem at first as well, but after the latest update it fortunately disappeared, I did a full wipe as well.
Same problem here! Partially solved with enabling home button to accept calls....
Same here....its a pain in the ass ?
Sent from my SM-G900F using XDA Premium 4 mobile app
rathga said:
Don't suppose anyone has found a solution to this yet? Or any alternatives to the stock dialer that might perform better?
I also get a lag between selecting a text field and the keyboard popping up which is very frustrating. Had expected more from a brand new phone
Click to expand...
Click to collapse
I disabled the lockscreen animation and that helped making the device more snappy. Here are some more usefull tips http://phandroid.com/2014/04/25/samsung-galaxy-s5-first-14-things-to-do/.
I also have this lag when I'm trying to respond. It only woks on the 2nd attempt.
There's definitely a knack to answering a call, which can be quite annoying. Cannot understand why they didn't just leave it alone. Would rather answer my calls with a quick swipe to the right.
Sent from my SM-G900F using Tapatalk
What FW version are you all on? ANG2 seems to have solved it for me!
johan81 said:
What FW version are you all on? ANG2 seems to have solved it for me!
Click to expand...
Click to collapse
I hadn't even noticed it was fixed since I got the new update. Just tested and problem is solved
Sent from my SM-G900F using Tapatalk
Until a firmware update, enable answer with home button.
Sent from my Galaxy S5 using Tapatalk.
Hi everyone.
Really struggling with my OPT.
It's really slow.
I have rooted and unlocked the boot loader. So I was on 2.0.2 then 2.0.2 then 2.1.0.
Each time the phone is very large between windows, between key presses, swipes.
Got a great antutu score of 58k.
But I cannot figure out why it's slow.
Press middle button takes about 2 seconds to load. Menu selects and swipes lag with 2 seconds.
Even typing this is taken around 10 minutes.
Any one got any advise?
Every one plus device has the home button, back button, recent button problem, I've posted a forum thread about this under this very section, check it out, for a temporary fix until this issue Is resolved (by OP or my forum post) go to settings then buttons and enable on screen navigation
Cons
Takes 1 row off the screen
Pros
Slow issue fixed, can still use fingerprint scanner.
Sent from my ONE A2003 using XDA Free mobile app
Tested with the one plus two with hardware buttons disabled. Still very slow and really un usable.
OS update changed nothing.
Any one got any ideas?
Sent from my ONE A2003 using Tapatalk
rctempire said:
Tested with the one plus two with hardware buttons disabled. Still very slow and really un usable.
OS update changed nothing.
Any one got any ideas?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
I had the similar issues, then I tried Ak's kernel [URL="http://forum.xda-developers.com/oneplus-2/orig-development/kernel-ak-t3208617"]http://http://forum.xda-developers.com/oneplus-2/orig-development/kernel-ak-t3208617[/URL]
everything feels much snappier,and cooler, give a try, I hope it helps
Maybe try a factory reset & reduce animations in developer settings.Mine is working without any issue
My oneplus 2 home button stopped working today it was working fine yesterday. Don't know what happened.
I'm on 2.1.1 stock not rooted.
Any solution!
Sent from my ONE A2001 using Tapatalk
And now I'm not able to use Facebook as well that's embarrassing!
Sent from my ONE A2001 using Tapatalk
Mines unresponsive 20% of the time. I may just use the on screen buttons if it gets any worse.
Finally Facebook starts working as I boot my phone in safe mode then reboot in normal mode or works for Facebook but fingerprint scanner still not working!
Sent from my ONE A2001 using Tapatalk
Same for me... Home button died.
I also fasing strange problems with my fp
Ok, joining the club guys. Mine went dead yesterday. And drying/reseting didnt worked. So, if anyone of you find out something. Seems to be hardware fault actually.
Mine was a hardware fault too. They just replaced my phone.
Happened to me a few weeks ago. Wiping the system partition on mine seemed to fix it. It worked for me and one other person but it could have just been a coincidence though because a 3rd person said it didn't work for them.
I have an online remote appointment with someone from OnePlus Techs level 2 next week, they are probably gonna check logs and console of the phone to ensure if it is a SW fault.
So far I have tried wiping cache of com.oneplus.fingerprint, wiping cache from recovery, wiping data and cache from recovery...
It seems to be a HW fault, because none of the SW resets have worked.
Yesterday I have also tried fingerprint autotest from menu at *#808# and it sates "FAILED". So, I guess thats it.
So I recommend trying out the test function, if it shows not failed, it could be only a stupid SW glitch and wiping cache should help you.
Anyone from OP is pretty far away from me, I am currently in the middle of europe, so I have no idea how to deal with returns/refunds/replacements, any experiences with that?
4n60 said:
I have an online remote appointment with someone from OnePlus Techs level 2 next week, they are probably gonna check logs and console of the phone to ensure if it is a SW fault.
So far I have tried wiping cache of com.oneplus.fingerprint, wiping cache from recovery, wiping data and cache from recovery...
It seems to be a HW fault, because none of the SW resets have worked.
Yesterday I have also tried fingerprint autotest from menu at *#808# and it sates "FAILED". So, I guess thats it.
So I recommend trying out the test function, if it shows not failed, it could be only a stupid SW glitch and wiping cache should help you.
Anyone from OP is pretty far away from me, I am currently in the middle of europe, so I have no idea how to deal with returns/refunds/replacements, any experiences with that?
Click to expand...
Click to collapse
I've passed the auto test but home button still not working
Sent from my ONE A2001 using Tapatalk
joshofali said:
I've passed the auto test but home button still not working
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
OP Technician remotely reflashed my OnePlus with new updated drivers and now fingerprint works, they asked me to stay in touch and in case of any further issues they are going to take care of repairment etc.
So, maybe the hope is not lost, I am still not sure if it was HW or SW issue, but I recommend you to open a ticket and make an appointment too. Those guys are very willing to help you.
We were done in like half an hour.
4n60 said:
OP Technician remotely reflashed my OnePlus with new updated drivers and now fingerprint works, they asked me to stay in touch and in case of any further issues they are going to take care of repairment etc.
So, maybe the hope is not lost, I am still not sure if it was HW or SW issue, but I recommend you to open a ticket and make an appointment too. Those guys are very willing to help you.
We were done in like half an hour.
Click to expand...
Click to collapse
Thanks for your reply and hope!
Can you kindly tell me the procedure of opening a ticket?
I have had the same problem a few times. When I wiped my rom and did a clean install, the FP was working again
joshofali said:
Thanks for your reply and hope!
Can you kindly tell me the procedure of opening a ticket?
Click to expand...
Click to collapse
Well sure, I was pretty direct and straight, because I was kind of angry when my FP stopped working, so I have waited line in "Live Chat" at oneplus website.
(oneplus.net -> Support section -> bottom of page)
You have two possibilities, complain in the live chat or submit ticket via internet form.
It took few days of waiting for the technician, but they have helped me, so it is worth the wait.
Good luck!
4n60 said:
Well sure, I was pretty direct and straight, because I was kind of angry when my FP stopped working, so I have waited line in "Live Chat" at oneplus website.
(oneplus.net -> Support section -> bottom of page)
You have two possibilities, complain in the live chat or submit ticket via internet form.
It took few days of waiting for the technician, but they have helped me, so it is worth the wait.
Good luck!
Click to expand...
Click to collapse
Thanks a lot for your reply and time
Sent from my ONE A2001 using Tapatalk
sometimes my home button stoppen working too
sometimes my home button stoppen working too,but not frequently.
And I use the H2os
joshofali said:
My oneplus 2 home button stopped working today it was working fine yesterday. Don't know what happened.
I'm on 2.1.1 stock not rooted.
Any solution!
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
After loosing the fingerprint scanner once for about 3 days until it just started working again and lost it again after about 2 months of no problems until 2 days ago when I lost it again.
This is what worked out for me.
1.I disabled the fingerprint option.
2.Turned off the on screen buttons.
3. Reboot into recovery
4. Clear cache
5. Reboot
6. Home button is working again!!! ??
I hope this helps someone.
Sent from my ONE A2005 using XDA Free mobile app
Hi all,
About two months ago I had a problems with my notifications, they suddenly stopped vibrating when one came through, this applied to both the loud and vibrate profiles, although phone calls vibrated it was just the notifications.... roll on a month later and it started happening again!
I totally forgot the settings I changed to fix the issue previously so over the last week or so I've been checking what could be the cause, I then found the culprit, for some reason the vibration intensity for notifications was set to zero, why this was set I don't know.
I've tried to replicate this problem by changing the sound profiles to see if the vibration intensity will go back to zero and it hasn't, I've manually enabled D.N.D that doesn't change it, therefore I'm puzzled what has caused this to change by itself, any ideas?
Very same issue dude, S7. Did you find a fix ?
martinburke said:
Very same issue dude, S7. Did you find a fix ?
Click to expand...
Click to collapse
I never did; it's happened several times since, normally about a month apart, at least I know how to fix it now. I'm running the nougat beta atm so will be interesting to see if it happens in this.
Sent from my SM-G935F using Tapatalk
Thanks for the reply. Appreciate it.
martinburke said:
Thanks for the reply. Appreciate it.
Click to expand...
Click to collapse
No problem!
Sent from my SM-G935F using Tapatalk
Do you know if this still happens on 7.0 or any other strange bugs showing up ?
martinburke said:
Do you know if this still happens on 7.0 or any other strange bugs showing up ?
Click to expand...
Click to collapse
I've been on Nougat for about 3 months and not had that bug at all ?
Sent from my SM-G935F using Tapatalk
That's good. I'm still holding off on 7.0 marshmallow is running smooth for me and can't find a good enough reason for update. They should have included the Google assistant.