yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] 2uk3y:
hai, can anyone see what the problem here? :confused:

because my phone suddenly freeze

sorry coz i really noob about all of this. :crying:

thanks for your help :highfive:

D/dalvikvm( 8831): Added shared lib /data/app-lib/com.tencent.mm-2/libxlog.so 0x
41a8ca18
D/dalvikvm( 8831): No JNI_OnLoad found in /data/app-lib/com.tencent.mm-2/libxlog
.so 0x41a8ca18, skipping init
W/MicroMsg.xlogger( 8831): JNI_Xlog_onCreate
I/Process ( 8831): Sending signal. PID: 8831 SIG: 9
I/ActivityManager( 5051): Process com.tencent.mm:tools (pid 8831) has died.
D/lights ( 5051): set_light_buttons: 2
D/dalvikvm( 7447): GC_CONCURRENT freed 1989K, 50% free 5428K/10776K, paused 3ms+
7ms, total 57ms
D/dalvikvm( 5051): GC_FOR_ALLOC freed 5796K, 45% free 22714K/40900K, paused 125m
s, total 125ms
D/dalvikvm( 5563): GC_FOR_ALLOC freed 2975K, 33% free 12003K/17796K, paused 27ms
, total 27ms
D/lights ( 5051): set_light_buttons: 1
I/ActivityManager( 5051): START u0 {act=android.intent.action.MAIN cat=[android.
intent.category.LAUNCHER] flg=0x10200000 cmp=com.oasisfeng.greenify/.GreenifyAct
ivity bnds=[362,556][475,686]} from pid 5563
I/ActivityManager( 5051): Start proc com.oasisfeng.greenify for activity com.oas
isfeng.greenify/.GreenifyActivity: pid=8854 uid=10122 gids={50122, 3003, 1007, 1
028}
D/dalvikvm( 5051): GC_FOR_ALLOC freed 4109K, 45% free 22651K/40900K, paused 106m
s, total 106ms
W/ResourceType( 5051): Skipping entry 0x7f040021 in package table 0 because it i
s not complex!
W/ResourceType( 5051): Skipping entry 0x7f040022 in package table 0 because it i
s not complex!
I/Cleaner ( 6735): Service is started.
I/ActivityManager( 5051): Displayed com.oasisfeng.greenify/.GreenifyActivity: +6
06ms
D/lights ( 5051): set_light_buttons: 2
W/GAV3 ( 8854): Thread[GAThread,5,main]: Service unavailable (code=1), will r
etry.
W/ActivityManager( 5051): Unable to start service Intent { act=com.google.androi
d.gms.analytics.service.START (has extras) } U=0: not found
I/GAV3 ( 8854): Thread[GAThread,5,main]: No campaign data found.
W/ActivityManager( 5051): Unable to start service Intent { act=com.google.androi
d.gms.analytics.service.START (has extras) } U=0: not found
W/GAV3 ( 8854): Thread[Service Reconnect,5,main]: Service unavailable (code=1
), using local store.
D/MobileDataStateTracker( 5051): default: setPolicyDataEnable(enabled=true)
D/lights ( 5051): set_light_buttons: 1
D/lights ( 5051): set_light_buttons: 2
I/InputDispatcher( 5051): Application is not responding: AppWindowToken{42c302b8
token=Token{42e684d8 ActivityRecord{41ab3820 u0 com.oasisfeng.greenify/.Greenif
yActivity}}} - Window{42b31eb0 u0 com.oasisfeng.greenify/com.oasisfeng.greenify.
GreenifyActivity}. It has been 5002.5ms since event, 5000.9ms since wait starte
d. Reason: Waiting because the focused window has not finished processing the i
nput events that were previously delivered to it.
I/WindowManager( 5051): Input event dispatching timed out sending to com.oasisfe
ng.greenify/com.oasisfeng.greenify.GreenifyActivity
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Kendroxide:
So I followed this guide to root my phone (wont let me post links so just add youtube in front of it): watch?v=mENI0ypxL5g

I followed everything exactly to what he did, and everything seemed to work until I tried opening superuser. When I opened it, it said:"The Superuser binery (su) must be updated. Please choose an installation method."

The only options were "recovery install" and "install". I tried them both and I get the same message "There was an error installing Superuser. Please send a log of the error to the developer."

Did I do anything wrong and if so, do I needed to unroot my phone before trying again (that is if I even rooted my phone)?

Thanks for bearing with me, this is my first time trying to root a phone.
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Kendroxide:
67 views and no replies?

