I was wandering how to get the newest Google apps even if they are in beta or testing say like the new market being released with gingerbread?
The new market is out, just do a search. For some of these someone pulls them, and then posts them. That's how I've seen it happen. I'm running Market version 2.2.7 right now.
Sent from my other girlfriend, according to my current girlfriend.
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.
If so, could you please let me know what version of Google Play Services it installs on the watch. Slow rollout means I can grab it yet...
See if you can update it from here:
https://play.google.com/store/apps/details?id=com.google.android.wearable.app
Not yet. Not sure what they've updated. The change log stated there seems the same as last time. BUT being hopeful they fixed a few bugs...
Hi all,
I have a simple app in the Play Store with an Open Beta. Would anyone like to beta test it and send me any crash / lag / etc... info they get?
Thanks a bunch in advanced!
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.