yashsingh1/xdaforums huggingface dataset:
[Google Chromecast] third son:
Sorry I should have seen this post first but I didn't and posted about my Nexus 5 and the 4.3.3 update. I can mirror using my rooted US Chromecast with Eureka-ROM. No sound when running video.
[Google Chromecast] q8wii:
Did there Havey lag or not
[Google Chromecast] Ridg-droid:
I've got the same setup N5 (stock rooter) and CC (US rooted). The screen casting was there before 4.4.3, it's pretty smooth but the lack of sound is the real kicker. Great for sharing photos.
[Google Chromecast] generationgav:
N4 on 4.4.3 and stock CC (usa) - mirror fails.
[Google Chromecast] xlxcrossing:
Its incredibly ironic to me that Google made JB Miracast compatible but haven't added support for native mirroring in Android. What's more I dont hear any major tech sources talking about it. Last news was that as of 4.3 Google was going to add support for Chromecast mirroring "soon". Its been half a year and doesn't seem to really be a priority for Google. I hope they focus their efforts on this feature for the next major release.
[Google Chromecast] extrem0:
I don't think it's about Android version, but google play services.
[Google Chromecast] samnaqvi:
Middle East has nothing

Strangely, I got the 4.4.3 update a couple of days ago, but the screen cast option does not show my chrome cast in the list of available devices. It appeared there once, with (beta) in brackets, but never after that - nor does it appear in quick settings.

Stock N5, rooted.
[Google Chromecast] e.lopez:
^^^

screen cast needs to be 'triggered' with a chromecast compatible app first. then your CC will show up (and fail to connect) as a screen casting device.
[Google Chromecast] r3pwn:
I believe in order to fully sort out how this works (may be same as before), please post

Android Version on the device FROM which you are streaming, whether or not your chromecast is running Eureka ROM, what region your Chromecast is from, and wether streaming has worked for you before.
[Google Chromecast] Asphyx:
While what Version of Android you have is important, it's not as important as having a rooted CCast is!

You must have a rooted CCast running Eureka to get mirroring to work!

If your CCast is stock then your SOL until such time as Google Whitelists the CCast Mirroring receiver!
[Google Chromecast] e.lopez:
^^^

even with rooted CC, still of little value to me and probably others with no sound.
[Google Chromecast] Asphyx:
Which could very well be the reason why Google hasn't really released this to the public yet!

I expect them to have it done by Google I/O.
[Google Chromecast] e.lopez:
i'm wondering if loss of app commissions is in play. screen casting would render app casting functionality moot.
[Google Chromecast] bhiga:
Actually this is very far from the case.

Screen casting:

+ Works for all apps

+ Works for interactivity (games, etc)

+ Works with more video/audio formats, especially if using player like MX Player

- Is prone to lag, requires hardware compression for maximum speed

- Requires the device to remain on and running

- Is dependent on stable bandwidth between the device and Chromecast

? Runs at device resolution

Chromecast playback:

+ Works at full resolution up to 1080p

+ Does not require casting device to remain on/connected

+ Control from any (supported) device on the network

- Does not work with all video/audio formats

- Interactivity requires app support

Screen casting requires significantly more system resources - and the native screen casting reportedly does not support audio at the moment.
[Google Chromecast] Asphyx:
Yeah I totally disagree...Mirroring REQUIRES the device you are mirroring to stay connected...

The Apps do not...

And Playing DIRECTLY to the CCast may increase quality because the Apps are forced to send lower quality streams to stay under the device's hardware limitations where sending links to the CCast could display content from a much better transcoder.

bhiga explains it all in more detail...

There is a REASON why Google made the CCast the way it did!
[Google Chromecast] e.lopez:
not sure i understand your point.

i'm saying mirroring functionality is possibly being delayed because once available, app casting is less important. apps drive some amount of revenue so why cut that revenue stream?
[Google Chromecast] Asphyx:
It's not!

Mirroring is less than 25% Quality of the Apps!

because it requires a mobile device to do the encoding while the CCast with a Server like Plex can show, transcode and stream full 1080P with Surround!

If you tried that with mirroring you would get 10 FPS....

It will NEVER replace Apps....

And google knows that the issue isn't what Mirroring will do to apps because it doesn't do anything towards that...

