yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] k3lcior:
Can you say something about erratic touch screen issues with Nexus 7 2013? And why ASUS / Google has never acknowledged or officially commented about it?

I'm not sure if i have to explain the issue as it's well known, but basically the touch screen has serious issues if it's laying on desk / bed (is not being held / not connected with usb or headphones)

I can guarantee it's affecting ALL Nexus 7 2013 devices, some people just dont know how to reproduce it.

It's shown on this videos for example:

[YOUTUBE]aBEEf8wlJRQ[/YOUTUBE]

[YOUTUBE]EgM5HZuzKN8[/YOUTUBE]

[YOUTUBE]5Y9oVUJ71Nk[/YOUTUBE]

Before you say it's isolated issue, here is amount of results searching for "Nexus 7 2013 touchscreen issue" on Youtube: https://www.youtube.com/results?search_query=neus+7+2013+touchscreen+issue (over 122.000 results for the lazy)

Here are some potential fixes but they are not working well AFAIK:

http://xdaforums.com/showthread.php?t=2535835

http://xdaforums.com/showthread.php?t=2428133

I had my Nexus 7 RMA'd (motherboard was replaced), and it changed nothing. Still the same issue. (i can send you RMA number if you want)

It seems to be grounding problem. (when tablet is being held or connected with headphones / USB there is no problem - as it's grounded properly)

Care to comment? Is this a bad design (Google) or production issue (ASUS) ?
[Nexus 7 (2013) Q&A] Scott@ASUS:
Hello pre4speed,

I am just as anxious as you to see the 4.4.4 update released for the LTE model. At this time I cannot give a release date for this because Google has not released an image for this device. When it comes to the Nexus line Google is responsible for the releases. It could be possible that the LTE edition might skip 4.4.4 and jump straight to Android L when it is released. Let’s hope we see something soon, If you need further assistance you can email me with the Case number N140822232 in the subject line for reference.
[Nexus 7 (2013) Q&A] Scott@ASUS:
Dear k3lcior,

There are reports of the Nexus 7 suffering from touch issues, most of these reports have been fixed with a software update. If the updates do not resolve the touch issues, I recommend sending it in to be diagnosed. I would be more than happy to help assist you and all others with our RMA process.

Since your Nexus 7 has already been to our repair facility I may be able to see what other options are available. If you are interested please feel free to email me at CL-Scott1@asus.com with your serial number. Also, please put case number # N140822280 in the subject line.

Best regards,
[Nexus 7 (2013) Q&A] pc323:
I have bought Nexus 7 (2013) last August and the warranty had been void already. Three of the sensors including the accelerometer, gyroscope and the magnetic sensor do not work properly which causing the malfunction of auto-rotating. I have sent the tablet for RMA process before and the sensors have been replaced. However, the sensors worked for a week only. In the most of the time, the accelerometer and gyroscope look like disabled but the magnetic sensor can return some value although I reboot the machine.

Will the smart cover case affect the sensors by magnetic field? <--I'm just guessing

I cannot figure out the reason why the sensors do not work. Can you give some opinions to me? Thanks;)

The related post: http://xdaforums.com/showthread.php?t=2746045
[Nexus 7 (2013) Q&A] Scott@ASUS:
Hello PC323,

I am sorry to hear about three of your sensors failing within a week of the repair. In regards to your question about the smart cover affecting the sensors, there is a very slight possibility, depending on which cover you are using. If you are using the official case for the Nexus 7 then there should be no interference, the magnet that is included should be small enough and placed properly so it does not affect other sensors. I cannot speak about third party covers though. You can always try wiping the cache (done through the recovery) or even a factory reset if you wanted to go that far. If the resets do not resolve you issues then it might be a hardware issue. If you would like you could email me and include case number 140822657 in the subject line for reference. If you provide your Serial Number I will be able to see what was repaired on your device as well.
[Nexus 7 (2013) Q&A] @non4:
Hi Scott! Great to see manufacturers represented on the forum! Never seen this before, guess I should have gotten a nexus device sooner. Is there any way we can see phonecall support for the LTE version? I've seen the asus padphone, is our radio missing something hardware wise or is Google/Asus holding back? When I get home from work I go straight from my phone to my nexus 7 but I would love to be able to just pop my sim in and not worry. I'm a job jumper and I need to receive calls on my nexus
[Nexus 7 (2013) Q&A] Scott@ASUS:
Hello,

