Hi
I'm kinda new around here so don't really now where to post it.
So today Google Assistant randomly appeared on my phone. I have done nothing to install it. I tried to open Google Now (via holding the Home button) and fully functional Assistant showed up. It works perfectly - just as on a Pixel device.
I'm running SliMM 3.8, obviously rooted, locked bootloader (I think). I also have 'N-ify' Xposed module installed, which I think may have something to do with that.
Anybody got any ideas how and why I suddenly got it on my phone?
Finezol said:
Hi
I'm kinda new around here so don't really now where to post it.
So today Google Assistant randomly appeared on my phone. I have done nothing to install it. I tried to open Google Now (via holding the Home button) and fully functional Assistant showed up. It works perfectly - just as on a Pixel device.
I'm running SliMM 3.8, obviously rooted, locked bootloader (I think). I also have 'N-ify' Xposed module installed, which I think may have something to do with that.
Anybody got any ideas how and why I suddenly got it on my phone?
Click to expand...
Click to collapse
Definitely it is Android N-Ify,if you want to disable it go to the N-Ify app and go to Check for Updates and click the N logo about 6 times until it says You have unlocked experimental features and then go back,open Experimental Settings and uncheck enable google assistant
Related
Hi there.
I am pretty new here & didn't read up on billboards yet, but I had something very strange happening to me yesterday. The phone automatically downloaded a 'Google Voice Search'-update and since it's installed, I keep encountering problems.
The most annoying one - the camera doesn't work anymore. If I click on the icon, the screen just turns black and remains like that until I either hit the HOME button - or if I wait long enough - I get an Force close-popup.
Furthermore, after calls, the screen also turn dark sometimes, but turn back on after a while. Other that that, everything works fine as before.
Am I the only one?
Does anyone know whether it's update-related or whether it's just a coincidence. Everything else works fine, so I doubt it's something else.
Is there a way to reinstall the camera app without having to flash the phone. As I said, I am a newy & don't want to end up with a brick.
The malfunction started only yesterday after the auto-update. I am on a Spanish GSM network, but I guess that's not of much relevance. The phone is running Gingerbread 2.3.4.
Tks for any suggestions.
t.
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Having that same issue. Not only does not "Ok Google" work, even after enabling it in the watch's settings, even when pressing down the crown, the whole thing is extremely slow. Furthermore, for sending a message, the "Ok" doesn't time out after a couple of seconds in order to send the message automatically. It requires me to tap the screen.
All in all, its looking more like a downgrade for me. The whole system feels sluggish and incoherent from a usability standpoint of view.
Edit: Didn't factory reset the watch after update
I have an another problem. Google Assistant isn't launched in Czechia yet and there isn't Google Now in Android Wear 2. So, I lost any speech control.
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Mr.Caution said:
I've too had issues with "OK Google" after Android Wear 2.0 install. I did get it sort of working after a device reset and reconnect to my phone. (Samsung Note 5). Its slow!! and now for sending text messages you have to confirm with a tap. All in all the functionality went down....
Anyone know how to revert back to the old rom?
Click to expand...
Click to collapse
So another issue is that even after going to the stupid settings where you actually have to enable Ok Google from any screen on your watch, it STILL wont work. I can only get it to work by using the power button which has a huge delay and then only when I am connected on Wifi. For some reason it no longer works when on my normal cellphone connection.
The phone is super laggy, battery dies fast...its a MESS.
Basically my watch is useless now for all the things I need it to do daily
Mine only works if i go and disable Bluetooth and enable WiFi else it complains it can't contact Google. Play store is the same too. Slow lagging assistant is not good especially sending txts with no auto send
Sent from my Moto G (4) using Tapatalk
Same issue here. "OK Google" is the most important feature...
You need to give permissions for the OK Google to work. Didn't notice about it until I read this thread (I think most particularly Phone access)
shaolin95 said:
So I got the upgrade but now I am unable to use the voice command Ok Google from watch face as before. I can only get it working by holding power button and even then it seems just laggy.
Anyone else having this issue activating it by voice?
Thanks!
Click to expand...
Click to collapse
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
venzislav said:
Yes , it is the same on my watch - it is laggy ! I am looking for a way to downgrade back to old android wear.
Click to expand...
Click to collapse
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
shaolin95 said:
I just got the ROM from this post and used the flash steps he listed and it worked fine.
https://forum.xda-developers.com/showpost.php?p=71823043&postcount=3
Click to expand...
Click to collapse
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
venzislav said:
Is it possible after downgrade to stop watch from upgrading again to 2.0 ?
Click to expand...
Click to collapse
I want to find out as its annoying to see the upgrade message over and over
shaolin95 said:
I want to find out as its annoying to see the upgrade message over and over
Click to expand...
Click to collapse
Pfff this 2.0 is a big s**t !!!
Doesn't lag on mine using the 2 core or 4 core kernel
almostthere said:
Doesn't lag on mine using the 2 core or 4 core kernel
Click to expand...
Click to collapse
Does OK Google work with voice commands and when not connected to Wifi???
shaolin95 said:
Does OK Google work with voice commands and when not connected to Wifi???
Click to expand...
Click to collapse
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
almostthere said:
Yup mine works perfectly without wifi (have been testing it outdoors since 2 days ago). Fix is to go to apps, system apps, google, permissions, enable permission to phone (maybe others too since IDGAF and ticked all)
Click to expand...
Click to collapse
Would you look at that! It works but WTH is google making it so complicated now for users? Most people dont hang around XDA to know these things. Like for instance apps now need to be downloaded on the phone as its not autmotically done, etc.
Really weird approach.
Thanks for the tip!
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Isham.padron said:
After a factory reset and being extremely patient, I was able to get Ok google to work. You have to go to the store on the app and update all of the apps and then enable, OK google in the settings. Problem is the response time is horrible. I'm going to stick with 2.0 and hope that they roll out updates to make it faster.
Click to expand...
Click to collapse
Responses time is horrible on the initial due to it running on single core at lower clock speeds and on conservative core governor.
Therefore you'll have to give it sometime for it to settle down or if you can't deal with it, you'll have to unlock the bootloader and flash in the dual or quad core enabled kernel file
Running in quad core kernel, battery life seems decent and response real snappy
Well that's just stupid because it worked fine on the previous android wear build. This is dumb on LG's part.
Start from the beginning. Back a few weeks ago, when 4.1.5 was leaked but not officially announced, I downloaded 4.1.5 and flashed it through TWRP. Then 4.1.6 was released officially right after I've done my upgrading. So I CLEAN FLASHED 4.1.6 again on my phone.
Now the weird part: after 2 days of normal use (no flashing, no new apps installed), I left my phone charging today while went asleep. After I woke up, my phone is at 15% of battery. Although connect to the DASH charger, the phone doesn't charge at all with its LED showing red.
More weird is I can't open the notification center. I can pull the 5 toggles down, but can't open the whole menu.
Plus, notifications don't show up (no toast notification, no icons while in the homepage either).
My access to developer options is also blocked (says "Developer options is not available to this user").
The home button, recent apps button DOESN'T work - no matter if u switch the buttons in settings, or toggle the on-screen soft buttons. Although the "return" button and the fingerprint sensor DOES work.
Root access is still there (using Magisk).
While using TitaniumBackup, the app warns "This device's Android ID has changed". And a few apps have logged themselves out (I guess because of the ID change).
I think I can solve the problem by simply factory reset it. But Questions is : what's going on with my phone?
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
elmarian756 said:
Its a common, not so common issue. I had exactly that same issue twice on two different fones. My old xperia L and my oneplus one. In my particular case, this was triggered when my settings were automatically restored from my google account (apps auto download, wifi settings, display settings etc.) After a factory reset.
After this, android id "crashes" showing that it has been changed, and statusbar only allows one pull down, along with the others bugs you described.
You should not allow google account to restore your settings (or at least that worked out for me) and restore manually your data. (Especially your display settings).
Hope it helps, i thought i was the only one.
Click to expand...
Click to collapse
Wow! I can't image someone had the same issue. So i actually re-flashed 4.1.6 and it's working.
But the charging problem persists. I've tried multiple power sources from the room, the kitchen, etc. None seem to be working.
Strangely, I was able to charge the device once a few hours ago at evening. And then it stopped charging again after I got the system working.
Any idea?
Just got this phone days ago and flashed fresh new .205 firmware, then configed the phone and installed apps on it.
Everything appears fine, but suddenly all auto-start apps stop auto-starting after phone boots, until I unlock my phone manually, then finally they can start in the background.
What could cause this to happen? My other phone, Xperia XZP with exact same apps and settings works fine with no problem.
Update: app-start turns normal after disabling PIN. But how? Why? Can I turn it on again?
Update: apps stopped auto-starting again after fingerprint(PIN) is enabled. Really need some help here. Smart lock also appears broken, it just shows a blank screen in its settings page.
Update 2:
OK now I know it's caused by a feature called "FBE" and I have to do a factory reset to get rid of it. So damn great. I hate these companies.
It's been months of on and off again trying to figure this out, still no luck.
I'm running the latest version of Lineage OS.
I'm running the latest download of OpenGAPPs
I'm using a cable that works with my wife's stock moto x4, but does not with mine.
When I connect my phone, I assume android auto tries to start, black screen, then crash back to launcher. My head unit displays "unsupported device"
When i pull down the shade to select a different usb mode, it always reverts back to "no data transfer". Clicking on anything will move the dot, then immediately go back to "no data transfer"
I've tried several troubleshooting guides, I've cleared data and cache for AA, Google, and Play Services.
I'm open to all suggestions.
sythus said:
It's been months of on and off again trying to figure this out, still no luck.
I'm running the latest version of Lineage OS.
I'm running the latest download of OpenGAPPs
I'm using a cable that works with my wife's stock moto x4, but does not with mine.
When I connect my phone, I assume android auto tries to start, black screen, then crash back to launcher. My head unit displays "unsupported device"
When i pull down the shade to select a different usb mode, it always reverts back to "no data transfer". Clicking on anything will move the dot, then immediately go back to "no data transfer"
I've tried several troubleshooting guides, I've cleared data and cache for AA, Google, and Play Services.
I'm open to all suggestions.
Click to expand...
Click to collapse
I thought that was a known Lineage bug. I could never get Android Auto working on Lineage, so I rolled back to stock.
Edit: Here's the open bug https://gitlab.com/LineageOS/issues/android/issues/397
elmerohueso said:
I thought that was a known Lineage bug. I could never get Android Auto working on Lineage, so I rolled back to stock.
Edit: Here's the open bug https://gitlab.com/LineageOS/issues/android/issues/397
Click to expand...
Click to collapse
Interesting. I knew it was an issue for me. not much other talk about it over on reddit for this phone (that i could find). what little i did find was to the tune of "open gapps was messed up from x to y, try installing an updated gapps after y." and that took months for me to do because for the longest time lineage's recovery was messed up, so i figured i'd just check back every now and then. Finally realized recovery was working and here i am. guess I'll go back to stock. Thanks.
Android Auto appears to be working flawlessly after May update of Pixel Experience 10 rom.