It's delayed because VERY FEW devices can actually do it and since there are no other big announcements to make about the CCast other than where it is now available, Google is waiting to perfect and then announce it at Google I/O
[Google Chromecast] e.lopez:
^^^

i'm fairly content with N7v2 mirroring to ptv3K. mirror dishanywhere daily with no delays. if run for several hours, audio will tend to drift. with latest kindle fire though, mirroring to ptv3k is rock solid.
[Google Chromecast] irish-sid:
So what you're saying is an aosp 4.4.3 rom on the note3 should do this very nicely indeed?
[Google Chromecast] e.lopez:
mirror to ptv3k? see no reason why not. the note3 has better resolution and newer wifi chipset than the n7v2. should work well.
[Google Chromecast] third son:
Correction :sound works for me
[Google Chromecast] q8wii:
How ???
[Google Chromecast] third son:
I dunno it just does.... Rooted everything and nexus 5 Eureka
[Google Chromecast] iconrd:
Hey guys , I don't know if anyone has done this already on there US non rooted CC to get the new mirror casting app to hold a connection with N7 2013. I enable NFC with android Beam in setting , then launched Castaway to connect CC, once connection was made I then launched the Cast Screen and connect to CC , while having my N7 physically touching the CC device (back to back) as indicated by the Beam instruction. I actually got it to hold the connection instead of it the usual fail to connect that everyone is getting in US. Anyhow I figured to share with you guys knowing you developers would know what to do next to further along the progress in getting it up and running correct. Hope this helps.
[Google Chromecast] bhiga:
I bet this works just as well with NFC off. The key is more likely the fact that both devices are getting the same WiFi signal quality as they're right next to each other.

Of course, I could be wrong and there is something magical about having NFC enabled...
[Google Chromecast] third son:
I will say it is far from optimal...I can cast a *.flv via MXplayer to my screen with sound but the sound will stutter a bit. The video is fine though.
[Google Chromecast] Stevethegreat:
Say you wanna cast some app with streaming video content on TV. Also (say) that app is using efficient compression so the total image is rather "lightweight", would I still get a stuttering image/video? If so can I have the audio playing "locally" and choose just the image to be casted?

I'm asking 'cause my chromecast came with an unrootable firmware, but if what you say works (I mean if it works well), I would sell it to buy a rootable chromecast so that to be able to cast my whole phone to my TV...
[Google Chromecast] bhiga:
Depends on what the choke point is. Without a hardware CODEC to handle the compression for what's being sent to Chromecast I would say in many cases you could be CPU-bound. But smarter apps like MX Player use hardware acceleration for the decode, leaving most of the CPU for compression. So again, difficult to say. Actually, since "lighter" compression tends not to be as problematic so it's sometimes less likely to use hardware acceleration and just uses CPU, which in this case would be a disadvantage since less CPU time is available.

Playing the audio locally would likely be out of sync with what you see on Chromecast because of the added delay for compression (to send to Chromecast), network latency, and decompression on Chromecast. So the audio on your device would play ahead of the associated video from Chromecast.

Since this functionality is in beta and will eventually be released to everyone, I'm not sure I would get a rooted Chromecast just for this, but it's your choice.
[Google Chromecast] Stevethegreat:
I would routinely play 1080p content using software decoder (the cpu does it all). My device offers galaxy S5 grade performance (~36000 antutu score). The only choke point can be on the client end (cc) or the protocol itself. And yes I know it's not officially supported but it may take at least 4-6 months to become so, and streaming *that* channel (if it is possible of course) *is* a big deal to me.

So as long as I'd be able to do so without a hitch it would indeed warrant the purchase of a new CC for me... Thanks for the info by the way...
[Google Chromecast] bhiga:
Encoding is more intensive than decoding (and it's more a matter of compression format than resolution) so I wouldn't put money on it just yet. ;)

Watch the video for mirror4cast to get an idea of what pure software compression lag is like.

But I do suspect that Google's mirroring is using some hardware acceleration, which is why the supported devices are limited.

-= this post enhanced with bonus mobile typos =-
[Google Chromecast] Stevethegreat:
Indeed but evidently CC mirroring works much faster than that, which is exactly what I'm trying to make out from users who tried it.

