Nexus 5 + Miracasting / Screencasting - Nexus S Q&A, Help & Troubleshooting

Hi everyone,
I'm trying to play with them miracasting dongles for a project I'm working on.
Just got myself a dongle from ebay, seems to work (producing video). However, upon attaching with Screen Cast (under display options) it works for 10-12 seconds and automatically disconnects without reconnecting.
Happened the same with a different Nexus 5 and a Nexus 7.
All devices were rooted, all have stock on them (4.4.2).
I've read somewhere that this issue might happen as part of a DRM mechanism (at Samsung Galaxy devices). When the Flash Counter is bigger than 0' the exact same smypthom happens.
Although I'm stocked, I did flash my phones (had to, they came with 4.4 and I wanted 4.4.2). CWM etc.
Anyone seen this issue? overcame it? couldn't find a lot of details about this in Nexus devices ..

Related

Slight WLAN issues (control channel13 not found)

Hey guys!
I just bought my Nexus 5 and had slight trouble.
It turns out that the Nexus 5 doesn't recognise channel 13 (and 12 apparently) while all my other devices (including my Galaxy nexus) do.
It works well on any other channels though.
Just wanted to let you know!

wireless display (miracast)

am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
I went from a Galaxy nexus to an N5 and a lot of stuff broke. My voice dialer for one and wifi is wonky for another. Wireless charging heats up the battery so much I've quit using it.
I really like the g2 and thought about returning the N5 and getting one. Only problem is that when the G2 gets kitkat all of the problems I'm having may very well come back. I hope that isn't the case with Miracast as well although LG will probably do better testing.
Good luck with Miracast. Sorry I don't have a way to test it for you.
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
I tried it on my friend's LG TV and my own Samsung and neither would get very far - hope it's a simple software bug
What TV you guys using for miracast... My LG TV says wireless display but nothing about miracast
Sent from my Nexus 5 using Tapatalk
Miracast wireless Display
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
prrred said:
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
Click to expand...
Click to collapse
so the n4 and n7 on 4.3 work okay but your n5 on 4.4 doesn't?
if so it makes me feel a little better than it's just a software issue that (hopefully) is cleared up soon in an update
Maybe. Both the N5 and 4.4 are different from n4 and 4.3. could be a HW issue. Likely a SW problem.
peter
prrred said:
Same issue no connection. N4&N7 A 4.3 work just fine using an adaptor on sony TV
Click to expand...
Click to collapse
I think there's a little confusion here - I understood this to mean:
You have the same problem with wireless connectivity - this is the same as I have noticed that with my N5 and my friends N4, neither of us could connect
With a cable the N4 and N7 work ok - I would expect this to be the case anyway, although I can't test my N5 with a cable as I don't have the USB to HDMI adapter (only one for my old GNex which was MHL which isn't compatible).
i feel like it's less of a hardware issue since miracast worked fine on my g2 and my note3 which are using the same SoC as the n5. maybe i'll try to flash 4.3 back onto my n7 and see if that connects.
is there any way to send this issue to google so they can be made aware of it?
and of course when i decide to do a logcat to see if i can see what's going on when it's trying to connect the phone (and tablet) decide not to see the tv at all for some reason.
Mis understood
Taomyn said:
I think there's a little confusion here - I understood this to mean:
You have the same problem with wireless connectivity - this is the same as I have noticed that with my N5 and my friends N4, neither of us could connect
With a cable the N4 and N7 work ok - I would expect this to be the case anyway, although I can't test my N5 with a cable as I don't have the USB to HDMI adapter (only one for my old GNex which was MHL which isn't compatible).
Click to expand...
Click to collapse
Not what I meant to say. The N4 and N7 work as a wireless display over WiFi as expected.
Peter
Tried to connect my N5 to Panasonic BluRay Model 230 - it finds the device, and then when you try to connect it just sits there, and sits there....
Honestly, where the hell is the V&V testing ?
prrred said:
Not what I meant to say. The N4 and N7 work as a wireless display over WiFi as expected.
Peter
Click to expand...
Click to collapse
good to know, so it seems to be a 4.4 issue more than a hardware issue.
maybe i'll downgrade my n7 today to test it out. (i was going to do it before but then the 4.4 update was officially released and of course i had to flash that first!)
i also emailed google support today to see what they have to say. it's frustrating not being able to use it in the car since i don't like the actual UI of my headunit.
adiliyo said:
am i the only one having issues getting my n5 to connect via miracast to my TV (Sony) and headunit (eonon) my g2 connected fine, but the n5 sits on connecting, on the car headunit it shows various steps to connecting and hangs on "waiting for rtsp"
i'm wondering if this is a 4.4 issue, or a n5 issue...
i'm bone stock on the n5 (no root, locked bootloader)
Click to expand...
Click to collapse
Kind of off topic here, but how do you like the Eonon head unit? I was thinking about getting one of those for myself! I'd love to hear your opinion on it.
adiliyo said:
good to know, so it seems to be a 4.4 issue more than a hardware issue.
Click to expand...
Click to collapse
Could be the make and model of the TV as well. I have an LG LA6200 and my N5 connected to it in about 3 seconds. Watched some youtube just for fun. It works fine on mine.
Edit: Asylum OMNI and Faux latest.
theesotericone said:
Could be the make and model of the TV as well. I have an LG LA6200 and my N5 connected to it in about 3 seconds. Watched some youtube just for fun. It works fine on mine.
Edit: Asylum OMNI and Faux latest.
Click to expand...
Click to collapse
Hmm if a custom kernel might help it might be enough to get me to unlock the boot loader and have to set up everything again...
Sent from my Nexus 5 using Tapatalk
bluegizmo83 said:
Kind of off topic here, but how do you like the Eonon head unit? I was thinking about getting one of those for myself! I'd love to hear your opinion on it.
Click to expand...
Click to collapse
it's pretty nice, it matches and fits in my GTI really well and looks very stock in terms of dials and finish, which i like.
i haven't had it long enough to comment on durability, but so far, i haven't had any issues with it. the UI is pretty responsive and quick (i loaded iGO maps onto it for navigation and it's much more responsive than the stock nav that i had before, i'm legitimately impressed with the navigation fluidity.
the radio reception is worse than stock, but the stock HU uses a dual antenna setup, so it's always going to get better reception, but personally i don't listen to the radio if i can help it. SD card mp3 playback is just as good as stock and sounds fine.
A2DP works fine, but you don't get any id3 metadata, which sucks, but it's fine, it connects to the phone very fast and hasn't dropped the connection once.
the dlna app crashes on my n5, i might try the iphone version on my 5s just to see how it works, but i get all my music from google play so i don't know if that will work anyways.
what i bought it for (miralink) i haven't gotten to work on my n5, but hopefully that will work soon and work well enough, because i would much rather use google maps and the play music app through the HU screen. those two things working even 90% of the time and i'll be a very happy camper.
overall for around $300 shipped to my door, it's really not a bad unit.
adiliyo said:
it's pretty nice, it matches and fits in my GTI really well and looks very stock in terms of dials and finish, which i like.
i haven't had it long enough to comment on durability, but so far, i haven't had any issues with it. the UI is pretty responsive and quick (i loaded iGO maps onto it for navigation and it's much more responsive than the stock nav that i had before, i'm legitimately impressed with the navigation fluidity.
the radio reception is worse than stock, but the stock HU uses a dual antenna setup, so it's always going to get better reception, but personally i don't listen to the radio if i can help it. SD card mp3 playback is just as good as stock and sounds fine.
A2DP works fine, but you don't get any id3 metadata, which sucks, but it's fine, it connects to the phone very fast and hasn't dropped the connection once.
the dlna app crashes on my n5, i might try the iphone version on my 5s just to see how it works, but i get all my music from google play so i don't know if that will work anyways.
what i bought it for (miralink) i haven't gotten to work on my n5, but hopefully that will work soon and work well enough, because i would much rather use google maps and the play music app through the HU screen. those two things working even 90% of the time and i'll be a very happy camper.
overall for around $300 shipped to my door, it's really not a bad unit.
Click to expand...
Click to collapse
Awesome man, thanks for the info!
Does miracast work then? I'm thinking of getting a dongle, or should I just use slimport
Sent from my Nexus 5 using Tapatalk
Anyone else have a 2013 lg TV with miracast? I just got one and there is a 10-15 second lag. Its pretty much worthless.
Is there something I'm missing?
Sent from my Nexus 5 using Tapatalk
i've tried it with faux's kernel and francos, both don't work for either of my devices. i emailed google and they replied with troubleshooting info but i haven't had a chance to reply to them and try what they have said (really basic stuff, i don't think it will help)
i refuse to go to crappy crappy touchwiz to make this work, but it makes me sad that i can't use my headunit like i want to.

Bluetooth Issues with brand new N5

So I just switched to a Nexus 5 from a Galaxy S4.... loved the phone until I connected it to my Tundra OEM bluetooth system. Hard to pinpoint an exact problem, it just doesn't work right. Randomly disconnects, etc. I had zero issues with bluetooth with my GS4. Is there some fix I should be aware of? i should mention that I rooted the phone right off the bat and am running Cyanogenmod Nightly.
Try it on stock to see if you have issues. It's most likely a rom issue
Sent from my Nexus 5
I've had a similar problem on stock rom with stock, chaos, franco and arkenstone kernels so I don't think the rom or kernel is the root of the problem. It will arbitrarily not connect, it will connect but when a call comes in won't automatically go to bluetooth but go to the handset etc.
I had hoped it was fixed somehow but happened again today out of the blue. It also comes with excessive bluesleep wakelocks that impact my battery life significantly (goes from draining at .7%/hr to ~3%/hr).

Wifi issues and Q about flashing stock ROM

Hi, I bought a used Verizon Note Pro 12.2 SM-P905V and when I got it, noticed that the wifi is very flaky. Initially, it connected to my router fine but took 9 hours to load 120 apps when I signed in to Play using my normal Google account. So I did a factory reset, and then it wouldn't see my router at all. Restart router, factory reset device, no dice.
In the notification shade, wifi icon is always green as if it's on, but when I go into settings, the toggle is off. When I slide it to on, it turns gray and after a minute or so goes back to off. Multiple hard resets, still the same issue. Occasionally, it will "see" the routers, but this only lasts for a few seconds and then they are gone.
So I decided to flash the firmware. I did not complete another factory restore before I embarked on this, but had only just gone through the initial language screens and signed in on the tablet with a brand new Gmail account that had nothing on it. So I downloaded official 5.1.1 ROM from Sammobile, installed device drivers, installed Odin, (followed some great instructions found on XDA, thanks), got the tablet into download mode, connected to laptop and Odin on my laptop showed connection was live and it began to do it's thing. So I left it alone for 30 minutes and when I came back, Odin read "all done!" (or something similar) highlighted in green , and the tablet had restarted, so I assumed all is good.
However, I expected that the flash process would have wiped the setup I had begun on the tablet, but it did not. And the wifi issue still exists. Looks to me like nothing has changed. So two questions for you:
1) Does this mean that the flash did not happen correctly?
2) Do you have any suggestions on how I can fix this wifi issue? (LTE works fine but I don't want to eat up all that expensive data.)
Thanks for any help!
Wifi circuit has many components on mainboard and I believe it's beyond abilities of most users even professionals as you cannot find components and schematic to fix them.
Your best source is looking for this tablet with a broken LCD like this one:
http://www.ebay.com/itm/172145691764?_trksid=p2060353.m1438.l2649&ssPageName=STRK:MEBIDX:IT
http://www.ebay.com/itm/Samsung-Gal...069075?hash=item1a15927393:g:D8MAAOSwbYZXZKDb
If you don't have the need to LTE connection, Note Pro wifi mainboard SM-P900 also fit but you need rear camera for SM-P900 as rear camera of LTE won't work in Wif mainboard.
Any LTE Note Pro 12.2 like P907T( Tmobile) P907A ( AT&T ) mainboard will fit to P905V as they are exactly the same mainboard, except firmware, bootloader and software loaded into it.
I swapped a SM-P907A mainboard to a SM-P905V tablet, it works as an AT&T tablet because the software is for AT&T.
I purchased a verizon note pro 12.2 SM-P905V refurbished from groupon last October. For the last few months the wifi on the tablet has been very flaky. I have a number of devices and only this one frequently drops connection. I never upgraded from kitkat I and was hoping that this issue was software related. Seeing that moransw is experiencing the same problem with this same model but is trying to get back to sock kitkat gives me concern that a software update will not resolve the problem. The other problem I've been having lately is that the device no longer recognizes the stock charger, and will now only charge painfully slow. I've tried a different charge cable from a samsung s6 to no avail. Is the SM-P905V a lemon?
You should use this one to test your charger and usb cable
http://m.ebay.com/sch/i.html?_nkw=u....Xusb+voltage+current&sqp=usb+voltage+current
If you're using correct cable and charger, current should be 1.7 A and voltage should be 5.3 V
Test with known working cable and charger, if nothing is different you should consider to buy new usb flex charging port, around $10.
These basic steps you should do first as nobody can give exactly an answer with many unknowns. It happens to many used tablets, not just this model.
These basic troubleshootings are easy done for simple problem of bad cable, charger or USB port
Try them first then post your results if you need more help for further steps
moransw said:
However, I expected that the flash process would have wiped the setup I had begun on the tablet, but it did not. And the wifi issue still exists. Looks to me like nothing has changed. So two questions for you:
1) Does this mean that the flash did not happen correctly?
2) Do you have any suggestions on how I can fix this wifi issue? (LTE works fine but I don't want to eat up all that expensive data.)
Thanks for any help!
Click to expand...
Click to collapse
1) I am using stock kitkat rooted and I was experiencing the same issue
2) I found this thread regarding our tablet that seems to suggest a bug with wifi if you are using a Bluetooth device
http://forum.xda-developers.com/galaxy-note-pro-12/help/wifi-disconnects-bluetooth-device-t2851406
I was streaming audio through bluetooth to my home surround system, I disabled the bluetooth radio and I haven't had an issue with wifi since. I now use chromcast to stream audio through my surround sound.

Nexus 5 - wifi stuck on 'turning on WiFi'

Hi everyone.
First off, I'd like to say that I don't like opening new threads, and I always read up on my problem first, but I'm simply at my wit's end.
The problem is fairly common (not only on nexus 5 phones), and something a lot of you forum guys have encountered and tried to help with, with more or less success.
Basically, my WiFi doesn't work, it shows 'turning on WiFi' most of the time, and sometimes (fairly rarely), has a couple of hours where it reboots to no end, but I'm thinking that's a power button that sticks. It usually fixes itself after I gently but firmly stroke it (lol) and doesn't happen again for weeks. The WiFi issue started randomly, totally out of the blue, and never happened before to any of my phones (it might have started a couple of days after the last OTA security update, but I can't say for sure). The phone was a 100% stock 16gb Nexus 5.
What I've tried (some steps even multiple times, with different variations):
- removing the sim card
- switching airplane mode on/off
- factory reset (3 times in total think)
- wiping cache
- reflashing stock ROM
- reflashing stock everything
- flashing TWRP and rooting, and manually changing/removing either the .macaddr and .btaddr files, or changing/removing their respective folders
- playing with ownership of those files
- flashing CM, flashing a custom kernel and flashing Paranoid Android
- all in all, i've wiped and rebooted the device like 50 times
Honestly, I don't know what I've missed, I've been at it for days, and I'd be very grateful if someone would point out an oversight.
Also, what's weird, my bluetooth didn't work too, but after i tinkered with .btaddr and .macaddr, it now works perfectly, no matter what I throw at it. This is what gives me hope that I still can resolve this issue without paying for a new motherboard/phone.
Thanks in advance, guys, you've been truly helpful so far.
A defective wifi chip could be the cause of the problem and, in my experience, is not that uncommon. I have come across two n5 and two Samsung s4 phones that work perfectly except the wifi either won't turn on or tries to turn on for about 10 minutes.
I tried different modems, bootloaders, and roms without any success.
Yeah, sadly, that's what I'm thinking too. I had some hope because bluetooth works, but not anymore. I've kinda already made my peace that I'm gonna have to spend +$200 on a repair or $400 on a new phone. I'm just thinking if anyone knows something that helps that I haven't tried yet, please come forward, possibly before I take it to a service centre :laugh:
Maybe look for a used N5 with a smashed screen and working motherboard?

Categories

Resources