Database Develop

Allshare Cast dongle connection problems

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

[Q] How can I tell what firmware my chromecast has?

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.

[Q] VZW Moto X as Hotspot

So I am strongly considering the Moto X not that Verizon has Moto Maker and the 32GB verizon. The one thing I love on my current phone running CM10.2 is the ability to tether my laptop to it for internet access without getting charged extra by verizon while I travel. Usually in a monthly billing cycle when traveling with work I'll consume about 20GBs of data. Can I do this with the Moto X without getting charged tether fees? Do I need to root it to do this?
FYI: I'm i'm on an unlimited plan

If you root with RockMyMoto, yes..
For using Wifi Tether for Root app, see -> http://forum.xda-developers.com/showthread.php?t=2449534 You MUST use the specific version now linked in the first post, or it wont work.... In other words, do NOT get the version from the Play store. (I'm using this way with my Rooted X, also unlimited plan)
To use the built in tethering app see -> http://forum.xda-developers.com/showthread.php?t=2443562 (I haven't tried it, but there are many reports in that thread of it working).
If you don't want to root, then you could try Foxfi. Not sure if it works, I've never used it.

I have always used THIS, on multiple phones. I'm on the 3.3 beta 2 and it works fine. Go into settings, and make sure the device profile is Generic ICS/JB (wlan0), and check the WiFi driver reload, MSS clamping, and Routing fix options.

gokart2 said:
I have always used THIS, on multiple phones. I'm on the 3.3 beta 2 and it works fine. Go into settings, and make sure the device profile is Generic ICS/JB (wlan0), and check the WiFi driver reload, MSS clamping, and Routing fix options.
Click to expand...
Click to collapse
For some reason I couldn't get that version to work on my Verizon X. While the PC and tablet saw the X, it saw it as WLAN0, and never properly connected to the phone.
The thread I linked to has a patched version that works properly for me, including seeing the "hot spot" as the SSID I set on the phone, and letting the PC and tablet connect to the phone and get to the internet.

The x is awesome for one. All u gotta do is root and follow the thread to use built In tethering appreciate. Works great. Or better yet flash Nitro's eclipse ROM. Its all done and its a great rom
Sent from my XT1060 using xda app-developers app

KidJoe said:
For some reason I couldn't get that version to work on my Verizon X. While the PC and tablet saw the X, it saw it as WLAN0, and never properly connected to the phone.
The thread I linked to has a patched version that works properly for me, including seeing the "hot spot" as the SSID I set on the phone, and letting the PC and tablet connect to the phone and get to the internet.
Click to expand...
Click to collapse
I did notice the wlan0 where on the other device I had u could change it or use the ssid, but my tab and others will connect? The initial connection always funks up, usually just have to cycle WiFi from the device and cycle tether too. U try reboot, fix perms, and cache/dalvik wipes? Haven't tried modifying that system apk, heard about some issues and this never gives much, if any.

gokart2 said:
I did notice the wlan0 where on the other device I had u could change it or use the ssid, but my tab and others will connect? The initial connection always funks up, usually just have to cycle WiFi from the device and cycle tether too. U try reboot, fix perms, and cache/dalvik wipes? Haven't tried modifying that system apk, heard about some issues and this never gives much, if any.
Click to expand...
Click to collapse
I tried everything. Yes.
I liked the way wifi tether worked on my past phones. Using the patched copy found in this thread -> http://forum.xda-developers.com/showthread.php?t=2449534 , which is also needed for the GNex w/4.2, works just like it did on my Bionic, Thunderbolt, and other past phones. No issues. After initial config and allowing SU, just launch the app, tap to start tethering, go to my PC, Tablets, etc.. and connect and go.
The APK is originally from https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c109 however, I just noticed lower down in that discussion a patch was added to the experimental 3.4 ( https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c197 ) so I might try that.
I don't feel the need to mess with those system files to use the phone's built in tethering app. I don't have to. I only offered that because some were using it since Wifi Tether for Root wasn't working.