I hate to bump this thread again but I would really like to know what I am doing wrong.

FYI I also tried the method listed on this site but it failed to work as well.

I guess I can give some more info on my phone:

Model number: SGH-1337M

Android version: 4.2.2

Baseband version: 1337MVLUAMG1

Kernel version: 3.4.0-897376 dpi@DELL157 #1 Mon Jul 1 16:58

Build number: JDQ39.1337MVLUAMG1
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] xBeerdroiDx:
you could reroot and use this method: http://xdaforums.com/showthread.php?t=2293800. its meant for the "M" variant of your device, unlike the video guide you used.

stick to xda.

cheers
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Agent:
Just wanna +1 that
[Nexus 7 (2013) General] WackyClash:
So I was having the multitouch issues.. putting two or more fingers closely together caused major freakouts, and some swipes would just count as taps, as well as phantom taps happening. I RMA'd. got it back, only to find out all they did was a factory reset, which I had already done. Obviously this did nothing to fix the problem. I was very angry. I went to Asus support and did a chat with a support guy ( trying to remember this is not his fault ) and politely stated that the RMA had done nothing. I set up a new one, explaining that it is a hardware issue and that I wanted the screen/digitizer to be replaced. I'm sending it tomorrow, so I'll let you guys know how that goes. Has anyone else RMA'd for this and gotten it back in perfect working condition?
[Nexus 7 (2013) General] sauofee:
Yes, me too, my N7 was returned to Amazon yesterday :crying:

unfortunately, I couldn't find any tablet like N7 spec and price.
[Nexus 7 (2013) General] bandit_knight:
My device only exhibits some multitouch jumpiness when not grounded. I decided to wait for Asus and Google to sort it out internally and then I will send it for repair. Now from what I heard they only replace one faulty units with another. Mine seems to be one of those better ones even though it has serious problems with basic pinch to zoom gestures when ungrounded. I keep it for now because I do not want to risk replacement with a worse one.

One question to the those of you who got a replacement. When you got your replacement devices what was the manufacturing date? Did anyone get a device from September production batch? Was it any better?
[Nexus 7 (2013) General] gadzooks64:
I just mailed mine in for repair yesterday. I was hoping this would resolve my screen issues but I'm getting the impression that I will be very lucky if it does.

Plan B will be to buy another one and return the first one with that receipt. Rinse repeat until I get one that works.
[Nexus 7 (2013) General] WackyClash:
So annoying that's what you have to do just to get one that works. Asus..... I don't know why they didn't just go samsung or htc, as badly as asus fudged up QC on the 2012 N7
[Nexus 7 (2013) General] bokoy:
I just mailed mine in for repair today, I don't know if I did right. Mine is also from the best ones between the bad ones and I don´t want to get one in worst conditions. I know a guy who send it to asus and got it back with the screen, front and gps changed, they did not even talk about the gps or gps problems at all, so we thought it was solved because they knew what to change. When he got it back at first it was perfect, he use to had a realy faulty unit, but the next day he came saying that it was failing again, much less than before but not perfect at all. He keeps talking with the people on asus and they told him to send it back, that may be an app... ???? I guess they don't have any idea on what the problem is.
[Nexus 7 (2013) General] sfhub:
Yeah, the app is called JSS15* OTA update.
[Nexus 7 (2013) General] bokoy:
There is a problem with that solution, I have the grounding issue, how could just a software problem do that? Mine works nearly perfect in my hands but if you put it over a sofa... Could be a software problem with some apps but not all.
[Nexus 7 (2013) General] danvee:
The 15x updates contained firmware (which effects the hardware) as well as software.

Sfhub's firmware patches have been 80-90% successful in minimizing or eliminating the touch problems for those who've tried them.

He knows what he's talking about.... :thumbup:
[Nexus 7 (2013) General] goofball2k:
So in essence, commit fraud?
[Nexus 7 (2013) General] danvee:
Apparently.

Sad that the sellers have to take it in the shorts because Google/ASUS are so clueless and unable to provide anything remotely resembling customer service.

They'll end up with a bunch of money tied up in defective stock that they'll have to sit on until they get credit.

Next time, how many Google/ASUS tablets do you think they'll be ordering?
[Nexus 7 (2013) General] bokoy:
Are you from the police? Is that fraud? So how would you call what asus/google are doing...
[Nexus 7 (2013) General] Bob Smith42:
I think people that buy a device and return defective units to the place of purchase are heroes. Especially if they return 3-5 or more. They beta test the devices, and take out the bad ones for the rest of us.

