yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] dbooth2:
We have three brand new Tytn IIs which are unable to conect to a Cisco Aironet AP. The AP is configured for WPA2-Enterprise (auth by a RADIUS server). An XDA Exec and an XDA Orbit and numerous laptops all connect to this AP fine. The Tytn IIs connect to various other APs ok too.

Anyone else come across problems between the Tytn IIs and Aironet APs?
[Tilt, TyTN II, MDA Vario III General] Alex07:
I am having a similar problem using Cisco Aironet APs with WPA2-AES-Enterprise. I can connect fine but occassionally the Tytn II crashes at various times during the wireless session (the screen goes blank, and I have to perform a soft reset -- none of the buttons are responsive, however the green light still flashes indicating the phone is still active).

Also, the AP is configured to accept connections using WPA-TKIP, WPA-AES, WPA2-TKIP, yet the Tytn II will only connect to the Aironet with WPA2-AES.

A Belkin WAP with WPA-AES and a preshared key works perfectly, however.
[Tilt, TyTN II, MDA Vario III General] alee:
Sorry to bump an old thread... just got through doing a dozen or so hard resets trying to debug a lockup problem.

Turns out even if the wifi radio is OFF, the Tytn II will lock up hard if I've added my Cisco Aironet 1200 series access points to the list of access points (WPA2/PSK AES). It'll take a few soft resets before I'm able to boot past the HTC logo screen.

I connected to a few random open access points without problems... the hard lockups seem to happen only on the Cisco access points.
[Tilt, TyTN II, MDA Vario III General] eras2r:
I have also have the exact same issue here with a Cisco 1100 (G-only) AP. Has anyone found a solution yet?

Regards,

e
[Tilt, TyTN II, MDA Vario III General] alee:
Flashing my Radio to 1.27.12.17 got rid of the lockup (now it just resets the phone when connecting to the Cisco 1200). However, my enterprise network Wi-Fi (with 802.1x/RADIUS, WPA2/PSK EAP) on 1130 access points seems to be working fine now.

See here for various radios.
[Tilt, TyTN II, MDA Vario III General] flashy:
http://xdaforums.com/showthread.php?t=378636

I have exactly the same problem, I have an ISR at home, and the TYTN II will not connect to it, I have tried everything possible, go round to a mates house, and it connects fine to his AP (cheapo one).

Somebody mentioned disabling ccx on the AP's, but i dont think my ISR has that. :(
[Xperia Z5 Compact Q&A, Help & Troubleshooting] featzhang:
As phone boot up,I just got tons pop-ups of "Google Play Services has stopped working""Google Play Store has stopped working"

MM,with root.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] toxic_garden:
the lack of information makes it really hard to help you in any way.

First of all, there's actually no root for MM.

Dirty or clean flash?

Which version did you flash?

how did you flash it?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] featzhang:
32.1.A.1.163 with flashtool,dirty flash.I get root by flash supersu
[Xperia Z5 Compact Q&A, Help & Troubleshooting] kevinwu128:
Are you sure root is working? I'm pretty sure it's not possible yet?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] featzhang:
I'm sure it's working,get new kernel here and get a twrp with it
[Xperia Z5 Compact Q&A, Help & Troubleshooting] featzhang:
And I get logcat for it.

java.lang.RuntimeException: Unable to create application com.google.android.finsky.FinskyApp: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.AppOpsManager.checkPackage(int, java.lang.String)' on a null object reference
[Xperia Z5 Compact Q&A, Help & Troubleshooting] toxic_garden:
yeah.....no. I know it's pretty convenient to keep all the app- and systemsettings and stuff, but dirty flashing MM over LP is going to mess up your system very likely. Even if you wipe cache and stuff, it just doesn't run any stable at all. So do yourself a favour and install clean.

Also, before installing TWRP and Custom Kernel, you might wanna try if your problem already exists with stock kernel and recovery. I didn't know there was any option for root w/ unlocked bootloader, so i can't say anything about the stablity of it.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] featzhang:
Problem occurs both stock and custom,well I'll try wipe and flash it.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] hipsterfont:
If you haven't wiped yet, try this. I dirty flashed from LP to MM using the FTF and this is how I got the play services to stop asking for an update so it might work for you too.

1) Uninstall updates for Google Play Services and let it revert to the copy in /system

You'll need to make sure you don't have Google Play Services listed as a device administrator first (android device manager, smart lock, Gmail on exchange, etc.)

2) Clear app data for both Google Play Services AND the Play Store app (this is crucial!)

3) Load up Play Store again and let it update Google Play Services.

