Google Assistant on screen resolution less than 720p - Android Q&A, Help & Troubleshooting

Google has rolled out Assistant support for tablet devices with the latest update. However there are certain RAM(>1.5 gb) and screen resolution (> 720p) constraints for enabling it.
Has anyone been able to run the assistant with lower screen resolutions ?I have a 1024x600 resolution device. I have been able to change the resolution with adb shell wm size to 1024x720 when connected to the device shell over wifi. This however, reduces the width of the screen and squeezes everything up even though Google Assistant starts working magically.
There must be a way to bypass the screen resolution check (WITH ROOT) or just fake it without actually changing the display . Have heard about Assistant Enabler on XPOSED but I'm scared I might brick my device with that unless someone has tested it already on it. Is there a better way ?
PS: Device is a Joying car entertainment unit (Intel Sofia) on android 6.0.1 .

Screen resolution 1228x720 seems to work good enough. I also changed the font size to huge

Google assistant on low res devices
Hi I'm Paul,
I AM DISABLED IN A WHEEL CHAIR I did have this running on a z80 full lollipop android watch and it worked great, for a whole year then the low res issue was installed on updates. This no longer works so I am also looking for a solution, for my new q1 pro watch running marshmallow.
please let me know how you resolve this if you can thank you, as I am wheel chair bound and the assistant on my wrist watch was invaluable.
Kind regards
Paul.
akshayarajdayal said:
Google has rolled out Assistant support for tablet devices with the latest update. However there are certain RAM(>1.5 gb) and screen resolution (> 720p) constraints for enabling it.
Has anyone been able to run the assistant with lower screen resolutions ?I have a 1024x600 resolution device. I have been able to change the resolution with adb shell wm size to 1024x720 when connected to the device shell over wifi. This however, reduces the width of the screen and squeezes everything up even though Google Assistant starts working magically.
There must be a way to bypass the screen resolution check (WITH ROOT) or just fake it without actually changing the display . Have heard about Assistant Enabler on XPOSED but I'm scared I might brick my device with that unless someone has tested it already on it. Is there a better way ?
PS: Device is a Joying car entertainment unit (Intel Sofia) on android 6.0.1 .
Click to expand...
Click to collapse

Great article
Does anyone have a actually solution to this issue? I've tried chasing resolution on my watch this almost bricked it but I managed to reinstall firmware also tried assistant enabler which did nothing as I can't root my watch coz I can't find a boot loader or twerp for it

plz help make google assistant work on 1024x600 device

Related

[Q] 4:3 Android Tablet: 16:9 HDMI output possible?

