Hello,
I have installed android versions 8,9 and 10 on my PX5 HU in order to try and isolate the problem of the plexamp music app visualisations crashing. The app itself works fine on all versions but I wonder why arent the visualisations working. WebGL(visualisations use this) works in all versions as well. Anyone using that music app and hvaing experienced same issues?
Thanks.
What does plexamp music support suggest?
I was able to pull the logcat from the headunit and identified the crash myself. I then decompiled the code with apktools, I applied my fix and recompiled it. Then I signed it in order to be able to install it.
The issue was a bug in the code causing the OpenGL 3D configuration to be loaded before the client version was set. That caused a crash on some devices. It had nothing to do with the headunit per se. I changed the order of the call of these 2 methods and it now works fine on every device I tried it. If someone wants to try, here is the modified version of Plexamp 3.1.1. You will get a lot of warnings of course when trying to install it but its because its self signed. Extract the archive first.
The fix was accepted by the plex team and will be deployed on the next release of the app.
Related
I dont know what going on but a bunch of apps are showing up in the market that were not there. Some background, Im using the unofficial MoDaCo 1.2 with a modified build prop. updated with MR info. Just checked the market and bust-a-move and Pic Say Pro are now back the market.
Anyone else having apps show up in the market?
That's a negative good buddy. Still no sign of SU File Manager 3.0.6. Yep I paid for it and it's gone along with a few of the TTS engines I paid for.
Not there yet for me.
eBuddy's not back on either
That's because the developers probably turned off copy-protection on the app but the issue hasn't been fixed.
just upgraded to modaco 1.2...and yes, i was missing a paid app (droidlive), but it has now reappeared.
also, for anyone interested, playing media via bluetooth speakers works perfectly on this ROM
Yea he did it by putting the old props file back in so it has the phone identify to the market that it's still version 1.26. I had mentioned in a few threads that I could add that to fresh rom if needed but wanted to see if Google/Sprint would fix the issue rather than tricking it in to something it wasn't. Although I've had multiple reports from people using Fresh that the apps were showing up for them even without a modified props.
I'm not sure yet. But maybe I'll put a modified one in mine also. I don't see how it could possibly affect it, but I wonder if that is some how related to the bluetooth speakers too? I'll check it out.
flipzmode said:
...but I wonder if that is some how related to the bluetooth speakers too? I'll check it out.
Click to expand...
Click to collapse
I can't see how. I can confirm that stock sprint rom with MR update Bluetooth works normally. I ran your 0.4 and saw the BT audio streaming issues.
hi, i don't know this is the right forum. i used "read it later" heavily in winmo (thanks to vizier and his latereader) and am now switching to android. it seems that the read it later client paperdroid is no longer supported by the developer in froyo. has anyone able to make it work or do you think some of our talented developers can make it work again?
Will it not install? Will it not launch? Does it run but just not work?
it installs fine but crashes right away after launching.
You should use logcat or any other log capture app to see why it crashes. It would help finding out what's going on and if its possible to fix.
FYI, paperdroid is running fine for me on 2.2 on my evo... Aren't there a few options for read it later on android? I thought I saw a few different apps for it on the read it later site.
Sent from my phone.
thanks for your responses. i will check again if it works or not (I tried several times already but if you got it working there may be hope). i will try logging the error reports also.
as for other ReadItLater clients, Paperdroid seems to be the only Android full RIL client. There seem to plugins for saving links etc.
Also, what phone do you have?
I have a HD2 and run Android off of the SD card. I don't know if that might be the problem.
I tried a different Android built and Paperdroid seems to work. So it's not a Froyo issue after all.
Thanks for all your replies.
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.
While working on an Android app for the company I work for, we have run into a very weird situation where the app doesn't work as expected. One of our paying subscribers reports seeing a black screen when opening our app on his Android, even though we have successfully tested our app on the same model of phone. We suspect the problem stems from other software running on his phone, what could it be?
Here are a couple things to consider:
1. To my best knowledge, the "black" screen is actually a dark gray color that is used within our app. This tells me that maybe a view is not rendering correctly, or possibly transparency is not working correctly.
2. We were informed that our latest version of the app in the Google Play Store was working momentarily, but then ceased to work (i.e. the dark gray screen). We don't have enough info to know how long it took for this behavior to start happening, but we cannot recreate this issue at all.
3. We have other customers using the same model of phone, but not calling up complaining about the issue. We don't think it's affecting others, but we do have evidence in our logs that suggests the users are using the app and making all the API calls that the app would normally make.
4. An older version of our app DOES work for them. There were a lot of changes to the build system that we made, including taking out hard references to the package name from the manifest and putting them in the gradle build system. I couldn't imagine anything I changed in code would affect this user except some of the manifest changes.
(example: com.company.app.activities was refactored to .activities in the manifest)
My questions to you are: Do you know of any apps that can interfere with another? Have you seen this or heard of this before? Are there any tricks for me, as a developer, to resolve this issue? (perhaps it's a problem with my AndroidManifest.xml or a dependency in my build.gradle file)
Thank you so much for your help! Even though this is affecting one customer, we're hoping that we can identify this problem and solve it so others facing this problem can learn from this post.