Reading the reports you can see that video works but sound doesn't, it either stutters or doesn't work at all. But what we do not know is the kind of setups those results happened. For example Nexus 7 (the original) is old news by now, any decent modern devices can post twice or thrice the performance. So having stutters there may not mean that we will have stutters "here" (2014 devices).

As for the sound playing first if it is to be played locally, I guess we can use some kind of sound delay overlay, which would synchronize the sound with the image. So you'd get both at the same time, I dunno, maybe there is already an xposed module for that (sound delay)...
[Google Chromecast] third son:
The audio is in sync it just stutters a bit... Video quality is excellent

---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
[Google Chromecast] xlxcrossing:
During Google I/0 I noticed they were using an app to mirror. Will the "cast screen" setting be used because it's been dormant since 4.3. I have a Droid DNA which works great with my Chromecast but does anyone have any info about the hardware requirements for mirroring?
[Google Chromecast] bkob024:
working for me

I'm using a nexus 7 2013 lte and I've been able to cast my screen for a couple weeks. They added the support for it in one of the recent updates. My Chromecast isn't rooted and I've tried it on the stock ROM as we'll as on CM which I'm running now. Sound and video work great. Even better than the results I experienced from casting from other apps like avia or plex. I can even hook up my otg cable with a controller and play games on my TV. There's about a half second latency so its not the best for playing from the TV but people can watch you play. It would be a good way to do videos for YouTube maybe.
[Google Chromecast] Asphyx:
The Stuttering or not working at all seems to be related to Audio Drivers baked into the ROM of the device...Not the actual Mirroring system itself...

If you read the Mirror Enabler thread you see that Many have solved their no Audio issues by asking their Rom Dev to include an additional Audio Package into their MK files.

As for the stuttering audio it can come from many things...Non Optimized ROMs, Slow/Old Hardware and Proc, Even a low Available Ram state because they installed 500 pounds of Apps and files which slows the device down to a crawl.
[Google Chromecast] hwong96:
Wifi latency could also impact audio. Are you using a fairly new n wifi router? The netgear nighthawk wifi router has up to 600 Mbps throughput on n wifi.
[Google Chromecast] Asphyx:
I'm not getting Mirroring to work at all...The CM Dev for the Droid4 hasn't incorporated the packages I need yet, and thats assuming those packages will change the Mirror situation for my device.

It's possible it needs some kernel support as well.

I have a Linksys 4500...About the best you can find in an N router than isn't an AC router...
[Google Chromecast] hwong96:
Here are the prerequisites for wifidisplay (cast screen) to work in kitkat straight from google source.

* The Audio Flinger audio_policy.conf file must specify a rule for the "r_submix"

remote submix module. This module is used to record and stream system

audio output to the WiFi display encoder in the media server. added manually or with mirrorenabler v2-v4

* The remote submix module "audio.r_submix.default" must be installed on the device. added by ROM devs or self compiled

Without these items wifidisplay/audio will not work.
[Google Chromecast] Asphyx:
Your kernel also has to be compatible with those packages otherwise those packages aren't enough.
[Android Q&A, Help & Troubleshooting] awaisagha:
HI

I am new to this forum but previously been reading articles on this forum.

I recently bought Huawei G610 Android phone and it has 4.2.1 and it is NOT rooted. I am using stock ROM and i am happy with it.

I have come across some problems which i wanted to ask for help.

1. In Huawei theme mode (native) i cannot set scrollable wallpaper, when i try to set it, it asks for cropping and it gives me 2 rectangles. If i am using a native screen resolution wallpaper, even then it asks for cropping. These 2 rectangles are in such way that i HAVE to set an area for best option even with full extreme resized. It doesn't allow scrolling the wallpaper and there is no option in "settings>display" to have scroll option enable or disable.

2. I installed Go Launcher and it allows to scroll the wallpaper BUT again resizes like the previous stock launcher. It scrolls but in the area of 2 rectangles. I cannot set the full length of wallpaper.

3. In stock theme when i hold the "menu" button it shows the currently running apps. I choose to run the ones i want and close the rest. In Go Launcher when i click on "background running apps" it shows me a big list of apps running in background BUT again when i hold-press the "menu" button to see the background running apps,then it has the ones which i want to run but in Go Launcher it is showing even the play store,clock,settings etc running. What is this difference?
[Galaxy S 4 Q&A, Help & Troubleshooting] ratto000:
Hello Guys,