It may take a few times forcing a Play Services update but it should work.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] featzhang:
No luck,still crashing
[Nexus 5X Q&A, Help & Troubleshooting] theorime2:
Hello !

I made the march update yesterday, and now my touchscreen freezes if I don't use it for a few seconds. To make it work again, I have to lock/unlock the phone, or to tap the screen until it works.

It's probably a software issue, because it happenned just after the update. Does someone have the same problem ?
[Nexus 5X Q&A, Help & Troubleshooting] thexman:
I'm having the same problem. It's the right 3rd of the screen that becomes unresponsive. If you swipe over on the left side of the screen, you will be able to use the right side again. This is my second day with this and it's becoming incredibly annoying.
[Nexus 5X Q&A, Help & Troubleshooting] theorime2:
I just realised it ! For me, the only responsive part is the left 4th of the screen. I hope Google Will fix it soon. I don't want to reset my phone.
[Nexus 5X Q&A, Help & Troubleshooting] k.s.deviate:
I'm not seeing this issue... how long is it taking to freeze? also what are you guys running? stock or stock rooted?
[Nexus 5X Q&A, Help & Troubleshooting] thexman:
I'm running stock. If you wait 5 seconds after the scroll bar vanishes, the right side of the screen is unresponsive. If you swipe the left side, it works again. It's really a problem when I'm doing remote desktop to my computer and when I'm playing candy crush.

---------- Post added at 04:26 PM ---------- Previous post was at 04:22 PM ----------

You should post any post March update issues you are having, here. https://productforums.google.com/forum/m/#!category-topic/nexus/other-discussions/2HXGtYoPwa4
[Nexus 5X Q&A, Help & Troubleshooting] theorime2:
I'm running stock too. It takes aproximately 6 seconds for the touchscreen to freeze.
[Nexus 5X Q&A, Help & Troubleshooting] theorime2:
I just tried to reboot in safe mode : it doesn't solve the problem.
[Nexus 5X Q&A, Help & Troubleshooting] Darke5tShad0w:
Does it happen in recovery or bootloader?
[Nexus 5X Q&A, Help & Troubleshooting] sfringer:
I just received the update this afternoon and I'm encountering the same issue. Quite frustrating.
[Nexus 5X Q&A, Help & Troubleshooting] mrlollog:
I got my Nexus 5X yesterday with exactly the same issue.. Flashing any older factory image did not help. :/
[Nexus 5X Q&A, Help & Troubleshooting] sfringer:
I wonder if opting in to the Android N beta would have any effect. Not sure I'm ready to commit to running beta on my only phone; but I am tempted.
[Nexus 5X Q&A, Help & Troubleshooting] mrlollog:
On my phone the problem existed on stock rom (I tried 3 drifferent versions), cm13 and N preview. I do not think that flashing any other Rom would make any difference.
[Nexus 5X Q&A, Help & Troubleshooting] sfringer:
Appreciate the information on your experience. Hopefully this is something Google can track down and is correctable in software.
[Nexus 5X Q&A, Help & Troubleshooting] bubble:
Exact same issue for me since MHC19J. This is driving me nuts.
[Nexus 5X Q&A, Help & Troubleshooting] k.s.deviate:
I've tried all versions except a full CM ROM. So stock, beta, and a few different AOSP builds. I cannot reproduce any screen issues being reported here.

Is there maybe a common app that you all share? No one has mentioned whether you are rooted or not.
[Nexus 5X Q&A, Help & Troubleshooting] chrdesl:
another day (not) in paradise

the best example: Open Wifi Analyzer (in Listview) wait for results and the tap the "Back" Button. (not taping or swayping around during the wifi scan process).

Open Wifi-Analyzer (Listview) wait for result and tap the Backbutton. It took 34 seconds and 34 tapps on the backbutton until the screen turns off, but no reaction until i activate the screen.

Nexus 5X

Stock

Build MHC19J; OTA

No Root Access

for me it's beginnig on entering the SIM-PIN. It takes a few tries to enter my PIN.

Sometimes it's the Back-Button (Back - Menu - Switching Apps)

And it seems to be on the left side of the screen

installed Apps:

3Kundenzone

Google Admin

Android Wear

Authenticator

Autokosten Komplett Pro

Barcode Scanner+ Simple

Google Chrome

Chromecast

Docs

Downloads

Settings

ES File Explorer Pro + Theme

feedly

Fing

Google Fit

Google Photos

Android Device Manager

Gmail

Google

Google Drive

Google+

Hangouts

Google Calendar

Camera

Contacts

Google Maps

Google Messenger

MyTechnisat