I am aware that there are some workarounds that involve using google voice and forwarding your calls. To me the easiest option would be to find an application that uses your Nexus 7 as a Bluetooth device. This will allow you to use your tablet to place phone calls and send text messages. I can’t personally recommend an application that will do this but I do know that there are applications that will let you do this. This would not require you to move your sim card form one device to the other. If you need to contact me your personal case number is N140823357.
[Nexus 7 (2013) Q&A] skyterrier:
trade LTE for non LTE?

I was one of the first purchasers of a Transformer Prime and needed solid GPS performance. Asus bought back my Prime and I purchased a TF 700. I replaced my TF-700 with a Nexus 7 2013 LTE so I could get the benefits of having the most current version of the Android OS. Well, we all know how the most expensive LTE model is the "ugly step child" who's updates actually lag behind non Nexus devices.

I am trying to stay positive here but this level of support isn't what we have been led to expect for Nexus devices. Is it possible to exchange a Nexus 7 2013 LTE for a non LTE model?

With the exception of the uber late updates to the tablet I truly love it. The most expensive model shouldn't be the Cinderella.
[Nexus 7 (2013) Q&A] hussam91:
Scott, my N7 2013 doesn't get recognised by PC when connected via USB. What may the issue? It is very frustrating. Gives me USB device not recognised(port reset failed) message every time I connect it any PC(I have tried connecting it to a few) using different cables.
[Nexus 7 (2013) Q&A] @non4:
But why no native calls? These apps you speak of are unreliable
[Nexus 7 (2013) Q&A] Mike21222:
Nexus 7 USB port needs replaced

Scott,

I saw your post and am taking you up on your offer.

Her's my story so far:

I called Asus this morning to inquire about replacing the USB port on a Nexus 7. After quite some time with the rep all he could say was the estimate was around $200 but it could come up cheaper depending on what the technician finds.

I know the problem with my sons Nexus 7 is simply the USB port needs to be replaced because the tablet still functions 100% in every way. The only issue I have is that when he plugs in the charging cable it will simply fall out. He has to make sure it stays in and not touch or move the tablet while it is charging. There is no need to troubleshoot, only to replace that USB connector part. I see the part on ebay ranging from $44 to $75, but I prefer to have the manufacturer repair my device as opposed to doing it myself or third party. Can you advise me if I can get a more solid price please as I feel that before I spend $200 to repair my sons almost 2 year old tablet I'd sooner replace it. If I replace it, it's likely I may choose the manufacturer that has been supporting me the best, and at the moment that is not Asus. Is this something you can help me with please? Thanks
[Nexus 7 (2013) Q&A] deadgiveaway:
Probably you can pinch the port .... They seem to open up and get loose pinch it down with a flat head and moderate pressure ..... Worth a try
[Nexus 7 (2013) Q&A] doloresmiska:
Hi! My nexus have problem with wifi. When i download apps from google play, speed is about 0.2-0.3 mb/s. It's very slow. On my phone is 1.0-1.5 mb/s. Chrome and others works great. Is this issue in hardware or software?
[Sprint Samsung Galaxy Note 3] sjr19:
Hello all,

Just looking to see if anyone knows what the current state of AOSP development for our phone is? It seems to have slowed down on the original development threads here...is there a paranoid Android rom? Thanks.
[Sprint Samsung Galaxy Note 3] miguelfp1:
AOSP ROMs are now unified, meaning one build that works with all the Snapdragon Note 3 variants. check over here for all the available ones: http://xdaforums.com/galaxy-note-3/development
[Sprint Samsung Galaxy Note 3] sjr19:
Holy crap thank you! I really was out of the loop, lol
[Fire TV Q&A, Help & Troubleshooting] Newcron:
Not exactly a question as I finally caved in and entered network information manually and everything is completely fine now.

I'm just curious as everything worked fine with DHCP before, in fact my son was in the middle of watching a youtube video when the FireTV suddenly lost network connection. I checked the setting and it asked me to enter the info manually, I power cycle my router, rebooted the FireTV, and nope, no DHCP. Tried this twice until I gave up and went the manual way.

Anybody else experiencing this?
[Fire TV Q&A, Help & Troubleshooting] mcsephoenix:
Did you power cycle the router? Sounds more like an issue with the router's DHCP server then the FireTV. At least that is where I would start.
[Fire TV Q&A, Help & Troubleshooting] Newcron:
I mentioned that I already did that in my OP that you quoted :D