Is it fraud to buy model ABC and return model ABC to the same store? The stores have a ASUS wonderful warranty program where they can return the devices for a full year for repair and resell them to unsuspecting customers. For example, I noticed Best Buy selling a Google device recently at full price that had an extra small sticker - Bug Fix A. Isn't that fraud? LOL

Seriously, it should be fraud to sell a consumer faulty devices and expect thousands of customers to deal individually with the known problems.
[Nexus 7 (2013) General] bokoy:
Even if you buy one in one shop, then buy another in another, or the same shop, and return the first one as the second, that is what the user said. If that's the way to get a good one working... but be careful with bar codes, they will know you are not returning the same item.

There's no damage for any shop as Bob said, they just return the unit and gets new one. The biggest problem is for the user, Google is just lucky for not having more returns.
[Nexus 7 (2013) General] player911:
They are are all screwed up I think. Some more then others. It can be fixed with Sfhub's patches for the most part. Mine still gets strange when I play extended periods of Terraria but it is only for a second or two. I don't even think it is the device at this point but rather the game itself.

Best thing to do is go into Dev options and turn on show touchscreen inputs. Before it would skitz out and I could see like 5 touch inputs randomly on the screen. Now after Sfhubs fix, I don't see any, even when the game gets wonky.

This is why everyone knows it can be corrected via a proper patch from Google. Whether they adjust the sensitivity to touch or grounding or whatever. If Sfhub can do it, Google can. Plus it is a tiny download, his directions are precise, you don't have to be unlocked or rooted to do. There is absolutely no harm to just patch it yourself until Google makes with a fix.

Touchscreen Patch Fix:

http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) General] oldtimer42:
Correction - "Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies"

That is extracted from his post.
[Nexus 7 (2013) General] furou:
So no one's had a positive experience RMAing the nexus? Do the majority of units have the multitouch problem?

Sfhub's fix helped but I still get the "grounding issue" where the touchscreen goes insane if I place the nexus on certain materials. It sometimes exhibits the same problem when connected to the charger.

Other than that, the tablet works great when I hold it in my hand, no other issue to report... so I'm worried about RMAing my N7 and getting back one that not only has the same multitouch issue but now also randomly reboots or has dead pixels or dust or whatever. My warranty applies to north america only because I bought it off ebay and I don't live in the US so shipping it off to get replaced will get costly if I can't guarantee I get a working replacement back. Can I be sure that like, the newest batch of nexus 7 has been fixed and the replacement will be of that batch?
[Nexus 7 (2013) General] danvee:
Since they're not sure what the problem is (one Google groups poster states that ASUS has had his for a month with no ETA on a fix, or when he'll get it back) I'm not sure how they can fix anything , or be certain that what they've been shipping is 'good'.

https://productforums.google.com/forum/#!topic/nexus/mG4JXaT-SHs[1-25-false]

Come and join in the fun.... :/
[Nexus 7 (2013) General] furou:
Looks like loads of fun. Seems I should be grateful I was lucky enough that my touch-based tablet only has a malfunctioning touch screen.
[Nexus 7 (2013) General] Bob Smith42:
Dude, that forum is almost like spam. I reported my issues early, 3 weeks ago or more.

Since then I get from 10+ to 20+ reports (of multiple posts) per day of people reporting issues in email. People might be worrying about me when I get two or three reports in one meeting and I'm chuckling at the comments. LOL

Seriously, it is a good idea to report your issues at that location. But, think twice about subscribing to the topic.
[Nexus 7 (2013) General] sfhub:
If you don't report the issue it'll never get fixed.

The pressure builds up and they prioritize, in part, based on reports.

You might assume they already know about the problem, but they already put out a "fix", so in their mind it might be all taken care of already, so time to move on to more pressing issues.

Subscribe or don't subscribe, doesn't matter, but please report.
[Nexus 7 (2013) General] unremarked:
Just so you guys know, Best Buy usually looks at the serial numbers when you try to return devices. ;) Not always, but most of the time. On top of that, they track the number of returns you do through your drivers license and will eventually refuse to return/exchange.

This forum makes me chuckle. There's a whole lot of first world problems and lack of common sense going on. "Doctor, doctor, my arm hurts when I do THIS -- Well then don't do that." If your tablet has issues with stacking three/four/five fingers on top of eachother, then don't do that. What reason would you need to do this, anyway? I've only been able to replicate the "issue" under those circumstance. The most common multitouch commands(i.e. pinch to zoom) work perfectly fine for me.
[Nexus 7 (2013) General] bokoy:
I reported in that thread and in these other 2 that are just multitouch related, and not about freezes and reboots