I have a S4 I9505 international with ZTO (Brasil) I9505VJUGNE2 firmware.

Today, after some screen locks issues, I decided to do a factory reset.

Everything works well, but I realized the option "lock instantly with power key" does NOT work anymore.

Even this option unticked or lock automatically set to more then Immediately, the phone goes to lock screen after timeout or after I press the power button.

In other words, if the screen turns off, the phone locks.

I've tried another hard reset, set/unset/change all relateds lock functions and not works.

The only way to get the phone unlocked after screens turns off is set Screen Lock to NONE.

Anyone have an idea to fix this? :eek:

Thank you very much.

UPDATE: The problem is solved when KNOX are configured. If I reset KNOX data or disable KNOX app, the problem returns and remains.
[Galaxy S 4 Q&A, Help & Troubleshooting] zuksh:
I am having the same problem. It only appeared after a recent update which added the Kids Mode feature (which I did not install). WTF samsung... stop messing about with basic features and fix this bug. I do NOT want the power button to instantly lock my phone...

Can you please explain how you fixed it? I never downloaded knox on my phone. Do I now have to have knox to resolve this isse?
[Galaxy S 4 Q&A, Help & Troubleshooting] ratto000:
Knox is like a virtual OS inside your actual android system. It was developed by Samsung for corporate and security purposes.

You can see more detail regarding here: http://xdaforums.com/showthread.php?t=2595889

If you have a oficial Kit Kat 4.4.2 from Samsung, you already have Knox, to setup it, just launch knox app from app drawer, choose a security option, put your password and you are inside Knox (if some files are necessary to run, setup will ask to download. Stay on a wifi at this point).

Thats all... play with Knox... for me, after this procedure, the lock behavior returned to normal..

Good luck
[Samsung Gear 2 Neo] BaXo95:
Hi, I've a gear 2 neo paired with my s3 with the latest omegarom (samsung based). I installed and paired without any kind of problem, it shows everything but notfications and media controls don't work! How could I solve it?
[Samsung Gear 2 Neo] BaXo95:
Fixed with an upgrade, moderators can close the thread! ;)
[One (M8) Q&A, Help & Troubleshooting] andiedee:
There is nothing (I accidently formated my data, system etc thinking it will fix something. In the SD card. I'm trying to sideload viperonem8 through recovery Using TWRP. & i get this error.

I also formatted "boot" ...

I tried sideloading it. (Yes i've tried .zip.zip as well.

http://puu.sh/9gt6E/0779ce3033.png

It's clearly in my folder named "ROM.zip"

http://puu.sh/9gtik/5640728ee6.png

If i try to push ... i get:

http://puu.sh/9gDew/e7aae6bf8e.png

I'm getting frustrated and out of options please help :(
[One (M8) Q&A, Help & Troubleshooting] wtoj34:
EDIT. Thought I was in Verizon qna however the answer is still practically the same. The ruu can patch you up fine
[One (M8) Q&A, Help & Troubleshooting] GermanGuy:
Looks like everything is in the right place. Maybe redownload your ROM to make sure the zip is not corrupted?
[One (M8) Q&A, Help & Troubleshooting] andiedee:
need more info then that ....
[One (M8) Q&A, Help & Troubleshooting] andiedee:
found another issue http://puu.sh/9gDew/e7aae6bf8e.png
[One (M8) Q&A, Help & Troubleshooting] xavier2k3:
And you can't boot into recovery directly and flash from there instead of going through adb?

If not, as mentioned previously, flash the RUU and that should fix everything.
[One (M8) Q&A, Help & Troubleshooting] andiedee:
Run me down by steps? because i cant flash into through recovery without having the file there? there is no rom on my phone. Nothing at all. the Internal SD is empty.
[One (M8) Q&A, Help & Troubleshooting] robocuff:
Too push the rom you used:

adb push rom.zip \scard

I believe it should be:

adb push rom.zip /sdcard

Notice the slash before sdcard.
[One (M8) Q&A, Help & Troubleshooting] NiquiSE:
Actually

adb push rom.zip /sdcard/

should work for him if he wants to push it that way
[One (M8) Q&A, Help & Troubleshooting] newstar:
Follow last poster

Posted From HTC 1 M8 via TapaTalk Pro .
[One (M8) Q&A, Help & Troubleshooting] andiedee:
I worked it out, The ROM.zip i was trying to sideload/push was corrupted. downloaded gpe stock rom and sideloaded perfectly fixed my phone..

thanks everyone ! :)
[One (M8) Q&A, Help & Troubleshooting] NiquiSE:
Glad to hear! Make that nandroid backup buddy :)
[Xperia Z2 Q&A, Help & Troubleshooting] rappa619:
Does a full wipe in CWM Recovery not work on the z2 since the kernel and recovery are together? Like in storage if you wipe /system and /data to fully wipe the phone and then install fresh. Would this just kick you out of recovery, making you have to flash the recovery using fastboot again?