Yeah of course I thought about it and did that. Nothing changed. And there are maybe a dozen total devices in my home that get their IP addresses from the same DHCP server and none of them are having any problem.
[Fire TV Q&A, Help & Troubleshooting] mcsephoenix:
Ha, my bad I guess I better get my morning coffee before I start replying to posts ;) I have not had any issues with DHCP on mine.
[Fire TV Q&A, Help & Troubleshooting] retroben:
I hate it when I can never get a consistently stable device!

My Fire TV,after long enough,has a video playback failure that pretty much forces me to ctrl+alt+del my box to "fix" it.

I blame Qualcomm for this one.

(heck,I blame Qualcomm for all of the issues in Fire TV)

I wonder what Fire TV would be like if it had Mali instead?

Would Dolphin Emulator actually run on it,or would it also fail with Mali?

If Dolphin Emu failed to run,would Reicast run without randomly rebooting when playing Sonic Adventure 1 or 2?

(I still wish Reicast would fix this issue with a workaround for Qualcomm devices.)

I never had this video problem with a Sony NSZ-GS7 I used to have.

Probably because it could turn off completely instead of waiting for a button press to start using it again.

I did have an entirely different issue though,where the screen would be covered in black in some occasions.

Can someone figure out how to "turn off" Fire TV so it will stop majorly glitching out after a long enough amount of time?

I have had numerous other glitches including navigation issues which required restarting my Fire TV to regain proper control.