https://productforums.google.com/forum/#!category-topic/nexus/nexus-7/zEqstgT2ZT8

https://productforums.google.com/forum/#!category-topic/nexus/nexus-7/W0Hfkq8hf-c[1026-1050-true]

Go and flood'em
[Nexus 7 (2013) General] KSTwitch:
I sent mine to ASUS for touchscreen issues too. Not responding to touches unless I was holding it in my hand or if it was plugged in the charger. Anyways I picked mine up from the FedEx store and went straight back to work and it worked great. I noticed they had taken the screen protector off. When I got home I promptly put a screen protector on it. This was an ASUS brand protector I got the day I bought it from Nebraska Furniture Mart. After about an hour or two the screen started not responding again. So I took the protector off. I have been using it without a screen protector for about 2 weeks now and have had zero problems. But now there is a small scratch on the glass!! I think I can handle the scratch a little more than the screen not responding to touches. Did they fix it? I am not sure. Maybe all they did was a factory reset or maybe replace the digitizer and glass. They didn't tell me what they did to repair it. I did send in my charger with the tablet as they recommended but I didn't get it back. I had to call them and they sent another one to me (a week later). That is my experience with ASUS RMA department.
[Nexus 7 (2013) General] rockingondrums:
My coworker RMA'd his flo and got a perfect one. I'm having issues with my deb. I'm going to try the patch and then RMA if necessary. Will report back.
[Nexus 7 (2013) General] WackyClash:
I hate that they don't tell you what they did... how stupid. It's literally like they make it as unpleasant as possible so that you won't ever do it again, that way they never have to hear from you again. I hope that's not actually how it is, but that's what it feels like.
[Nexus 7 (2013) General] Bob Smith42:
They don't want to admit using sfhub's touch fix on returned tablets. LOL

Seriously, RMA is painful if you have to wait weeks. One advantage of buying from local retail stores. Yet, WackyClash, I think you have a good point.

I wish there was a pinned RMA experiences thread on every device (or vendor like ASUS) in xda - in my opinion. Previous experience with ASUS RMA process shows there are differences at each RMA repair center. Some users have reported issues with RMA centers damaging devices. Some misleading customers on policy - like never return accessories with the device. But, how would you return an accessory with problems? There are surely tips and suggestions to help protect the consumer.

The only way to improve the RMA experience is to have a public forum for discussion, q & a, and reporting of RMA problems.

Also, reporting Nexus 7 (2013) issues on Google services forum helps, but we don't get any hardware update news from ASUS on Google's forum. If the RMA goes back to ASUS then Google forum complaints are not sufficient. Google's forum helps Google fix Android software - it remains unclear to me what process ASUS uses for hardware revisions.

This is a good discussion topic, hopefully we can get some feedback from/about ASUS too.
[Nexus 7 (2013) General] player911:
The bad part about subscribing is you get an email every time someone posts. Its great to be able to post bugs to Google directly but when they email spam the group, its hard to not unsubscribe.

Typically I have to setup a gmail folder and filter to bypass the inbox.

I will have to admit sfhubs patch really truly works miracles. Mine is in a Portenzo book case with an official Asus SP. Using TS20 I don't have hardly any issues at all. I'm partial to say its a 100% fix but I can't replicate any issues anymore (outside of that N7 screen touch tester that freaks the device out).

You have to unlock, which means wiping your device, but its super easy. Connect to PC. Boot into bootloader. "Fastboot OEM unlock". Then flash Sfhubs fix.

You can even relock afterwards by "fastbook OEM lock". You can be fully stock and locked after the patch. It sticks across roms and formats. So its a 1 time deal.
[Nexus 7 (2013) General] WackyClash:
With respect to how easy I'm sure that is, I just want my tablet to work as it should ootb. I shouldn't have to rig it to work (better), although it may be what I have to do. I just want my money back really.
[Nexus 7 (2013) General] WackyClash:
Sorry, I'm unfamiliar with flo and deb. What does that mean?
[Nexus 7 (2013) General] bananagranola:
Flo is the WiFi version. Deb is the LTE version.
[Nexus 7 (2013) General] WackyClash:
Ohhhh well it's certainly good to know his was fixed. Gives me a little hope.I also have that version.
[Nexus 7 (2013) General] rockingondrums:
N7 2013 : Flo = WiFi, deb = LTE
[Nexus 7 (2013) General] danvee:
Flo=N7 2013 WiFi

