Related
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do
GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app
well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work
I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.
mine still says rooted so i'm kinda screwed right now
Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?
Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it
The only solution is returning the phone
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
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
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
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
Or againg, a ROM you may be using.
More detail would be helpful
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.
He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.
Hey forum peeps,
I've got an issue with my Moto G4 Plus (XT1643). Using any custom ROM available (official or unofficial) causes the flashlight to basically disappear. Only by using the stock ROM can I get the flashlight to work. The odd thing is, I can still use it while taking pictures, just not for usage as a tool. I can't find its Quick Settings tile, nor can I get the chop-chop gesture to work (it always says "CMActions stopped working." Since only CM-based ROMs have actions, I use them. Non-CM ROMs like Slim6 don't have gestures.)
Any known way to fix this? It's pretty annoying not having the ability to use the flashlight when I actually need it.
I'm also having Bluetooth issues (stock or non-stock). I can't connect to media devices ONLY (I can connect to my Moto 360 just fine, but I can't connect to say JBL Bluetooth speakers.) I have no idea what's causing this. I've tried everything (flashing modem files through fastboot/recovery ZIP; reverting back to stock; ****ting myself from sheer force of anger), but nothing seems to fix it (it really pisses me off not being able to use a Bluetooth headset.)
Any suggestions for this as well?
Any help on either would be much appreciated.
I'm just ruling out simple things.
Did you try rebooting on the ROMs you installed to see if chop-chop works?
For the latter, I believe you shall need a log for a developer to comment. I have no problems connecting to media devices on the XT1643.
I've noticed this issue as well.
A workaround:
Go to Gestures (or depending on the ROM you're using, wherever the Chop Chop feature can be turned on/off) and switch it off.
Reboot your device. After its rebooted, check your quick settings and verify the flashlight toggle is back.
Then go back into Gestures and Enable the Chop Chop feature..
:ROFIT::
zeomal said:
I'm just ruling out simple things.
Did you try rebooting on the ROMs you installed to see if chop-chop works?
For the latter, I believe you shall need a log for a developer to comment. I have no problems connecting to media devices on the XT1643.
Click to expand...
Click to collapse
Yeah it's like an instruction on all posts to reboot after installing a new ROM, even with stock I have to do that.
For the Bluetooth thing, I'm not really sure on that or really who to contact about it so...
Jleeblanch said:
I've noticed this issue as well.
A workaround:
Go to Gestures (or depending on the ROM you're using, wherever the Chop Chop feature can be turned on/off) and switch it off.
Reboot your device. After its rebooted, check your quick settings and verify the flashlight toggle is back.
Then go back into Gestures and Enable the Chop Chop feature..
:ROFIT::
Click to expand...
Click to collapse
Well I tried that too and it didn't work, still not there -___-
I've had Bluetooth issues with this phone, as well as my previous Moto G 2015. Something that's been working for me is an app called Quick Fix. Not sure what files it actually cleans up as it doesn't require root to run.
themajod said:
Yeah it's like an instruction on all posts to reboot after installing a new ROM, even with stock I have to do that.
For the Bluetooth thing, I'm not really sure on that or really who to contact about it so...
Click to expand...
Click to collapse
I don't remember which custom ROMs have it but in some, there's an option to put flashlight as an option in your power menu.
After that, toggling it on from there triggers a soft reboot. After that both the QS tile and gesture work fine for me.
I don't know why you are having issues in stock ROM though...
Sent from my Moto G4 Plus using Tapatalk
GuruBuilt said:
I've had Bluetooth issues with this phone, as well as my previous Moto G 2015. Something that's been working for me is an app called Quick Fix. Not sure what files it actually cleans up as it doesn't require root to run.
Click to expand...
Click to collapse
Well idk how that fixes anything for you given the fact that this disclaimer was in the app's description:
***Disclaimer: This is a placebo app. It only asks for a reboot. Regularly rebooting your device can have many positive effects***
Anyway I tried it for the hell of it, and nothing; same stupid ****.
1chrome said:
I don't remember which custom ROMs have it but in some, there's an option to put flashlight as an option in your power menu.
After that, toggling it on from there triggers a soft reboot. After that both the QS tile and gesture work fine for me.
I don't know why you are having issues in stock ROM though...
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Actually, I tried that earlier, but it ended up the same. Apparently, I bought a new phone just for some stupid but oddly important things not to work on it -_-
Also, what I meant with stock is that I also have to reboot to get the flashlight to work, after that it's 100% fine. Thing is, I'm not a fan of OEM ROMs, all of them have a certain feature on it that just ruins it for me,so I use RR or CM mostly.
Anyone? Any help?
No matter what rom I'm on....stock or modified...whether I'm fully wiped or not..."OK GOOGLE" detection stops listening and unchecks itself, (Always on and Personal results turn off).
Restarted, wiped cache, downgraded Google app, etc, etc. This is a major flaw and the ONLY reason I'm unhappy with this phone...isn't anyone else having these issues? H910 here, rooted with DirtySanta. VERY frustrated.
THIS is the closest thing I've seen relating to the bug I'm experiencing....but Accessibility fixes NOTHING. https://www.xda-developers.com/psa-disabling-accessibility-services-breaks-ok-google-feedback/
I don't have that issue. I am using NotSoStock rom on vs995. The only thing I changed was the build prop so that I can use the pixel launcher and google assist.
yes, I see it as well. Out of the blue the Hot Word Detection will be turned off. I am forced to turn it back on. My voice model is still in tact though, have no idea as to why this setting keeps turning itself off either.
curious, are you using TBO Black Out gapps?
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
The app doesnt seem to be forgetting my voice. The setting just gets turned off for what ever reason. When I toggle it back ON its not asking to train, so the voice remains there.
edit...I have a android wear device (smart watch) with the "OK Google" enabled. maybe it gets turned off on my v20 in favor of the wear device.
here is when it crashes
Code:
01-18 05:02:43.939 3064 23321 W AlwaysOnHotwordDetector: startRecognition() failed with error code -19
full log, from enabling to the auto disable that occurs if anyone is interested
http://pastebin.com/Qc5YRTGT
I also have an android wear watch. You may be right, I haven't been wearing my watch the last fortnight, about the time the V20 has been behaving...
reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
I thought it was only me...maybe it's a Google thing
bobafx said:
I don't have that issue. I am using NotSoStock rom on vs995. The only thing I changed was the build prop so that I can use the pixel launcher and google assist.
Click to expand...
Click to collapse
I had it on that rom, too. Worked, no updates at all, no system apps restored from Titanium...then stopped. Tried all of the "solutions" I found online, none worked. Kept toggling itself back off and freezing. Same as on stock. I'm on bone stock now with attkernel that I flashed and it's flying. So far, so good. But...give it a few more days. LOL.
reaktor TuT said:
I also have an android wear watch. You may be right, I haven't been wearing my watch the last fortnight, about the time the V20 has been behaving...
Click to expand...
Click to collapse
Nope, I definitely don't have a watch or anything. The above post talks about a bug with Accessiblilties but none of what he said fixed my issue.
cordell12 said:
The app doesnt seem to be forgetting my voice. The setting just gets turned off for what ever reason. When I toggle it back ON its not asking to train, so the voice remains there.
edit...I have a android wear device (smart watch) with the "OK Google" enabled. maybe it gets turned off on my v20 in favor of the wear device.
here is when it crashes
Code:
01-18 05:02:43.939 3064 23321 W AlwaysOnHotwordDetector: startRecognition() failed with error code -19
full log, from enabling to the auto disable that occurs if anyone is interested
http://pastebin.com/Qc5YRTGT
Click to expand...
Click to collapse
I don't have a watch. Only a bluetooth headset, car audio and bluetooth speaker. Other than that...no paired anything, in any way. It just decided to toggle "Always On" off and stay off...even after retraining, it freezes and untoggles, even on a restart or battery pull.
reaktor TuT said:
I'm on stock with no root and OK Google keeps forgetting my voice. It was OK at first, then I think it broke with an update. I have it sorta stable for now.
Click to expand...
Click to collapse
I thought so too...but I blocked updates...and am on root so I froze all apps that I usually install. Broke again. I'm on stock w/ root and att kernel at the moment and all SEEMS good...been a day. But, I'll update when it breaks again.
cordell12 said:
yes, I see it as well. Out of the blue the Hot Word Detection will be turned off. I am forced to turn it back on. My voice model is still in tact though, have no idea as to why this setting keeps turning itself off either.
curious, are you using TBO Black Out gapps?
Click to expand...
Click to collapse
Nope. No gapps. Was on Not So Stock...but for weeks have been going back and forth to stock w/ root and back, trying to troubleshoot. I'm now on bone stock, w/ Nova launcher and att kernel. I'm flying on it...same as other roms...and Google Now works just fine, but it's been a DAY. I'll update when/if it stops working.
Yup I had thought I may have fixed it once - but turns out it still switches off on me too. I'm on H910 with NSS ROM. I'm wondering if it has something to do with the kernel if yours is working currently on complete stock. But at least it does work on my home screen so I dont really mind much.
But yeah when going into the settings and switching Always On to ON state, and then when you go back in - the app freezes up for awhile (like about 30secs to a minute). Then it comes back up, but the Always On is toggled OFF again.
Edit: or maybe it is due to being a deODEX'ed ROM? I know occasionally issues happen for different apps when its deODEXed.
twistedvip said:
Yup I had thought I may have fixed it once - but turns out it still switches off on me too. I'm on H910 with NSS ROM. I'm wondering if it has something to do with the kernel if yours is working currently on complete stock. But at least it does work on my home screen so I dont really mind much.
But yeah when going into the settings and switching Always On to ON state, and then when you go back in - the app freezes up for awhile (like about 30secs to a minute). Then it comes back up, but the Always On is toggled OFF again.
Edit: or maybe it is due to being a deODEX'ed ROM? I know occasionally issues happen for different apps when its deODEXed.
Click to expand...
Click to collapse
FANTASTIC! I was trying to tell people I wasn't imagining it! LOL. Here's the kernel I'm using, which flies for me, zero lag, and is bone stock AT&T. https://www.androidfilehost.com/?fid=385035244224411218...Thank Team DevDigitel for providing this awesome kernel thread. https://forum.xda-developers.com/v20/development/device-kernel-aka-boot-img-s-carrier-t3533426
I'm running this...day two of perfection... AlkaliV2's https://www.androidfilehost.com/?fid=457095661767123457 BONE STOCK IMAGE...attboot.img here :https://www.androidfilehost.com/?fid=385035244224411218.....whatever else you want like Viper4Android from here...http://downloadmirror.co/2zYA/ViPER4Android_2.5.0.5_guitardedhero.zip (Don't forget to delete or add .bak to audio_effects.conf, in file manager in TWRP at system/vendor/etc, after mounting system) ...and of course lastly, don't forget to flash SuperSU 2.79 flashable zip from here: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip. I then, only use Titanium Backup Pro to restore apps only, no data...and no system apps.
Try it and lemme know how you fare. I'm glad I'm cruising beautifully for now...with the exception of Viper4Android stopping working like I've experienced on all roms.
Best of luck!!!!:good:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
Can Tasker achieve something like this? I have only returned to Android after a 3 years break, any advice is much appreciated!
dancooper93 said:
Hi there,
Is there a workaround or a root function to enable Always On listening for 'OK Google' while the screen is off/AOD?
It is really bugging me but I cannot see a workaround already posted.
Thanks!
Click to expand...
Click to collapse
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have that setting enabled. It works on the lock screen where you can swipe to unlock, but not on the darker lock screen, where it shows the time and the outline of your notifications.
srdjanLeo said:
OMG. Just set up Google Assistant and enable Voice unlock. Just explore your phone.
Click to expand...
Click to collapse
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
dancooper93 said:
I have enabled them options. It works on the light lockscreen, where you can scroll your notifications and have the 2 icons in the bottom corners.
It does not work on the darker lock screen, or the Always On Display screen, where it only shows the time and the outline of notifications you have.
Click to expand...
Click to collapse
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
srdjanLeo said:
Works here as it should. With AOD and without. Are you rooted? If you are try other ROM. If you are not, try reflashing stock firmware with Odin or with Side Sync or whatever Samsung kies is now called.
Click to expand...
Click to collapse
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
MilgeS said:
Same for me Dan, works after you swipe but not from AOD, every tutorial I have seen says the same, has to be "open" before it will work.
Bixby will unlock from the AOD screen if you set that up, hope that helps
Click to expand...
Click to collapse
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
dancooper93 said:
I am not rooted. I heard if you root you can only charge your battery to 0%?
Okay, I will have a look into reflashing if that'll fix it.
Are you rooted?
Click to expand...
Click to collapse
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
srdjanLeo said:
I am rooted. With custom ROM, NOTE 8 Port.
Charging works as it should, OK Google trigger works as well. I really don't have any problem.
Click to expand...
Click to collapse
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Okay, I see.
Does charging not stop at 80% for you because you are rooted?
artikle said:
It works for you because you are using a Note 8 ported ROM. Because Samsung enabled this feature on the Note 8. It will not currently work on the stock S8 ROM. Some people seem to be in a server side test to enable this feature though.
Click to expand...
Click to collapse
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
srdjanLeo said:
It was working for me on Bat Stock ROM and it is S8 ROM. I never used stock ROM so I can't say anything about that, I rooted my device and flashed custom ROM before even setting it up after unboxing.
Click to expand...
Click to collapse
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
dancooper93 said:
I forgot to quote you, sorry.
Question:
Does charging not stop at 80% for you because you are rooted?[
Click to expand...
Click to collapse
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
srdjanLeo said:
It stops. But there is a workaround if you have Snapdragon version. Mine is Exynos so it is as Samsung set it up.
Click to expand...
Click to collapse
I am now rooted
What Note 8 ROM did you use?
dancooper93 said:
What do you mean 'open'?
I have Bixby set up, which I just use to open Google now, not ideal, but it is a workaround nonetheless!
Click to expand...
Click to collapse
I meant "open" as in on lock screen re your above post, the screen after AOD, sorry for any confusion
Same here works after you swipe but not from AOD, every time tutorial I have seen says the same has to be "open" before it will work.
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
scatterthought said:
It's best to think of the always-on display as "Screen Off", which is why OK Google doesn't work on stock ROM. That's standard Android procedure to avoid draining the battery by always listening for voice commands.
At one point, Google Assistant was able to listen when the screen was off, so long as the phone was being charged. Unfortunately, that feature disappeared at some point in the past half year or so (which caused me some confusion when it stopped working and I could no longer find the toggle).
Click to expand...
Click to collapse
That's not true. It still works on a Google Pixel running stock Android with the screen off and not charging. You never had to have it plugged in or charging for that to work. Samsung is the ONLY Android phone I know of that OK Google doesn't work with the screen off.
Source: I've owned the Nexus 6, Nexus 5x, the Nexus 6P, the Pixel XL, a number of Galaxy phones, and a few Motorola's and a couple LGs.
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
None of these problems here. All that tested and works fine. Phone is super fast after update. Oh and i didnt format the phone after update
klemen241 said:
None of these problems here. All that tested and works fine. Phone is super fast after update
Click to expand...
Click to collapse
Thanks for your reply! I hope somebody facing similar problems has overcome and provide suggestions.
But Sammobile blog has also confirmed these issues.
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
shuvadeep said:
II havent faced any of these issues post update.
Did you try doing a factory reset? If not, try the same if its not too much of an issue for you.
Click to expand...
Click to collapse
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
Whiskey103 said:
I have the same but I updated today over mobile data.
Came home and it started to behave like described above.
So I figured it is something with the updated WiFi drivers.
Switched off Wi-Fi and all seems fine now.
Click to expand...
Click to collapse
Wow let me try this, shall update you soon.
***Update***
Yes this trick is working.
---------------
Also one more question I don't know if it's my phone or everyone is facing this issue. Whenever I switch on VoLTE calls (Screenshot Attached) my phone temperature increases and battery drains.
Nitin5556 said:
No I didn't do factory reset as I have checked from other forums that factory reset is not helping, the new update is broken.
Click to expand...
Click to collapse
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
gee2012 said:
Not true, its a good update and everything butterysmooth here. Did factory reset after the update though because of the size of the update.
Click to expand...
Click to collapse
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Nitin5556 said:
Hello Guys,
I am from India, I got the latest update attached screenshot.
I am facing few issues:-
The phone has become laggy in some departments such as:
1. The fingerprint mark stays on the screen after the screen unlocks.
2. Even after pressing the power button screen doesn't lock. The screen does black out but when I double tab on the screen it directly takes me to the home screen without showing the lockscree first. I am not using Google trusted location or devices to unlock without taking my fingerprint or face recognition.
3. When I try to dial a number it doesn't call at a single go, after pressing multiple times it calls the person whom I am trying to call. It looks very choppy as if the system responding to my commands little later.
4. Whenever I am trying to take the screenshot it doesn't take at a single go, after pressing multiple times the system recognises I am trying to take the screenshot and respond little later.
All the apps are working fine without any lags but the above said things are bothering me a lot.
I hope someone from XDA can assist me with this.
P.S.: I have tried to clear the cache from the boot screen. Also did a test on graphics from the same menu.
****Update v1****
I have got something to support my comments!
https://www.sammobile.com/2019/05/27/latest-galaxy-s10-update-has-some-serious-bugs/amp/
*****Update v2****
Switch off your WiFi, your phone will start behaving normal you will not face this problem in Mobile data usage.
Credit goes to @Whiskey103
Click to expand...
Click to collapse
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
cbotadra said:
Mine fingerprints stopped all together..Started to get error that something is wrong with sensor..Went to service centre..they downgraded to april..they conf that some issue in may update..Hope samsung fixes asap..
Click to expand...
Click to collapse
Yes the problem is there in the May update.
Samsung should do something about this.
Nitin5556 said:
Everyone is not facing this issue, some of them are facing!
Are you using data over WiFi or Mobile data?
Click to expand...
Click to collapse
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
gee2012 said:
Both, but i flashed the rom with Odin. I don`t realy like OTA`s tbh.
Click to expand...
Click to collapse
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Whiskey103 said:
So, you're saying only the ppl that took the OTA are facing the issues? In that case i will probably try that then if the bug returns for me.
For now after switching WiFi On/Off for me it is gone.
Seen reports that plugging in the charger does the same.
Weird stuff indeed.
Also now i see a fellow Dutch, you by any change using Rabobank stuff (Wallet/App) with tripped KNOX and have no problems with it?
#sorryforofftopic
Click to expand...
Click to collapse
No, its possible that some users who do flash a rom with Odin could face some issues too but i personally don`t. I`am using the ABN bank app and i haven`t rooted for a long time now. I used to do it because of theming and getting updates/upgrades but nowadays i personaly don`t see a reason anymore to root anymore. So i can`t help you with your question.
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Virgo_Guy said:
I happened to flash "ASE5" build two ways :
1. First using ODIN 2 days back . Did a factory reset ,erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced -> None.
2. Went back to previous "ASD5" build, downloaded the "ASE5 OTA" update and installed. Did a factory reset, erased cache in recovery, reinstalled all apps & after setting them up:-
issues faced so far -> None.
*One glitch I'm noticing from the beginning with "ASE5" :
When I click on my apps & games(playstore app>drop down menu on the left), it freezes for a split second while it takes into the main page. With all my effort, I could not fix it. (App cache cleaning only temporarily fixes this).
Click to expand...
Click to collapse
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
gee2012 said:
A split second delay bothers you? What apps are running in the background? Do you have the FaceBook app installed? How did you set your animations?
Click to expand...
Click to collapse
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Virgo_Guy said:
No it does not "bother"but is a step back in smoothness if that counts. It's a "difference" that I noticed since I was testing both builds back and forth for a comparison. Rest be assured that it's not related to apps installed and animations set.
Click to expand...
Click to collapse
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
gee2012 said:
I have my animations set to 1,0 and i don`t have a delay, on 0,5 however there is a slight delay.
Click to expand...
Click to collapse
Erase playstore cache and you won't even notice it for a while only to re-appear after sometime.
"Less noticiable" and "very much noticiable" in my usage in 1x & .5x respectively. In ASD5 build, this transition slips like a soap.