Sorry for "free for all'ing" you with my list of issues.
[T-Mobile Samsung Galaxy Note 3] _bhaves_:
This worked for me! Followed your steps and I now have root with Knox counter 0x0. Thank you for the guide! The only issue I had was while updating the Super SU binaries I received an "installation failed" message after updating and disabling knox, but after flashing back to the NF4 kernel I had root and Super SU works fine. You might want to add something to the guide so people know this is normal. :good:
[T-Mobile Samsung Galaxy Note 3] effortless:
Thanks for the feedback _bhaves_! I'll be adjusting the guide as I get more feedback. I was only able to test this twice as my phone is already KNOX 0x1 and I had limited time with the KNOX 0x0 phone. I concentrated on ensuring KNOX would stay 0x0 during my testing. I had different results than you regarding installing the binaries. Now I feel that running SuperSU and updating it and disabling KNOX should be done after flashing back to NF4 kernel. I feel the reboot clears stuff up and enables SuperSU to function more fluidly. I'll change it to that and await further feedback.
[T-Mobile Samsung Galaxy Note 3] elosogrande7076:
Thanks for the guide! I was on NF1 and used your guides to successfully go to NF4 with no issues and still have not tripped KNOX...thank you good sir.
[T-Mobile Samsung Galaxy Note 3] MajorTux:
I really wish this had came out when started rooting my Note. I had to send my phone out to Samsung and had to pay to have it fixed :(
[T-Mobile Samsung Galaxy Note 3] conchchowder:
N900TUVUDNE6_KERNEL.tar.md5 is not present in the folder. Only a CF root file is there and a recovery file.

Towelroot states the device isn't supported.

Knox Warranty Void 0x1
[T-Mobile Samsung Galaxy Note 3] effortless:
You're mixing my how-to threads and files. You didn't download the EffortLessRootPrep file... you downloaded the EffortLess ROM Prep.zip which is used to install a custom recovery and custom rom (both of which will trip your KNOX if flashed).

Also, the whole purpose of this thread is to downgrade to the NE6 kernel which supports towelroot (before running it). I specifically mention not to run it (until after you downgrade to the NE6 kernel), because it's not compatible with NF4.
[T-Mobile Samsung Galaxy Note 3] conchchowder:
[emoji15]
[T-Mobile Samsung Galaxy Note 3] GregL:
worked perfectly for me !!!
[T-Mobile Samsung Galaxy Note 3] pete4k:
I would like to thank OP and other developers for all their efforts, it worked like a charm.

But I do have a quick question: I stayed on 4.3 until now due to SD card access being broken and fix requiring root access, that trip Knox.

Of course this solution solved Knox worry and therefore I went ahead updating, however I don't seem to have any SD card issues yet, even before I applied the fix. I just would like to know why?

1. Is it because Google or Samsung fix it in later release?

2. Is it because all the apps I use were already updated?

3. is it because ROMs were somehow fixed either by rooting, or by the people posting the ROM.

Or maybe it's not fixed? When I use ES explorer, I see the folders, but many appear empty, like titanium backup for example.

Now this would be the most stupid thing, if all those folders showing empty weren't, since I always delete empty folders as a rule.

So are SD Card access restrictions fixed in NF4 or not and if not which fix is working well, since I came across some posts that claim broken BT, after applying the fix.

TIA
[T-Mobile Samsung Galaxy Note 3] effortless:
This is a copy and paste of a previous statement I've made about this topic:

A lot of people are very confused on the SD card changes. YOU DO NOT LOSE SD CARD access! The change was that if an app created a folder on your SD card to store stuff, another app cannot access and make changes to it (Which is how it should have been from the beginning). There are many reasons as to why this is the better way (many security related as well as programming related scenarios).

This means that each app can create and write changes to SD card folders it creates and no other folder. The app has to be the creator of the folder it's making changes to.. that makes sense right?! You can still put all the music and pictures and documents you want on the SD card and they will still work like in the past. A few apps had to be updated because they were doing things the old way, but that's been done and you shouldn't have any issues that people had when the change first was done.

4.4 adds a host of new features, bug fixes, network efficiency enhancements and security patches (some are very serious and if you're still on 4.3, your phone is at risk daily). I highly suggest everyone upgrade. If you have any particular issue, private message me and I will help you address it!

To address your current questions though, the change wasn't something that was broken by Google. It shouldn't have been called an SD Card Fix either (like I said, it didn't break), but there were changes in the way Android Apps interacted with the SD card. You can still do this SD Card Fix manually or just use an app in the play store to make the changes for you. There are still certain situations where the "SD Card Fix" is useful, but if it's working for you, then leave it the way it is. Most problems initially were due to needing updates for apps at the time.
[T-Mobile Samsung Galaxy Note 3] pete4k:
Thank you for response and again great job on the root.

The reason I used word "broken" was because originally it broke many programs. I would hate not to be able to access DCIM directory created by camera, to view or delete pics with my favorite third party view program, just to give an example, of why limiting access to SD card could create major issues, but it seems to be working fine so far, so I leave it alone for now.

Another quick question: phone status says official, so do I need to worry about future updates breaking the root, or is OTA updates not possible despite official status.
[T-Mobile Samsung Galaxy Note 3] effortless:
Don't accept the OTA updates (you can be notified even when rooted). They will most likely result in a softbrick.

Wait for someone to test it or you might have to unroot and take the update and then perform a similar method to get root back. It depends on what they do to prevent things like this in the future (if anything).
[T-Mobile Samsung Galaxy Note 3] pete4k:
thanks for your quick reply, on my previous root phone status was custom, so no OTA there. I guess I just freeze the update app to be on safe side, kids play my phone sometimes and could update by accident, I remember from the time before root how pesky those update reminders can be and how easy it is to press accept instead of cancel.
[T-Mobile Samsung Galaxy Note 3] lanwarrior:
Quick question: I am already at NE6, rooted with TowelRoot and KNOX is NOT tripped. Which steps I need to follow to upgrade to NF4?

Or is the steps shown here is not applicable in my case?
[T-Mobile Samsung Galaxy Note 3] effortless:
This guide will work for you. However, you should start from fresh stock NF4 unrooted. Odin stock NF4 and proceed.

It's a lot harder to update a rooted NE6 to all the NF4 files then it is to root NF4 using the NE6 kernel.
[T-Mobile Samsung Galaxy Note 3] lanwarrior:
I just did an upgrade from NE6 to NF4 following the thread here: http://xdaforums.com/note-3-tmobile/general/n900tuvudnf4-extracted-stock-firmware-t2834398/page3

But my phone is now hosed - cannot use keyboard ("Unfortunately, Samsung Keyboard has stopped" error) and APN is gone from SIM card. So I am trying to salvage this.

If I Odin NF4 (add the NF4 file to "AP" in Odin), wouldn't this trip KNOX?
[T-Mobile Samsung Galaxy Note 3] effortless:
No.. Knox is only tripped with custom kernel or custom recovery. Flashing stock NF4 in Odin will not trip Knox. Just flash NF4 in Odin and reset your phone through the settings and it will be working fine again.

Don't continue to flash the recovery or root your phone through my other guide as it will trip Knox (If that is something you are avoiding).
[T-Mobile Samsung Galaxy Note 3] lanwarrior:
Oh, I thought this guide refer to rooting NF4? I was reading through the steps and it talks about "downgrading" to NE6 kernel if one already have NF4.

If needed to, I can flash stock NE6, do a system update to NF4, then follow this guide.

Err.. I just realized that my phone still have SU and root still working, even after hard reset. That means system update won't work. I guess flashing stock will wipe out root?
[T-Mobile Samsung Galaxy Note 3] effortless:
Sorry for the confusion. I edited it to say my other guide (my other guide is for custom recovery and custom rom).. through this guide is fine. Don't root through Odin, root using the NE6 kernel and towelroot like it says and you'll be ok with Knox.
[Sprint HTC One (M7)] KeithDavid1181:
Hi all. Like the title says. My headphone jack won't work properly. If I plug in headphones the phone doesn't recognize them and media sound still comes from the speakers. But, if I power off and plug in the headphones and power on, the phone recognizes them and they work. If I unplug the headphones after that, then sound won't come through the speakers. Any help is appreciated.
[Sprint HTC One (M7)] thicklizard:
This does not provide the needed information to help you at all. What rom are you on, are you on a custom kernel, and what mods have you flashed.
[Sprint HTC One (M7)] KeithDavid1181:
Im on renovate, no custom kernel. it's not the rom. I've flashed several different roms and the problem is persistent. The only mods I'm running is chocolate milk from xposed.
[Sprint HTC One (M7)] thicklizard:
I would flash a stock rom with no mods and see if the problem persist. If it goes away then it is rom or mod related just back up your current rom in case you wish to go back
[Sprint HTC One (M7)] racingmatt1:
I'm having the same problem with my headphone jack and I'm stock and unrooted
[Sprint HTC One (M7)] StormyNight:
1. Have you tried another headset?

2. Have you tried to move the headphone connector around?

3. Have you tried blowing in the headphone jack?

If you've tried all of these (possible) solutions, and if the problem persists, go to Sprint and tell them the problem.
[Sprint HTC One (M7)] KeithDavid1181:
Tried all three of those, still doesn't work. Flashed stock rooted Rom, still no dice. Would the firmware cause a problem like this? Just curious, does anybody know what Sprint would charge for this repair. I've got insurance but the deductible isn't worth it when I can just upgrade my phone in January.
[Sprint HTC One (M7)] StormyNight:
I'd say that it's unlikely that the firmware's causing this. No idea what Sprint would charge for repairing; bought this device used in India.
[Galaxy S II Q&A, Help & Troubleshooting] TheJackal69:
Hi, I have an i9100P on O2 upgraded to official stock 4.1.2 and I am having problems find an exact way to root, with the intention of then upgrading CWM Recovery to at least 6.0.4.3 so I can install Resurrection_Remix_KK_v5.1.1-20140507-i9100.zip KitKat ROM

[IMG="screenshot"]http://s24.postimg.org/o5eqekuph/Screenshot_2014_08_12_18_52_16.png[/IMG]

As far as I can make out I can use Philz kernel (does anyone know the exact version for my phone, as I cannot post in his thread).

Can anyone confirm if these are all compatible with my phone.

Also, I thought I read somewhere that ROM Manager doesnt like this phone, is this true? If so, can I just upgrade to a Kitkat compatible CWM Recovery by flashing it in the recovery installed with Philz kernel?

I am basing my info on this thread:

http://xdaforums.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270

And this article http://galaxys2root.com/galaxy-s2-roms/how-to-install-android-4-4-kitkat-rom-on-galaxy-s2-gt-i9100sgh-i777/

Thank you for any info you may have.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] mohmtr:
What is the best rom in terms of speed and also games and all cheesed
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] mohmtr:
Where developers?

I want to answer :)
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] epipok:
There is no such thing as best rom mate, you may try each rom on dev section and see their differences and choose the one that suits you. :)
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] mohmtr:
According to your experience what is the best rom :) :good:
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] TheFixItMan:
Please follow XDA Rules! Best rom threads are not allowed - I shall get this thread closed
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] nuiseefah:
hello, now my s3 shv-e210s can't touch screen, :crying::crying::crying:every botton can do, how I can

Before I do flash wrong on mobile Odin,

Please help me, Thank you