Google News & Weather

Google Keep

Google Play Movies

Google Play Music

Google Play Games

Play Store

Google Presentations

Pulseway

RD Client Beta

Calc

SafeInCloud

Shazam pro

Sonos

Speedtest

Stocard

Google Streetview

Google Tables

Teamviewer

Phone

tinyCam Monitor pro

Google Translator

Google Clock

Weather Pro

WhatsApp

Wifi Analyzer

Youtube

Google Cloudprint

Google Now Launcher
[Nexus 5X Q&A, Help & Troubleshooting] sfringer:
I'm running stock without root.

Reviewing the previous posters list of apps, the only things I have in common are the standard Google apps.
[Nexus 5X Q&A, Help & Troubleshooting] bubble:
Stock without root.

The issue is still there even when rebooting in safe mode, so it seems to be unrelated to any installed app.

Time to RMA I guess.

Edit:

Just read this in a reddit thread:
[Nexus 5X Q&A, Help & Troubleshooting] Chris0706:
Same issues here.. Just found that thread.. Got my phone yesterday and thought it might be a hardware issues and thinking of shipping it back.. But now..

Tried newest factory image unrooted, CM13, Bliss, DU every single ROM has it.

It also appears directly after bootloader I think, where you can lock your Phone before booting the real ROM.. It's a pain in the ass!
[Nexus 5X Q&A, Help & Troubleshooting] INDIANAJONNY:
I have this too on my wife's phone. My 5x is fine. March update caused the right side of screen to go dead to touches after 6 seconds of non use...

So annoying ..
[Nexus 5X Q&A, Help & Troubleshooting] bubble:
I tried formatting every partition and flashing MDA89D, this didn't fix anything.

This phone has simply become unusable since MHC19J. I'm pissed.
[Nexus 5X Q&A, Help & Troubleshooting] bubble:
I logged a new bug:

https://code.google.com/p/android/issues/detail?id=205223

Please follow if you are affected.
[Nexus 5X Q&A, Help & Troubleshooting] sfringer:
Thanks for filing the bug. I've commented and followed as an impacted party.
[Nexus 5X Q&A, Help & Troubleshooting] Chris0706:
Just got my replacement, works just fine.. But also reported the bug.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I have plenty of experience with these touchscreen fiascos from the Nexus 7 2013 days.

In case anybody was curious as to what is *likely* happening here...

Most likely MHC19J included a new synaptics touchscreen firmware.

This might have been to address the touchscreen not responsive while charging issue or it might have just been coincidentally released with the MHC19J update (which did attempt to resolve the charging/touchscreen issues probably from the USB Power Delivery side of the problem)

The way touchscreen firmware updates work, if there is a newer firmware available in the release, it is uploaded to the touchscreen device.

Once you have that newer touchscreen firmware, it is physically in the touchscreen device's firmware area (which is separate from the Android system image that you get in the OTAs) and no amount of downgrading your stock Android releases will get you your old touchscreen firmware back.

This is one of the few cases where factory images will *not* get you back to where you started.

Without depending on Google, it is still possible to get your old firmware back but it would involve some work and testing of the resulting fix, not something simple you can do with adb or installing something in TWRP.

Easiest thing would be for Google to realize there was a bad touchscreen firmware update (affecting some users only) and send out a new OTA to address it.

This is all conjecture as I don't feel like updating my device to confirm my theories only to find that my perfectly functioning touchscreen becomes annoyingly unusable.

If some folks on this thread wanted to use 'adb shell' to do some investigation I could probably confirm 99.9% whether this is what happened.

Preferably someone with a device on MHC19* and another with a device on MMB29* could run the following in a shell.

dmesg | grep rmi4_i2c

and post the output(s)
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
In case anyone is curious there have been 3 touchscreen firmware updates since original release. These cannot be rolled back using factory images. Once you install these Android releases, for better or for worse, you get the associated touchscreen firmware.

So for example, once you get the mhc19j (or newer) update, you are stuck with the mhc19j touchscreen firmware even if you flash mda89e factory images to try and get back to stock. Factory Reset will NOT roll back the touchscreen firmware either.

This is the likely reason some people on this thread are experiencing very annoying touchscreen behavior seemingly appearing overnight when your phones picked up the mhc19j update. I am guessing they adjusted the touchscreen firmware to try and compensate for the "noise" from the defective chargers and were too aggressive, ending up causing issues for people who aren't even plugged in and have never had touchscreen issues.

mhc19q did not include any new touchscreen firmware so upgrading to that will have no effect.

If I didn't list a release it just means it is using the same firmware as the most recent listed predecessor.

