Related
I'm in Canada, and it won't show up on the store unless I (presumably) spoof my location. I know people have had it working from other countries already - could someone upload this? Much appreciated!
f3tf said:
I'm in Canada, and it won't show up on the store unless I (presumably) spoof my location. I know people have had it working from other countries already - could someone upload this? Much appreciated!
Click to expand...
Click to collapse
I live in Canada and it installed and works great, so you should have no problems.
Yes, I'm a retard. There's a link to the app from the Shield store (when you press the home button), but this goes no where in the google play store - turns out the GRID beta was already installed on my shield automatically with update 65. Found under all apps.
Could someone rip it for me?
It ism't working for me in Indonesia, it is not installed in the update, I don't want to wait to get back to the UK, I'm here for a couple of months
Agree, grid beta apk is needed. Someone please upload apk.
please upload apk
thanks
Grid working in uk!
Hi,Grid is working in northern Ireland In the UK On the shield!
here you go
Here you go! http://icloudserv.com/gridapp.apk
But it will only work on Shield (I tried on my HTC one and it says "this device is not supported") I also tried to open file and change something, but everything is encrypted , and other files dont have needed information on how to change the file to work with Every Android device, as far as I understand Cloud Gaming has nothing to do with NVIDIA TEGRA GPU. Is it possible to decrypt it and make see Remote Desktop with all graphic Features such as D3d or OpenGL? Kelper GPU supports passthrough.
iCloudServ said:
Here you go! http://icloudserv.com/gridapp.apk
But it will only work on Shield (I tried on my HTC one and it says "this device is not supported") I also tried to open file and change something, but everything is encrypted , and other files dont have needed information on how to change the file to work with Every Android device, as far as I understand Cloud Gaming has nothing to do with NVIDIA TEGRA GPU. Is it possible to decrypt it and make see Remote Desktop with all graphic Features such as D3d or OpenGL? Kelper GPU supports passthrough.
Click to expand...
Click to collapse
Nether Tegra Note 7 support it.
From nvidia forum:
"The TegraNote 7 doesnt have integrated 5Ghz wifi in it, which we know can result in some stuttering. "
Só maybe you device should have integrated 5GHz wifi to work.
Hi,
Maybe changing the build.prop might help?
http://forum.xda-developers.com/showthread.php?t=1948558
As for the 5Ghz routers, that's only a recommendation. I live in Portugal (170+- latency), and I can play Grid just fine with my 2,5Ghz routers (RT-N16 with Tomato).
Obviously they should be fined tuned to offer the best possible performance to wireless clients.
Anthonws
try a logcat while launching the app to see why it's unhappy. On one device I had, Tasker installed but would not run without one of the framework files supplied by Maps. Just copying in the framework file was enough to get Tasker running, didn't need the app itself.
Anyone tried a nodded build prop? It would be cool to get this working on a nexus 10
Thought I would start a thread for chromecast mirroring, I have tried without success to get this working. Chromecast works perfecty in the normal way and is great.
Chromecast firmware latest 17977
Chromcast app 1.7.4
MirrorEnabler v1
Crombi-KK latest build 0719 on internal
Logcat attached
mirror enable
I have try it and it hasn't work for me i hear there has to be file directory with : audio.r_submix.default. I ask the same question on crombikk rom and they told me that the file is there but it still doesnt work. I have been trying to use it with r3pwn experimental apk found here http://forum.xda-developers.com/hard...evice-t2812193
I haven't actually had a chance to look at this properly yet. When I get around to it I'll have a play. I see there are other tegra 3 devices working so there is hope.
I believe in the thread for the chromecast screencasting any device thread there's a known issue with devices with Tegra chips. If memory serves me well, there's some kind of issue one of the libraries and it being closed source so where is needed is not being properly accessed.
I'm not sure, but I don't believe any of the officially supported devices, right now, are running Tegra chips, so it's possible a fix won't be found till a Tegra device is officially supported.
Thanks. I have seen reports of people with tegra 3 devices saying it works for them so I have hope. I think the bigger issue is with tegra 2 devices which sounds like the problem you described.
Only progress I have made so far is to update to v5 mirror enabler, try the various options in there, and also tried different resolutions. Without success I'm afraid.
I might root my HTC one x+ just to try this out on.
Tegra 3 does support. miracast which is the same as. Mirroring. AFIK. Here is a good read: http://en.m.wikipedia.org/wiki/Miracast
OK, I have spent a bit of time digging with this. I can see a few options that may help. I still seem to get ApOpps errors with audio and CM11 has a known problem with this, however a fix may be to use this patch;
http://review.cyanogenmod.org/#/c/69871/ However I don't know how to do anything with that information. I can't see an obvious flashable zip and assume I would need to make one, but don't know how. It sounds like this is what may be causing the crashes when we try to stop casting.
The blank screen issue may be solved with this;
Check the BoardConfig.mk file in /android/system/device and the config.xml file in /frameworks/base/core/res/res/values directory in the Linux computer you used to compile. Also check hardware_composer.h to determine the HAL version. HAL v1.2 and greater don't require gralloc buffers, but HAL v1.1 requires gralloc buffers. Most likely chromecast is using video buffering. Generally, low ram devices do not use dedicated video buffering since that will reduce available for system/programs. Again I don't think there is anything I can do with this info because I don't compile Crombi-KK.
As far as I can tell we have the audio_policy.conf in /system/etc/ r_submix section added and the audio.r_submix.default.so in /system/lib/hw/
There is a database entry that must be present in go to /data/data/com.google.android.gsf/databases/gservices.db
open that database with sqlite editor and open the overrides and add
name
gms:cast:mirroring_enabled
value
true
I believe that the above is present in our gservices.db but I can't be 100% as I don't have SQLite editor, only a basic "reader" of sorts.
SELinux looks to be disabled so I don't think we need to worry about being in a permissive mode.
If someone from the Crombi-KK dev team wants to look into the above and write me a flashable zip to try I am more than willing to do so. However I don't think there is much more that I can do myself I'm afraid.
I have tried - different versions of mirror enabler with the various fixes in place. I am on latest GPS and chromecast app. I have tried the clear data, etc, etc. Powered the chromecast from an AC plug rather than the TV and I never get anything other than a blank screen. Logcat shows ApOpp audio errors and surface flinger errors. I don't get a GPS crash, the cast screen option exists and appears in the quicksettings with the later versions of mirrorenabler. The tab will "think" it is casting, but I get a blank screen and when trying to stop casting will soft reboot. That is about all I have I think..
Hope that may help someone!
I should also note that I have tried removing ViperFX as this is known to cause some issues with chromecast mirroring. I have tried different kernels and various options for GPU rendering etc, with no success either.
Gudders said:
OK, I have spent a bit of time digging with this. I can see a few options that may help. I still seem to get ApOpps errors with audio and CM11 has a known problem with this, however a fix may be to use this patch;
http://review.cyanogenmod.org/#/c/69871/ However I don't know how to do anything with that information. I can't see an obvious flashable zip and assume I would need to make one, but don't know how. It sounds like this is what may be causing the crashes when we try to stop casting.
The blank screen issue may be solved with this;
Check the BoardConfig.mk file in /android/system/device and the config.xml file in /frameworks/base/core/res/res/values directory in the Linux computer you used to compile. Also check hardware_composer.h to determine the HAL version. HAL v1.2 and greater don't require gralloc buffers, but HAL v1.1 requires gralloc buffers. Most likely chromecast is using video buffering. Generally, low ram devices do not use dedicated video buffering since that will reduce available for system/programs. Again I don't think there is anything I can do with this info because I don't compile Crombi-KK.
As far as I can tell we have the audio_policy.conf in /system/etc/ r_submix section added and the audio.r_submix.default.so in /system/lib/hw/
There is a database entry that must be present in go to /data/data/com.google.android.gsf/databases/gservices.db
open that database with sqlite editor and open the overrides and add
name
gms:cast:mirroring_enabled
value
true
I believe that the above is present in our gservices.db but I can't be 100% as I don't have SQLite editor, only a basic "reader" of sorts.
SELinux looks to be disabled so I don't think we need to worry about being in a permissive mode.
If someone from the Crombi-KK dev team wants to look into the above and write me a flashable zip to try I am more than willing to do so. However I don't think there is much more that I can do myself I'm afraid.
I have tried - different versions of mirror enabler with the various fixes in place. I am on latest GPS and chromecast app. I have tried the clear data, etc, etc. Powered the chromecast from an AC plug rather than the TV and I never get anything other than a blank screen. Logcat shows ApOpp audio errors and surface flinger errors. I don't get a GPS crash, the cast screen option exists and appears in the quicksettings with the later versions of mirrorenabler. The tab will "think" it is casting, but I get a blank screen and when trying to stop casting will soft reboot. That is about all I have I think..
Hope that may help someone!
Click to expand...
Click to collapse
Good info :good: Our source guy @lj50036 needs to review to see if we can implement it
Gudders said:
OK, I have spent a bit of time digging with this. I can see a few options that may help. I still seem to get ApOpps errors with audio and CM11 has a known problem with this, however a fix may be to use this patch;
http://review.cyanogenmod.org/#/c/69871/ However I don't know how to do anything with that information. I can't see an obvious flashable zip and assume I would need to make one, but don't know how. It sounds like this is what may be causing the crashes when we try to stop casting.
The blank screen issue may be solved with this;
Check the BoardConfig.mk file in /android/system/device and the config.xml file in /frameworks/base/core/res/res/values directory in the Linux computer you used to compile. Also check hardware_composer.h to determine the HAL version. HAL v1.2 and greater don't require gralloc buffers, but HAL v1.1 requires gralloc buffers. Most likely chromecast is using video buffering. Generally, low ram devices do not use dedicated video buffering since that will reduce available for system/programs. Again I don't think there is anything I can do with this info because I don't compile Crombi-KK.
As far as I can tell we have the audio_policy.conf in /system/etc/ r_submix section added and the audio.r_submix.default.so in /system/lib/hw/
There is a database entry that must be present in go to /data/data/com.google.android.gsf/databases/gservices.db
open that database with sqlite editor and open the overrides and add
name
gms:cast:mirroring_enabled
value
true
I believe that the above is present in our gservices.db but I can't be 100% as I don't have SQLite editor, only a basic "reader" of sorts.
SELinux looks to be disabled so I don't think we need to worry about being in a permissive mode.
If someone from the Crombi-KK dev team wants to look into the above and write me a flashable zip to try I am more than willing to do so. However I don't think there is much more that I can do myself I'm afraid.
I have tried - different versions of mirror enabler with the various fixes in place. I am on latest GPS and chromecast app. I have tried the clear data, etc, etc. Powered the chromecast from an AC plug rather than the TV and I never get anything other than a blank screen. Logcat shows ApOpp audio errors and surface flinger errors. I don't get a GPS crash, the cast screen option exists and appears in the quicksettings with the later versions of mirrorenabler. The tab will "think" it is casting, but I get a blank screen and when trying to stop casting will soft reboot. That is about all I have I think..
Hope that may help someone!
Click to expand...
Click to collapse
Wow that is a lot of stuff....
Let me take a look and see what I can find
Thx Josh
Updates?
Would really love to be able to use screen cast on crombi kk. Anyone?
I get the same black screen and reboot on 2014-09-06-RC3
I would love to get this to work.
Gudders said:
Thought I would start a thread for chromecast mirroring, I have tried without success to get this working. Chromecast works perfecty in the normal way and is great.
Chromecast firmware latest 17977
Chromcast app 1.7.4
MirrorEnabler v1
Crombi-KK latest build 0719 on internal
Logcat attached
Click to expand...
Click to collapse
Any update on this, folks? I'm on the latest (patched) Crombi-KK, latest Chromecast firmware and app, and MirrorEnabler V6. The "Cast Screen" shows up fine, but I still get the blank screen on the TV. When I "Disconnect" I get the reboot.
Thanks in advance
I am on the lastest release of Crombi-KK with Stability Patch and latest chromecast release. Same problems blank screen then soft reboot. Would love a fix.
Hi, can somebody help me with this please? I want to edit build.prop of Oneplus 7 pro to look like Snapdragon S10+. I know where build.prop is, how to edit it, I have root etc. I just have no idea what edit to what exactly. I want just fool some incompatible apps.
Or at least pls post build.prop of some snapdragon s10+ version which HW is closest to Oneplus 7 pro.
I am noob in this, I was happy to make it with rooting itself, so I would prefer specific answer which lines edit and to what exactly, but I could also use some old guides for other phones if I had S10+ build.prop and info which lines to change.
I also have no idea if I need build.prop from exactly same HW samsung (and if there is 10+ like that - 8gb/256gb) or this do not matter. If I edit build.prop to 128gb variant of samsung and i have 256gb storage will it screw something? Will apps and file managers think I have only 128gb and will it lock half of my storage somehow? I want little to none consequences other than fool app compatibility. Thx for any possible info on this subject
Qué?
Seriously, though... It is not really clear what you are trying to achieve.
Is it that you want the Samsung apps without the OneUI wireframe?
If so, that is not really something you can do - you would need ported versions of the apps and some of them might be so tied into the wireframe that they have dependencies that cannot be ported.
...if it is the overall look you are looking for, then try changing the launcher.
Build.prop edits?? What for???
Edit it to install Heroes III which was supported by Note 8 but cant be installed on Oneplus 7 pro and to unlock 60fps in Fortnite which is 100% supported by snapdragon S10. I had succes with Fortnite but Heroes III still cant be installed, maybe its not supported even in s10, only Note series or I need to edit more lines in that build.prop. I simply need to fake my phone model to something that supports highest FPS in games and has Heroes III support. CoD early acces would be nice too, I will probably wait some time and fake it to Note 10 later
I am here to request the file feature_list in /system/etc to test what works on older oneplus phones and what doesn't. I've already tested warp charge and 90hz screen refresh rate on my OnePlus 7 and both works without issue. Please contribute to help me learn more
Shen Ron said:
I am here to request the file feature_list in /system/etc to test what works on older oneplus phones and what doesn't. I've already tested warp charge and 90hz screen refresh rate on my OnePlus 7 and both works without issue. Please contribute to help me learn more
Click to expand...
Click to collapse
No change in it since 6t. Full engineer mode has been modified on my device and only difference is ways to manually set standalone bands and some carrier specific frequency changes I don't recommend touching.
Modify persist, change eng flags
FullOfHell said:
No change in it since 6t. Full engineer mode has been modified on my device and only difference is ways to manually set standalone bands and some carrier specific frequency changes I don't recommend touching.
Modify persist, change eng flags
Click to expand...
Click to collapse
The file I mentioned adds certain features to OnePlus phones, e.g. OnePlus 7 Pro has the option to switch between 90hz and 60hz but the OnePlus 7 doesn't. If the line that gives the 7 Pro the option to make those changes is added for the 7 as I've done, I can have that feature as well. That's why I'm in need of the file to see what other unavailable features for the 7 is in the newer models
So I know we're still in the early stages of this device. But I just wanted to get a thread going for V4A on our device.
For those who came from the 6 Pro like I did, you're probably already aware of this, but for those who did not here's the current situation:
V4A was working fine on Android 12 but when Android 13 came around there were some issues. For most phones they got ironed out and at this point I think basically every other phone on A13 has V4A working EXCEPT for the Pixel 6/6 pro. I tried installing V4A myself on my 7 pro to no avail. I don't know much about the details of why it's not working or what's going on "underneath the hood" so to speak but I can only assume that whatever it is that's causing V4A to not work on my 7 pro is at least somewhat similar to the reason it doesn't work on the 6 pro. There are a few people trying to figure out the issue in a thread over in the 6 pro section on XDA which I will link here if you want to stay more up to date about what's going on:
https://forum.xda-developers.com/t/anyone-get-viper4android-worked-on-a13.4480467/
As a side note, I did manage to get JamesDSP to work on my 7 pro, which is an okay alternative for the time being. Not exactly the same but it's better than nothing for sure. The main thing I don't like about it is that it doesn't auto switch profiles when you change between audio devices of the same type, for example switching from bluetooth earbuds to bluetooth car speakers.
I use wavelet and it works really well. Always had trouble getting v4a working
Have you tried Viper Android Repackaged?
I just got my device late yesterday, so I haven't bothered rooting just yet, but it's in my plans. There's usually a certain install method to get it working coming from my older devices, but you can try this as well.
GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.
A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.
github.com
The difficulty is now with the Pixel 7 using a different and exclusive cpu architecture, as viper can't even now even attempt to install the driver.
I've reached out to the dev of that one to see what he says....
Update: they got back to me and said as they can't obtain the source code it can't be recompiled to x64.
I see some 'change petition' from 3 years ago asking for it to be updated to x64 but still nothing, and that was years ago.
Ain't looking good for viper on our new pixels by looks of it...
+1 for wavelet. just paid for the full version and the bass booster is prettyy f**king good.
kinda worth the 8CAD$ not to have to deal with Viper issues all the time or everytime the system OS changes.
I found the following program that may be helpful:
Introduction — LIEF Documentation
lief-project.github.io
Maybe it can be used to convert libv4a_fx.so header from 32-bit into a 64-bit library.
sarabraj.singh said:
+1 for wavelet. just paid for the full version and the bass booster is prettyy f**king good.
kinda worth the 8CAD$ not to have to deal with Viper issues all the time or everytime the system OS changes.
Click to expand...
Click to collapse
Does wavelet work at a root level? Any additional battery drain using it, or does it work as well as viper?
Really doubt V4A will ever work again, the project has been abandoned for years.
People try to "patch" it instead, as there has been no real update.
Also the pixel 7 use 64bit only app and drivers, V4A was never updated to use 64bit drivers.
kdrag0n (look on github) has been working on a POC called PhantomAmp to use rootless audio DSP effects.
The app is for patreon sub only for now.
It's in early stage and only a POC so maybe at some point this could be used.
Deadmau-five said:
I use wavelet and it works really well. Always had trouble getting v4a working
Click to expand...
Click to collapse
I honestly always assumed that EQ apps from the google play store were never as good a something like V4A, but I gave Wavelet a shot and I'm really liking it so far. I like that it automatically switches your settings based on what is connected to your phone, a feature I missed from V4A and that was lacking in JamesDSP. I also like that you don't necessarily need to have a persistent notification, it at least gives you the option to swipe it away. Thanks for bringing this to light (can't believe I didn't know about this for so long lol), will be using this now as it seems like a pretty viable alternative to V4A. It's made by the same guy so it's actually quite similar. Will miss spectrum extension and ViPER clarity though.
Dolby Atmos works with some success. The issue is that it will take a few reboots to get your pin/pattern working on your lockscreen.
Be sure to enable USB debugging in case you need to disable the magisk modules if you get locked out (adb shell magisk --disable-modules)
https://www.pling.com/p/1908400
RJR
cd993 said:
Does wavelet work at a root level? Any additional battery drain using it, or does it work as well as viper?
Click to expand...
Click to collapse
+1 on your battery drain question.
It works without root. I don't see battery drain. Doesn't show up on Accu Battery
Deadmau-five said:
I use wavelet and it works really well. Always had trouble getting v4a working
Click to expand...
Click to collapse
As a long time Viper user, thanks for posting this, it's always a little puzzling to me how audio is a distant priority for Google and how much better it sounds with a little external assistance using the same hardware.
Can't lie, I miss the phones (Samsung?) that let you fine tune both left and right output by playing tones and you indicating if you heard them or not and it adjusting each channel specifically to your abilities to hear each frequency band. As someone with unequal hearing damage this really makes audio better on those phones that provide it.
A possible light at the end of the tunnel is this project, they are aiming to reverse engineer Viper and modernise the files (hopefully that means using x64!). We'll just have to monitor the progress....
GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX
Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.
github.com
Deadmau-five said:
It works without root. I don't see battery drain. Doesn't show up on Accu Battery
Click to expand...
Click to collapse
Battery Guru here and after only a few mins usage, it's showing up. Not that it's a bad thing of course! Will monitor and see how it goes...
cd993 said:
A possible light at the end of the tunnel is this project, they are aiming to reverse engineer Viper and modernise the files (hopefully that means using x64!). We'll just have to monitor the progress....
GitHub - AndroidAudioMods/ViPERFX_RE: Reverse Engineering of ViPER4Android FX
Reverse Engineering of ViPER4Android FX. Contribute to AndroidAudioMods/ViPERFX_RE development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
This is amazing news!
I'll gladly test it out for you as I've a keen interest in having this working once again! Feel free to send me a message with any contact details, (email or telegram perhaps) if you like and we'll go from there
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
I'll gladly test it out also!!!!
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
Legend!
iscle said:
Hi! I'm one of the guys working on that project, and I can already tell you it's going smoothly
We have a few effects already working (although some extra work will be needed to check if they are 1:1, any small change in the code can lead to huge changes in audio quality).
My initial goal was indeed creating a 64 bit version of it, and also removing the need for pathing selinux (and yep, i was able to achieve that, no selinux patches needed amymore).
Overall it's looking good but I don't own a Pixel 7 Pro so I'll need some volunteers to test it once it's ready
Click to expand...
Click to collapse
Id like to help test also!