So this doesn't work outright on the new Lollipop build for the N7, but it can easily be made to work. Unfortunately the MirrorEnabler app doesn't work on Lollipop yet, and the SQLite Installer app that would make it work hasn't caught up; it installs a non-executable binary that even when set with the correct permissions doesn't run. Credit goes to @r3pwn for finding the initial method for doing this.
UPDATE: MirrorEnabler had been updated for 5.0, and i've seen reports it works now. You can try it Here. Don't forget to thank @r3pwn if it works for you! Otherwise, this method still works, so take your pick. [emoji2]
UPDATE 2: The update of the crhomecast app supposedly supports this natively now on ALL devices, so this may not even be needed anymore. If someone who has not applied this fix can test that out (Has to be chromcast v 1.9.6 or higher) and report back in this thread, that'd be great.
So because I wanted my screen mirroring back, I dove in and made it work. Yes, there are 20 steps, but they are all outlined precisely. If done correctly this shouldn't take more than 5 minutes.
Here's how:
1) Be rooted on Android 5.0 (L)
2) Install chromecast app from play store - Link
3) Open the chromecast app and set up your chromecast device
4) Install busybox (I prefer sterricson version) - Link
5) Open Busybox app and click Install.
6) Install SQLite Editor (not free, but works great on L and worth the money if you like to tinker) - Link
7) get adb shell and issue the commands:
Code:
[email protected]:/ $ su
[email protected]:/ # setenforce 0
[email protected]:/ # getenforce
Permissive
[email protected]:/ #
DO NOT EXIT ADB YET!
8) Open SQLite Editor on your device and navigate to "Google Services Framework"
9) Under google services Framework, select "gservices.db"
10) In gservices.db select "overrides"
11) Click "+ NEW RECORD"
12) In the name field put (exactly as shown):
Code:
gms:cast:mirroring_enabled
13) In the value field put (exactly as shown):
Code:
true
14) Click Save
15) Click "+ NEW RECORD" again
16) In the name field put (exactly as shown):
Code:
gms:cast:remote_display_enabled
17) In the value field put (exactly as shown):
Code:
true
18) Click Save
19) Exit SQLite Editor
20) In your adb shell ( you didn't close it, right? ):
Code:
[email protected]:/ # am force-stop com.google.android.gsf
[email protected]:/ # am force-stop com.google.android.gms
[email protected]:/ # am force-stop com.google.android.apps.chromecast.app
[email protected]:/ #
If it worked you won't see any output from these three commands; You can now exit adb and disconnect your device.
If you see this:
Code:
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:298)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:249)
You didn't do step 7 correctly. Repeat step 7 and then try this step again.
That's it! NO reboot required! You should now be able to stream screen mirror to a chromecast device from your N7(2012) using Lollipop!
To test it, you should now be able to use your quick settings "Cast Screen" button, or the "Cast Screen" option from within the chromecast app.
Enjoy!
Nice guide !
Gesendet von meinem GT-I9195 mit Tapatalk
Nice guide.
Can confirm after following this guide casting from settings pull down is indeed working on lollipop N7 2012!!
Cheers!
Its works great! thank you!
I think Mirror Enabler only set the first one row, and it is the reason it stopped working on this tablet
Unfortunately not working with panasonic ptv3000
does this hack survive a Google Services Framework update, and is there really need to install chromecast app?
thanks
m52 power! said:
Unfortunately not working with panasonic ptv3000
Click to expand...
Click to collapse
Never said it would.
Sent from my leanKernel 3.11.3 powered stock 4.4.2 (NF9) SM-N900T
donpippo said:
does this hack survive a Google Services Framework update, and is there really need to install chromecast app?
thanks
Click to expand...
Click to collapse
Theoretically yes. It's just a data change. Add for having to install the chromecast app, you can try without installing it but i do believe it's required.
Sent from my leanKernel 3.11.3 powered stock 4.4.2 (NF9) SM-N900T
Wow. Yep. Works with Chromecast.
not working on my N7 [emoji26]
Edit: tried again with success. I started from 0 again. thank you
I would like to annonce that this method worked perfectly in the Moto X 2014 (Lollipop)... the only problem is, when i restart the phone it stops working and i need to do the whole process again..... Any way to fix that?
Thank you
toastido said:
So this doesn't work outright on the new Lollipop build for the N7, but it can easily be made to work. Unfortunately the MirrorEnabler app doesn't work on Lollipop yet, and the SQLite Installer app that would make it work hasn't caught up; it installs a non-executable binary that even when set with the correct permissions doesn't run.
So because I wanted my screen mirroring back, I dove in and made it work. Yes, there are 20 steps, but they are all outlined precisely. If done correctly this shouldn't take more than 5 minutes.
Here's how:
1) Be rooted on Android 5.0 (L)
2) Install chromecast app from play store - Link
3) Open the chromecast app and set up your chromecast device
4) Install busybox (I prefer sterricson version) - Link
5) Open Busybox app and click Install.
6) Install SQLite Editor (not free, but works great on L and worth the money if you like to tinker) - Link
7) get adb shell and issue the commands:
Code:
[email protected]:/ $ su
[email protected]:/ # setenforce 0
[email protected]:/ # getenforce
Permissive
[email protected]:/ #
DO NOT EXIT ADB YET!
8) Open SQLite Editor on your device and navigate to "Google Services Framework"
9) Under google services Framework, select "gservices.db"
10) In gservices.db select "overrides"
11) Click "+ NEW RECORD"
12) In the name field put (exactly as shown):
Code:
gms:cast:mirroring_enabled
13) In the value field put (exactly as shown):
Code:
true
14) Click Save
15) Click "+ NEW RECORD" again
16) In the name field put (exactly as shown):
Code:
gms:cast:remote_display_enabled
17) In the value field put (exactly as shown):
Code:
true
18) Click Save
19) Exit SQLite Editor
20) In your adb shell ( you didn't close it, right? ):
Code:
[email protected]:/ # am force-stop com.google.android.gsf
[email protected]:/ # am force-stop com.google.android.gms
[email protected]:/ # am force-stop com.google.android.apps.chromecast.app
[email protected]:/ #
If it worked you won't see any output from these three commands; You can now exit adb and disconnect your device.
If you see this:
Code:
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:298)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:249)
You didn't do step 7 correctly. Repeat step 7 and then try this step again.
That's it! NO reboot required! You should now be able to stream screen mirror to a chromecast device from your N7(2012) using Lollipop!
To test it, you should now be able to use your quick settings "Cast Screen" button, or the "Cast Screen" option from within the chromecast app.
Enjoy!
Click to expand...
Click to collapse
I would like to annonce that this method worked perfectly in the Moto X 2014 (Lollipop)... the only problem is, when i restart the phone it stops working and i need to do the whole process again..... Any way to fix that?
Thank you
Anyone have any idea if this is necessary on the newer ver2 N7 after OTA?
MLT2004 said:
Anyone have any idea if this is necessary on the newer ver2 N7 after OTA?
Click to expand...
Click to collapse
Not sure after OTA update, but my son's N7 (2013 / gen 2) needed zero mods to get screen casting to work. It worked fine after installing the google N7 image from https://developers.google.com/android/nexus/images
Sent from either Maguro or Grouper via XDA free
On step 9) Under google services Framework, select "gservices.db" i get the error
An error occurred while opening the database. attempt to write a readonly database (code 776) while compiling: select * from sqlite_master where type in('table','view') order by name
How can i solve this?
theone_s_me said:
I would like to annonce that this method worked perfectly in the Moto X 2014 (Lollipop)... the only problem is, when i restart the phone it stops working and i need to do the whole process again..... Any way to fix that?
Thank you
Click to expand...
Click to collapse
Unknown. Don't own that device. Only tested on the n7 2012.
boriznl said:
On step 9) Under google services Framework, select "gservices.db" i get the error
An error occurred while opening the database. attempt to write a readonly database (code 776) while compiling: select * from sqlite_master where type in('table','view') order by name
How can i solve this?
Click to expand...
Click to collapse
No idea. You are rooted, right? Might see if remounting /system in read/write mode would help. Also make sure you granted root privileges to sqlite editor if it asked.
Sent from my SM-T320 using Tapatalk
Creds? Or at least link to my source code that you took this from.
r3pwn said:
Creds? Or at least link to my source code that you took this from.
Click to expand...
Click to collapse
I didn't steal any source code, since it's a guide and not an application. I will, however, credit you for finding the method initially, although your app did not work in Lollipop at the time.
toastido said:
I didn't steal any source code, since it's a guide and not an application. I will, however, credit you for finding the method initially, although your app did not work in Lollipop at the time.
Click to expand...
Click to collapse
I know you didn't "steal the code", but parts of this guide are letter-for-letter in the code of my app. And don't worry, Lollipop-compatible version coming soon.
EDIT: Thanks for adding that to the OP, but I found the ActivityManager commands to kill the required processes, too.
r3pwn said:
I know you didn't "steal the code", but parts of this guide are letter-for-letter in the code of my app. And don't worry, Lollipop-compatible version coming soon.
EDIT: Thanks for adding that to the OP, but I found the ActivityManager commands to kill the required processes, too.
Click to expand...
Click to collapse
D'oh. My bad. Updated OP to be a bit more generic.
Also, when you get the Lollipop compatible version ready, let me know and I'll gladly update the OP to point people that way for those who don't want to manually do this
Related
This thread will be used for the discussion of packaging the ouya store into a flashable zip for easy install onto CM10, or hopefully any other custom rom that might not have the ouya store on it (or dare I say phone! untested, just a thought).
---------------------------------------------
Notes:
The good news up front we have both the ouya and play stores running on CM10!
I was working on this a few days ago and was running into what looked like issues with the data/system/packages.xml file giving out the right permissions. Toast message FC about ouya framework, and tv.ouya permissions to uid="10032".
I flashed back to OTA to try the exposed play store. After playing with that for a bit I decided to go back to work on this so we can have both the play store and the ouya store working on both OTA and CM10. I flashed over the ouya bits and set perms and was getting ready to look at the logcat expecting the same errors... but the launcher came right up, asked for my login and into the play menu I went!
What changed? I said I was working on permissions in the /data/system/package.xml... well I forgot to wipe data before flashing CM10. I think that was the secret, it must have skipped some step that was causing the error as something it was looking for was already there.
In any event the store and framework are working... mostly. I am still having issues getting into the "discover" menu as I get a toast message that says something about "attempted read from closed stream". in logcat it looks like "error checking for update". so I think it may be that I'm working on old apk's from an old download.
There is also an issue with the controller mapping, home seems not to work and while testing shadowgun the x/y axis on the right thumb stick was reversed. I think I remember someone saying something about that.
In the end it turned out to be about the same process as getting google music to work on stock OTA. basically grab the framework and launcher apks and put them in system. (At least up to this point! lol) The Idea will be to use this to build a complete install zip without the need to have a data partition from OTA. Who knows what other issues this might cause as usually its not a good idea to keep data from different roms.
------------------------------------------------------
So manual step...
!!!This is for Dev purposes only, this does not work 100% yet!!!
If you want to give it a try and/or help solve an issue or 2, by all means continue!
-1. Make sure you have access to OUYA store on an OTA based rom.
0. Flash CM10 via cwm !!!DO NOT WIPE DATA!!!
http://forum.xda-developers.com/showthread.php?t=2348548
instructions on flashing the google apps are also there to get play store working.
1. I used the deodexed files from IncognitoMan's stock plus rom. Basically from /system/app/ grab anything that starts with "ouya" at this point I'm not sure all are need but this is what I did to get to where I'm at now... I will update as I test further on what all exactly is needed or not.
link to rom http://forum.xda-developers.com/showthread.php?t=2347214
a. ouya-framework.apk
b. OUYAKeyboard.apk
c. OUYALauncher.apk
d. OUYAOOBE.apk
e. OUYAWallpaper.apk
For each of these files copy over to sdcard
adb push ouya-framework.apk /sdcard/.
adb push OUYAKeyboard.apk /sdcard/.
adb push OUYALauncher.apk /sdcard/.
adb push OUYAOOBE.apk /sdcard/.
adb push OUYAWallpaper.apk /sdcard/.
Click to expand...
Click to collapse
2. Remount system in rw
adb shell
su
mount -o rw,remount /system
Click to expand...
Click to collapse
3. Copy over to /system/app/
cat /sdcard/ouya-framework.apk > /system/app/ouya-framework.apk
cat /sdcard/OUYAKeyboard.apk > /system/app/OUYAKeyboard.apk
cat /sdcard/OUYALauncher.apk > /system/app/OUYALauncher.apk
cat /sdcard/OUYAOOBE.apk > /system/app/OUYAOOBE.apk
cat /sdcard/OUYAWallpaper.apk > /system/app/OUYAWallpaper.apk
Click to expand...
Click to collapse
4. Set permissions.
chmod 644 /system/app/ouya-framework.apk
chmod 644 /system/app/OUYAKeyboard.apk
chmod 644 /system/app/OUYALauncher.apk
chmod 644 /system/app/OUYAOOBE.apk
chmod 644 /system/app/OUYAWallpaper.apk
Click to expand...
Click to collapse
5. Reboot.
reboot
Click to expand...
Click to collapse
6. Launch the "ouya launcher" from the app menu and log in.
All games you had from the OTA rom should be there.
Again issues:
Cant get into "Discover" menu in ouya launcher. - working on this now as this is obviously the deal breaker for most.
Controller keymapping. -biggest issue with this is home button mapping! in android settings the ouyaKeyboard is grayed out... ouya framework issue.
Some games show a ouya-framework fc 2-3 times as the game loads... but once the game is up its fine.
Some games might not like the high dpi.
Some games just wont open (paid?)... - thinking this might be related to the Discover menu issue.
irc, FreeNode/#ouya-dev
Thanks; khanning88 for CM10, IncognitoMan for deodexed OTA.
So on with the work then.
here is a pastebin of the logcat while clicking the discovery menu item. Looks like it gets the menu, kind of interesting how they are sending the list.
http://pastebin.com/wHPyvskN
the logcat from clicking the ouyaKeyboard setting in language/input
D/InputMethodPreference( 642): IME's Settings Activity Not Found: android.content.ActivityNotFoundException: Unable to find explicit activity class {tv.ouya.console.ime.keyboard/com.example.android.softkeyboard.ImePreferences}; have you declared this activity in your AndroidManifest.xml?
I/ActivityManager( 325): START {act=android.intent.action.MAIN cmp=tv.ouya.console.ime.keyboard/com.example.android.softkeyboard.ImePreferences u=0} from pid 642
Click to expand...
Click to collapse
^thinking this might be an issue with matching up activity and class in /data/system/package.xml... might have different userid tags?
Hey after doing this does the Ouya keyboard work?
professorpoptart said:
So on with the work then.
here is a pastebin of the logcat while clicking the discovery menu item. Looks like it gets the menu, kind of interesting how they are sending the list.
http://pastebin.com/wHPyvskN
the logcat from clicking the ouyaKeyboard setting in language/input
^thinking this might be an issue with matching up activity and class in /data/system/package.xml... might have different userid tags?
Click to expand...
Click to collapse
That looks like its just missing a preferences add-on apk or it needs an activity from Settings.apk that's missing.
So why the sudden halt? Everyone give up, get it working or lost interest?
I'd love to get my CM11 into a Hybrid with Ouya app's.
Please help me set up Xposed zenfone 5. zenfone 5 bootloop when using x86 was installed framework.
Please post a logcat of the bootloop.
Hold Power button + volume Up button to access Recovery mode.
Then select Factory Reset by volume up/down and Power button
I have same case
rovo89 build an unofficial build for asus x86, Xposed ver 2.5 beta 2, but he is not share them on xda. just do a little search on his github or google (asus x86 xposed). i've tested them on my zenfone 6, but basically 5 and 6 is almost same so i think it will work, as the installer is for another asus phone but worked on my z6.
as for bypassing your current bootloop, just press vol down (i think as i randomly press all button) after 30second of bootloop (or plug your usb, when led shows orange or yellow, depends on your battery status) it'll trigger xposed safe mode, and you can uninstall your framework then install ver 2.5 beta 2.
Sent from my ASUS_T00G
minatovladoski said:
rovo89 build an unofficial build for asus x86, Xposed ver 2.5 beta 2, but he is not share them on xda. just do a little search on his github or google (asus x86 xposed). i've tested them on my zenfone 6, but basically 5 and 6 is almost same so i think it will work, as the installer is for another asus phone but worked on my z6.
Click to expand...
Click to collapse
See http://forum.xda-developers.com/xposed/asus-me302c-problem-t2737886/post52741226
The offset required for your ROM might vary, but if the test version I had posted on GitHub worked for you, try 0x98.
rovo89 said:
See http://forum.xda-developers.com/xposed/asus-me302c-problem-t2737886/post52741226
The offset required for your ROM might vary, but if the test version I had posted on GitHub worked for you, try 0x98.
Click to expand...
Click to collapse
yeah thanks a lot mate, as i have no confidence on edit code, i choose to use the test version
Sent from my ASUS_T00G
minatovladoski said:
yeah thanks a lot mate, as i have no confidence on edit code, i choose to use the test version
Click to expand...
Click to collapse
Well, that's the whole point... in 2.6, you just need to create a file with the offset (e.g. "0x98") in it, as explained in the post I linked to. No need to edit code or recompile anything.
rovo89 said:
Well, that's the whole point... in 2.6, you just need to create a file with the offset (e.g. "0x98") in it, as explained in the post I linked to. No need to edit code or recompile anything.
Click to expand...
Click to collapse
little question here, if i update from 2.5 beta 2 to 2.6, should I create that file with the offset or not?
Sent from my ASUS_T00G
minatovladoski said:
little question here, if i update from 2.5 beta 2 to 2.6, should I create that file with the offset or not?
Click to expand...
Click to collapse
If you had to use the special build I posted on GitHub, then yes, you have to create the file. If 2.6 is working fine for you without the file, then don't create it.
trying offset
rovo89 said:
If you had to use the special build I posted on GitHub, then yes, you have to create the file. If 2.6 is working fine for you without the file, then don't create it.
Click to expand...
Click to collapse
Rovo
I have rooted my x86 based new Zenfone5 and installed xposed framework 2.5 but I have not full installed the framework yet.
I tried to use the following offset after some research:
su
echo 148> /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
however I keep getting error "No such file or diredtory" even though if I tree down through /data/data I can see that file de.robv.android.xposed.installer is there.
Not sure what to do next? Any help will be greatly appreciated as I must have xposed framework on this device or it is pretty much useless! Thank you in advance!
Root MUST be done. USB debug turned on. Windows only and Driver for Intel and ASUS must be ready on PC.
Step1: download xposed apk and install the apk. DO NOT RUN APP AND DO NOT INSTALL FRAMEWORK.
Step2: Rn command promt (Run / cmd). assume adb folder is on C:\ drive and you are now in C:\ADB
Step 3: Type following (or copy and paste)
adb devices (make sure your phone show!)
adb shell (hit Enter)
su (hit Enter, then look on your phone and touch OK)
echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset (hit Enter)
chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset (hit Enter)
Step4: Now go to app drawer and run Xposed which you installed earlier. Touch "Framework" and touch "Install/Update"
DONE. Now install addons.
rovo89 said:
See http://forum.xda-developers.com/xposed/asus-me302c-problem-t2737886/post52741226
The offset required for your ROM might vary, but if the test version I had posted on GitHub worked for you, try 0x98.
Click to expand...
Click to collapse
My ZenFone 6 (also an Intel Z2580 SoC) is running Android 4.4.2 (closed beta version),
I tried whether set 0x98 offset or not, the phone can boot normally but system lags and will be freezed / reboot randomly.
Thus I set "dalvik.vm.execution-mode=int:fast" now and Xposed framework / module works fine.
I attached the libdvm.so from my ZenFone 6 running Android 4.4.2.
Thanks...
i have zenfone 5 with 1.18 ww firmware (from 1.96 cucc)
i tried to install xposed using instruction here below
####################################
*** Install Xposed: Root is a MUST. USB debug turned on. Windows only and Driver for Intel and ASUS must be ready on PC.
Step1: download xposed apk and install the apk. DO NOT RUN APP AND DO NOT INSTALL FRAMEWORK.
Step2: Run command promt (Run / cmd). assume adb folder is on C:\ drive and you are now in C:\ADB
Step3: Type following (or copy and paste)
adb devices (make sure your phone show!)
adb shell (hit Enter)
su (hit Enter, then look on your phone and touch OK)
echo 148 > /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset (hit Enter)
chmod 664 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset (hit Enter)
Step4: Now go to app drawer and run Xposed which you installed earlier. Touch "Framework" and touch "Install/Update"
DONE. Now install addons.
##########################
but echo command failed because ther isn't a conf folder in /data/data/de.robv.android.xposed.installer/
any suggestion?
Thanks
Stefano
UPDATE 27th November 2014
I have added an Xposed module for the clients below that will work around the issue with Google Play services 6.5
UPDATE 25th November 2014
Google have released Google Play services 6.5 which has strengthened security, effectively making this app useless (clients will be unable to connect). Until Google either loosen the security (which is unlikely to happen), or someone somehow were able to get a hold of the private keys from the chromecast/Android TV this app will no longer work and will no longer be updated.
Thank you all for your support!
Hi everyone! I've decided to finally release my modified Cast Receiver app from the ADT-1 for Android that will work on most devices (though not sure what the minimum api requirement is).
If you don't know what this is it's basically a chromecast receiver for your Android; I use it on my Android mini PC that's hooked up to my TV.
Downloads
Last updated Nov 05 2014.
Recovery install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiaU5WSWRxeC02Tzg
Signed
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiVDR1a1o0WFVSWjg
System install (requires KitKat or newer, or the Xposed module below)
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiNFJGUE1acGZTeFE
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiOTRoanlyX19pVmc
If you are not rooted and can only install it as a regular apk, use the signed version. Note however that casting the screen from another Android device will not work due to a signature mismatch (Google Play Services checks the signatures of the app before allowing screencasting).
If you are rooted you should go for the recovery/system install option, as that will allow screencasting to work.
Xposed module for receiver
If you want to be able to use the system install version on devices older than KitKat you can use the following Xposed module:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiZEFrN1RqLTRFdkk
Xposed module for client
Version 6.5 and newer of Google Play services makes it impossible to connect to the receiver due to some added security. This Xposed module works around that:
https://docs.google.com/uc?export=download&id=0B4FOzj4b2EYiWG1tU3NfYWwwV00
Install
Recovery install
No special instructions needed, simply copy SYSTEM-CastReceiver.zip to the internal storage (or sdcard) on your device and flash it through your recovery (follow the instructions for your specific recovery).
Signed
Simply install the apk as you would with any apk, either through adb:
Code:
adb install -r AndroidMediaShell-signed.apk
or by installing it from your sdcard.
System install
You will need rooted adb for this to work correctly.
If you come from an old install, you can safely remove the old lib first:
Code:
adb remount && adb shell rm /system/lib/libmedia_shell_content_view.so
Once that's done, run:
Code:
adb remount && adb push libcast_shell_android.so /system/lib/ && adb shell chmod 0644 /system/lib/libcast_shell_android.so
adb remount && adb push AndroidMediaShell.apk /system/priv-app/ && adb shell chmod 0644 /system/priv-app/AndroidMediaShell.apk
(Change priv-app to app on devices older than 4.4)
Running
Amazon Fire TV
Because the Whisperplay app implements a DIAL protocol of its own on port 8008, which the Cast Receiver app also uses and that causes a conflict between the two apps.
To get the app running correctly you need to rename WhisperplayCore.apk:
Code:
adb shell mv /system/app/WhisperplayCore.apk /system/app/WhisperplayCore.apk.bak
once that's done, reboot and follow the instructions below.
For the receiver to start you can simply reboot provided you are using the system install. If you are using the signed version you need to run:
Code:
adb shell am broadcast -a android.intent.action.BOOT_COMPLETED -n com.google.android.apps.mediashell/.AutoStartListener
After that it will run automatically in the background after each reboot, so you will be good to go!
Keep in mind that it might take a few minutes for the receiver to show up in the cast list, if it doesn't show after 10 minutes, try rebooting the device.
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
Supported Apps
Currently not every app is supported. The ones I've tried are:
YouTube - Working
Google Play Music - Working
Google Play Movies & TV - Working
Google+ - Working
Google Photos - Working
Screen Cast - Working (if you follow the instructions above)
Chrome for computer - Working
Netflix - NOT Working (I'm looking into this)
Plex - Working
Chrome for Android - Workinghttps://drive.google.com/file/d/0B4FOzj4b2EYiWVlDTWNGOEw3UTg/view?usp=sharing
Those are the ones I've tried, others may or may not work.
Whether the app will work may also depend on what device you are running the cast receiver on, as well as the region you are in.
FAQ
My device doesn't show up in the official Chromecast app
This is a known "problem" that also affects the ADT-1. There is nothing I can do about it in the Cast Receiver app, only Google can fix it by modifying the Chromecast app. Screen casting etc should work though, it's only the Devices screen that doesn't show any devices.
The receiver doesn't work on my Amazon Fire TV
Please read the instructions under the Running category.
I can't find the receiver device in the cast list
Give it a few minutes. If that doesn't work, try backing out of the app, and enter it again. If it still doesn't show, post a new reply to this thread with a log from logcat.
App X doesn't work
Get me a log when you try to initiate the connection, keeping in mind that some apps may be easier to fix than others. And some may be next to impossible due to them being regional.
How?
I've had some people ask how this was done, so I've written up a list of the changes and a brief summary here:
https://docs.google.com/document/d/1tXnjDdurdoJ4ufulzaqGpuaNpLLt6LGAUk22MO2jta4/edit?usp=sharing
You can get a patch of the smali changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiTHZBRGVUWmlSV1U/view?usp=sharing
And a bsdiff of the lib changes here:
https://drive.google.com/file/d/0B4FOzj4b2EYiNFRfVDhtZXZGcjg/view?usp=sharing
The source code of the Xposed receiver module can be found here:
https://github.com/HomerSp/XposedCastReceiverFix
The source code of the Xposed client module can be found here:
https://github.com/HomerSp/XposedCastClientFix
And finally here is the code I used while testing the receiver, and writing the MediaDrm and JmDNS code:
https://github.com/HomerSp/CastTest
Changelog
Nov 05, 2014
* Fixed receiver not working while connected to ethernet (may be restricted to the Fire TV)
Oct 29, 2014
* Fixed app not working on API level 15 (tested by me on a real device).
* Disabled logging to file - this should significantly reduce the size of the data that's used by the app.
Oct 26, 2014
* Updated to new 5.0 preview from the ADT-1.
* Lowered API level to 15 on the signed version, keep in mind that this is untested by me. This also includes disabling some DRM API calls that were added in API level 18, so Play Movies will not work on API 17 or lower.
Oct 17, 2014
* Fixed receiver not always starting correctly due to device not being provisioned, thanks to @rkirmeier!
Oct 10, 2014
* First version!
Finally I would like to give out a big thank you to @death2all110 for doing extensive testing for me, as well as providing me with the system dump from the ADT-1. I couldn't have done this without him!
Enjoy!
Great! Works flawlessly on my Ouya (CM11). Run on boot via ScriptManager.
If you need help with Netflix you know where to find me!
Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!
krosk said:
Hi,
First of all, thanks, because this works nicely with my laptop! I can finally cast to my living room tv that has an android device connected.
I can cast from Chrome browser (Cast Extension) on OS X, but can't from a 4.2 Android handset (I've tried youtube and google play music). Whenever I try to connect to the Server on a 4.4 radxa rock, the server disappears from the list. It comes back after 10 seconds more or less. Can I help with debug logs or something?
Thanks!
Click to expand...
Click to collapse
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
@death2all110 I probably will, yes. It seems to be restricted to the US for now - I've tried hard-coding a proxy in the code, which makes it go further, but not far enough for it to work. I'll get back to you when I have something for you to test!
HomerSp said:
Do you mean 4.2 or 4.4 (you mentioned both)? I haven't tried compatibility with 4.2, but 4.4 should definitely work. In any case, I would need a logcat from the receiver device to be able to see what's wrong.
Click to expand...
Click to collapse
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.
krosk said:
My phone (4.2) is not connecting to the server (screen) in 4.4. Your app is installed in the 4.4 device. I will send you logs later.
Click to expand...
Click to collapse
Of course, I completely misread your post. Sorry!
Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!
Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.
rkirmeier said:
Im not having any luck on a minix 8h (stock rooted rom - 4.4.2) or Note 12.2 running cm11. Same thing happens for me. Devices show up in the list but when you try to connect it fails and that device disappears from the list for a little while. I installed using root explorer by putting the files in the respected folders then setting the correct permissions and rebooting.
Click to expand...
Click to collapse
What version of Google play services do you have installed on the sender device? Also, a logcat from the receiver would be useful.
astro128 said:
Nexus Q Install?
Any chance this can be installed onto a Nexus Q - I would love to get my Q-Ball back up and running!
Click to expand...
Click to collapse
I don't own a Nexus Q myself, so I won't be able to do any testing. The Q is running a full Android system, right? If it is, the receiver app most likely requires a later API version, or the Q doesn't support some of the features the cast receiver app requires to function.
I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?
rkirmeier said:
I'm casting from a LG G3 and the Google Play services is on version 6.1.74
How can I send you the logcat? Can you PM me your email address?
Click to expand...
Click to collapse
You can attach the logcat to your post, or use something like pastie.org or pastebin.com
Log attached to this post.
rkirmeier said:
Log attached to this post.
Click to expand...
Click to collapse
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
That is correct. I'll work on getting the log from my minix and tablet tonight as they both have the receiver installed and do the same thing.
HomerSp said:
Am I right in assuming that's from your phone? I would need one from the receiver (your X8) because the sender wouldn't output any logging if there was anything wrong, but the receiver will
Click to expand...
Click to collapse
Minix log attached...
Thanks!
rkirmeier said:
Minix log attached...
Thanks!
Click to expand...
Click to collapse
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).
HomerSp said:
Okay, I know why it happens now, but not the reason unfortunately. Do you think that you would be able to get a new log when you restart the media shell service? You should be able to connect to the Minix through the local network using ADB Konnect (https://play.google.com/store/apps/details?id=com.rockolabs.adbkonnect). Simply run ADB Konnect on the device and start the connection, then from your computer run:
adb connect <ip>
adb logcat
From another terminal run:
adb shell am force-stop com.google.android.apps.mediashell
adb shell am startservice -n com.google.android.apps.mediashell/.MediaShellCastReceiverService
The problem is that the signature that is used for device authentication is empty for some reason, and your log doesn't say why (the signature is generated when the service is first started).
Click to expand...
Click to collapse
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.
rkirmeier said:
I'm mostly new to adb other then a dozen or so roots I have applied (by guide) so I'm not sure if I'm doing something wrong here or what. I can connect from both computers and on the device I enter logcat then replies with "- waiting for device -". I know I"m connected because if I try to connect again it says I'm already connected. From the other computer I get the same response for logcat and when I enter your other commands to stop/start the service I get "error: device offline"
Any ideas to work around these issues? I would really like to get you the logs as it seems to be a common issue.
Click to expand...
Click to collapse
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.
HomerSp said:
Is USB debugging enabled on the Minix? Settings > Developer options > USB debugging should be ticked.
Click to expand...
Click to collapse
I confirmed USB Debugging is enabled. Wouldn't this be required to even make the connection?
Now that we have root, what things are we going to be focusing on next? Probably Safestrap and ROMs. What cool things have you guys found with root?
Vlasp said:
Now that we have root, what things are we going to be focusing on next? Probably Safestrap and ROMs. What cool things have you guys found with root?
Click to expand...
Click to collapse
Well for one thing if you disabled/uninstall Unified Search, it allows google search to work correctly in the launcher, also without root you can replace the amazon keyboard with the google keyboard and get voice search.
Edit: We need to probably install Google play services properly to get Google Play Games to work correctly but I am not sure.
The ability to install apps depending on root is awesome.
If you are asking for wishes, then I wish I could use CyanogenMod on this device.
I have de-amazonified my tablet a bit. Cant wait to get a custom rom installed on it though.
we need a safe list with what apps can we delete... i did the same but i don't know for sure what to delete and what to keep... i mention that i don't use amazon apps nor i logged in..
Sent from my KFFOWI using XDA Forums
balanigga said:
we need a safe list with what apps can we delete... i did the same but i don't know for sure what to delete and what to keep... i mention that i don't use amazon apps nor i logged in..
Sent from my KFFOWI using XDA Forums
Click to expand...
Click to collapse
For the moment......
http://forum.xda-developers.com/showpost.php?p=63605889&postcount=77
If wants to remove more can give chmod 000 to apk & reboot before delete
What about reassigning the home button to a different launcher?
xT29c said:
What about reassigning the home button to a different launcher?
Click to expand...
Click to collapse
Just install another launcher and remove FireLauncher from system.
csolanol said:
Just install another launcher and remove FireLauncher from system.
Click to expand...
Click to collapse
Oh, nice. Okay, thanks!
csolanol said:
Just install another launcher and remove FireLauncher from system.
Click to expand...
Click to collapse
how can i do this? thanks in advance
Edit: nevermind I found it, thanks anyway
joelwylde said:
how can i do this? thanks in advance
Click to expand...
Click to collapse
You can use titanium backup, and remove it like that. I would make a backup firs though just in-case.
Also, I need help trying to unhide the firelauncher process. I have the command here "adb shell pm unhide [package:com.amazon.firelauncher]"
But I need the other command first so ADB can talk to my tablet. Because I ran the command, and it just says "true" when it should say "false".
joelwylde said:
how can i do this? thanks in advance
Click to expand...
Click to collapse
Working Launcher replacement thanks to @diegocr and @Awesomeslayerg ! Here's the steps:
1. See @diegocr post at http://forum.xda-developers.com/showpost.php?p=63599598&postcount=23 and download "boot-firelauncher.img"
2. Enable USB debugging
3. Install your launcher of choice!
4. On your computer, run
adb reboot bootloader
Click to expand...
Click to collapse
5. Once your tablet reboots in to fastboot, run on your computer (if you are not in the same directory as boot-firelauncher.img, put the full path):
fastboot boot boot-firelauncher.img
Click to expand...
Click to collapse
6. Tablet will reboot
7. Once booted open an adb shell:
adb shell
Click to expand...
Click to collapse
8. To back up the existing app, run:
cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/Download/com.amazon.firelauncher.apk
Click to expand...
Click to collapse
9. Then nuke it!
rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk
Click to expand...
Click to collapse
10. Now, run to restart your device:
reboot
Click to expand...
Click to collapse
Confirmed working on my tablet with FireOS 5.0.1.
Enjoy!
Forget all the formatting problems
Sent from my KFFOWI using Tapatalk
If you are already rooted you don't need to do all that stuff.
Just adb shell
su
mount -o remount,rw /system
rm -r /system/priv-app/com.amazon.firelauncher or whatever the package is called.
Reboot and it's done.
Remember to install a launcher before this.
csolanol said:
If you are already rooted you don't need to do all that stuff.
Just adb shell
su
mount -o remount,rw /system
rm -r /system/priv-app/com.amazon.firelauncher or whatever the package is called.
Reboot and it's done.
Remember to install a launcher before this.
Click to expand...
Click to collapse
Will this work if I hid the process with ADB before hand? If not, how do I unhide it? What command would I use before "adb shell pm unhide [package:com.amazon.firelauncher]"
Don't know, try if it works hiding, but I doubt it.
I want to replace the hosts file with the one of my Lenovo S660 (China phone). The S660 hosts file is about a mile long and has entries like "0.0.0.0 bad.ad.server" - a very basic but effective way to avoid a lot ads, even at apps. I have not yet took a closer look but I think I would create a mix of both files for the fire.
So, what are the steps?
I have done similar things to my rooted Sony Experia Tipo concerning modifying files at /system, which is mounted RO as default. So I remounted it RW with ES-Explorer, modified what I had to and mounted RO with ES-Explorer again.
I wonder, if this is ok, because of the security means the fire/android has.
I took a chance and I was successfull.
I attached the unchanged hosts file from my Lenovo S660 /system/etc/ as hosts.lenovo.zip file. The fire hosts has just 1 line: 127.0.0.1 localhost. The lenovo's hosts has 25858 lines.
Code:
- unzip hosts.lenovo.zip -> you get host.lenovo
- rename hosts.lenovo to hosts
- connect fire
- adb push hosts /data
- adb shell
- $ su -
- # cd /data
- # chmod 644 hosts
- # exit
- $ exit
- ES Explorer
- Enable root explorer
- remount /system rw
- go to /data
- mark hosts
- cut hosts (to memory)
- go to /system/etc
- mark hosts
- rename hosts to hosts.old
- insert hosts from memory
- remount /system ro
- exit ES Explorer
done.
should work, use at own risk.
Note: You cannot chmod 644 at /mnt/sdcard1 because it is vfat there, that's why you use /data.
Note: You cannot write to /system/etc while at adb shell, even if it is mounted RW, that's why you have to use ES Explorer which will ask you to choose the path with android overlay window - which makes it work (at least my experience).
If you have apps which showed ads before, then you might keep on seeing the very last forever. Or a broken link sign. Or even a popop with broken link sign. Or your ads hosts is missing at the lenovo hosts file and you keep on seeing ads. There even my be websites you cannot visit anymore - which I have not yet experienced, but the risk exists, or will come.
If interested, take a look at http://winhelp2002.mvps.org/hosts.htm for more information and use for your windows or linux pc.
If you don't like it you can go back, you have a copy of your old hosts file.
I want to replace the hosts file with the one of my Lenovo S660 (China phone). The S660 hosts file is about a mile long and has entries like "0.0.0.0 bad.ad.server" - a very basic but effective way to avoid a lot ads, even at apps.
Click to expand...
Click to collapse
Check out the adaway app (open source). It blocks ads through the host file just like you're doing except it puts the host file in place for you, combines host files from a couple different sources (running de-duplication on them) & auto updates your host file as new ad severs are added or removed. Absolutely beats rolling your own host file manually.
That is new information to me, thanks.
Hi all,
Found my old Kindle Fire2 lying around so thought i'd have a go at building whatever I can for it. Seems like there was already source code in the repo's for CM 12.1 but nobody had built it. Well I've built it and it seems to work fine!
Only had to fix a script which had broken since CM 11 for wifi and all seems good.
NOTE RE MAC ADDRESS
FYI your MAC address will now get randomly generated at first boot. If keeping your existing MAC address is important, don't flash this.
I can't take any responsiblity for this, I've purely built it and fixed a couple of issues. Please thank whoever contributed to the source in the repo's.
I've only installed from a complete wipe. Don't try it unless you're prepared to wipe your device.
Enjoy...
ROM
cm-12.1-20170728-UNOFFICIAL-otter2.zip
Open Gapps pico for 5.1
http://opengapps.org/?download=true&arch=arm&api=5.1&variant=pico
Going to have a go at building CM13 next. Tried 14.1 but got hung up on selinux issues so going to take a step back to CM13.
Original link fixed
I need to fix the wifi script at boot. Currently if you install the rom you'll need to open a terminal and run:
/system/bin/fix-mac.sh
Wifi should start shortly after...
works perfect.
also perfect timing. i picked the otter2 yesterday from my dads house, who didnt use it anymore, because he switched to an galaxy tab long time ago.
I am currently having trouble with the Wi-Fi
It just hangs at Turning on Wi-Fi!
I have tried to clear cache and dalvik cache after installing gapps and lineage
I also performed a full wipe before flashing the rom
EDIT: Sorry didn't read further down
I am having an interesting problem with this ROM. It appears stable until I install any app, either from APK or play store. afterward everything force closes and will not work again until data is wiped or permissions repaired. when the permissions are repaired, any installed apps from APK or play store vanish like they were never installed. copying anything to /system/app works fine, but that is not a long term solution.
Raised a couple of threads about the wifi issue for a bit of help but nobody had replied. I'll have another look when I have time. Can't say i had any issues after installing app's though.
Think I might have fixed the selinux policy as i misread the neverallow rule and didn't realise it actually excludes sdcards from remount, so I can explicitly allow it.
Hopefully new fixed build to come soon.
Hi, I know a few people have asked about the Wi-Fi issue, but im not aware of how to open a terminal once everything is installed. the only terminal I can find is in the recovery mode but it wont find the file you mentioned
I just flashed and executed /system/bin/fix-mac.sh after installing "super su", but still WIFI does not start. Any additional hints? Thank you very much for the efforts.
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
guys do you have the latest twrp for kf2? all links are dead on other threads.
Apologies if this is obvious - but how did you install the latest SuperSU without Wi-Fi? Is it a case of downloading the apk and transferring via adb?
Is the build working otherwise? The old CM one is beyond repair - works for a couple days and then gets itself into boot loop.
Thanks!
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse
---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse
not work:crying:
rapmen said:
---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
not work:crying:
Click to expand...
Click to collapse
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...
nebula_rider said:
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...
Click to expand...
Click to collapse
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!
androidbenutzer said:
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!
Click to expand...
Click to collapse
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!
nebula_rider said:
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!
Click to expand...
Click to collapse
I tried all the steps, and still no luck.
pakidermo5000 said:
I tried all the steps, and still no luck.
Click to expand...
Click to collapse
Actually you wouldn't get too far even if you could turn the wi-fi on. The build is plagued with the "Trebuchet has stopped" error, which apparently is common in CM. I tried every fix recommended online, without success.
I didn't read the entire thread but here's a super easy way to fix the wifi issue. Connect a USB cable from the Otter2 to your computer. Make sure you have adb installed. Open a command prompt and type:
adb.exe /devices
Now look at the security message on the tablet. Click yes
adb.exe shell
At the shell prompt, type the following:
[email protected]:/ # /system/bin/fix-mac.sh
---------- Post added at 02:42 PM ---------- Previous post was at 02:05 PM ----------
SuperSu is here:
http://rootmygalaxy.net/download-latest-supersu-v2-82/