Is anyone else running the beta version of the Google App and the Chrome Beta having issues getting Google Assistant to open when Chrome Beta is open? Seems to work fine with the regular Google App or regular Chrome. Also, has anyone else noticed that long-press shortcuts don't seem to be working for the beta version of the Google App?
I have noticed that. I thought it was because I was on facebooks website, interesting to know its the apps. Guessing it has to do with chrome. Google Beta + Chrome Stable = assistant works fine for me.
y2whisper said:
I have noticed that. I thought it was because I was on facebooks website, interesting to know its the apps. Guessing it has to do with chrome. Google Beta + Chrome Stable = assistant works fine for me.
Click to expand...
Click to collapse
Same! Google Beta + Chrome Stable = no problems, Google Stable + Chrome Beta = no problems (and long-press shortcuts work), Google Beta + Chome Beta = Google Assistant giving me the cold shoulder.
Edit: Chrome Beta seems to be the problem. Google Assistant wouldn't open with the regular or the beta build of the Google App installed when Chrome Beta was open. Both worked no problem with regular Chrome. Long-press shortcuts seem to be gone from both builds of the Google App as well.
Related
So first time MIUI user. Im liking it a lot, but i can't figure out how to install google voice. I go to the market and search for it, it doesn't come up. I go to the home page of google voice and go to the direct app page and it says no result found. I go to the android market place in the browser and it doesn't do anything when i try to install. Any clues?
That's pretty weird, are you just running stock(ish) MIUI without an altered framework or build.prop? I'm running the latest MIUI using Google voice and it shows up in the market for me.
Hi.
There's two issues with Google Maps in bubor's CM10.2 build 20130902:
1. On a clean install, Voice Recognition is not installed. This makes Google Maps crash when pressing the Voice Search button.
Solution: Install Google Voice Search
2. When Maps is open and the phone goes to sleep (both timeout and pressing the power button work), after turning the screen back on, Maps only displays a white screen (flickering when trying to scroll).
This seems to be an NVidia/GL problem, this pops up in logcat, just before sleep and just after wake up:
E/gralloc ( 115): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
Later, there's multiple failed calls to NvRmChannelSubmit.
Restarting Maps fixes the problem.
Full logcat dump attached.
Solution: I have no idea.
/edit: Same in the 20130904. Keyboard light confirmed working, though.
wuselfuzz said:
Hi.
Restarting Maps fixes the problem.
Click to expand...
Click to collapse
I noticed that I had issues last time I used google maps on my phone, not just sleeping but when switching apps and then switching back to it ... pretty useless if I want to check anything and then go back to the phone when using GPS to navigate.
Maybe re-applying GAPPS might fix it, just don't update gmaps anymore ... ?? ... I donno man.. pretty BS they dropped support of our phones because of lack of neon support. Our hardware is still to this day more than adequate ... side by side, my phone is faster response than an S3 with JB.
The new GMaps is still buggy. The glitches are present on other devices as well.
Sent from my LG-P880
Adam77Root said:
The new GMaps is still buggy. The glitches are present on other devices as well.
Click to expand...
Click to collapse
Other devices as in other Tegra 2 devices, or all 4.3 devices?
I found a post referring to a similar issue on the nvidia devzone where it turned out to be an application problem.
Google Earth does not show this issue. Can't do a logcat right now, but I suppose that's an EGL application, too.
/edit: Alright, I just learned that Google Maps 7.x is pretty new (first 7.0.0 release in July) and that downgrading to 6.14 might solve my issues. Oh the outrage in Google Maps for Android product forum on Google Groups.
/edit2: http://productforums.google.com/forum/#!category-topic/maps/mobile-android/aRr10hYi8AU[1-25-true]
I'm on a Tegra 3 device, the LG O4X HD and do experience the issue sometimes.
Sent from my LG-P880
Glide with CM10.1.2, same issue except my Maps goes black.
Adam77Root said:
The new GMaps is still buggy. The glitches are present on other devices as well.
Sent from my LG-P880
Click to expand...
Click to collapse
thanks for clarifying that for us!
This thread has a link to the latest Maps 6 (6.14.4):
http://forum.xda-developers.com/showthread.php?t=2357873
It works just fine without those issues mentioned above.
I also had the black screen issue in Maps when switching apps. As others reported, this issue is not present in Maps version 6 so I downgraded to this version.
Now I'm wondering if there is a way to fix Maps to version 6? It is annoying to update the other apps one by one, since clicking in the "Update all" button in Google Play will update Maps as well.
Same issue
I have the same issue on v7.2 with both CM and Stock Rom.
My device is the Captivate Glide (i927)
I notice that some users are reporting that through Google Play they can update to Maps 7.x, however I am unable to do so, from Google Play i can only update to Maps version 6.14.4 on my 4x HD.
What firmware version are the people getting 7.x running?
Regards,
Cecu
wuselfuzz said:
Hi.
This seems to be an NVidia/GL problem, this pops up in logcat, just before sleep and just after wake up:
E/gralloc ( 115): NvGrPost: Failed, TEGRA_DC_EXT_FLIP 6 No such device or address
/edit: Same in the 20130904. Keyboard light confirmed working, though.
Click to expand...
Click to collapse
I suspect that this may be due to too new of a kernel. More specifically, nvidia appears to have made a lot of commits to the tegra kernel drivers. I'm going to take a closer look at the diffs tonight.
Just my $0.02.
Cecu said:
I notice that some users are reporting that through Google Play they can update to Maps 7.x, however I am unable to do so, from Google Play i can only update to Maps version 6.14.4 on my 4x HD.
Click to expand...
Click to collapse
Now on CM 11.0 I have a reverse problem: I can't delete the stock 7.x version of Maps and install working 6.14 version. The only solution I found was to roll back on CM 10.1.3, install 6.14 Maps, make a Titanium backup of 6.14 version, reflash CM 11.0 and restore 6.14 from Titanium backup. But after every reboot Google Maps are reverting to 7.x version. So I have to restore 6.14 backup every time I reboot my phone, and that's rather inconvenient. I glad that the CM 11 is very stable and allows weeks of uptime.
Dear bubor, can you make your next CM build with 6.14 Maps version or without Maps at all? 7.x version isn't working properly on Glide anyway...
Well many people have reported this . . But for the time being as a temp fix you can do this .. it works or me .
http://forum.xda-developers.com/showthread.php?t=2566159
Sent from my SGH-I927 using xda app-developers app
thefusor said:
Well many people have reported this . . But for the time being as a temp fix you can do this .. it works or me .
http://forum.xda-developers.com/showthread.php?t=2566159
Click to expand...
Click to collapse
I froze stock 7.x Maps and installed modded 6.14.4 from this link. Yes, working as intended, thanks!
When I open chrome beta it is not full screen. How do it get it to its usual full size?
Use chrome.
#stayparanoid
Yea I switched to chrome. I guess not using beta isn't that big of a deal. Thanks for the response
Sent from my XT1096 using Tapatalk
I'm going to jump on this thread while it's still fresh, if nobody minds.
I just switched my Nexus 5 from CM11 to PA4.6b6 two days ago, and this is the only remaining issue. I launched Chrome Beta the first time, and it showed up as a small, greyed window in the middle of my screen. Eff that, I said, and looked for advice on the internet. I found this thread, installed Chrome itself, launched that and was pleased to see it occupy the full screen (not immersively, mind you).
I just tapped my Chrome shortcut again moments ago to find that it was now opening in that little, greyed out window. Wtf, I wondered. I tried Beta. Same thing. I closed both windows by tapping the home nav, and then i opened Chrome again from the recent apps list. Et voila, it's back to full size.
My questions are "wtf?", "how do I make it just use the available real estate and not open in that terrible tiny dark window?", and "should I file a JIRA issue for this? Is this srsly expected behavior?"
I love the ROM, I love the work you guys do, and I wanna be helpful, so let me know if there's anything else I can provide or tell you about my experience.
Thank you!
Well, Google pushed their beta changes to stable. The problem is a flag that Google set that launches chrome in windowed mode...
We are trying to figure out a way around it but with work heavy on lollipop right now, kitkat may fall by the wayside.
The temporary solution is to go back to an older version of chrome.
#stayparanoid
I can get behind the idea of work being heavy on Lollipop, so no worries there. I'll be seriously excited to see new builds based on 5.0, so work away! I presume there's no ETA on that as of yet, right? :angel:
No EtA
#stayparanoid
Workaround:
Open Chrome
Hit Home
Relaunch chrome from recent apps
As long as Chrome isn't killed, it will remain full screen.
I also got a backup from Chrome v38.
Will share on request.
Ratmak said:
My questions are "wtf?", "how do I make it just use the available real estate and not open in that terrible tiny dark window?", and "should I file a JIRA issue for this? Is this srsly expected behavior?"
Click to expand...
Click to collapse
No, it's not expected behavior
https://code.google.com/p/chromium/issues/detail?id=423685
franatic08 said:
Workaround:
Open Chrome
Hit Home
Relaunch chrome from recent apps
As long as Chrome isn't killed, it will remain full screen.
Click to expand...
Click to collapse
Nicely found, confirmed on a n7
For anyone running Xposed. Download Xhalofloatingwindow module and blacklist Chrome. That worked for me
Sent from my SGH-T999 using XDA Free mobile app
stastnysnipes26 said:
When I open chrome beta it is not full screen. How do it get it to its usual full size?
Click to expand...
Click to collapse
I'm sorry, but do you mean Chrome beta on Paranoid Android, or just Chrome Beta in general? I have used Chrome Beta before, but this has never happened to me.
cyanogen_patrick said:
I'm sorry, but do you mean Chrome beta on Paranoid Android, or just Chrome Beta in general? I have used Chrome Beta before, but this has never happened to me.
Click to expand...
Click to collapse
Any ROM that has floating mode.....
ANY ROM.
Google has fixed it in their latest beta though.
#stayparanoid
Pirateghost said:
Any ROM that has floating mode.....
ANY ROM.
Google has fixed it in their latest beta though.
#stayparanoid
Click to expand...
Click to collapse
Oh, okay.
Hello there,
I recently purchased a used HTC 10 (original purchase date ~5.2016)...
Every time I am searching the flash deals in the Amazon App (I think I have similar problems with AliExpress too, but I am not able to reproduce this on poruse. Amazon is every time making these problems.), I have this weird scrolling behavior.
Procedure:
1. Open App - enter flash deals
2. scroll list, click on entry, go back
3. scroll further
---> Screen will return to the position, where you last checked one entry by clicking on it.
It looks like the "keyboard-choosing-cursor" is stuck there. (Yellow frame around the entry), and I can't go much further down, until it will scoll up again.
Fixing is going back to previous page, going back again, scrolling down to the last items I was.
This is not the workaround I could live with, since I am very limited on using these apps.
Already shoot some google searches, but only got things like "not responsive touch" etc...
Other apps seems normal, eBay has no such problem since now...
Amazon seems to have this problems only within the flash-sales, not the normal.
For AliExpress I wasn't able to reproduce this on purpose.
Is this a app specific fault? Or is it my device?
I am coming from a M7 with CyangenMod 13 (6.0.1) and I am running on the 10 6.0.1 Stock...
Someone else experiencing this? Or heard about it?
I am very clueless..
Thanks
houston
I've noticed this behaviour too with Swipe for Facebook and Chrome Browser. I could reproduce with Swipe by opening an external link with, for example, a floating browser like Flynx, returning to Swipe app i can't scroll well, same behaviour as your. I noticed that to the dev and it comes with a fix, but in the same time i had an update from Google Webview (Beta) in the Play Store, so i can't say who was the guilty one., but I don't have this problem now.
I make these statements because both Swipe for Facebook, Chrome Brtowser and Amazon use html wrapper/webview, but i can be wrong.
I just received the instruction to update webview from the amazon support.
Well ... I oped out the beta program, reinstalled webview and now I am fine
I have read your post to late. But you are mentioning webview too, so I think it is all about webview. Do you use the beta too?
Conclusion for me:
WebView Beta was the culprit. Reinstalling the stable fixed it for me.
houston_ said:
I just received the instruction to update webview from the amazon support.
Well ... I oped out the beta program, reinstalled webview and now I am fine
I have read your post to late. But you are mentioning webview too, so I think it is all about webview. Do you use the beta too?
Conclusion for me:
WebView Beta was the culprit. Reinstalling the stable fixed it for me.
Click to expand...
Click to collapse
Today another update from WebView BETA
benzo said:
Today another update from WebView BETA
Click to expand...
Click to collapse
Fixing it again?
I think I will stay with stable
It happens with beta chrome and webview. If an item is selected it will scroll back to that item. It has to stay in the viewport. Just deselect the item to fix it.
Dear friends,
I'm using Epic ROM MIUI 9 (https://forum.xda-developers.com/mi-6/development/epic-rom-7-6-8-epic-team-mrraines-mi-6-t3619699).
Using Google Chrome, or Chromium, or any derivative of those (RSBrowser, YuBrowser, Chrome Canary/Beta, Brave and others), I'm getting the following "address bar bug":
http://en.miui.com/thread-1008044-1-1.html
as seen on: https://www.youtube.com/watch?v=w0E5l6PgYXQ
As from this reports, the bug doesn't seem to be neither Custom Rom, MIUI 9 nor Mi6 exclusive.
This bug happens 100% of the time on any Chrome/Chromium (original or derivative), and Microsoft Edge. I've tried a bunch of "flags" on Chrome browsers and nothing changed.
Is anyone able to use any Chrome based browser without that bug? How so??
prytoluk said:
Dear friends,
I'm using Epic ROM MIUI 9 (https://forum.xda-developers.com/mi-6/development/epic-rom-7-6-8-epic-team-mrraines-mi-6-t3619699).
Using Google Chrome, or Chromium, or any derivative of those (RSBrowser, YuBrowser, Chrome Canary/Beta, Brave and others), I'm getting the following "address bar bug":
http://en.miui.com/thread-1008044-1-1.html
as seen on: https://www.youtube.com/watch?v=w0E5l6PgYXQ
As from this reports, the bug doesn't seem to be neither Custom Rom, MIUI 9 nor Mi6 exclusive.
This bug happens 100% of the time on any Chrome/Chromium (original or derivative), and Microsoft Edge. I've tried a bunch of "flags" on Chrome browsers and nothing changed.
Is anyone able to use any Chrome based browser without that bug? How so??
Click to expand...
Click to collapse
No issue for me with Chrome beta (browser) / SwiftKey (keyboard) / latest xiaomi.eu build / Mi6
Sent from my MI 6 using Tapatalk
axman79 said:
No issue for me with Chrome beta (browser) / SwiftKey (keyboard) / latest xiaomi.eu build / Mi6
Sent from my MI 6 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply!
I've tried installing the latest Chrome beta and SwiftKey, rebooting the phone, and the problem persists, as seen on the attached gif...
I'm thinking that should be a ROM related issue, or some obscure configuration I did. That's weird...
I've found the fix!!!
I had turned off the "Activate MIUI optimization" on Developer Options.
Turning it back again instantly fixed the issue!
This is entirely MIUI BUG. I had it even on my Mi5 (any miui based rom)