Or does the recovery stay in the memory until a reboot? So that you can install a kernel with recovery again before rebooting?
[Xperia Z2 Q&A, Help & Troubleshooting] Michealtbh:
It works fine
[Xperia Z2 Q&A, Help & Troubleshooting] funky0308:
Full wipe won't harm recovery.

You could always make flashable recovery and flash after wipe (before restarting, of course) just to be sure...
[Xperia Z2 Q&A, Help & Troubleshooting] KrisPerry:
I don't think the kernel and recovery are together as such
[Xperia Z2 Q&A, Help & Troubleshooting] pvyParts:
On most of the sony devices i have played with the recovery is in the Ramdisk ( in the boot.img ) or it can be stored in the FOTA Partition and called upon by the kernel / ramdisk at boot.

a full wipe wont touch either of these.

pvy.
[Xperia Z2 Q&A, Help & Troubleshooting] rappa619:
Ok thank you for explaining.
[Xperia Z2 Q&A, Help & Troubleshooting] KrisPerry:
On all of the Android devices if had a full wipe has never wiped recovery.
[Xperia Z2 Q&A, Help & Troubleshooting] pvyParts:
Early xperias with locked bootloaders and root exploits had recovery in system partition. ;)

Pvy

Sent via my wireless blackbox
[G Pad 8.3 Q&A, Help & Troubleshooting] IBJamon:
Does anyone know if any scripts are executed (or can be executed) when the SD card is mounted? Of course this would include on boot.

What I am trying to accomplish is that I would like to mount in a second path the fat32 external partition as the system user (with an appropriate umask) so that I can symlink data from the /data/app directory. I don't mind copying the .apk files and just symlinking them individually; I currently have over 5GB of files there, so I know it should really help with saving space. And, this way I can still take advantage of the space as is, rather than losing it all to a directory symlink.

I don't mind resymlinking once in a while after I add/remove some software. I am a long time Linux user (personally and professionally) so a little command line doesn't scare me one bit. :)

I thought I should mention that I am currently using LRS G Pad, so a solution that works on stock (or stock-like) ROMs is preferred, though I am curious what a custom ROM can buy me in this area also.

Thank you for your help!
[G Pad 8.3 Q&A, Help & Troubleshooting] sleekmason:
Maybe take a look at tasker to initiate a command. I too had hoped to use a Linux command for a different reason, only to find everything to be different enough to be a problem. Tasker will allow the command, but knowing where to put it will be the problem. Writing a script that recognizes "fuse" initiation, outing it in init.d, and then using tasker to initiate the script?

Maybe just tasker, as you can write simple one liners for different tasks(turning things off and on with a simple path).

Doing this from the kernel ramdisk would probably be better.

Please describe exactly how you do this if you figure it out please!

Best regards,
[JAM, MDA Compact, S100 General] max414:
hi wanna ask if am i am sending a file larger than 8mb through resco explorer and if i press power on jam while it is sending it doesnt send anymore and i have to keep screen on while sending is it usual?

what is best method to send files via bluetooth.....?
[Nexus 4 Q&A, Help & Troubleshooting] shaggydiamond:
Today I got a call but the title of the call was: "currently only supporting US numbers"

What is this? It was a number in my home country but I'd rather have the dialer not show me this title.

I'm on c-rom and I think it's Google dialer

Help would be appreciated
[Nexus 4 Q&A, Help & Troubleshooting] shaggydiamond:
Found it, it were the people lookup settings