mda89e

original synaptics touchscreen

mdb08i

updated synaptics touchscreen

updated qualcomm wireless lan

updated DRM

mmb29k

updated synaptics touchscreen

updated fingerprint

updated sensors

updated qualcomm wireless lan

updated qualcomm video

updated modem

mhc19j

updated synaptics touchscreen

updated sensors

updated bluetooth

updated modem

updated DRM
[Nexus 5X Q&A, Help & Troubleshooting] unicorns-fart-rainbows:
I downloaded the MMB29V image and followed sfhub's instructions to reflash the synaptics_rmi4_i2c firmware . Happy to report that the issue is fixed, screen works well :) .

Also, I'm not sure if it was mentioned elsewhere in this thread. The unresponsive screen primarily effects the right side. It occurs after 6 seconds of screen inactivity. It took me a while to figure out that swiping from the left to the to the right side restored screen responsiveness. Still super annoying, but way less frustrating than randomly clicking around until it magically works again, or spamming the power button.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
Thanks for testing out the fix. It actually helps me also as I was holding out on upgrading to latest ROM waiting for someone with the problem to verify this fixes the issue, lest I be left with a non-functioning touchscreen that can't be easily fixed.

For anyone who tries this in the future, please move discussion to this thread:

http://xdaforums.com/nexus-5x/general/potential-fix-touchscreen-dead-zones-t3361123

For new folks searching for a solution, t is hard to find this fix buried 3 pages into this thread and I can control updates to the first posts easier when new information/better solutions become available.
[Nexus 5X Q&A, Help & Troubleshooting] sfhub:
I forgot to update this thread, but I posted an update.zip (which can be flashed from TWRP) that has been verified to fix this problem:

http://xdaforums.com/nexus-5x/general/potential-fix-touchscreen-dead-zones-t3361123

It basically automates the steps listed above.

If you have questions regarding the fix please use that other thread as I don't usually check this one.
[Nexus 5X Q&A, Help & Troubleshooting] ewertonrp:
Vote for a solution at Google Development page

Please, vote for a solution at Google Development page:

Issue 205223:	5X touch screen unresponsive since MHC19J:

code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=&colspec=ID%20Status%20Priority%20Owner%20Summary%20Stars%20Reporter%20Opened&groupby=&sort=&id=205223

You only need to click at the Star (at top-left), in front of " Issue 205223:	5X touch screen unresponsive since MHC19J" title.
[Nexus 5X Q&A, Help & Troubleshooting] MORADESSA:
guys there's app called touch screen repair in the play sotre so if u down grade to the old toch firmware and still have an issue try to calibrate using the app
[Nexus 5X Q&A, Help & Troubleshooting] gereksiz9090:
Half Solution

After my touch freezed, i have find a tipp, how can i start the phone without freeze. I installed original first image rom in google page (android version 6). Then i started the phone with holding touch screen. Also: first power off, then holding touch screen, then start phone. This trick helped me on version 6.

After i find this trick, i did an update on version 8. The same trick is gone with version 8.

Then i sad "i do factory reset and set up my phone agaion." i cannot more set up, because, look at video:

I will install again the old version, will set up my phone, will update it on version 8 and i will not do factory reset.
[Nexus 5X Q&A, Help & Troubleshooting] zhecho:
Touchscreen Nexus 5X v8.1 freeze

Hello All,

I've problems with touchscreen as well:

Hardware:

- Nexus 5x 32G - variant bullhead LGH791 32G

Software version:

- Android 8.1.0/OPM7.181205.001/5080180 (stock version)

Problem:

- Boot until "enter your Pin" screen

- Touch display doesn't respond (No visual damages)

- Going to recovery mode (After FLASHBOOT Mode) gives:

Error: Recovery error "No command" (check out screenshot)

Logs:

(flashboot (select recovery) -> pw button + 2times voluem up )

Exploring logs:

Note: Random errors, That I might be connected to the issue ??

(radnom errors from /cache/recovery/last_log)...

[libfs_mgr]fs_mgr_read_fstab_dt(): failed to read fstab from dt

(random error from /cache/recovery/last_ksmg)

init: Running restorecon...

selinux: Couldn't stat /dev/block: No such file or directory

....

init: Couldn't load property file: unable to open '/system/etc/prop.default'

...

init: Couldn't load property file: unable to open '/odm/default.prop'

...

init: Couldn't load property file: unable to open '/vendor/default.prop'

...

msm_rng: Data not available!

Plan A: with attempt to recover data from the device

- How can I get logs from the device ?

- trying adb with no success.

