Good news: I took adavantage of Samsung's 50% off special to pick up an Allshare dongle for $50.
Bad news: Can't get it working on my rooted TMO GNII.
This is what happens *every time* I try to connect (20-30 times)
Hooked up dongle to TV via HDMI. TV shows Allshare ready to connect on the screen.
With the red led flashing on dongle, I press the reset button and the led changes to solid blue.
On phone, try to connect with Allshare Cast utility.
Phone sees and connects to dongle.
Screen on TV changes to screen with black background and says connecting, but never gets any further and never shows the phone screen on the TV. (See attached image)
Connection is lost after 10 seconds and this message appears in a pop up on phone: "Current AllShare Cast connection will end."
Here's what I've tried so far. Each time getting the same result as described:
Updating Allshare Cast app from Play store.
In SuperSU app, unrooting phone by unchecking Enable Superuser.
Restoring stock T-Mobile rom from nandroid backup, with and without Superuser enabled.
Installing and running Triangle Away 3 times in a row. This got the flash counter down to 1, but not 0. Also shows Binary status: Custom.
In stock rom and with SU disabled, the phone downloaded and sent a firmware update to the dongle, but this update did not change results at all.
Hoping someone can give me something else to try. If not I may have to completely unroot and restore stock image to verify this works at all. Then go step by step through rooting, adding back Clockwork recovery, etc. to see where the Allshare connection gets broken.
Get the triangle away app. Reboot and enjoy. Theres a thread on getting this to work, and I can attest to it working cause im rooted custom rom and enjoying my allshare
Also try uninstalling triangle away and reinstalling. When you run the app does it reboot your phone for you? Mine does and thats when I know it works.
Sent from my SPH-L900 using Tapatalk 2
globen said:
Get the triangle away app. Reboot and enjoy. Theres a thread on getting this to work, and I can attest to it working cause im rooted custom rom and enjoying my allshare
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Already tried this, 3 times. Yes, it rebooted my phone. I wish it had worked for me! Will try uninstall/reinstall of TA as you suggest. So what rom/recovery are you using? When you do a Vol down/Home/Power button boot up, what does it say for your Counter and Binary Status?
Yup I'm seeing the same problem but with Wanam RIM.
Sent from a Toaster using XDA App
Had same problem. I could almost cut and paste your post OP. Its not root status, nor does a custom rom necessarily bugger allcast function; its the kernal. You currently cannot run any custom kernal and have allcast function. Triangle Away is powerless in the face of this vial DRM kernel menace.
You can mix and match or use some modded roms and you can debloat and/ or freeze much of your junk. When using triangle away for the allcast dongle TA activation must be done in a paticular sequence...
Chainfire gives detailed info in his "triangle away" thread. ( you've propbably found this already but if you haven't, then it is a must read.)
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
vizographic said:
Had same problem. I could almost cut and paste your post OP. Its not root status, nor does a custom rom necessarily bugger allcast function; its the kernal. You currently cannot run any custom kernal and have allcast function. Triangle Away is powerless in the face of this vial DRM kernel menace.
You can mix and match or use some modded roms and you can debloat and/ or freeze much of your junk. When using triangle away for the allcast dongle TA activation must be done in a paticular sequence...
Chainfire gives detailed info in his "triangle away" thread. ( you've propbably found this already but if you haven't, then it is a must read.)
Click to expand...
Click to collapse
So if I understand correctly, being rooted and having a custom ROM do *NOT* prevent the dongle connection from working. It's having a non-stock kernel that makes it not connect, is that correct? So in theory if I restore the stock rom from my nandroid backup, and correctly run TA, it should work fine? Now what about having a custom recovery? Does that have any effect on the Allshare dongle? I have Clockwork. Do I also need to restore the stock recovery?
Also, in the TA thread, I'm not seeing the part about "When using triangle away for the allcast dongle, TA activation must be done in a paticular sequence... " Could you please copy and paste that part into this thread? Thanks.
Yep, you got it right vouty. The kernal must be stock to connect allcast dongle. The rom can be modified stock or custom but your success may vary.
You can be rooted....and you can use custom recovery, I am using use twrp (cmw is said to also work).
[But if you use a custom recovery, my current understanding is that, your flash counter will be reset from 0 to 1 on a boot up. Take this with a grain of salt. ]
I refered to a sequence, sorry if I made it more complicated than necessary. Just reflash triangle away, and don't check the counter, if you do it will set counter back to one if you have a custom recovery. Hope this helps, the dongle works really well, you're going to like it.
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
vizographic said:
Yep, you got it right vouty. The kernal must be stock to connect allcast dongle. The rom can be modified stock or custom but your success may vary.
You can be rooted....and you can use custom recovery, I am using use twrp (cmw is said to also work).
[But if you use a custom recovery, my current understanding is that, your flash counter will be reset from 0 to 1 on a boot up. Take this with a grain of salt. ]
I refered to a sequence, sorry if I made it more complicated than necessary. Just reflash triangle away, and don't check the counter, if you do it will set counter back to one if you have a custom recovery. Hope this helps, the dongle works really well, you're going to like it.
Click to expand...
Click to collapse
Thanks for getting back Vizo. So I got it working! I tried restoring the stock rom from nandroid, restoring the stock recovery, then running TA, but still didn't work. At that point I know I'm gonna have to do a full stock image restore and what I chose was this method from mrRobinson: http://forum.xda-developers.com/showthread.php?t=1975560
If you follow the simple steps, as written in the thread, this will fully restore stock ROM, recovery and wipe the Internal SD space putting your T-Mobile Note II back to perfect, out of box condition, with Device Status showing "Normal" and counter status as original... BUT PHONE IS ROOTED! And it does it all in just one easy step. Definitely owe mrRobinson a beer.
The dongle is now working with my phone and it is awesome! Already got Netflix streaming installed and working. Gotta hand it to Samsung. Allshare cast is a "Killer App"!!!
Only remaining issue is that I don't have a custom recovery, so no flashing any goodies like custom toggles, status bar mods, or 4.2 camera for now. Want to enjoy the Allshare goodness for awhile before I risk breaking it with Clockwork and TA not being able to fix it. Hoping Chainfire can work his magic on this issue and break the triangle's back permanently!
interesting to hear everyone's experiences with the dongle problem. i was having similar problems but had the luxury of testing out with my rooted t-mobile note II and wife's stock ATT note II. i was getting the exact same "connection will end message" on both phones. decided to change TV's and found that i was able to use the allsharecast dongle without any problems. didn't have to restore or change anything. worked right away after plugging in to different tv. i'm wondering if there may be some incompatibility with the HDMI signal or connection with the TV that could be contributing to dongle connection problems?
Disclaimer: troll post.
ok, here we go:
mochishiro said:
interesting to hear everyone's experiences with the dongle problem
Click to expand...
Click to collapse
Lmao. and
Super lmao:
Hi everyone. I get the same issue as Vouty.
vouty said:
This is what happens *every time* I try to connect (20-30 times) (...)
Click to expand...
Click to collapse
My phone has never been rooted or changed - it is totally original, straight out of the box. I can't do anything to connect to this Dongle thing. Please help me if you can.
Hmm have you tried a different tv. It has worked on all the tv's I've tried mine on but some have reported that this can work...also just to clarify things did u run the update from the play store?
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
mjaz85 said:
Hi everyone. I get the same issue as Vouty.
My phone has never been rooted or changed - it is totally original, straight out of the box. I can't do anything to connect to this Dongle thing. Please help me if you can.
Click to expand...
Click to collapse
Things to check:
System settings>About device>Status - Scroll to last item, Device status. It should say "Normal." If it says anything else, like "modified," then it probably won't work.
Check everything is right with the dongle connections:
I would suggest using the HDMI cable that comes with the dongle, just to rule that out.
Ensure you are "pairing" correctly. The correct steps are to *FIRST* put the dongle in pairing mode. Start by unplugging the power and plug back in. Wait for the led on the dongle to start flashing red. Tap (do not long-press) the reset button. This should immediately make the led turn solid blue. It *will not* pair unless the led is solid blue. When the led is solid blue, the dongle is ready to pair. Now on the phone, pull down the notification bar and tap the Allshare toggle (it's way over on the right). It should see and connect to the dongle. Like bluetooth, you only need to pair the first time. After that, it will auto-connect everytime you toggle on Allshare and the dongle is in range.
Once I restored my GNII to factory stock, as I described, the pairing worked perfectly, the first time, and has been working ever since. Good luck!
vizographic said:
Hmm have you tried a different tv. It has worked on all the tv's I've tried mine on but some have reported that this can work...also just to clarify things did u run the update from the play store?
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I suppose anything is possible and that there could be TV's out there with old, non-compliant HDMI inputs. But if anyone was gonna have this issue, it would be me. My TV is a cruddy, 5 yr old Olevia 26" 720p hunk of junk from Frys. Yet every HDMI signal I've ever plugged in (Windows laptops, weird DVI-HDMI ebay media players, even my old HTC Sensation with an MHL adapter) have worked fine. Hoping Santa brings me a nice shiny new "ultra-thin" full HD resolution HDTV for XMAS!
Help Please
Got my Note 10.1 about a week ago along wıth AllShare Cast Dongle. Everything worked fine at first but after doıng a factory reset (which I was advısed to do by Samsung Support because of some dısappearing icons) I can connect but after about 2-5 minutes of video the pıcture freezes on both TV & Tablet . Get a message on tablet - Allshare connection is unstable - then - Current Allshare Cast Connection will end. The frozen pıcture on the screen then breaks up and goes to green screen.
If I try to connect at this stage Tablet cannot see the dongle (blue light on) & only way to get ıt seeıng ıt agaın ıs to take out power lead for a few minutes.
Unfortunately I am in Turkey at the moment so cannot go to Samsung Service Centre (language problems) so if anyone can give me any advice it would be much appreciated.
This is my fırst Android device and everything is stock. Still running ICS.
1st Have you applied the allshare cast update? There were a lot of reports of sketchy connection issues with the allshare dongle. The recent firmware update from the playstore seems to have fixed many of them.
2nd which phone are you on? You mention you are on ics. If its not the dongle it does complicate matters a bit, since I'm on jellybean. Still, If you can answer the first update question, and provide ,model ,make ,rooted and /or
non/stock plus kernel info, I'll do what I can to help.
3rd, Turkey! You traveling on business or pleasure? What are your impressions? Always wanted to travel out that way, find it a fascinating country as a serious history buff......
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
vouty said:
System settings>About device>Status - Scroll to last item, Device status. It should say Normal.
I would suggest using the HDMI cable that comes with the dongle, just to rule that out.
Ensure you are "pairing" correctly.
Click to expand...
Click to collapse
Everything is just as described above. Can't connect to my home TV but I've connected without any problems to different TV. Can the problems relate to WiFi settings? How is data transmitted between dongle and TV?
Thanks for your time Vizographic
Did mention in my post usıng Samsung Galaxy Note 10.1 Tablet. Received an update to dongle last nıght just before I posted, did not appear to make any difference. Just tried again and video ran for just under 5 minutes before connection stopped and reported unstable. Everything stock (have not played with anything apart from factory reset) Android Version 4.0.4 as have not yet received the upgrade to JB.
I now live in Turkey and have no intentions of movıng again - beautiful country, very friendly people (now have a Turkish wife) and a nice climate. If you are a history buff Ephesus about 1.5 hours away and Troy about 5 hour drive. Did not buy tablet here as electronics about double the price of the States.
uzumlubay, its seems I missed this detail, in the first sentence of your post....
"Did mention in my post usıng Samsung Galaxy Note 10.1 Tablet."
How sad is that? Well, i sure can't blame you if you ignore any of my proffered advice! My bad..lol. Ok, I've come up with two things you can try.
1st download wifi analyser free from the market. The dongle has it's own wifi built in, it will show up along with all the surrounding wifi routers and the channels they use. The app will detect and suggest optimum channel settings and highlight crowded channels. If the dongles channel is crowded it would display the issues your describing. It would be best if you could moniter the connection with your tablet on a second device, but either way it might help with figuring this out.
2nd,There have been a few posts on power supply to the dongle being fickle. If you haven't already, try a different power supply, one that puts out 5 volts...it seems to have worked for a few.
3rd, substitute the suppied hdmi cable with another one known to work well.There is at least one case, displaying connection issues very similar to yours, that turned out to be caused by a bad allcast cable.
4th "I now live in Turkey and have no intentions of movıng again - beautiful country, very friendly people (now have a Turkish wife) and a nice climate. If you are a history buff Ephesus about 1.5 hours away and Troy about 5 hour drive." If any of my half baked ideas solve your problem, I fully expect you to invite me to stay with ya'll in Turkey. ..and does your wife have any sister's
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
Ok, finally my dongle started to work. How? I don't really know I changed again HDMI ports on my tv ... and it started to work like magic. So as info for all the others - just try everything you can: different hdmi ports, another hdmi cable, power source, other tv etc
Wysyłane z mojego GT-N7100 za pomocą Tapatalk 2
Related
Hi All,
I'm in the UK and have a US version P7310 wifi only (Samsung refurb bought off ebay)
Up until the ICS update 3 days ago it was in my opinion an awesome piece of kit
however, since the update, my wifi connection (or data transfer) is down at least 70% to what it was on HC 3.2
I am NOT losing the connection to the router, it is the data transfer that is down!
Many times I get the page is not available try later link might be down or if the page does load most of the data many images do not!
Repeated refreshes seem to have no affect! It was super fast before the update!
I have rebooted and still nothing, so I feel it is an issue in the tab rather than any other kit I have at the moment?
I have a wifi laptop and other android device and they perform as before on wifi so it's not the router!
I have also put the tab next to the router and it has made no difference!
I have searched the settings in the tab for anything obvious like load images or choke the bandwidth or whatever
and have turned many things on and off without success! I use the standard browser and the dolphin browser and both
act the same!
The tab has never been routed, it came with HC3.1 then I updated over the air to HC3.2 and then to ICS4.04
I know there is a folder for wifi in the settings and wondered if there was anything I could change to see if it improves anything?
Or has anyone else found their wifi is poor?
The 70% was accurate, not exaggeration, so much so that the tab is unusable for me like this!
I know it is early days for the ICS and the 8.9 world but would REALLY appreciate some advice for things to try please?
Kind regards
PS loved the noob video
Is it possible to go back to 3.2? I I restore factory settings it shall go to 3.1 and I assume 4.04? Would it go to 3.2 first?
Hmm...
Well, the support thread for the official ICS update has no mention of such issues.
Doing a factory reset will only reset the current ICS 4.0.4 to its default settings and will not revert the tablet to Honeycomb 3.1 or 3.2.
To downgrade, you should attempt through Kies, though I am not sure it offers the feature.
What I am certain of is that you can downgrade to 3.2 fairly easily by manually flashing a 3.2 firmware release.
You can download an official Honeycomb 3.2 United Kingdom release for the P7310 HERE
If you have no idea how to flash it through ODIN, please download this .zip archive that holds all the necessary tools. Then refer to THIS thread (where the archive came from) and read the short instructions on using ODIN in the How-to Section, last topic named "Using ODIN 1.85".
If you proceed to downgrade, consider to load the provided .pit file in ODIN 1.85's folder and checking "Repartition" in the program. Clicking Start with the .pit file loaded will wipe all data from your device, including everything that resides on the SD card.
After successfully downgrading to Honeycomb 3.2, you can attempt the ICS upgrade once again, but make sure to execute a factory reset from within Honeycomb's settings (or through recovery mode) on your device, before doing the update.
If the Wi-Fi issues continue within ICS, I am afraid I am short of knowledge to help track down the issue.
Good luck.
Solution?
Hi.
Maybe this will work for you: http://forum.xda-developers.com/showthread.php?t=1846766
strange
I doubt this is related to the 5ghz issue (that has different symptoms = not being able to connect).
Did you go to ICS using Odin, Kies or OTA?
Have you tried flashing the Stock ICS through Odin?
Have you tried doing a full data wipe? (reset to Stock)?
If you need to keep your app data, then save it with something like Titanium Backup (or make a Nandroid backup so you can return to current state, after experimenting)
What is your router? anything "exotic" about your WLAN settings?
fred_be9300 said:
I doubt this is related to the 5ghz issue (that has different symptoms = not being able to connect).
Click to expand...
Click to collapse
Not different symptoms. Equal symptoms. nakedninja42 was referring to the 5GHz band in his post,
[Guide] Enable Wifi 5GHz Stock ICS: I noticed that I could not connect to 5GHz after updating to stock ICS.
Click to expand...
Click to collapse
but did not say that he couldn't connect at all. And thus it makes sense to try it. Especially since Bananajet writes
that he doesn't lose connection - only speed (transfer).
Connection
Gentlemen,
thank you for your concise replies! To answer the points I think worth noting!
I downloaded OTA using the tabs own system (the 300mb file) it updated ok!
I did notice that I had to download 3 times as each previous one did fully download but didnt do anything!
On these downloads, I did not have the charger plugged in but had approximately 75+% of battery!
When I did do it the third time with charger plugged in, it updated as you would expect!
Strangely the tab has improved today and I would say 95% of clicks to a website or a refresh have performed as usual!
However (using dolphin browser) with one site open and a new tab for another, it would again not load all the images on the second page
but did NOT give me the page down link like the day before!
I would say it was a bad day for my wifi BUT the other bits of kit I use ALL performed as usual when the tab didnt
so I am still unsure of the problem? I did consider that the other bits of kit (nokia phone, Android Phone and a Laptop)
although NOT actively connecting to anything to download except being on whatsapp might be bullying the tab out
but I tried turning them off and it didnt change anything!
So I think I shall watch what happens and report back and see if anyone else mentions poor transfers?
By this I mean I REMAIN connected to the router and im NOT sure of the actual transfer rates BUT its like
the connection stops half way when the page loads (link down or photos half loaded) and no amount of refresh makes them reload
until such a time (usually 5 mins) that it does! This then does NOT start working normally (fast loading) but usually repeats itself
and doesnt load again! I do feel that any sites with mainly text and mininal graphics did load ok giving the impression
of a burst of power and then giving up hallf way if there was too much to load (my words, not one from a tech manual haha)
So just to say, the tab is working much better but not perfect! Shall report again when have more hours online!
Thank you again for your help
Kind regards
Bananajet
Update
Gentlemen (and any ladies)
after a few weeks using ICS 4 here are my findings! If anyone can help I would be very grateful as right now, the frustration doesnt compare!
I also realise my original title was slightly misleading, please note I NEVER lose connection to the router, it is the data that seems to
be choked! Almost like the tab only allows a bit through at a time and if there is a load to come through (images or streaming television), it chokes it and very little gets through? Interesting though I dont seem to have any issues wastching youtube much!
To recap, p7310 8.9 wifi version which was a refurb from the US direct from Samsung! Im in the UK! Originally came with HC3.1
I downloaded 3.2 straight away and have done nothing to this machine to alter what came out of the box!
I was very very happy with it and 3.2! Of course, as everyone else, was excited to get ICS 4.04
Downloaded ICS OTA with the update on the tab
I have noticed nothing for my type of usage much difference in ICS apart from possibly better battery but battery was ok anyway!
Back to my problem!
Web pages which contain any amount of thumbnails which might change (alter their positon on the page) when requested as a new page or refreshed very rarely load all of the images! It might load about 5-10% of them when the problem exists which is about 75% of the time! Also streaming live television is very poor to connect although when connected, it works perfectly!
On 3.2 even in my garden I could load web pages that were graphic intensive (nothing extreme, just were there might be mulitple thumbnails etc)
they would load as quick as you would want, reloads, new pages, browsing etc all worked perfectly and streaming television too!
I use the stock browser and one called dolphin
On ICS I would say about 75% of the time, any pages as mentioned above do not load all of the images, only probably about 10% of the images would load, the reast would have place marks showing where the other images should go! It would then stop! Any amount of recycle does not improve it until such time (can be a minute, can be 5 minutes)! The other 25% it works basically as it should, quite fast and normal!
One other issue is IF it is working correctly and I try and load a new tab or page in the background then the new page is highly unlikey to load correctly with any images it might want to display! Like "You cant have both mate" haha
On 3.2 any streaming video or television was perfect, fast and never failed! On ICS it has a 80% failure first time and requires usually 3-4 recyles to 'hook it'! Once it is in, it stays in and works well! If I try and change channel or view something else, it reverts to failure again!
I have changed no settings on router, changed nothing about anything! All other items in the house that might use wifi still perform as before!
The change in the quality happend immediately after ICS download.
This issue has left what was a fantastic bit of kit very frustrating to use and almost unusable!
I would really like to go back to 3.2 if I can but am unsure how easy this is although I do understand that was mentioned in an earlier post
I cannot try the 5ghz method as it is not rooted and to be honest, I am in the UK and that issue is regarding the US networks! My ccode says GB and not ALL btw.
To summarise, it seems that any new or data that requires a lot of refreshing rather than drawing from a cache doesnt want to load?
Any advice would be very helpful,
thank you all again.
Bananajet
Perhaps to do with the wifi channel used by router? Try to use channel 1 (or 6 or 11, avoid higher)
Try an app that gives WiFi diagnostics, like WiFi Analyzer.
Alternatively, reflash any other stock HC or ICS Rom through Odin... You might lose data (downloaded apps, settings, ...) along the way though (not sure, depends on exact approach, etc)
Have you try to test the speed connection wit your tab? I try whit speedtest.net in that site you can find the version for mobile, download it and try, just to see if it is a problem related whit your browser or with you wifi drivers
hope it could help
PS. you can find the app in play store too (same name)
I have just received a chromecast in its box. How can I tell what firmware is on the device? If it is still original firmware I'd like to root it. I didn't see this question posted elsewhere.
You must not allow the chromecast to connect to a wifi ssid / network which has Internet.
In my case, I had an old asus (dd-wrt) router laying around. I powered it up with nothing plugged into it. No rj45 cat 5/6 cables connected. Switched my phone wifi to this wireless ssid network. Ran the chromecast app, it found the chromecast, set up the chromecast to use this no Internet network by selecting it & typing in the router's password. After setting up the chromecast, the app shows the firmware version as being 12072.
If you allow the chromecast to connect to a wifi network which has Internet, then it will quickly auto update to a firmware version which can not currently be rooted
View attachment 2246393
It's tucked away a little in the chromecast app, but this should help some.
Arrow points to the firmware version location
Medicstud007 said:
I have just received a chromecast in its box. How can I tell what firmware is on the device? If it is still original firmware I'd like to root it. I didn't see this question posted elsewhere.
Click to expand...
Click to collapse
Just get the chromcast app and select the chromecast u are using. Then look at pic below should be there.
Sent from the TermiNOTEr 2!
Thank you all my build is 12072 which means I can root it. I believe I saw a thread on here somewhere which gave more detailed instructions on how to root the device. Where is the correct file to flash to root the device without having to worry about pesky updates?
Medicstud007 said:
Thank you all my build is 12072 which means I can root it. I believe I saw a thread on here somewhere which gave more detailed instructions on how to root the device. Where is the correct file to flash to root the device without having to worry about pesky updates?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45176635&postcount=133
I suggest you read the beginning few pages of the thread before flashing though.
Dying to know my fw version
Hello,
I've thoroughly read the instructions on how to root my Chromecast. Right after buying it, I set it up and I'm pretty much sure it got the official updates... so I ran to Best Buy to exchange it for a new one.
From thread comments, I know I have a shot at it having a vulnerable bootloader, now my problem is that OTG cables don't seem to exist where I live and I might have to go to Best Buy again to get one (long trip for a cable). Before I do that, I want to be certain that it'll work, but I cannot find where to see the build number. I somehow cannot get to the screen from the pictures.
I'm trying to set it up with a router that has no internet. Since this was a recommended method to check the build number, I thought it was possible, but so far I'm stuck with a message saying that ChromecastXXX connected to yournetwork, but cant access the internet..
At first I thought they had removed that from the Chromecast app, but I have installed the two older apks with the same results.
Could anyone tell me which step I'm missing?
I thought maybe I had this issue, but it's old and I was able to set up the previous Chromecast flawlessly.
keep on trying to make it connect even though there is no internet eventually it will give up and give you the number, thats who i got mine, it will say Chromecast XXX connected to network but cant access internet, and fail but then if you keep going it will eventually show you the build number.
BurnOmatic said:
keep on trying to make it connect even though there is no internet eventually it will give up and give you the number, thats who i got mine, it will say Chromecast XXX connected to network but cant access internet, and fail but then if you keep going it will eventually show you the build number.
Click to expand...
Click to collapse
ugh I did but it just times out and comes back to the same message. Perhaps it is a sign of a new firmware.
it will work dude eventually it will say that it went through even though clearly you havent got internet, and it will show the version number on the app , i did it through my pc not through the phone.
BurnOmatic said:
it will work dude eventually it will say that it went through even though clearly you havent got internet, and it will show the version number on the app , i did it through my pc not through the phone.
Click to expand...
Click to collapse
Thanks!. Got it working now. Somehow it never worked at home but I tried it at work where internet is filtered through mac addresses and that did the trick. Unfortunately it has an updated bootloader.
Not sure how much this will help, but I just went to Best Buy to return the 2nd Chromecast I had bought, since it came with a firmware newer than 12072. When I had purchased my first one, I hadn't done any research on rooting a Chromecast yet, and unfortunately allowed it to receive Google's OTA update. Before returning it, I took a picture of the serial number, pictured below. Tonight I decided to just get a refund at first, but then decided to take one third and final stab at getting one with a vulnerable bootloader. Thankfully, I kept the picture of the first one's serial number, and used it to compare against all of the Chromecasts that Best Buy had in stock. I only found one that began with "390...", since my originally purchased one began with "3901...". I live about an hour away from the closest Best Buy, so I decided to ask someone in Geek Squad if I could test it out to make sure it had the old firmware on it. He checked with someone else and was given the go ahead. We didn't plug it into the HDMI port, but he allowed me to plug it in to the USB port on a TV. Using the powered OTG micro USB cable I got in the mail today and a FlashCast drive I had created, I held the Chromecast button down and plugged the micro USB cable into the Chromecast. I waited to see if it the red light would go away after about 9 seconds, and VOILA, it did. I'll soon officially test it out on my TV so that I can see if the FlashCast logo comes up on the screen, and I will report back.
EDIT: Sorry for the delay in reporting back. Looks like the 3rd time was a charm, and the Chromecast I purchased last finally worked. So it looks like it's safe to at least assume that Chromecasts with serial numbers that begin with at least "390", with a range between "3901..." and "3907..." may have vulnerable bootloaders. Not to say this is the end all be all if figuring this out, but the guesswork might be if some use for now, until all the old stock gets sold completely.
Sent from my HTC One using Tapatalk
Damn. I bought my chrome cast the other day and allowed it to update without knowing any of these forums existed
sent from a LG-MS870 using Katana v3 ROM by GT
I picked up 2 chromecast's over the weekend from Best Buy (Mall of America). The first one had a 3Axxxxxxxx SN and was at 12940. The second one was a 39xxxxxx and was at 12072.
Versions with 12072 are still out there. Look for CC's with SN starting with 39 or 37.
guy4jesuschrist said:
Not sure how much this will help, but I just went to Best Buy to return the 2nd Chromecast I had bought, since it came with a firmware newer than 12072. When I had purchased my first one, I hadn't done any research on rooting a Chromecast yet, and unfortunately allowed it to receive Google's OTA update. Before returning it, I took a picture of the serial number, pictured below. Tonight I decided to just get a refund at first, but then decided to take one third and final stab at getting one with a vulnerable bootloader. Thankfully, I kept the picture of the first one's serial number, and used it to compare against all of the Chromecasts that Best Buy had in stock. I only found one that began with "390...", since my originally purchased one began with "3901...". I live about an hour away from the closest Best Buy, so I decided to ask someone in Geek Squad if I could test it out to make sure it had the old firmware on it. He checked with someone else and was given the go ahead. We didn't plug it into the HDMI port, but he allowed me to plug it in to the USB port on a TV. Using the powered OTG micro USB cable I got in the mail today and a FlashCast drive I had created, I held the Chromecast button down and plugged the micro USB cable into the Chromecast. I waited to see if it the red light would go away after about 9 seconds, and VOILA, it did. I'll soon officially test it out on my TV so that I can see if the FlashCast logo comes up on the screen, and I will report back.
Click to expand...
Click to collapse
Sorry for the delay in reporting back. Looks like the 3rd time was a charm, and the Chromecast I purchased last finally worked. So it looks like it's safe to at least assume that Chromecasts with serial numbers that begin with at least "390", with a range between "3901..." and "3907..." may have vulnerable bootloaders. Not to say this is the end all be all if figuring this out, but the guesswork might be if some use for now, until all the old stock gets sold completely.
Sent from my HTC One using Tapatalk
I can verify that 3904 "should" have the original firmware. Spent an hour looking for one, and another 45 minutes making sure that the Wifi, and my phone had no internet connection to them, and then trying to get it to connect fully, so I could see the firmware version. As soon as I switched from using the Chromecast app on my OG RAZR, to using it on my Nexus 7(2), it connected right away .It was the only one they had in the Best Buy near me, that was even close as far as serial numbers go. Time to get my brick..uhh. I mean, unlock on
I can verify that 3As all have newer firmware, thus can't be rooted. I tried two from my local Best Buy
Greetings:
I'm trying to connect without updating since I just got my CC but to no avail since yesterday!!
I'm doing the "no internet router" option but don't even see the "home screen" when I connect
the CC to my TV set!! All I see is few colored "dots"!!
Am I doing something wrong? or do I have a faulty CC?
Any input is much appreciated.
P.S= My phone is a Nexus 4
My CC's SN starts with 3805xxxxxxxxxxx
samteeee said:
Greetings:
I'm trying to connect without updating since I just got my CC but to no avail since yesterday!!
I'm doing the "no internet router" option but don't even see the "home screen" when I connect
the CC to my TV set!! All I see is few colored "dots"!!
Am I doing something wrong? or do I have a faulty CC?
Any input is much appreciated.
P.S= My phone is a Nexus 4
My CC's SN starts with 3805xxxxxxxxxxx
Click to expand...
Click to collapse
Little dots means you are in recovery mode.
Trying installing FlashCast and Custom ROM.
If you know the version is OK before you even connect it to a router and set it up you can setup the root!
mastermind278 said:
Little dots means you are in recovery mode.
Trying installing FlashCast and Custom ROM.
If you know the version is OK before you even connect it to a router and set it up you can setup the root!
Click to expand...
Click to collapse
I certainly didn't do anything to be on "Recovery" partition"!!
I'm not sure what my build/firmware is but I guess I can always
just try to go for "root" and see if it'll happen, right? I mean there
is no harm in that!! I'll get my OTG by Monday so I can try it.
My Chromecast just updated to build 16041. Anyone know what's new?
Looks like some people started getting this build a few days ago, but nobody has noticed anything significant: http://www.reddit.com/r/Chromecast/comments/1zswmd/chromecast_updated_to_build_16041/
No idea.
Here's a link for a Google forum beginning on March 4th where they're asking questions at the end as if new problems deserve entry level debugging questions. (What router do you have?)
https://productforums.google.com/forum/m/#!topic/chromecast/xXyNrzm-e8g/discussion
A posts saying a change log would be linked when available - but nothing there.
They used to put it here - http://googlechromereleases.blogspot.com/2013/12/chromecast-update.html
Then somewhere else for 15250, I can't search from the XDA app.
I got it tonight. Had to force quit Netflix at first, then had no problems after that.
No idea if anything else is working or broken for me yet.
Lots of complaints out there though.
EarlyMon said:
No idea.
Here's a link for a Google forum beginning on March 4th where they're asking questions at the end as if new problems deserve entry level debugging questions. (What router do you have?)
https://productforums.google.com/forum/m/#!topic/chromecast/xXyNrzm-e8g/discussion
A posts saying a change log would be linked when available - but nothing there.
They used to put it here - http://googlechromereleases.blogspot.com/2013/12/chromecast-update.html
Then somewhere else for 15250, I can't search from the XDA app.
I got it tonight. Had to force quit Netflix at first, then had no problems after that.
No idea if anything else is working or broken for me yet.
Lots of complaints out there though.
Click to expand...
Click to collapse
I think that with the release of GoogleCast Beta, which coincided with the 150XX Update that perhaps Google is in play mode with the device and OS and don't want to admit they may have screwed a few pooches!
I have seen the Googlecast crash behavior both with the Beta and Original and the Beta would not even work with Plexweb so I Uninstalled it.
I canceled Netflix so I can't test if that is truly broken.
I gave the new build a quick test with Netflix and Plex. Everything seems fine, no crashes.
I sometimes get the Chromecast failing to connect to Netflix successfully the first time it tries, but it always works the 2nd time, so I haven't bothered worrying about it.
DJames1 said:
I gave the new build a quick test with Netflix and Plex. Everything seems fine, no crashes.
I sometimes get the Chromecast failing to connect to Netflix successfully the first time it tries, but it always works the 2nd time, so I haven't bothered worrying about it.
Click to expand...
Click to collapse
I also expect to see things break for the first few days while an update rolls out.
Everything is so damn interconnected between multiple parties such as Google making a change, The App dev (Netflix, Plex Etc) having to support the changes to work with the new update and finally the user updating the apps to get the changes made.
It's like a really bad Square Dance! LOL
Asphyx said:
I think that with the release of GoogleCast Beta, which coincided with the 150XX Update that perhaps Google is in play mode with the device and OS and don't want to admit they may have screwed a few pooches!
Click to expand...
Click to collapse
Yep.
14651 really broke it for me and hosed Netflix and YouTube. And I told them so in a bug report - everything working until that update with no app changes and after app changes.
Two weeks after 15250 came out, that fixed my personal issues with both apps, without me updating either app, Google emailed me to tell me that my defect report was being rejected because clearly, I had a Netflix issue and ought to take it up with them.
The beginning of my defect report said: "Do not look at this as a Netflix issue, it's happening with YouTube too and just started with 14651."
I still love my Chromecast, I still think it's great and I still think Google is pretty Mickey Mouse when it comes to being forthcoming and working with people.
EarlyMon said:
I still love my Chromecast, I still think it's great and I still think Google is pretty Mickey Mouse when it comes to being forthcoming and working with people.
Click to expand...
Click to collapse
The fact they are averaging an update every week or two just underscores the fact they keep messing with the works and when you fix what isn't broke you tend to break it.
The Windows Chromecast app does not load for me anymore after this update. In the task manager I can see it open then it shuts right down.
After this update my chromecast doesnt boot Only Google Logo then black screen on my TV Samsung... Thx Google...
I tried to disconnect USB and plug in it to POWER adapter - it doesnt help me, then I tried to hard reset from physical button on Chromecast - it doestnt helps to me too! Any ideas? After HR chromecast now displays on my TV like "Player". Chromecast app cant connect to Chromecast...
Skazki said:
After this update my chromecast doesnt boot Only Google Logo then black screen on my TV Samsung... Thx Google...
I tried to disconnect USB and plug in it to POWER adapter - it doesnt help me, then I tried to hard reset from physical button on Chromecast - it doestnt helps to me too! Any ideas? After HR chromecast now displays on my TV like "Player". Chromecast app cant connect to Chromecast...
Click to expand...
Click to collapse
Sounds like maybe you had it plugged into USB power and it may have lost power during the update process?
Did it boot successfully to the wallpaper after it applied the update?
bhiga said:
Sounds like maybe you had it plugged into USB power and it may have lost power during the update process?
Did it boot successfully to the wallpaper after it applied the update?
Click to expand...
Click to collapse
I fixed it! Now it works. I connected AC POWER and wait around 2-3 minutes. Now it works!
Skazki said:
I fixed it! Now it works. I connected AC POWER and wait around 2-3 minutes. Now it works!
Click to expand...
Click to collapse
Great! This, along with the ability to turn on the TV, is why I highly recommend using wall/utility power rather than a TV USB port which often loses power when the TV is turned off.
Even mine got updated to this version. I feel this update is crappy, getting disconnected even for YouTube casting every 5 mins.. It used to work flawless until now. But then ... Waiting patiently for a fix
Sent from my Nexus 4 using xda app-developers app
bhiga said:
Great! This, along with the ability to turn on the TV, is why I highly recommend using wall/utility power rather than a TV USB port which often loses power when the TV is turned off.
Click to expand...
Click to collapse
Or for those with a home theater, you can connect the CC directly to you AVR.
Sent from my Nexus 5
Guess this answers our questions @Asphyx
Sent from my DROID RAZR HD using Tapatalk
sting098 said:
Even mine got updated to this version. I feel this update is crappy, getting disconnected even for YouTube casting every 5 mins.. It used to work flawless until now. But then ... Waiting patiently for a fix
Click to expand...
Click to collapse
I feel ya. My YouTube and Netflix are working fine. If it's not broken for everyone, no telling how long before they take it seriously.
This update sucks!
SENT FROM MY SM-N900T/NEXUS 5 USING TAPATALK
EarlyMon said:
I feel ya. My YouTube and Netflix are working fine. If it's not broken for everyone, no telling how long before they take it seriously.
Click to expand...
Click to collapse
It may actually be something which is Lot Number (Device Version) specific.
It seems to be affecting a lot of folks so I expect it will be handled in the next release provided they can even figure out what is causing it by the time that release is available.
How many of you are rooted and did the update with flashcast and a USB cable?
Sent from my DROID RAZR HD using Tapatalk
I'm stock.
http://liliputing.com/2014/07/google-brings-chromecast-screen-mirroring-android.html
I would love to be able to wirelessly mirror my Rooted but locked Moto X on 4.4.3 to the chromecast. It seems like it's working on devices about as fast as the moto x so I would imagine they just have it disabled for devices not officially supported. Would there be a way through Xposed or some other method to enable this feature? THANKS!
Is it possible it's in the 4.4.4. Code?
Spacemonkie4207 said:
Is it possible it's in the 4.4.4. Code?
Click to expand...
Click to collapse
I think it's supposed to already work with devices that are still on 4.4.2. It seems more to do with the new version of the chromecast app itself (version 1.7). I just don't know how to trick it into thinking the moto x is a supported device. Maybe just a build prop tweak would be enough?
atomb said:
I think it's supposed to already work with devices that are still on 4.4.2. It seems more to do with the new version of the chromecast app itself (version 1.7). I just don't know how to trick it into thinking the moto x is a supported device. Maybe just a build prop tweak would be enough?
Click to expand...
Click to collapse
I'm sure they will add support. Probably just started on Devices that are in high demand.
atomb said:
http://liliputing.com/2014/07/google-brings-chromecast-screen-mirroring-android.html
I would love to be able to wirelessly mirror my Rooted but locked Moto X on 4.4.3 to the chromecast. It seems like it's working on devices about as fast as the moto x so I would imagine they just have it disabled for devices not officially supported. Would there be a way through Xposed or some other method to enable this feature? THANKS!
Click to expand...
Click to collapse
Guys, see here: http://forum.xda-developers.com/moto-x/general/chromecast-mirroring-moto-x-t2810937
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Enviado desde mi XT1053 mediante Tapatalk
As this topic is on Screen Mirroring, can anyone successfully connect a rooted X to a smart TV? I have been trying to connect it with my W6 series Bravia for past half an hour and could not be able to. It just says connecting but never connects! I am not talking about the Chromecast feature here, but the built in Miracast of X which can be found under Display.
S4 had the same problem when I rooted it, wouldn't connect, but with stock kernel S4 did connect fine. Anyone?
devilsdouble said:
As this topic is on Screen Mirroring, can anyone successfully connect a rooted X to a smart TV? I have been trying to connect it with my W6 series Bravia for past half an hour and could not be able to. It just says connecting but never connects! I am not talking about the Chromecast feature here, but the built in Miracast of X which can be found under Display.
S4 had the same problem when I rooted it, wouldn't connect, but with stock kernel S4 did connect fine. Anyone?
Click to expand...
Click to collapse
My rooted X works perfectly with my Netgear Push2TV (this is branded to use "WiDi", which according to wikipedia is 100% compatible with "Miracast"). It comes in very handy for presentations.
I always have multiple people asking me "How did you do that with your phone?!?!" after the presentations
samwathegreat said:
My rooted X works perfectly with my Netgear Push2TV (this is branded to use "WiDi", which according to wikipedia is 100% compatible with "Miracast"). It comes in very handy for presentations.
I always have multiple people asking me "How did you do that with your phone?!?!" after the presentations
Click to expand...
Click to collapse
Great. My router is Netgear too! So why isn't it working with mine? Do you have Xposed installed? Also what kernel do you use?
I guess I have made Screen Mirroring my enemy in past life.
devilsdouble said:
Great. My router is Netgear too! So why isn't it working with mine? Do you have Xposed installed? Also what kernel do you use?
I guess I have made Screen Mirroring my enemy in past life.
Click to expand...
Click to collapse
My router is not netgear...I don't have a smart TV, so I'm using a "Netgear Push2TV" device which just plugs into the HDMI port of any TV and is made specifically for WiDi / Miracast (you can google it if interested - it's actually been out for several years now).
Yes, I'm using Xposed. I'm rooted with several root apps, but using the Stock ROM / kernel.
When I first connect my phone to the "Push2TV", the Push2TV displays a 4 (or 6?) digit code on the screen and asks me to enter it on my device. The phone pops up a number pad and I enter the code. A few seconds later, screen mirroring is ON.
I also want to add that though I've seen some reports of the "Chromecast" method resulting in choppy video and/or no sound, the built-in mirroring has worked flawlessly for me. Sometimes I use the "Xfinity TV-Go" app to stream television episodes to the TV. You can't tell that it's not being played directly from the TV. Picture and sound have both been excellent.
samwathegreat said:
My router is not netgear...I don't have a smart TV, so I'm using a "Netgear Push2TV" device which just plugs into the HDMI port of any TV and is made specifically for WiDi / Miracast (you can google it if interested - it's actually been out for several years now).
Yes, I'm using Xposed. I'm rooted with several root apps, but using the Stock ROM / kernel.
When I first connect my phone to the "Push2TV", the Push2TV displays a 4 (or 6?) digit code on the screen and asks me to enter it on my device. The phone pops up a number pad and I enter the code. A few seconds later, screen mirroring is ON.
I also want to add that though I've seen some reports of the "Chromecast" method resulting in choppy video and/or no sound, the built-in mirroring has worked flawlessly for me. Sometimes I use the "Xfinity TV-Go" app to stream television episodes to the TV. You can't tell that it's not being played directly from the TV. Picture and sound have both been excellent.
Click to expand...
Click to collapse
Oh I get it, it's a device like Chromecast or sort. I guess it's the kernel, I am on Faux's. Let me see if it works with stock kernel. Do you happen to have a zip of stock kernel?
I get that four digit code thingy, I did that when I had the S4 and it used to connect successfully.
See also...
See also:
http://forum.xda-developers.com/moto-x/development/cast-moto-x-screen-to-chromecast-t2812322
devilsdouble said:
Oh I get it, it's a device like Chromecast or sort. I guess it's the kernel, I am on Faux's. Let me see if it works with stock kernel. Do you happen to have a zip of stock kernel?
I get that four digit code thingy, I did that when I had the S4 and it used to connect successfully.
Click to expand...
Click to collapse
Hmm, I've never used a custom Kernel, but boot.img contains the Kernel. I bet that is your issue. You should be able to download the SBF for your carrier, extract "Boot.img", and fastboot flash it.
I suggest making a backup first, just in case something goes awry.
Let us know if that does the trick.
samwathegreat said:
Hmm, I've never used a custom Kernel, but boot.img contains the Kernel. I bet that is your issue. You should be able to download the SBF for your carrier, extract "Boot.img", and fastboot flash it.
I suggest making a backup first, just in case something goes awry.
Let us know if that does the trick.
Click to expand...
Click to collapse
Lol, thanks mate. I did extract the boot.img some days back from the ROM and I flashed it via Fastboot, everything went fine and I even got the stock kernel back, but WiFi would not turn on, and without WiFi I can't do this test. I guess something is missing from the boot.img file, something else needs to be flashed as well, just don't know what.
I am giving up. I will format the phone when 4.4.4 will be released and that time I will check if Screen Mirroring works or not, it should, just for the peace of mind, then I will have to flash custom kernel and then it will stop working again.
I've got a Verizon DE, 4.4.2 rooted, running Faux 007m. I can use wireless display (screen mirroring) through my Netgear PTV2000 or my miracast enabled Samsung TV without issue.
Sent from my XT1060 using XDA Free mobile app
Has anyone been able to screen mirror to their SmartTV / Bluray using their Note 4. I have been trying to mirror to my Sony device yet all I get is an error message that the connection failed. Screen mirroring works perfectly with my Galaxy S4. I was hoping to continue mirroring directly without having to buy a Chromecast or Roku. I contacted Samsung support and as always they were worthless. Thanks in advance.
I mirror without issues to my Samsung Tv. Are you rooted or any mods installed?
Sent from my SM-N910T using XDA Free mobile app
flipq88 said:
I mirror without issues to my Samsung Tv. Are you rooted or any mods installed?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
The Galaxy Note 4 is not rooted and running stock ROM. The Galaxy S4 is rooted. Both are running 4.4.4.
I mirror all the time to my Smart TV no issues
I don't have any issues. Maybe try Odin th ed stock firmware. Worth a shot.
If your connected to WiFi network try disconnecting from it. Also make sure you forget the network settings as well. Do not want to reconnect to WiFi while attempting to screen mirror. See if screen mirroring works that way?
I had an issue before on my mirracast device before on an older firmware. Where it had connection issues when I was connected to a WiFi network.
I connect my note 4 to my samsung tv pretty easily, but they are both samsung so that might make a difference. However when I connect my phone to my WD live box, I fequently get the same thing you do. If I reset the box I can get it to work for awhile but then the errors cone back. It seems like it should work easily. I'm still working out the bugs but will report back if I fix it. For future reference, if you root your note, it seems that the stock kerenel is best for mirroring. Custom kernels may need some items added to the build. Prop to get it to work properly.
Edit: you motivated to find a solution! For my device, and I havent tested yet, but a suggestion was made that both devices be on wifi. My WD is hard wired. Is your sony? That could make a difference.
Thanks for the suggestions but so far nothing works. The Note 4 attempts to connect but always fails. It's surprising how easily the S4 connects yet the Note 4 can't. I wonder what Samsung did in the newer version that would cause the error.