Deb=N7 2013 4G
[Nexus 7 (2013) General] rockingondrums:
I received my warranty replacement, it was not better. In fact, upon first boot it said erasing data, so it was probably another one returned for the same reason.
[Nexus 7 (2013) General] bokoy:
Already in other threat, but I will paste it here

Mine got back from asus one week ago, they replaced screen, front and gps. Nothing was fixed, multitouch is still going mad, single touch is a bit improve, as before it works nearly well grounded but over a table or a sofa it works worst.

One friend got it back for a second time, the first time they did the same they have done to mine, now they changed main bd-2g, rear camera, screen, front and gps, 24hrs later he is reporting me that problems are back. Do you know what main bd -2g is? Motherboard?
[Nexus 7 (2013) General] rockingondrums:
Main board to ground?? But that'd be kind of a weird way to write it...
[Nexus 7 (2013) General] threepwood960:
I sent my tablet twice. Both of them they told me that the multi-touch was changed, and the Gps module and rear camera (yes, rear camera).

Now multi-touch seems better (only a little), but it fails sometimes, for example using Swype, each 10-20 words.
[Nexus 7 (2013) General] SovereignKnight:
I was gunna buy one of these but now I'm not so sure. Looks like ASUS doesn't know how to build tablets. Google needs to drop ASUS like a bag of hammers because it's quite clear ASUS doesn't know what the hell they are doing!
[Nexus 7 (2013) General] hasenbein1966:
BS. You also have to see that this (like the old N7 and many other Asus devices) is a really budget device, and if you want low price, then not all can be perfect!

They could've built a tablet with Apple-like QC, but then either the specs would have been much lower, or the price much higher -> in both cases the "Whoah, such a strong tablet for THAT price" effect would not have happened, and no one would be interested in the device.
[Nexus 7 (2013) General] sfhub:
Budget android devices at Walmart don't have problems with touchscreen so I don't accept Google and Asus couldn't put out a tablet at this higher price point where the touchscreen works for most people.

This isn't some fringe or cutting edge feature. It is something very basic and critical for the usage of the device.
[Nexus 7 (2013) General] hasenbein1966:
With sfhub's touchscreen fix my device works very reliably...perhaps you should try that first and then balk at Asus...
[Nexus 7 (2013) General] Pfeffernuss:
Yeah, will advice anybody with a borked touch screen to use that fix. Asus has nothing to do with this issue. Bunch of silly complainers we all are.

</sarcasm>
[Nexus 7 (2013) General] WackyClash:
I don't care if it was $20 if the touchscreen doesn't work on your touchscreen device, it's worthless. I don't accept that since it costs less, it's allowed to be ****ty. I'm sorry, I just don't agree with that.
[Nexus 7 (2013) General] player911:
Its a software driver problem. It was introduced in one of the updates. There is a fix for it here on the forums. You have to unlock to flash it.

Asus can't fix it. You're wasting your time.

That or wait until Google fixes it.
[Nexus 7 (2013) General] player911:
It does work great out of the box as long as it doesn't have the updates on it.

The OTA updates is with flashes the bad touchscreen driver. If you get a new one with the old driver, it works flawless. Then either don't update or flash a custom rom that doesn't update the touchscreen driver.

Out of the Box, the N7 2013 is flawless.

Its just a bad update. Google will probably fix it in the next patch. KitKat is right around the corner too.

For today, there is a fix to get you by until Google releases a good driver.
[Nexus 7 (2013) General] sfhub:
Having packaged the workaround, I've seen more than my fair share of touchscreens helping people get their tablets into usable shape again, and IMO the story is more complicated than a bad driver.

There are hardware differences or variances in the screens and with each iteration of the touchscreen software they are trying to address some of the variances.

However they are having trouble creating one single touchscreen software to address all the variances. They fix one sample and that breaks some other sample.

It may be possible they come out with a single unified touchscreen software that addresses most of the units, but by no means is this a foregone conclusion.

Also it isn't true that all 2013 N7s have a flawless touchscreen out of the box. Many do work ok but some need the newer touchscreen software to make things work right.
[Nexus 7 (2013) General] player911:
I think the majority worked fine though. I'm sure Google can check for specific variances and apply corrected fix appropriately.

Thanks for clarifying the details, gracing the thread, and providing the fix.
[Nexus 7 (2013) General] cmhowsden:
Ditto. So I can, dare I say, go buy an iPad Mini Retina.