- step:

Soft reset: remove battery and wait for a 30sec doesn't work ...

Plan B: without recovering data

- step:

try to upload only drivers (download android/drivers#bullhead from OTA)

- step:

factory reset

- step:

new screen

Summary Questions:

How can I get logs from the device ?

What is the bes way to Recover data?
[T-Mobile LG G3] nitin.chobhe:
Thanks Bilal, [MENTION=5126285]odpm1977[/MENTION] and [MENTION=5072061]Tazlo73[/MENTION]

Screenshots...
[T-Mobile LG G3] nitin.chobhe:
one more
[T-Mobile LG G3] marcdw:
Oh man. I just got LiquidDark setup and even installed DU KitKat for the fun of it (thinking we wouldn't get a build soon).

I'll be trying DU out ASAP!

Thanks, man. ?

LG G3 D851, LiquidDark ROM, Tapatalk 4.9.5
[T-Mobile LG G3] Andrewoidd:
My facial reaction was priceless when I saw this. I thought I was on another variant....I always keep trying to see if the old DU versions for the D851 worked but the links always were dead....now there is this...I am in paradise! I have to flash it! You. Rock.
[T-Mobile LG G3] Alukrad:
You are my hero
[T-Mobile LG G3] Alukrad:
Issues came up. SD Card reading as corrupted and Google Play services issue which I think is because of banks dynamic gapps all in all worked well other than those two issues.
[T-Mobile LG G3] nitin.chobhe:
I'm not sure about the SD card issue; Bank's dynamic gapps should be ok. THey should not cause any issue with Google Play services... Try clearing their data from settings -> Apps -> Google Play services and Google Play store
[T-Mobile LG G3] Alukrad:
Not sure what's going on either. Flashed with AOKP MM SD reads fine, no Google play services problem using Open Gapps 6.0 which won't flash with DU, can take screenshots of flash if you wanna see?
[T-Mobile LG G3] Alukrad:
There was no data to clear. Wipe cache and dalvik, factory wipe, clean flash, checked md5 all match. Gonna try a different set of Gapps from banks and read up on other MM ROMs with the SD corruption issue. AOKP so far has has zero issues on latest build. Cant even add Gmail to account on initial startup or in OS. Can I dig through the build prop and compare to another D851ROM?
[T-Mobile LG G3] marcdw:
I'm still in the process of testing her out. Going blacked out so I used DU_TBO gapps and extras. Core set of apps restored via Titanium Backup.

SD card works fine. With MM I always get two sdcard1 notifications. One will be listed as corrupt. Ignored as I'm sure it refers to my ext4 partition on the card and MM doesn't know what to make if it.

Was gettin' sleepy so only tested a few things. Bluetooth speaker with Tomahawk player was good (dig that Pulse).

Default APN was MetroPCS instead of T-Mo but provided reliable data for initial setup.

Will do another or couple installs using Banks and other gapps to see if I can reproduce Alukrad's Play Services FCs.

On a related note, there are times after installation when a sync might be missing like contacts or calendar or what have you. Checking permissions in Settings -> Apps is sometimes recommended.

For today I had only four items syncing, no calendar or contacts. Before we would consider flashing again with diff gapps but sync just needs a kick start.

Adding a second Google account caused sync to do the right thing on the primary where everything showed up and synced. Then I removed the second account.

I'm thinking maybe removing and re-adding the main account will do the same. Not sure.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[T-Mobile LG G3] Andrewoidd:
Had that issue with the contacts not syncing. I just clicked on import contacts from SIM card and it fixed the issue. I don't know why but it worked. Chromium had issues with logging in with my google account but I removed it and installed Chrome Dev and it worked fine
[T-Mobile LG G3] kamen94:
Someone tell me about the battery,please? I felt it is's not good
[T-Mobile LG G3] Andrewoidd:
I have only used it for one day. Seems better than other roms I have tested out. I have never really noticed a big difference in battery life with whatever rom I had.
[T-Mobile LG G3] Alukrad:
Was able to get rid of the system ui and gp services problem by doing a manual advanced wipe of system and data partitions after a full factory wipe. The ROM still isn't reading my SD card if I bypass the corrupt SD message. Using an LG OEM SD HG with 64 gigs. Went back to EOS 5.1.1. Backup and SD card works fine again. ROM is very quick but took 8 hours to restore all my apps from backup. Security setting crashes after I changed lock from swipe to pattern or pin. But all in all...it shows amazing promise.
[T-Mobile LG G3] nitin.chobhe:
[MENTION=6046143]marcdw[/MENTION] can you help here?