I created a new thread for convenience to anyone looking for bluetooth support on Ouya black edition. Here is a nightly build of CM-11 with firmware copied from stock Ouya update. Wifi isn't working but I presume it should be an easy fix. I'm not an android developer and prefer wired connections.
https://drive.google.com/file/d/0BzWvTrOKC7GtdWRVTkFaSlhneWs/view?usp=sharing
Hope this helps!
Dumb girl needs a little help with Bluetooth Issue
I found the patch for fixing the bluetooth issue for the Ouya Anthracite for CM11 but I have no clue how to install this patch. I uploaded it to the Ouya I have tried to unzip the file. And I cant seem to open it. I am just not sure how to apply this patch so I may sync the controller with the Ouya. Many thanks for any help!!
puya cm11 nightly updates
jusplainmike said:
I created a new thread for convenience to anyone looking for bluetooth support on Ouya black edition. Here is a nightly build of CM-11 with firmware copied from stock Ouya update. Wifi isn't working but I presume it should be an easy fix. I'm not an android developer and prefer wired connections.
https://drive.google.com/file/d/0BzWvTrOKC7GtdWRVTkFaSlhneWs/view?usp=sharing
Hope this helps!
Click to expand...
Click to collapse
if i update to a different version of cm11 will i lose the blue tooth capabilities?
alquistador said:
if i update to a different version of cm11 will i lose the blue tooth capabilities?
Click to expand...
Click to collapse
Anyone have an answer??
Bump
alquistador said:
if i update to a different version of cm11 will i lose the blue tooth capabilities?
Click to expand...
Click to collapse
The bluetooth/wifi issues are only a concern for Anthracite OUYA owners. If that's the case for you, I would stick with this ROM since there are virtually no updates happening for CM11 now. If you really want to update, then find the bluetooth driver in the ROM and simply copy it like the OP did.
If you don't have the Anthracite version just use mlq's CM11.
I have the Anthracite Ouya. Thanks for the info. I have no idea how to copy the Ouya driver's so I will just stay on cm11.
Related
I would love to use Google now on CM9 (cant update to CM10.1 because bluetooth does not work and I use a few bluetooth devices. (also I get less screen space due to there now being 2 menu bars (and no 120dpi setting)
Has anyone gotten google now to work with the HP touchpad on CM9, if so then is there an APK, or CWM flashable file to install it?
Razor512 said:
I would love to use Google now on CM9 (cant update to CM10.1 because bluetooth does not work and I use a few bluetooth devices. (also I get less screen space due to there now being 2 menu bars (and no 120dpi setting)
Has anyone gotten google now to work with the HP touchpad on CM9, if so then is there an APK, or CWM flashable file to install it?
Click to expand...
Click to collapse
Honestly, it's just too much work, and it never works as intended. Install a CM10 rom that supports bluetooth (such as Schizoid v1.20 , a great ROM!) and you'll have it working.
Razor512 said:
I would love to use Google now on CM9 (cant update to CM10.1 because bluetooth does not work and I use a few bluetooth devices. (also I get less screen space due to there now being 2 menu bars (and no 120dpi setting)
Has anyone gotten google now to work with the HP touchpad on CM9, if so then is there an APK, or CWM flashable file to install it?
Click to expand...
Click to collapse
Yes
Razor512 said:
I would love to use Google now on CM9 (cant update to CM10.1 because bluetooth does not work and I use a few bluetooth devices. (also I get less screen space due to there now being 2 menu bars (and no 120dpi setting)
Has anyone gotten google now to work with the HP touchpad on CM9, if so then is there an APK, or CWM flashable file to install it?
Click to expand...
Click to collapse
Are you forgetting about CM10 (.0) ?
jcsullins said:
Are you forgetting about CM10 (.0) ?
Click to expand...
Click to collapse
I think, for some reason, a lot of people dont realize that CM10 and CM10.1 are two different things.
To the OP...Try CM10 like jcsullins mentioned. Bluetooth works. And the status bar/navbar are combined at the bottom.
Hi.. When I first got my chromecast I immediately flashed it with flashcast.. I didn't check updates/roms after doing this, so I have used the chromecast flashed with flashcast several times, and it has updated itself.. When I look at the Chromecast build in my IOS app it shows as 13330 or something. Now, my question is... can I still update the Flashcast software to the latest version, and put a rom on it? Is there anything I can do with the chromecast with it being updated, etc.. thank you for help.
dyslecix said:
Hi.. When I first got my chromecast I immediately flashed it with flashcast.. I didn't check updates/roms after doing this, so I have used the chromecast flashed with flashcast several times, and it has updated itself.. When I look at the Chromecast build in my IOS app it shows as 13330 or something. Now, my question is... can I still update the Flashcast software to the latest version, and put a rom on it? Is there anything I can do with the chromecast with it being updated, etc.. thank you for help.
Click to expand...
Click to collapse
Flashcast itself is just a tool that (once setup using the Chromecast) can be used to flash a custom ROM. Flashcast itself is not a ROM and does not root your Chromecast or prevent it from updating. Do you know what ROM you initially flashed using Flashcast? If you did not actually take the next step of using Flashcast to flash a rooted, no-update ROM, then it is not currently possible to root your updated Chromecast or flash a custom ROM. (If you are still on 13300, that does make me wonder if you might have installed a custom ROM because Google has released 2 newer builds OTA since 13300 that you should have received by now if the CC is connected to the Internet.)
dyslecix said:
Hi.. When I first got my chromecast I immediately flashed it with flashcast.. I didn't check updates/roms after doing this, so I have used the chromecast flashed with flashcast several times, and it has updated itself.. When I look at the Chromecast build in my IOS app it shows as 13330 or something. Now, my question is... can I still update the Flashcast software to the latest version, and put a rom on it? Is there anything I can do with the chromecast with it being updated, etc.. thank you for help.
Click to expand...
Click to collapse
Flashcast was/is the first of two steps and the second was to install the ROM which roots the CC. It won't accept a Google update then. If you did both steps your good but if you only did the first step your stuck. I'm guessing that you did both steps as your CC would have the latest Google build by now.
Well, when I plug my chrome cast in the TV and it boots, it does show a google chrome icon with a 'pwned' in red next to it, but I am not sure if that is from when I just tried to add Eureka Rom to chromecast today. Is there anyway to check whether I have a ROM installed on the chromecast for sure? I did try logging into the web ui thing that I believe is a feature of this rom, and it does not seem to work.
dyslecix said:
Well, when I plug my chrome cast in the TV and it boots, it does show a google chrome icon with a 'pwned' in red next to it, but I am not sure if that is from when I just tried to add Eureka Rom to chromecast today. Is there anyway to check whether I have a ROM installed on the chromecast for sure? I did try logging into the web ui thing that I believe is a feature of this rom, and it does not seem to work.
Click to expand...
Click to collapse
Depends how long ago you flashed the ROM. The current ROM with the Web Panel was released just before Xmas.
dyslecix said:
Well, when I plug my chrome cast in the TV and it boots, it does show a google chrome icon with a 'pwned' in red next to it, but I am not sure if that is from when I just tried to add Eureka Rom to chromecast today. Is there anyway to check whether I have a ROM installed on the chromecast for sure? I did try logging into the web ui thing that I believe is a feature of this rom, and it does not seem to work.
Click to expand...
Click to collapse
Yeah, if it says PWNED that means you are using my old PwnedCast ROM, which was before Eureka-ROM was released. if you leave the device on for 10~ minutes, it should check for an update from the team server, and self-update to the latest Eureka-ROM Release, unless you disabled the OTA service. In that case, you will have to flash Eureka-ROM manually using the latest flashcast, and a jump drive.
ddggttff3 said:
Yeah, if it says PWNED that means you are using my old PwnedCast ROM, which was before Eureka-ROM was released. if you leave the device on for 10~ minutes, it should check for an update from the team server, and self-update to the latest Eureka-ROM Release, unless you disabled the OTA service. In that case, you will have to flash Eureka-ROM manually using the latest flashcast, and a jump drive.
Click to expand...
Click to collapse
Is the latest Eureka build 14975?
Sent from my SPH-D710 using Tapatalk 2
third son said:
Is the latest Eureka build 14975?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
the latest Eureka-ROM is build 14975.002. You can always check what version is the latest from our OTA website. http://ota.team-eureka.com/
ddggttff3 said:
the latest Eureka-ROM is build 14975.002. You can always check what version is the latest from our OTA website. http://ota.team-eureka.com/
Click to expand...
Click to collapse
I know this is the wrong forum or procedure but could someone point in the direction how I can find the chromecast forums
Sent from my SCH-I535 using xda app-developers app
MIKEYSAKZ said:
I know this is the wrong forum or procedure but could someone point in the direction how I can find the chromecast forums
Click to expand...
Click to collapse
Main area is here: https://forum.xda-developers.com/hardware-hacking/chromecast
If you're looking for other discussion sites, there are quite a few on Google+
I have read (and experienced) the failure of location issues with pa_gapps-modular-mini-4.4.2-20140524. Do we have any solutions to the issues? I am hoping someone has a solution which I have missed.
Shyamani said:
I have read (and experienced) the failure of location issues with pa_gapps-modular-mini-4.4.2-20140524. Do we have any solutions to the issues? I am hoping someone has a solution which I have missed.
Click to expand...
Click to collapse
Exactly what rom are you running?
jcsullins
sstar said:
Exactly what rom are you running?
Click to expand...
Click to collapse
11-20140409-SNAPSHOT-jcsullins-tenderloin.
Shyamani said:
11-20140409-SNAPSHOT-jcsullins-tenderloin.
Click to expand...
Click to collapse
I'm currently on Milaq's latest and have also had problems, here is what I've done :
Installed PA micro Gapps so that map's isn't a system app. Then disabled automatic update in Google play and installed this version of maps https://app.box.com/s/xepi3tqyu06bc01l8q6y which works after that I manually updated on play which has worked. If it doesn't just uninstall the latest version and revert back to the one you dl from the box link.
I hope this helps.
Works, kind of.
Thank you, the apk you linked to works.
Unfortunately, manual update breaks it again. I can restore to the downloaded apk, no problem.
I still have problems with location(even with the linked apk) for other applications(weather, etc.) not getting location.
I am guessing this has something to do with 4.4.2 builds and their interaction with Google.
Shyamani said:
Thank you, the apk you linked to works.
Unfortunately, manual update breaks it again. I can restore to the downloaded apk, no problem.
I still have problems with location(even with the linked apk) for other applications(weather, etc.) not getting location.
I am guessing this has something to do with 4.4.2 builds and their interaction with Google.
Click to expand...
Click to collapse
Sorry that didn't work for , you could make a backup of your current install and then see if Milaq's latest works for you as jcsullins rom I believe is based on Milaq's. That's what I ended up doing and am really pleased with it.
All the best and good luck.
Every time i OTA update the rom, Some pages of the launcher disappear. I am on the last Nightly, bit I can't guess what's the problem
gigsaw said:
Every time i OTA update the rom, Some pages of the launcher disappear. I am on the last Nightly, bit I can't guess what's the problem
Click to expand...
Click to collapse
AOSP's new launcher code as of kitkat doesn't play nice with apps2sd (since any currently supported Android device has unified internal storage)
Entropy512 said:
AOSP's new launcher code as of kitkat doesn't play nice with apps2sd (since any currently supported Android device has unified internal storage)
Click to expand...
Click to collapse
Thank's for reply do you know if I nave to remove something? With omnirom 4.4.2 I didn't have this problem. I have a nexus 4 and I unlocked, Flashed TWRP 2.7.0.1 and wiped..then I started using omnirom since it was fixed the WiFi in 4.4.3 so I guess the 11-06-2014..I think it is only a problem of mine, since nobody else said anything on xda, but I can't find the origin of the issue.the only apps that use root access are aptoide and bootunlocker..i think I haven't touched nothing else..
gigsaw said:
Thank's for reply do you know if I nave to remove something? With omnirom 4.4.2 I didn't have this problem. I have a nexus 4 and I unlocked, Flashed TWRP 2.7.0.1 and wiped..then I started using omnirom since it was fixed the WiFi in 4.4.3 so I guess the 11-06-2014..I think it is only a problem of mine, since nobody else said anything on xda, but I can't find the origin of the issue.the only apps that use root access are aptoide and bootunlocker..i think I haven't touched nothing else..
Click to expand...
Click to collapse
odd, apps2sd isn't relevant on mako, and also, the apps2sd issues have existed since the very beginning of the 4.4 cycle
Why the filth-flarn-flarn-filth can't i cast the screen of my Android to my (stock) Chromecast yet, as announced?
I have a S4 (jflte), listed as supported. Running latest Omniron nightly (and up to date SuperSU, but that shouldn't matter), and i tried the following;
- update CC app to 1.7.4 from Android File Host
- update gapps to 20140708 and then to 20140716 in the hope Play Services would fix it
- reboot and factory reset chromecast until my fingers bled
- edited build.prop to appear as a hammerhead device, as advised by @murdoch1 in a different thread
- uninstalled CC app, rebooted
- re-installed Playstore version of CC app (also 1.7.4, now)
Please advise!
SCM020 said:
Why the filth-flarn-flarn-filth can't i cast the screen of my Android to my (stock) Chromecast yet, as announced?
I have a S4 (jflte), listed as supported. Running latest Omniron nightly (and up to date SuperSU, but that shouldn't matter), and i tried the following;
- update CC app to 1.7.4 from Android File Host
- update gapps to 20140708 and then to 20140716 in the hope Play Services would fix it
- reboot and factory reset chromecast until my fingers bled
- edited build.prop to appear as a hammerhead device, as advised by @murdoch1 in a different thread
- uninstalled CC app, rebooted
- re-installed Playstore version of CC app (also 1.7.4, now)
Please advise!
Click to expand...
Click to collapse
I don't know much about Omniron but all ROMs have things that have been removed/are missing, because the developer thought it makes the rom better/faster and they might have removed something with the functionality. Have you tried testing from a different rom? Maybe a TW ROM?
Znomon said:
I don't know much about Omniron but all ROMs have things that have been removed/are missing, because the developer thought it makes the rom better/faster and they might have removed something with the functionality. Have you tried testing from a different rom? Maybe a TW ROM?
Click to expand...
Click to collapse
That, i have not. didn't think that would be related, because the casting is initiated from the CC app and not from System>Display.
And i've been on Omni since the first official release for jflte.
Edit. I seriously had to look up what you ment by TW:silly:. If that what it takes i'll live without...
Most likely it's something to do with your phone's ROM. Like Miracast, Chromecast screen casting is dependent on both the device itself and the ROM, and it might depend on kernel/bootloader too. We don't know exactly what hardware/software components Google has leveraged to make this happen.
The only 100% guaranteed working configurations consist of:
Supported phone/tablet
Stock ROM on phone/tablet (root or not shouldn't matter)
Build 17xxx or newer on Chromecast (stock or rooted shouldn't matter as long as build is proper version)
Updated Google Play Services
Chromecast 1.7.4 app (not required in some cases)
SCM020 said:
Edit. I seriously had to look up what you ment by TW. If that what it takes i'll live without...
Click to expand...
Click to collapse
For the rest of the class, TW = TouchWiz = Samsung stock ROM (took me a while to figure that out too )
SCM020 said:
Why the filth-flarn-flarn-filth can't i cast the screen of my Android to my (stock) Chromecast yet, as announced?
I have a S4 (jflte), listed as supported. Running latest Omniron nightly (and up to date SuperSU, but that shouldn't matter), and i tried the following;
- update CC app to 1.7.4 from Android File Host
- update gapps to 20140708 and then to 20140716 in the hope Play Services would fix it
- reboot and factory reset chromecast until my fingers bled
- edited build.prop to appear as a hammerhead device, as advised by @murdoch1 in a different thread
- uninstalled CC app, rebooted
- re-installed Playstore version of CC app (also 1.7.4, now)
Please advise!
Click to expand...
Click to collapse
Try mirrorenabler http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
hwong96 said:
Try mirrorenabler http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Click to expand...
Click to collapse
That mysteriously fixed it somehow. Thank you!!
SCM020 said:
That, i have not. didn't think that would be related, because the casting is initiated from the CC app and not from System>Display.
And i've been on Omni since the first official release for jflte.
Edit. I seriously had to look up what you ment by TW:silly:. If that what it takes i'll live without...
Click to expand...
Click to collapse
bhiga said:
Most likely it's something to do with your phone's ROM. Like Miracast, Chromecast screen casting is dependent on both the device itself and the ROM, and it might depend on kernel/bootloader too. We don't know exactly what hardware/software components Google has leveraged to make this happen.
The only 100% guaranteed working configurations consist of:
Supported phone/tablet
Stock ROM on phone/tablet (root or not shouldn't matter)
Build 17xxx or newer on Chromecast (stock or rooted shouldn't matter as long as build is proper version)
Updated Google Play Services
Chromecast 1.7.4 app (not required in some cases)
For the rest of the class, TW = TouchWiz = Samsung stock ROM (took me a while to figure that out too )
Click to expand...
Click to collapse
I apologize to both of you, forgot I was in the Chromecast Thread and not a Samsung device thread, Touchwiz(TW) is thrown around and just expected to be understood over there. I forgot to change my lingo when I enter into the real world...
Znomon said:
I apologize to both of you, forgot I was in the Chromecast Thread and not a Samsung device thread, Touchwiz(TW) is thrown around and just expected to be understood over there. I forgot to change my lingo when I enter into the real world...
Click to expand...
Click to collapse
Haha no worries, my brain just kept going to Time Warner and thought "they're taking over cell phones now?? " It's all good.
Znomon said:
I apologize to both of you, forgot I was in the Chromecast Thread and not a Samsung device thread, Touchwiz(TW) is thrown around and just expected to be understood over there. I forgot to change my lingo when I enter into the real world...
Click to expand...
Click to collapse
It's just that's the last ROM I'd consider. Would have understood PA or AOKP in a heartbeat
SCM020 said:
It's just that's the last ROM I'd consider. Would have understood PA or AOKP in a heartbeat
Click to expand...
Click to collapse
It's not as absurd as you would think. I own a Galaxy note II, and I have to use custom versions of Touchwiz so that I can get the S-pen to work, and all other "Note specific" applications.