KidJoe said:
I tried everything. Yes.
I liked the way wifi tether worked on my past phones. Using the patched copy found in this thread -> http://forum.xda-developers.com/showthread.php?t=2449534 , which is also needed for the GNex w/4.2, works just like it did on my Bionic, Thunderbolt, and other past phones. No issues. After initial config and allowing SU, just launch the app, tap to start tethering, go to my PC, Tablets, etc.. and connect and go.
The APK is originally from https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c109 however, I just noticed lower down in that discussion a patch was added to the experimental 3.4 ( https://code.google.com/p/android-wifi-tether/issues/detail?id=1661#c197 ) so I might try that.
I don't feel the need to mess with those system files to use the phone's built in tethering app. I don't have to. I only offered that because some were using it since Wifi Tether for Root wasn't working.
Click to expand...
Click to collapse
editig one cell in the system settings to get the built-in hotspot app to work is hardly messing with the system files. i've done this on my last three phones and they've all worked flawlessly. plus the built-in app has decent security features.

640k said:
editig one cell in the system settings to get the built-in hotspot app to work is hardly messing with the system files. i've done this on my last three phones and they've all worked flawlessly. plus the built-in app has decent security features.
Click to expand...
Click to collapse
I know you read the one thread I posted a link to as you asked about doing the SQL edit, and posted a screen shot from your D4.. Its OP talks about replacing a bunch of APK files which are system files...
In Post #24 of that thread, thepolishguy the SQL tweak doesn't work.
... hence my saying I didn't want to mess with a bunch of system files.
Not to mention, side loading an APK and using it is easier. It might not be "cleaner" or seem as "integrated" but it works.

Awesome thanks everyone. I defintely plan on rooting my phone and installed xposed.

[Q] Screen Mirroring

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.

Re-enabling Tethering & Portable Hotspot option somehow on Stock or CM12.1/Nexus rom

Re-enabling Tethering & Portable Hotspot option somehow on Stock or CM12.1/Nexus rom
Is this possible ? The third party stuff is absolutely horrible and doesn't work.
Seems they turned this flag off this from tablets with Lollipop and M while its still works for phones (if the networks allow or rooted).

Xplic1T said:
Is this possible ? The third party stuff is absolutely horrible and doesn't work.
Seems they turned this flag off this from tablets with Lollipop and M while its still works for phones (if the networks allow or rooted).
Click to expand...
Click to collapse
How are you getting the internet to be shared via hotspot/tether onto the tablet if not via the WiFi?

Xplic1T said:
Is this possible ? The third party stuff is absolutely horrible and doesn't work.
Seems they turned this flag off this from tablets with Lollipop and M while its still works for phones (if the networks allow or rooted).
Click to expand...
Click to collapse
Please explain what you are trying to accomplish so others are better able to assist. Are you trying to turn your device into an AP to serve out local content? What is the purpose of the tether and would it be used in conjunction with WiFi? While I don't have a solution in mind understanding what you are trying to do may surface some remedies. If the capability has been disabled in Android 5/6 as you claim then the only workaround will likely come via Xposed.

Davey126 said:
Please explain what you are trying to accomplish so others are better able to assist. Are you trying to turn your device into an AP to serve out local content? What is the purpose of the tether and would it be used in conjunction with WiFi? While I don't have a solution in mind understanding what you are trying to do may surface some remedies. If the capability has been disabled in Android 5/6 as you claim then the only workaround will likely come via Xposed.
Click to expand...
Click to collapse
Hi Davey, yes I'm trying to serve local content through a 3rd party app called KWS server. In order to do this on my other tablets, I need to enable a hotspot so that others can connect to it. This feature is invaluable to me as I make presentations that I host from an inconspicuous tablet. Google must of nixed it off the official dev path.
I've installed the XPOSED framework on the Nexus rom and they only had one plugin (X Tether I believe the name) and it didn't work.
All the 3rd party apps out there that say they do this absolutely suck.
Maybe there's some generic unofficial CM10 (Kitkat) rom out there I can try ?

Xplic1T said:
Hi Davey, yes I'm trying to serve local content through a 3rd party app called KWS server. In order to do this on my other tablets, I need to enable a hotspot so that others can connect to it. This feature is invaluable to me as I make presentations that I host from an inconspicuous tablet. Google must of nixed it off the official dev path.
I've installed the XPOSED framework on the Nexus rom and they only had one plugin (X Tether I believe the name) and it didn't work.
All the 3rd party apps out there that say they do this absolutely suck.
Maybe there's some generic unofficial CM10 (Kitkat) rom out there I can try ?
Click to expand...
Click to collapse
Yep - looks like it's a goner in Android 5.1+ in the absence of a mobile radio. Tried to force it but was only successful in disabling WiFi reception and amplifying a distant hotspot that I never connect to (standard WiFi weirdness in the presence of multiple radios). No sign of a functioning AP. The code is likely there but disabled when a mobile radio is not found. Possible it could be enabled via a build.prop tweak. Spent some time searching but didn't find any promising hits. Guessing it's not a high demand item that warrants a lot of attention.
Options (don't shoot the messenger):
- keep searching for a Lollipop solution ... good luck
- snag a cheap KitKat tablet that still supports single radio tethering. Many to choose from including rootable 3rd gen HDXs which have much better specs than 2015 Fire; supports Nexus and CM ROMs. I confirmed the portable hotspot function does work on HDX Nexus. A 2013 Nexus 7 is another fine choice.
- grab an older phone with decent memory specs (eg: Moto X or mini) that will support tethering regardless if running KitKat or Lollipop. You don't need to put it on a mobile plan; just use it as a stand-alone device/server.

Davey126 said:
Yep - looks like it's a goner in Android 5.1+ in the absence of a mobile radio. Tried to force it but was only successful in disabling WiFi reception and amplifying a distant hotspot that I never connect to (standard WiFi weirdness in the presence of multiple radios). No sign of a functioning AP. The code is likely there but disabled when a mobile radio is not found. Possible it could be enabled via a build.prop tweak. Spent some time searching but didn't find any promising hits. Guessing it's not a high demand item that warrants a lot of attention.
Options (don't shoot the messenger):
- keep searching for a Lollipop solution ... good luck
- snag a cheap KitKat tablet that still supports single radio tethering. Many to choose from including rootable 3rd gen HDXs which have much better specs than 2015 Fire; supports Nexus and CM ROMs. I confirmed the portable hotspot function does work on HDX Nexus. A 2013 Nexus 7 is another fine choice.
- grab an older phone with decent memory specs (eg: Moto X or mini) that will support tethering regardless if running KitKat or Lollipop. You don't need to put it on a mobile plan; just use it as a stand-alone device/server.
Click to expand...
Click to collapse
Thanks, yeah I figured that would be the case... It's a pretty big feature for them to just take off like that without input from people.
Whats weird is that none of the 3rd party ones work at all ... even FoxFi.