Plugging my Nexus Player in through my HDMI receiver outputs the res as 576p. Whereas when I plug it directly into the TV it does full 1080p.
I know it's not an issue with the soundbar because the Chromecast that is plugged into the same receiver runs in 1080p just fine.
Anyone else experiencing this?
Any chance you could post your receiver's EDID, or if you don't know what that is, could you post a dmesg from the Nexus Player after unplugging and replugging the HDMI cable?
I'd. Like to know as well
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
xBIGREDDx said:
Any chance you could post your receiver's EDID, or if you don't know what that is, could you post a dmesg from the Nexus Player after unplugging and replugging the HDMI cable?
Click to expand...
Click to collapse
Not sure about the EDID but the model is a Sony HT CT660.
I'll see about getting logs but I'm not sure if I can use the adb shell without root.
rog1121 said:
Not sure about the EDID but the model is a Sony HT CT660.
I'll see about getting logs but I'm not sure if I can use the adb shell without root.
Click to expand...
Click to collapse
On mine I'm able to run 'adb shell dmesg > dmesg.log' and it gives me the log. No root.
I've got an Acer projector that apparently can't handle RGB Limited when it's in 720p mode, so while I was trying to figure that out I found that the dmesg will dump the EDID (the display's capabilities info block) right after you connect the HDMI cable.
Man I am having the same exact issue. It automatically chooses 480p when connected to my receiver. Has anyone figured out how to fix this?
Its apparently a hdmi edid/hdcp handshake issue. I've been trying to figure this out for 2 days straight now. Doesnt seem like there is anything we can do. Either there is a firmware update to the nexus player that extends the time it tries to do the handshake or possibly we can use an HDMI splitter that strips the HDCP from the signal.
xBIGREDDx said:
On mine I'm able to run 'adb shell dmesg > dmesg.log' and it gives me the log. No root.
I've got an Acer projector that apparently can't handle RGB Limited when it's in 720p mode, so while I was trying to figure that out I found that the dmesg will dump the EDID (the display's capabilities info block) right after you connect the HDMI cable.
Click to expand...
Click to collapse
Here it is.
Code:
<6>[ 2683.579311] *********** Print EDID block 0 start **********
<6>[ 2683.579324] 00 ff ff ff ff ff ff 00 4d d9 03 28 01 01 01 01
<6>[ 2683.579329] 09 17 01 03 81 6e 3e 78 8a a5 8e a6 54 4a 9c 26
<6>[ 2683.579333] 12 45 46 20 00 00 01 01 01 01 01 01 01 01 01 01
<6>[ 2683.579337] 01 01 01 01 01 01 8c 0a d0 90 20 40 31 20 0c 40
<6>[ 2683.579342] 55 00 b9 88 21 00 00 18 01 1d 80 18 71 1c 16 20
<6>[ 2683.579346] 58 2c 25 00 b9 88 21 00 00 9e 00 00 00 fc 00 53
<6>[ 2683.579350] 45 35 30 55 59 30 34 0a 20 20 20 20 00 00 00 fd
<6>[ 2683.579354] 00 32 4b 18 3c 0b 00 0a 20 20 20 20 20 20 01 3b
<6>[ 2683.579358] *********** Print EDID block 0 end ************
<6>[ 2683.596053] *********** Print EDID block 1 start **********
<6>[ 2683.596059] 02 03 35 74 4b 02 03 11 12 13 04 14 05 1f 90 20
<6>[ 2683.596064] 32 0f 7f 07 15 07 55 3d 1f c0 57 07 00 67 54 00
<6>[ 2683.596068] 5f 7e 01 83 5f 00 00 6d 03 0c 00 21 00 88 3c 20
<6>[ 2683.596072] 00 60 01 02 03 01 1d 80 d0 72 1c 16 20 10 2c 25
<6>[ 2683.596076] 80 b9 88 21 00 00 9e 01 1d 00 bc 52 d0 1e 20 b8
<6>[ 2683.596080] 28 55 40 b9 88 21 00 00 1e 00 00 00 00 00 00 00
<6>[ 2683.596084] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
<6>[ 2683.596088] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8a
<6>[ 2683.596092] *********** Print EDID block 1 end ************
rog1121 said:
Here it is.
Click to expand...
Click to collapse
Thanks. I put that into edidreader.com and it shows that in the first block, there are 2 timing descriptors. The first one lists 720x576p, and the second one lists 1920x540i (which is 1920x1080 but interlaced). So it looks like the Nexus Player reads the first timing descriptor and goes with that.
It also shows that in the extension block, it lists VIC 16 (1080p) as native (full list of VIC codes on Wikipedia, if you're interested), so I'm not sure why it wouldn't use the native format over the Block 0 descriptor. Maybe they'll have an update for that soon.
(The website also shows that the checksums are valid, so your EDID's not corrupt or anything. It's just the Nexus Player acting weird.)
xBIGREDDx said:
Thanks. I put that into edidreader.com and it shows that in the first block, there are 2 timing descriptors. The first one lists 720x576p, and the second one lists 1920x540i (which is 1920x1080 but interlaced). So it looks like the Nexus Player reads the first timing descriptor and goes with that.
It also shows that in the extension block, it lists VIC 16 (1080p) as native (full list of VIC codes on Wikipedia, if you're interested), so I'm not sure why it wouldn't use the native format over the Block 0 descriptor. Maybe they'll have an update for that soon.
(The website also shows that the checksums are valid, so your EDID's not corrupt or anything. It's just the Nexus Player acting weird.)
Click to expand...
Click to collapse
Well I hope they roll out an update for this soon, or an unsecure boot img so I can root this thing and force 1080p
felizf said:
Man I am having the same exact issue. It automatically chooses 480p when connected to my receiver. Has anyone figured out how to fix this?
Click to expand...
Click to collapse
I'm seeing the same thing. Pushing it through a Yamaha receiver and it picks something really wonky for a resolution.
Jim
there seem to be a lot of HDCP issues with this device that aren't present in other machine.. hopefully, Google will push some fixes here soon..
Updating the Yamaha RX-v3900 firmware fixed me...
I updated my amp firmware and it cleared my resolution issues. I know get full 1080p through the amp.
Did the same
jbresee said:
I updated my amp firmware and it cleared my resolution issues. I know get full 1080p through the amp.
Click to expand...
Click to collapse
Did this too. I can force 1080p on my reciever, but no picture from drm movies. Video quality is wonky. Works fine when connected directly to tv. Hope Google fixes this ASAP. My Fire tv works fine though.
Mine is connected to my Yamaha V673 @ 1080p no probs.
Related
Just waiting for my Nook Touch to arrive...
is there any internal pictures of the Touch?
I'm interested in the differences between the Nook Color and the touch. I believe they are very similar, but not identical, which is why CyanogenMod runs on the color but not on the touch. What are the differences, what drivers need to be added to have customs ROMs on the Touch?
When my Touch arrives I'll start poking around the filesystem and update this thread. Hopefully the kernel modules are kepts as modules rather than built into the kernel.
Edit :
Touch - http://www.techrepublic.com/blog/it...replaceable-same-processor-as-nook-color/2639
Color - http://www.zdnet.com/photos/nookcolor-teardown/487636
- and chipsets in the Color for kernel module drivers to compare with http://nookdevs.com/What_we_know
So to compare:
(Touch in Italics
Color in Bold)
3.7V 1530mAh, 5.66Wh Li-Ion battery (Model No: MLP305787)
6″ Pearl e-ink screen with Neonode zForce touchscreen
^ well, the Color has a real touch screen whereas the Touch uses a IR grid
800MHz Texas Instruments OMAP3621 applications processor
^ color has Samsung S3C6410 ARM processor (no major change)
Texas Instruments TPS65921B Integrated Power Management IC with USB HS Transceiver
Texas Instruments TPS65181 Power Management IC for E Ink Vizplex Enabled Electronic Paper Display
Texas Instruments MSP430F2272 16-bit Ultra-Low-Power Microcontroller
Texas Instruments CD74HC4067 High Speed CMOS 16-Channel Analog Multiplexer/Demultiplexer
Texas Instruments 2624I
SanDisk SDIN5D2-2G NAND Flash chip
Samsung K4X2G323PC-8G08 512 mobile DDR SDRAM
Lattice Semiconductor ispMACH 4032ZE CPLD
Jorjin Technologies WG7310-2A 802.11b/g/n Wi-Fi SiP module
^ Color has CyberTAN Technology (802.11 b/g) (libertas sdio sd8686), CM7 uses tiwlan_drv.ko More info: http://www.jorjin.com/WG7310-20.html
Now to determine what these parts are using for kernel modules...
Any other links for reference:
A slow mention at Cyanomod7 forums: http://forum.cyanogenmod.com/topic/30624-nook-simple-touch-mod/
Cyanomod7 for Nook Color, to study that image for alteration: http://www.cyanogenmod.com/devices/nook-color
Other notes:
Important - the Nook Color is known as the Encore on the CM7 github dev site:
https://github.com/CyanogenMod/android_device_bn_encore
edit: Definately no bluetooth -
Sorry definitely no Bluetooth. At first we thought it did but we were getting confused with a very similar chip (part number ending 0A rather than 2A). The block diagram for the chip in the Nook clearly has Bluetooth crossed out:
http://www.jorjin.com/WG7310-20.html
What made it confusing was that it still has `BT` in the specs, but this is referring to WiFi BT coexistance mode.
So the only way to add Bluetooth would be to get a 0A chip and replace it with the 2A chip on the board. But this scale of soldering is too fiddly to be worth it and practically impossible at this scale.
Hope this clears things up.
Click to expand...
Click to collapse
good summary. Anyone know the best way to get GPS with nook touch? I can't select 'allow mock locations' in settings to try tethering.
Any progress on cyanogenmod 7 for our device? The CM7 site thread points here and this thread points there.. but nothing else out there re CM7 for NT.
And what about partition table of internal flash? Does it look the same?
I wonder what happens if we just try loading CM7 onto the Touch that was designed for the Color.
Probably the screen input will fail. I've noticed that there's no /dev/input/mice
maybe there's something custom in /dev/socket
Code:
E:\ProgramFiles\androidSDK\platform-tools>adb shell ls -R /dev
/dev:
bc_example
pvrsrvkm
rm_server_in
pm_server_out
pm_server_in
timer
controlC0
pcmC0D0p
pcmC0D0c
DspBridge
vcsa
vcs
ptmx
tty63
tty62
tty61
tty60
tty59
tty58
tty57
tty56
tty55
tty54
tty53
tty52
tty51
tty50
tty49
tty48
tty47
tty46
tty45
tty44
tty43
tty42
tty41
tty40
tty39
tty38
tty37
tty36
tty35
tty34
tty33
tty32
tty31
tty30
tty29
tty28
tty27
tty26
tty25
tty24
tty23
tty22
tty21
tty20
tty19
tty18
tty17
tty16
tty15
tty14
tty13
tty12
tty11
tty10
tty9
tty8
tty7
tty6
tty5
tty4
tty3
tty2
tty1
tty0
console
tty
network_throughput
network_latency
cpu_dma_latency
log
binder
alarm
android_adb
android_adb_enable
twl4030-madc
ashmem
kmsg
urandom
random
full
zero
null
kmem
mem
snd
graphics
watchdog
ttyS1
ttyS0
usbdev1.1_ep00
usbdev1.1_ep81
usb1
block
i2c-2
i2c-1
rtc0
input
socket
pts
/dev/log:
radio
events
main
/dev/snd:
timer
controlC0
pcmC0D0c
pcmC0D0p
/dev/graphics:
fb0
/dev/block:
vold
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram15
ram14
ram13
ram12
ram11
ram10
ram9
ram8
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
mmcblk0p8
mmcblk0p7
mmcblk0p6
mmcblk0p5
mmcblk0p4
mmcblk0p3
mmcblk0p2
mmcblk0p1
mmcblk0
/dev/block/vold:
179:8
179:7
179:6
179:5
179:4
179:3
179:2
179:1
179:0
/dev/input:
event2
event1
event0
/dev/socket:
wpa_tiwlan0
keystore
installd
dbus
zygote
vold
property_service
/dev/pts:
2
9
8
7
6
5
4
3
1
0
I'd love to have a go at CM7... but it's dicey. What would help a lot is being able to run live straight off the SD card so that any testing is done there without changing the nook itself.
re: partition table: I'll have to have a look. I'll see if I can push something like fdisk to it. See this thread: http://forum.xda-developers.com/showthread.php?t=1241728
re: Mock locations. I don't have that option either. I'm only on version 1.0.0. Perhaps we need to upgrade?
Hi all
I suppose many of us are dreaming of having CM (I hope . So as Nook Color and Nook Touch are almost the same from technical point of view I tried to install CM on my Nook Touch. I was sure that at least touch screen wouldn't work so it was just an experiment.
1. Installed Rommanager - success
2. Flashed CWM (4 Nook Color) - success
3. Reboot into recovery - failed (hang)
Any ideas?
P.S. Moderators, I suggest to move this topic to android development, not general.
Which hardware specs is right?
jago25_98 said:
Just waiting for my Nook Touch to arrive...
Touch - www.techrepublic.com/blog/itdojo/no...replaceable-same-processor-as-nook-color/2639
800MHz Texas Instruments OMAP3621 applications processor
Samsung K4X2G323PC-8G08 512 mobile DDR SDRAM
Click to expand...
Click to collapse
I'd like to buy an ereader, like Nook Simple Touch, Kindle Touch, or Sony PRS-T1. And I want to know the hardware before I buy it.
However, I am very confused about Nook Touch specs.
It says 800 MHz CPU + 512 MB memory here.
From B&N website, it is 600 MHz + 256 MB memory link www.barnesandnoble.com/u/Compare-NOOKs/379003181
Another post (mikecanex.wordpress.com/2011/06/13/nook-touch-rooting-june-13th-news) says it has a TI OMAP3621 CPU but the clock is 600 MHz (BTW: does BogoMIPS : 597.64 in the post mean 600 MHz?) and 228 MB usable memory.
According to wiki (en.wikipedia.org/wiki/Texas_Instruments_OMAP#OMAP_3) OMPA3611 clocked at 800 MHz is used in Nook Simple Touch.
Which one is accurate? If it is 512 MB, I will go for Nook Touch as it will be much better to load Android apps.
PS: Microcenter says Sony PRS-T1 has 256 MB memory. (www.microcenter.com/single_product_results.phtml?product_id=0375288)
Himalayas said:
Which one is accurate? If it is 512 MB, I will go for Nook Touch as it will be much better to load Android apps.
Click to expand...
Click to collapse
The NST has 2GB of flash memory used for internal storage + 512MB of DDR SDRAM
Edit: Just looked inside mine, it has a Hynix 256MB chip, so the 512MB claim over at techrepublic doesn't hold water.
---------- Post added at 11:53 AM ---------- Previous post was at 11:50 AM ----------
Did a check on my NST just to see how much of that chip is usable:
Code:
<6>[ 0.000000] Memory: 256MB = 256MB total
<5>[ 0.000000] Memory: 232448KB available (3328K code, 798K data, 144K init)
That might not be what you wanted to hear
Himalayas said:
Another post (mikecanex.wordpress.com/2011/06/13/nook-touch-rooting-june-13th-news) says it has a TI OMAP3621 CPU but the clock is 600 MHz (BTW: does BogoMIPS : 597.64 in the post mean 600 MHz?) and 228 MB usable memory.
Click to expand...
Click to collapse
It's clocked at 800mhz even if cpuinfo reports diferently
ros87 said:
Just looked inside mine, it has a Hynix 256MB chip
Did a check on my NST just to see how much of that chip is usable:
Code:
<6>[ 0.000000] Memory: 256MB = 256MB total
<5>[ 0.000000] Memory: 232448KB available (3328K code, 798K data, 144K init)
That might not be what you wanted to hear
Click to expand...
Click to collapse
eded333 said:
It's clocked at 800mhz even if cpuinfo reports diferently
Click to expand...
Click to collapse
Then the official B&N website give us correct memory (256 MB) but incorrect CPU frequency ( 600 MHz instead of real 800 MHz).
It is not as sweet as I thought. But at that price, we can't expect more, right? I may start looking at Sony PSR-T1, then.
Hi Developers,
I have asked this question couple of times in the forum, however no one is interested in responding, therefore thought of starting the new thread.... Please merge if one already exists.
I have been using the CM7 Nand build and everything works fine except for the Wifi Hotspot & USB Tethering on the CM7 Nand build. I use a 3G connection and it works absolutely fine on the phone, however when I use the Hotspot or USB tethering feature my laptop does not connect to the internet, I have tested this on multiple systems and its always the same. Also tried to re-flashing, however did not work. Reinstalled wm6.5 and everything worked fine. The CM7 SD card version and the R175 & R169 from code.google work absolutely fine and my laptop is able to connect to the internet via my phone. Also if i connect the phone to a wi-fi router it works absolutely fine. Therefore I feel that this is something related to the CM7 NAnd build and not specific to the laptop
Not sure if I am the only 1 facing this problem. If anyone has found a fix for this please upload the steps.
About Phone:
Android VErsion: 2.3.7
Base Band Version: 32.2803.05.06U_0.63.05.36
Kernel VErsion: [email protected] #45
Mod Version: cyanogenMod-7.2.0-RC0-photonic-KANG
Build: GWK74
Laptop Information:
HP Probook 6460b
OS: Windows 7 x64
Also tried on Windows 7 x32, Windows Vista (x64), Windows XP x32
Thanks
Maq
I think problem with mac
Sent from my Photon using XDA
Thanks Derefas.... can you guide me to any thread where i can find a fix.
I tried searching for over a month, but could not find any fix/thread for this problem.
Yes, same problem here unfortunately. 3G works fine on Mini, router is available and connection to it goes fine, but then router is not routing at all, internet connection doesn't go through. Win7 shows a yellow "!" mark on the wifi icon and that's it. Sounds weird that SD version has working tethering though. Any hint or test we can make?
Yes, i think problem is mac 11:22:33:44:55:66 but why devs can not not add old wifi driver with static harcoded nvs? I using it with fixed mac addr and boot.img is easy to hex edit becouse is not compressed, for example users will be able to hex edit their boot.img with his real mac addr:
photon boot.img with static nvs:
Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00493DC0 73 69 73 61 76 32 67 3D 30 78 33 0A 62 78 61 32 sisav2g=0x3.bxa2
00493DD0 67 3D 30 0A 63 63 6F 64 65 3D 41 4C 4C 0A 63 63 g=0.ccode=ALL.cc
00493DE0 74 6C 3D 30 78 30 0A 63 63 6B 64 69 67 66 69 6C tl=0x0.cckdigfil
00493DF0 74 74 79 70 65 3D 30 0A 6F 66 64 6D 64 69 67 66 ttype=0.ofdmdigf
00493E00 69 6C 74 74 79 70 65 3D 31 0A 72 78 70 6F 32 67 ilttype=1.rxpo2g
00493E10 3D 32 0A 62 6F 61 72 64 6E 75 6D 3D 31 0A 6D 61 =2.boardnum=1.ma
00493E20 63 61 64 64 72 3D 30 30 3A 35 33 3A 32 32 3A 34 caddr=[color=red]00:53:22:4[/color]
00493E30 38 3A 34 31 3A 35 30 0A 6E 6F 63 72 63 3D 31 0A [color=red]8:41:50[/color].nocrc=1.
00493E40 6F 74 70 69 6D 61 67 65 73 69 7A 65 3D 31 38 32 otpimagesize=182
00493E50 0A 68 77 68 64 72 3D 30 78 30 35 66 66 66 66 30 .hwhdr=0x05ffff0
00493E60 33 31 30 33 30 30 33 31 30 30 33 31 30 30 30 30 3103003100310000
00493E70 30 0A 73 64 5F 67 70 6F 75 74 3D 30 0A 73 64 5F 0.sd_gpout=0.sd_
00493E80 67 70 76 61 6C 3D 31 0A 73 64 5F 67 70 64 63 3D gpval=1.sd_gpdc=
00493E90 30 0A 73 64 5F 6F 6F 62 6F 6E 6C 79 3D 31 0A 52 0.sd_oobonly=1.R
00493EA0 41 57 31 3D 38 30 20 33 32 20 66 65 20 32 31 20 AW1=80 32 fe 21
00493EB0 30 32 20 30 63 20 30 30 20 32 32 20 32 61 20 30 02 0c 00 22 2a 0
00493EC0 31 20 30 31 20 30 30 20 30 30 20 63 35 20 30 20 1 01 00 00 c5 0
00493ED0 65 36 20 30 30 20 30 30 20 30 30 20 30 30 20 30 e6 00 00 00 00 0
00493EE0 30 20 34 30 20 30 30 20 30 30 20 66 66 20 66 66 0 40 00 00 ff ff
Thanks,
Can you point to a guide/link or provide the steps which will help fix this.
Regards,
Maq
Same problem here. How can we change Mac adr?
I've got an HTC Aria but I'm on the same boat here. What I've did is to install an app called OpenGarden and since then Wifi Tethering works perfect. USB tethering still not working.
I'm trying on Windows 7 x64
Found a work around.... installed barncel wi-fi tether... configured Adhoc Network....works like charm.... enjoy.....
Nice, working on Photon with CM7 (boot sd card)
ps : it's "Barnacle wifi tether"
this is only for WIFI what about USB?
Yes only for wifi, i don't use usb to share (it' for my ipad wifi...)
trying to figure out something for that too.... will keep you updated if i get something
USB Tethering Fix
Hi All,
The latest posts were about usb tethering , I'm using pdanet 3.50 for this purpose and it's working properly follow this link:
https://play.google.com/store/apps/...ult#?t=W251bGwsMSwxLDEsImNvbS5wbi5oZWxwZXIiXQ
Thanks to xda member esn_bmd ( Profile Link: http://forum.xda-developers.com/member.php?u=4516525) who helped figure this out.
Please thank him not me...
Regards,
Maq
Fix for this **** - fix proc/calibration, use bcm4329_204 and softap
Proof
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey folks,
Recently picked up a Nexus Player and having an unusual problem when switching the TV off and on. If I turn the TV on, and then turn the Nexus Player on, the output looks normal. But if I switch the TV off and on while leaving the Nexus Player on, the output of the Nexus Player becomes blurry. Not horribly so, everything is still legible, but it's still noticeable. It's comparable to showing 720p output on a 1080p screen, however, the Nexus Player is still outputting in 1080p according to 'dmesg' and 'dumpsys display'.
I have a Sony KDL-46Z5500. Here's the EDID dump from dmesg:
Code:
*********** Print EDID block 0 start **********
00 ff ff ff ff ff ff 00 4d d9 01 ba 01 01 01 01
01 13 01 03 80 a0 5a 78 0a 0d c9 a0 57 47 98 27
12 48 4c 21 08 00 81 80 01 01 01 01 01 01 01 01
01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
45 00 40 84 63 00 00 1e 01 1d 00 72 51 d0 1e 20
6e 28 55 00 40 84 63 00 00 1e 00 00 00 fc 00 53
4f 4e 59 20 54 56 20 58 56 0a 20 20 00 00 00 fd
00 30 3e 0e 46 0f 00 0a 20 20 20 20 20 20 01 85
*********** Print EDID block 0 end ************
*********** Print EDID block 1 start **********
02 03 30 f0 50 1f 10 14 05 13 04 12 11 16 15 03
02 07 06 01 20 26 09 07 07 15 07 50 83 01 00 00
68 03 0c 00 30 00 b8 2d 0f e3 05 03 01 e2 00 7b
02 3a 80 d0 72 38 2d 40 10 2c 45 80 40 84 63 00
00 1e 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 40 84
63 00 00 1e 01 1d 80 18 71 1c 16 20 58 2c 25 00
40 84 63 00 00 9e 01 1d 80 d0 72 1c 16 20 10 2c
25 80 40 84 63 00 00 9e 00 00 00 00 00 00 00 fe
*********** Print EDID block 1 end ************
I've compared dumpsys display outputs with a diff tool from when the screen is sharp and when it's blurry and there are no meaningful differences (just PIDs and what looks like a hash on android.os.BinderProxy). Here's the dmesg output from when I turn the TV back on (excluding the EDID which I've already shown above):
Code:
<6>[ 602.079619] [otm_hdmi]: __hdmi_irq_handler_bottomhalf: hdmi state switched to 0
EDID SHOWN HERE
EDID SHOWN HERE AGAIN
<6>[ 603.043781] [drm] setting fifo size, arb2:0xc0300, arb: 0x20080100
<6>[ 603.043800] [drm] dsp stride=7680 bpp=32
<6>[ 603.046468] request_suspend_state: wakeup (3->0) at 602839491618 (2015-05-27 13:05:29.417151656 UTC)
<6>[ 603.067435] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.097477] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.138095] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.144209] [otm_hdmi]: android_hdmi_encoder_dpms: hdmi state switched to 1
<6>[ 603.167878] it8566_hdmi_cec 1-0068: cec tx bus err
<3>[ 603.188058] had: had is not in suspended state
<4>[ 603.188098] dhd_set_suspend: Remove extra suspend setting
EDID SHOWN HERE
<6>[ 603.208366] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.238509] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.278478] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.307996] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.347109] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.376730] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.438371] it8566_hdmi_cec 1-0068: cec tx direct nack / bcst reject
<6>[ 603.489896] it8566_hdmi_cec 1-0068: cec tx direct nack / bcst reject
<6>[ 603.676647] it8566_hdmi_cec 1-0068: cec tx bus err
<6>[ 603.706179] it8566_hdmi_cec 1-0068: cec tx bus err
At this point I'm stumped about how to resolve this - I just restart the NP every time I turn the TV on. Has anyone had any experience with this issue and know of any fixes I can try?
Thanks for the help!
I am seeing the same exact issue with my Nexus Player after I power cycle my Panasonic VT60 TV or receiver. I assumed the picture was 720p being upscaled internally by the NP at first as well, since the TV indicated a 1080p/60Hz signal.
The slight blurriness that causes me to be unable to distinguish individual pixels looks almost identical to upscaled 720p input on this and other TVs.
As in your case, power cycling the player gets the correct, non-blurry output back, and it appears the NP still believes it is rendering a 1080p picture in either case.
So it's not just me then!
For what it's worth, I upgraded to Android M but the problem remained. I've now switched to a Nvidia Shield which works perfectly, suggesting that the issue is specific to the NP and not Android TV.
Hope you find a fix.
On usb tether to my linux notebook, I get about 1Mbps down and 14Mbps up. Using the speedtest on the phone, I get 16Mbps down and 6MBPS up. Yes I know these results are not repeatable, but I consistently can't break 1Mbps download on tether. Further down I will show this is related to packet framing errors.
But first, device data. The OnePlus5 is running Android 7.1.1 Oxygen 4.5.10 Oneplus A5000. This is the 128G flash/ 8G ram version.
Notebook data:
Code:
Linux linux-0u81 4.4.79-19-default #1 SMP Thu Aug 10 20:28:47 UTC 2017 (2dd03e8) x86_64 x86_64 x86_64 GNU/Linux
Output of lsusb for the phone follows, but note this message:
iInterface 5 RNDIS Communications Control
** UNRECOGNIZED: 05 24 00 10 01
** UNRECOGNIZED: 05 24 01 00 01
** UNRECOGNIZED: 04 24 02 00
** UNRECOGNIZED: 05 24 06 00 01
Click to expand...
Click to collapse
Code:
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2a70
idProduct 0xf00e
bcdDevice 4.04
iManufacturer 1 OnePlus
iProduct 2 OnePlus
iSerial 3 (censored)
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 75
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4 rndis
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 224 Wireless
bFunctionSubClass 1 Radio Frequency
bFunctionProtocol 3 RNDIS
iFunction 7 RNDIS
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 3 RNDIS
iInterface 5 RNDIS Communications Control
** UNRECOGNIZED: 05 24 00 10 01
** UNRECOGNIZED: 05 24 01 00 01
** UNRECOGNIZED: 04 24 02 00
** UNRECOGNIZED: 05 24 06 00 01
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 6 RNDIS Ethernet Data
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8e EP 14 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0f EP 15 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Binary Object Store Descriptor:
bLength 5
bDescriptorType 15
wTotalLength 12
bNumDeviceCaps 1
USB 2.0 Extension Device Capability:
bLength 7
bDescriptorType 16
bDevCapabilityType 2
bmAttributes 0x00000006
Link Power Management (LPM) Supported
Device Status: 0x0000
(Bus Powered)
Test Data (for nitpickers):
(removed due to forum rules but available on request.)
Note only the RX path has frame errors:
Code:
usb0 Link encap:Ethernet HWaddr (censored)
inet addr:192.168.42.215 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: 2607:fb90:8635:67b8:78a2:7bff:febe:7afb/128 Scope:Global
inet6 addr: fe80::78a2:7bff:febe:7afb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12497 errors:1062 dropped:0 overruns:0 frame:1058
TX packets:22595 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4121815 (3.9 Mb) TX bytes:27795493 (26.5 Mb)
I have run this on Opensuse, Fedora, Mint, and Ubuntu with similar results.
It would be useful if someone could duplicate this. I don't think the flavor of linux matters. I don't have a problem on windows.
Using the google on the interwebs, there is some chatter about RNDIS being dropped on "later" versions of Android. Reality? Perhaps OnePlus has attempted to add it back and didn't do it correctly.
I should also point out I'm using Tmobile, which is a IPV6 system. I'm using the Linux "network manager", but using "wicked" produced the same error.
I'm encountering the same issue.
Any hint on how to resolve it?
Sorry about the late reply. I'm not a regular here.
If you are on a OnePlus, please complain to them. I still have no solution.
This appears to be fixed on Oxygen OS rev 4.5.14
usb0 Link encap:Ethernet
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13690 errors:0 dropped:0 overruns:0 frame:0
TX packets:11644 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15616702 (14.8 Mb) TX bytes:8406490 (8.0 Mb)
yes 4.5.14 worked for me another thread here
https://forum.xda-developers.com/oneplus-5/help/slow-tether-usb-t3649501
I updated a OnePlus 5 from Android 8.0 to Android 8.1 and lost the ability to USB tether. Hotspot works fine. I've verified that some other users have this problem on the OnePlus subreddit. I'm on Opensuse 42.3.
Linux 4.4.126-48-default #1 SMP Sat Apr 7 05:22:50 UTC 2018 (f24992c) x86_64 x86_64 x86_64 GNU/Linux
This link indicates a "fix" similar to one on a Lineage forum. It doesn't solve the problem, but figured I would put it here to prevent similar posts from showing up in this thread.
https://forums.oneplus.com/threads/hotspot-not-working.769592/
At least this fix didn't break anything.
There are suggestions regarding changing the APN, but I no joy.
Using lsusb, it is clear that the phone is seen by the PC. However the phone doesn't show up when I run ifconfig.
This is the lsusb verbose output when usb tether is selected.
Code:
lsusb -s8:10 -v
Bus 008 Device 010: ID 2a70:f00e
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2a70
idProduct 0xf00e
bcdDevice 4.04
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 75
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 239 Miscellaneous Device
bFunctionSubClass 4
bFunctionProtocol 1
iFunction 7
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 239 Miscellaneous Device
bInterfaceSubClass 4
bInterfaceProtocol 1
iInterface 5
** UNRECOGNIZED: 05 24 00 10 01
** UNRECOGNIZED: 05 24 01 00 01
** UNRECOGNIZED: 04 24 02 00
** UNRECOGNIZED: 05 24 06 00 01
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 6
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8e EP 14 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0f EP 15 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
For completelness, this is the lsusb verbose output when tether is NOT selected.
Code:
lsusb -s8:13 -v
Bus 008 Device 013: ID 2a70:f003
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2a70
idProduct 0xf003
bcdDevice 4.04
iManufacturer 1 OnePlus
iProduct 2 OnePlus
iSerial 3 (redacted)
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4 mtp
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 5 MTP
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x001c 1x 28 bytes
bInterval 6
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 6 Mass Storage
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)