Hi there!
Hope someone can help me here...
I have a 10" Teclast A10t (Allwinner A15 CPU, based on Cortex a8) running ICS which sports an HDMI Output.
Now, I'd like to use it as a upnp client hooked up to a widescreen 1080p display via HDMI,but the picture I get on the big display is always 4:3 which ends up being either an incredible waste of display when playing widescreen media or quite blurry and overall fugly when stretched to fit the screen using the display's settings (and, of course, it's stretched which makes watching movies not exactly enjoyable).
Anyways, I can't find an option to select the AR of the HDMI output... Does anyone here know how to do the trick? Am I overlooking something, is there an app for that (tm) or am I just f*cked and it's not achievable?
Tried CM9, CM10, googled around for hours qnd searched the market but to no avail...
Thanks in advance
Eck
Hi same here... well almost.
I have rk3066 tablet, screen resolutinon 1024x768 (4:3).
Output via HDMI gives picture that is not corect. Circles are not circles anymore ,but horizontal elipses
skymanuva said:
Hi same here... well almost.
I have rk3066 tablet, screen resolutinon 1024x768 (4:3).
Output via HDMI gives picture that is not corect. Circles are not circles anymore ,but horizontal elipses
Click to expand...
Click to collapse
You can do this with AOKP I believe.
You can use Resolution Changer to change the resolution from 4:3 to 16:9 (https://play.google.com/store/apps/details?id=com.lugalabs.resolutionchanger&hl=en).
Note: The app REQUIRES ROOT.
I had the same problem as my 4:3 tablet has an HDMI output, yet when connected to a 16:9 TV, the picture was stretched making circles turn into horizontal ovals. I also tested this with Chromecast and it worked well, too.
The SecondScreen app (free) and a bit of additional research let me find a way of getting this working without having to root.
This solution will work well for those that want to use a 4:3 tablet (e.g. 9.7" 2048x1536) with HDMI and/or Chromecast/Miracast on a 16:9 format screen (TV/projector) and have found the picture looks squashed (egg.shaped instead of round). This will fix those problems well WITHOUT needing to root. It just needs a little effort to install this properly.
First of all, you need to install SecondScreen on the tablet (or smartphone).
Then you need a PC (preferably Windows 7 as anything higher needs additional security steps) with Google Chrome installed and a bit of patience.
Follow the instructions on this page up to and including step 6:
https://medium.com/sentio-superbook/enabling-sentio-desktop-dpi-resolution-change-d1a0b40e2c84
For step 7, use this exact command, instead: pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS
After that, you can proceed to setup the app, there are now no more root issues and it works well. I recommend setting up profiles with 160 (for smaller and more text on screen) and 240 dpi (normal size). If you go higher than that, you start losing icons on your desktop that have to be setup again.
Alternatives:
If you just want to play videos properly, use VLC Player as that natively sends the videos in the correct aspect ratio to the TV (second screen method). This also works well with Chromecast.
For images, Google Photos does have a cast button, that will then display the images in the correct aspect ratio on Chromecast - this will NOT work with HDMI. Showing still images with Chromecast is somewhat frustrating, as the pictures are often pixelated at first and by the time they look good, the slideshow goes on to the next picture. HDMI is MUCH better than Chromecast in this aspect. Pity that many Tablets do not have an HDMI port.
My recommendation is clearly to use the HDMI port and this solution, when showing videos and images. HDMI is much easier to use (just plug in the cable), as well. If your tablet does not have an HDMI port, Chromecast is just as good with videos, but worse with still images. Chromecast also requires a local Wi-Fi router and internet connection to work. Miracast does not require a local Wi-Fi or internet, but suffers from pixelation the most. This could be OK for static slides, but videos rarely look good on Miracast.

[APP][2014.12.08] TVHZ

This app allows you to switch the hertz of your display. This is a tool for advanced users, please read this entire description. Hopefully this app will be obsolete sooner rather than later.
If you have a compatible TV or monitor, you may want to view specific content on a different hz. Apps can actually switch the hz used by your device. This feature is new to Android, and thus very few apps support it yet, which is the main reason an app like this one can come in handy.
Unfortunately, at the time of this writing, even if developers added this functionality to their apps (devs: check preferredRefreshRate in WindowManager.LayoutParams), it may not work right or at all. There are several issues with Google's current implementation, as it exists on the Nexus Player, firmware LRX21V:
- The available modes appear to only be detected on Android TV boot. This means your TV or receiver needs to be turned on and switched to the correct input before booting the Android TV device, or not all the modes your TV supports will be recognized.
- Switching hz may break audio. This app provides an option to fix that, but that does require your device to be rooted. Note that this may be both Android TV device as well TV dependent - your setup may not display this issue.
- Switching hz may randomly reboot the device
- The Android API lies. It'll happily report the current refresh rate to be X hz while it is actually Y hz, which may cause timing issues for video apps that actually take refresh rate into account.
- There is no hz override in display settings
So, until these things are fixed Google-side - and it would actually start to make sense for developers to include the functionality in their apps - at least you can play around with this.
Note that 'forcing' a certain hz might be wording it too strong. Android is still free to ignore the setting, and if an app really wanted to, it could override it as well.
Disclaimer: works for me, provided as-is, this app has no support, the situation describe above may change at any time
Why?
I was looking at committing this feature into xbmc/kodi, so I built a quick proof-of-concept app first, as I has not used the API before. During testing I quickly noted that the API doesn't work reliably enough yet to be part of that project.
Download
Google Play (this link is pending Play cache update and Play team approval)
Gonna be a bit off-topic here, sorry about that.
I don't have a Nexus Player, but changing the external display's refresh rate was one of the features I wanted for a long time, it was the last missing thing to have a nice, smooth movie playback experience in an app like xbmc/kodi.
How device-dependent is this app? Can I use it on a N5 for instance? (or a Chromecast?) It has power to pretty much play any video file, it has an 1080p display and can send 1080p through hdmi, so a ~24 hz refresh rate for movies is all that's missing.
It's nice to see Android itself supporting this (even if it currently broken as you say).
What about the external display's modes or the external display's resolution, can they also be changed? The other problem for a good movie experience is with devices not having an exact 1080p display (like the N7 2013). Since the external display is always mirrored (and not extended), the device's 1920*1200 image will be shrunk to the TV's 1920*1080 screen leaving black bars on the sides which really sucks. I've seen some root-required hacks for the N7 2013 to force a standard 1080p resolution, but that's not a real solution... It would be nice to have these sorted out, because until that, even a Raspberry Pi provides a way superior movie-experience than pretty much any Android-powered stuff...
Will this work on the ADT-1?
What about 120Hz TVs?
I dont see 120Hz in the selection is that because of some limitation?
scorpeeon said:
Gonna be a bit off-topic here, sorry about that.
I don't have a Nexus Player, but changing the external display's refresh rate was one of the features I wanted for a long time, it was the last missing thing to have a nice, smooth movie playback experience in an app like xbmc/kodi.
How device-dependent is this app? Can I use it on a N5 for instance? (or a Chromecast?) It has power to pretty much play any video file, it has an 1080p display and can send 1080p through hdmi, so a ~24 hz refresh rate for movies is all that's missing.
It's nice to see Android itself supporting this (even if it currently broken as you say).
What about the external display's modes or the external display's resolution, can they also be changed? The other problem for a good movie experience is with devices not having an exact 1080p display (like the N7 2013). Since the external display is always mirrored (and not extended), the device's 1920*1200 image will be shrunk to the TV's 1920*1080 screen leaving black bars on the sides which really sucks. I've seen some root-required hacks for the N7 2013 to force a standard 1080p resolution, but that's not a real solution... It would be nice to have these sorted out, because until that, even a Raspberry Pi provides a way superior movie-experience than pretty much any Android-powered stuff...
Click to expand...
Click to collapse
First, this app is written only with the main display in mind. As such, it won't work for external displays as it seems you are after. It won't work on an N5 or N7 either as this incarnation of the app only has a TV interface. It won't run on a Chromecast, because that doesn't actually run Android apps. Also, I'm pretty sure the main screens of the N5 and N7 only support 60hz.
That being said, and I have never tried this myself (I really should get a mini-HDMI cable to I can play with this stuff), so take this with a big grain of salt, but from what I've seen and read, the scaling and mirroring you mention is app-based. The Android API does provide mechanisms to display content in the full resolution of the external display (since API 17), but the app requires (potentially a lot of) extra code to do this. The mirroring (and thus auto-scaling) is merely the default thing Android does when an app does not override that behavior. Quickly checking the API docs, it also appears to be possible to adjust the hz of the secondary display in the same way (since API 21). However, again, the currently active app is the one who must control this.
TVHZ uses a trick to get around the restriction of having to be the currently active app. It does not appear this trick can be used the same way to control the hz of an external screen, through the regular API. This does not necessarily mean it isn't possible (without root), it just means more investigation would be required to know for sure.
xamadeix said:
Will this work on the ADT-1?
Click to expand...
Click to collapse
I have not tried.
the_mentor said:
What about 120Hz TVs?
I dont see 120Hz in the selection is that because of some limitation?
Click to expand...
Click to collapse
No. 120hz is display panel refresh rate, not an input refresh rate. Don't worry about it
With stuff like this the rule is pretty much, if you don't know why you would change it and what you would change it to, you're probably best off with the default (unless someone specifically tells you otherwise).
Chainfire said:
First, this app is written only with the main display in mind. As such, it won't work for external displays as it seems you are after. It won't work on an N5 or N7 either as this incarnation of the app only has a TV interface. It won't run on a Chromecast, because that doesn't actually run Android apps. Also, I'm pretty sure the main screens of the N5 and N7 only support 60hz.
That being said, and I have never tried this myself (I really should get a mini-HDMI cable to I can play with this stuff), so take this with a big grain of salt, but from what I've seen and read, the scaling and mirroring you mention is app-based. The Android API does provide mechanisms to display content in the full resolution of the external display (since API 17), but the app requires (potentially a lot of) extra code to do this. The mirroring (and thus auto-scaling) is merely the default thing Android does when an app does not override that behavior. Quickly checking the API docs, it also appears to be possible to adjust the hz of the secondary display in the same way (since API 21). However, again, the currently active app is the one who must control this.
TVHZ uses a trick to get around the restriction of having to be the currently active app. It does not appear this trick can be used the same way to control the hz of an external screen, through the regular API. This does not necessarily mean it isn't possible (without root), it just means more investigation would be required to know for sure.
I have not tried.
Click to expand...
Click to collapse
This is amazing.. Will it work on a ouya do you think?
Chainfire said:
This app allows you to switch the hertz of your display. This is a tool for advanced users, please read this entire description. Hopefully this app will be obsolete sooner rather than later.
If you have a compatible TV or monitor, you may want to view specific content on a different hz. Apps can actually switch the hz used by your device. This feature is new to Android, and thus very few apps support it yet, which is the main reason an app like this one can come in handy.
Unfortunately, at the time of this writing, even if developers added this functionality to their apps (devs: check preferredRefreshRate in WindowManager.LayoutParams), it may not work right or at all. There are several issues with Google's current implementation, as it exists on the Nexus Player, firmware LRX21V:
- The available modes appear to only be detected on Android TV boot. This means your TV or receiver needs to be turned on and switched to the correct input before booting the Android TV device, or not all the modes your TV supports will be recognized.
- Switching hz may break audio. This app provides an option to fix that, but that does require your device to be rooted. Note that this may be both Android TV device as well TV dependent - your setup may not display this issue.
- Switching hz may randomly reboot the device
- The Android API lies. It'll happily report the current refresh rate to be X hz while it is actually Y hz, which may cause timing issues for video apps that actually take refresh rate into account.
- There is no hz override in display settings
So, until these things are fixed Google-side - and it would actually start to make sense for developers to include the functionality in their apps - at least you can play around with this.
Note that 'forcing' a certain hz might be wording it too strong. Android is still free to ignore the setting, and if an app really wanted to, it could override it as well.
Disclaimer: works for me, provided as-is, this app has no support, the situation describe above may change at any time
Why?
I was looking at committing this feature into xbmc/kodi, so I built a quick proof-of-concept app first, as I has not used the API before. During testing I quickly noted that the API doesn't work reliably enough yet to be part of that project.
Download
Google Play (this link is pending Play cache update and Play team approval)
Click to expand...
Click to collapse
Good job man, thanks for developing for the nexus player
Absolutely awesome!
Hopefully this will work for the Amazon Fire TV in the future too!
Chainfire said:
I was looking at committing this feature into xbmc/kodi, so I built a quick proof-of-concept app first, as I has not used the API before. During testing I quickly noted that the API doesn't work reliably enough yet to be part of that project.
Click to expand...
Click to collapse
FYI, I've also dabbled with refresh rate switching with Kodi, very WIP code (i.e. full of commented trial-and-error code ) is at https://github.com/anssih/xbmc/commits/android/refreshrate_wip (2 commits).
I also noticed the audio breaking (haven't investigated further yet), but I didn't see any reboots occurring.
If I remember correctly, this did not work on ADT-1 last I tested.
dsfdfsdfs said:
FYI, I've also dabbled with refresh rate switching with Kodi, very WIP code (i.e. full of commented trial-and-error code ) is at https://github.com/anssih/xbmc/commits/android/refreshrate_wip (2 commits).
I also noticed the audio breaking (haven't investigated further yet), but I didn't see any reboots occurring.
If I remember correctly, this did not work on ADT-1 last I tested.
Click to expand...
Click to collapse
The audio breakage occurs in device-specific code, so it may not happen on different devices. On the other hand, it may have been an oversight in the Android framework itself that many TVs will disconnect the audio channel as well when switching hz's - in essence completely severing the connection and building it up again.
Fixing the audio can be done by manually killing /system/bin/mediaserver (it is automatically restarted after a few seconds), or calling "stop media && start media". As a side effect this may actually crash apps using audio (or video) at that time, so actually doing this at the start of a video is not really an option - even if it didn't require root and wasn't device-specific.
The reboot is rare, but I've switched hz's a couple of hundred times now, and it does happen.
Glad to see someone else is looking at this though, if you put it in Kodi (when it actually works) that means I won't have to
Chainfire said:
The audio breakage occurs in device-specific code, so it may not happen on different devices. On the other hand, it may have been an oversight in the Android framework itself that many TVs will disconnect the audio channel as well when switching hz's - in essence completely severing the connection and building it up again.
Click to expand...
Click to collapse
Sorry, by "not working on ADT-1" I meant that the refresh rate switching wasn't working there.
Anyway, the HDMI audio stuff is one-way communication (except for EDID, which can't be "disconnected" in that sense), so there is no "disconnecting the audio channel" from the TV side.
Chainfire said:
Fixing the audio can be done by manually killing /system/bin/mediaserver (it is automatically restarted after a few seconds), or calling "stop media && start media". As a side effect this may actually crash apps using audio (or video) at that time, so actually doing this at the start of a video is not really an option - even if it didn't require root and wasn't device-specific.
The reboot is rare, but I've switched hz's a couple of hundred times now, and it does happen.
Glad to see someone else is looking at this though, if you put it in Kodi (when it actually works) that means I won't have to
Click to expand...
Click to collapse
Argh, and I was thinking the opposite here But yeah, I'll work on it as long as time permits.
Have you reported the audio/reboot issues to Google yet?
dsfdfsdfs said:
Sorry, by "not working on ADT-1" I meant that the refresh rate switching wasn't working there.
Click to expand...
Click to collapse
I wasn't implying it might work on any specific device, just that at least the log spam from the audio issue come from a fugu-specific driver, a different driver may behave differently, or not if it's really a framework issue. Anyway, we're knee-deep in speculation here, it matters not.
Anyway, the HDMI audio stuff is one-way communication (except for EDID, which can't be "disconnected" in that sense), so there is no "disconnecting the audio channel" from the TV side.
Click to expand...
Click to collapse
I'll admit I know nothing about these things, but if the TV cuts all power to the port, wouldn't the device 'sense' that and possibly interpret that as a disconnect?
Argh, and I was thinking the opposite here But yeah, I'll work on it as long as time permits.
Click to expand...
Click to collapse
Maybe my test videos weren't great, but I didn't think things looked noticably better at 24hz than they did at 60hz. Though admittedly that may be related to the renderer not actually knowing the display is at 24hz. It was more of an experiment for me than that I truly need it - I have some other issues to figure out with my NP that have higher priority.
Have you reported the audio/reboot issues to Google yet?
Click to expand...
Click to collapse
Nope, because I have not had the time (or will) to produce a decent error report yet.
Chainfire said:
I'll admit I know nothing about these things, but if the TV cuts all power to the port, wouldn't the device 'sense' that and possibly interpret that as a disconnect?
Click to expand...
Click to collapse
Yeah, though I'd be somewhat surprised if that happens - if the source device sees a disconnect/reconnect, it may consider the to be a "new device" and do all sorts of enumeration... but anyway, as you said, pointless to speculate really
Chainfire said:
Maybe my test videos weren't great, but I didn't think things looked noticably better at 24hz than they did at 60hz. Though admittedly that may be related to the renderer not actually knowing the display is at 24hz. It was more of an experiment for me than that I truly need it - I have some other issues to figure out with my NP that have higher priority.
Click to expand...
Click to collapse
Yeah, I too have a hard time seeing the 24/60Hz difference with most videos - not immediately sure if renderer thinking it was 60Hz could cause visible issues, though. With 25/50p European TV footage the 50/60Hz difference is more pronounced.
Chainfire said:
Nope, because I have not had the time (or will) to produce a decent error report yet.
Click to expand...
Click to collapse
OK. I'll probably make one after I've had the time to gather some more data/info.
Update?
Can anyone update me on the current status of frame rate switching for android tv, specifically within Kodi? I'm hoping by the time the Shield console comes out I will be able to playback movies at 24hz.
anyone? I've searched around and haven't been able to find if this has been officially implemented in any apps.
Chainfire said:
This app allows you to switch the hertz of your display.
Click to expand...
Click to collapse
Will your tool conflict with modes that are built in to integrated Android TVs, such as the forthcoming Sonys?
please get 24hz working on the Shield Tv
This is now finally implemented in Kodi (version 15.0 Beta 2, on Google Play, formerly XBMC). It works in at least Nexus Player and Shield TV, but should work in any Android system that supports refresh rate switching. You need to enable automatic refresh rate switching in the Kodi video settings.
I wrote the support back in December, but the problems mentioned in this thread prevented putting it in officially until now. Those issues seem to have been resolved in the Android versions released since then.
Works, somehow
The app does it job, although it seems to reset to 60Hz at reboot (even with the option set to keep at reboot).
Now, I agree, Google should set the output Hz to match the video stream at hand. Yes, it will be a short blackout, but so what!?.
Thanks for the app. I'm running it on the latest 6.0 available today.

How does Superscreen work?

Hi guys... I am new to this forum and therefore couldn't post to the developer forum, even though I am one.
There is this Kickstarter campaing "Superscreen" which promises to give you a low-cost, tablet-like device, which streams your phones display to the 10" "Superscreen". They make several interesting claims on their FAQ section:
- the devices uses no mirroring... they seem to use their own streamingprotocol from within an app, you have to install on your phone (no Chromecast or something like that involved).
- the stream displayed on the tablet part is not bound to the phones resolution! So they claim that a 4k video on a 1080p phone will be displayed as 2k on the tablet (which is 2k) (and I understand that they do not use upscaling)
- you can actually use your phone to do different things than the tablet is doing (so it isn't just streaming)... they call it "dual screen" or something like that
- less interesting, just FYI: The seem to establish a wifi-direct connection between phone and superscreen
Now I am wondering how is that possible and which APIs the Superscreen app is using (they claim it all works on Android 4)?
- I can't find anything in the Android API to grab the whole screen content and to stream it (except for chromecast maybe, which these guys don't use)
- How can the "Superscreen App" convince another video player app and the Android system to render at a different resolution then the phone's?
- How can they render apps offscreen to enable this dual screen thing?
I would love to hear your ideas, as I have no clue how they do it without any rooting and on Android 4...
EDIT: I watched some youtube videos about the product and (while it still may be a prototype) 1) regular apps definetely seem to be upscaled (opposed to what the Kickstarter claims specifically for videos) and 2) there is considerable lag it seems, not suprisingly...

Is it possible to change resolution in stock Oreo?

Hello,
I am waiting for the new Oreo update for my Tab S3 T820. Currently running a Magisk rooted 7.1 version and I have Second Screen installed in order to change the resolution of the screen.
This is needed for mircast to my Microsoft WiFi Direct dongle so I can cast to the TV in 16:9 vs 4:3. I have not found a stock ay to do this resolution change.
Unfortunately rooting the device has caused some apps like my United and Delta video apps to stop working since it detects root and I can't find a way to hide it properly. Magisk hide doesn't work. I would like to get all my apps working properly but this would require a non-rooted device that allowed screen resolution changes.
Has anyone who has seen Oreo on the Tab S3 noticed if you can change the resolution nativly on it?
Thanks.

Screen Mirroring

Though Reno 10 X has wi fi direct, multi screen interaction and DLNA it was not detecting my TV powered by Mi BOX3. I have tried many screen mirroring apps but nothing worked perfectly. With few apps able to mirror but not able to see amazon prime.
Searched on different forums and found a work around. Download Google Home app. Under Account look for additional settings and Mirror device option. Vola, now able to mirror the screen. Its a pity that for a expensive phone, screen mirroring is not straight forward. I had no issues with three year old Xiaomi phones for mirroring.
Hope this issue be addressed in the next software update.
I have no issues with my Fire TV Stick. It's readily available in multi screen option of Reno 10x. Working without lag. No separate application is required for screen mirroring.
I have the same problem .. my phone oppo reno 2f and hope repiar it the next software update or i well change my phone because i nead thins function

Categories

Resources