yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] RogerPodacter:
I still get the touch sensitivity bug on 4.1, it actually seems far worse than 4.0 for me. It happens constantly and I have to lock the screen. Grrrr
[Samsung Galaxy Nexus] matteventu:
Me too :(

I hope that with "rtm" 4.1.1 the bug is gone...

or it is also an hardware-related bug that happens only on old-producted Galaxy Nexus?
[Samsung Galaxy Nexus] jonstrong:
I still wonder what's really causing this. I've been using my VzW GNex since December, and increasingly use it for a lot of my online activities every day....some days see quite a bit of interactive use. The ONLY times I ever found the screen less than very responsive were when I had some poorly implemented apps running...maybe competing for resources or spinning out of control.

Wish I had kept better notes...but some of the oddities I've seen included:

Somehow wound up with Accuweather spawning multiple processes

Early version of United Airlines app seemed to be a hog. (Better now)

Some streaming news apps seemed to misbehave...

I've been aware lately of what I install, and despite having about 99 apps installed and using the phone a lot...it never lags or hesitates, and the screen is always responsive...(IMM76K).

What are the chances that some of what's reported here is a byproduct of installed apps and / or mods?
[Samsung Galaxy Nexus] RogerPodacter:
Just for clarity, this bug is in no way lag or chop or hesitation. Its smooth as butter the entire time. Its just the sensitivity being reduced so only medium presses are registered. For me it is system wide and happens on all apps including Google apps gmail, browser, maps, etc. Its definitely gotta be a kernel bug is my hunch.
[Samsung Galaxy Nexus] chlehqls:
Yep, same here. I used my phone for pretty lengthy times and the sensitivity gets significantly reduced to the point where it seems to have a delay in which I touch the screen to go from one homescreen to the other. Same thing happens in apps where I have to scroll down a list. It doesn't seem to want to follow my finger movements precisely after a while.

I figured it was a kernel or some bug they overlooked. At first I thought it was because my fingers were getting greasy but after a quick wipe down of my finger tips, the issue remained.
[Samsung Galaxy Nexus] robstamack:
This may sound crazy:

Take off the back battery cover and push down on the area right beside the power button. Give it a good press and see if your problems go away.

I had a problem where the digitizer would stop responding, or would seemingly "queue up" swipes and presses. I think there is a bad connection internally and pushing on that spot pushes a connector back into another board. Of course, that's pure speculation on my part, but it fixed the problem 100%.

Picture attached if you're not sure what I'm talking about.
[Samsung Galaxy Nexus] BrUhNiGGs:
Just tried that and the touch sensitivity issue is still there. Lol it was worth a try I guess...Maybe I didnt push it hard enough? Eh, whatever. Im getting a replacement Gnex on tuesday. This issue has went over board for me.
[Samsung Galaxy Nexus] akira02rex:
I've specifically noticed this oddity when using the keyboard sometimes. It seems I have to press harder? on the keys -or- it doesn't register my touches on the keys which then I have to re-type a word. It is indeed annoying at times but doesn't happen often so I live with it.
[Samsung Galaxy Nexus] petrsiri:
Crazy, might be a placebo... but I think it worked for me 2! I ll revert after I test it further!
[Samsung Galaxy Nexus] dark06:
Im still having this issue.anyone fixed it already?

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] BrUhNiGGs:
I don't think there is a fix. I think its just a hardware problem. I may be wrong but I decided to get a replacement will see how it goes tommorow
[Samsung Galaxy Nexus] dark06:
Let us know if its till there.im a bit hesitant to replace mine because its the only problem i have.the replacement might have charging/screen issues that alot are having

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] BrUhNiGGs:
Yeah, I was a bit hesitant too. I didn't want to give up my brand new gnex for a refurb. But even if the first replacement doesn't go well (other issues besides the screen sensitivity) you can just call back Verizon and they will send you another one. It will keep going until you find the perfect replacement so I don't think there is much to lose ;)
[Samsung Galaxy Nexus] webmaster:
1) I started experiencing this issue as soon as I upgraded to 4.0.4, and it has remained even though I am running 4.1.1. Mine isnt quite as bad as the others, but I really hope they fix this!

2) As for returning multiple units, DONT DO IT! I had to go through roughly 6 Sensations before getting my GNEX, and each unit was more defective than the last. I basically stopped caring about the issue so that I could root my phone and get on with life. The biggest issue is that they will ONLY send you refurb units, and the reason they have those on hand is because they were defective for someone else. If you think they actually fix those before sending them out then you are in for an unpleasant surprise....
[Samsung Galaxy Nexus] dark06:
Its definitely a sofware bug.my gnex started with 4.0.2 and had the mt bug so i quickly rooted and flashed latest aokp.didnt know that i had this sensitivity issues till i came across this thread.there is a saying what you dont know wont hurt.:p. I doubt google will fix this since they themselves haven't addressed this issue yet. And btw did you try using stock 4.1.1 kernel?is it still there?

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] akarach:
Does pointer speed setting help this issue?

System settings ---> Language & input ---> Mouse/Trackpad ---> Pointer speed

I'm just test it first day, didn't found problem. Maybe have to test long time.

I don't know Pointer speed for what? Could someone explain,please?
[Samsung Galaxy Nexus] BrUhNiGGs:
Well...I just got my replacement gnex, rooted it, flashed Jelly Belly 3.6 with franco kernel r212 and still experience the screen sensitivity issue. I guess it was a software bug after all! I just wish more people actually knew about this issue so Google and make a fix for it but it just looks like only a handful of us only notice it. Thats it, I am going to try every kernel I can to see if the issue is there.
[Samsung Galaxy Nexus] dark06:
Did your phone started with 4.0.4 already out of the box?

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] BrUhNiGGs:
Nope, it started with 4.0.2, updated to 4.0.4, rooted, flashed 4.1.1 and issue is there.
[Samsung Galaxy Nexus] kennethpro22000:
I think we should report the issue to Google and seek for the solution. I have just make a comment to the link below.

code.google.com/p/android/issues/detail?can=2&start=0&num=100&q=touch%20screen%20sensitivity&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars&groupby=&sort=&id=29734
[Samsung Galaxy Nexus] dark06:
Im gonna comment there too. Btw if anyone would confirm trinity a32 fixed it?it hasn't showed up for the last 4 hours im using my phone now without locking it

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] EP2008:
Here's something interesting.

When I'm not holding my GN and try to use the screen, it simply doesn't work. I need to hold it to get the screen to respond to my touch.

I have a case on my device, so maybe that compounds the problem.

Has anyone else observed the same?
[Samsung Galaxy Nexus] dark06:
Only when charging.its grounded

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] dark06:
A little update. Latest trinity is performing well haven't seen it occur while browsing and such BUT when i use voxer it would literally occur in just seconds after lock and unclock it would occur seconds after.this would be a proper way of narrowing the problem.maybe its because of latency or i dont know lol

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] kennethpro22000:
Dark06,I have tried latest Trinity kernel.my nexus works not well as yours, the issue appear very quickly after I use the phone, so I change back to Franco 221
[Samsung Galaxy Nexus] dark06:
Damn! Im using a32 1344-384 if thats helps.

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] kennethpro22000:
Dark06,I think gpu frequency affects the performance.I have tried the 512 mhz one,it doesn't works, I may try the 384 today!
[Samsung Galaxy Nexus] phazerorg:
I've had my phone since December and I experienced this issue for the first time yesterday. I was out for a bike ride and stopped in a park to answer a text. I thought it was just my sweaty hands causing my touches to not always register on the keyboard but then it happened again today in my cool air conditioned office. The phone itself was operating smoothly but it took multiple (and harder) touches to get it to register presses on the soft keyboard. It was very frustrating to type anything coherent.

So far it's only happened these two times in the entire time I've owned the phone, but it's definitely the exact issue being described here. I'm running stock takju 4.1.1. Never had the issue with the 4.1 leak or 4.0.x.
[Samsung Galaxy Nexus] delf0s:
I purchased my GN and it came with yakjuxy (or whatever) with 4.0.2, no issue. Ever since I updated to 4.0.4 ICS and to 4.1, I've had that same touch problem. Its kind of annoying, but seems to go away when you lock the phone....then unlock it. Could just be a placebo effect.
[Samsung Galaxy Nexus] kennethpro22000:
I have tried the Trinity 384mhz for android 4.1,and the situation is not good, the issue is still there.
[Samsung Galaxy Nexus] adrynalyne:
I am glad I have never seen this issue.
[Samsung Galaxy Nexus] dark06:
My gf didn't even notice the issue, i lend it to her for a week. Depends on how you use it to know where the problem is

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] BrUhNiGGs:
This proves its not a software problem. A user over at Rootzwiki who is a VZW tech agent advised to keep getting replacements as its not a software problem since it doesn't/never happened to him, himself. I'm on my first replacement Gnex and was skeptical about it at first but all is good except for this sensitivity issue. What were the odds of getting another gnex with this specific issue? Not all gnex's get this issue or people dont notice it. Wonder when we will find the real answer...its sooooo easy to notice for me!!

I shall go for replacement #2 and see :P
[Samsung Galaxy Nexus] dark06:
If its not anymore on your 2nd replacement then i will replace mine.be sure to update!:)

Galaxy Nexus w/ 4.1.1 and trinity
[Samsung Galaxy Nexus] Guicrith:
Bought it for emulation using it for a paperweight.

Doing emulation with this bug sucks and to test for it very slowly drag your finger in from the edge of the screen then push harder and move around the screen and bottom nav bar if the point lets go and reconnects a few times you have the bug.
[Samsung Galaxy Nexus] BrUhNiGGs:
Hope I get my second replacement sometime this week. I am just as committed to find out if this is in fact a software or hardware defect. Won't leave this thread hangin' until we come to the conclusion! Will keep updated
[Samsung Galaxy Nexus] petrsiri:
Using which app (I am referring to the test described 2 posts ago)?
[Samsung Galaxy Nexus] Guicrith:
I never said you need an app just on the home screen will do.
[Samsung Galaxy Nexus] chjade84:
I had this problem as of yesterday morning. Phone was fine since release. Upgraded to JB and was fine, upgraded again and was fine until about the next day. Restoring to a backup does not help.

Mine does this ALL of the time though. Screen lock/unlock does nothing. Seems to only be the bottom 1/3 of the screen as a multitouch test app responds well on the top 2/3 but miserably on the bottom 1/3.

Not sure where to go from here...
[Samsung Galaxy Nexus] slickrickstyles:
Mine does this all the time as well I have to restart the phone because of it
[Samsung Galaxy Nexus] delf0s:
I'm thinking its software related. When I turn my screen off...then back on...the sensitivity goes back to normal. Very weird...
[Samsung Galaxy Nexus] chjade84:
Restart doesn't help me either...

---------- Post added at 08:42 AM ---------- Previous post was at 08:11 AM ----------

So I just restored all the way back to my ICS rom and the issue seems to have gone away. It still misses 1/25 keypresses or so but that's a lot better than missing 15/25 like the JB roms did...

But it's weird because JB worked fine for a couple weeks then all of a sudden it stopped, even restoring back to a time when it was working (factory reset/wipe) did nothing to help.
[Samsung Galaxy Nexus] aeoveu:
I, too, think it's software-related since I didn't face this issue with ICS.

For me, 95% of the time, it gets triggered with the app switcher menu (task list). Tap a few other apps, and it begins to jerk.

Strangely, someone else in the office has a GN too and NOTHING like that happens o his phone (he's using the deodexed, v1 of the initial leak - hasn't upgraded to the full OTA).

To be sure, I factory-installed yakju AND takju (at different times) and used the OTA method to upgrade. Same issue. No apps were installed. Even my Google account wasn't configured - PURE stock!

So for me, it's a software issue.
[Samsung Galaxy Nexus] chjade84:
Right.

What would cause it to persist through a wipe and restore though? I did my first upgrade to JB on the 17th and it worked just fine. Then on the 23rd I updated the rom to the next version; so I have a nandroid for ICS from the 17th, JB #1 from the 23rd, and JB #2 from the 26th.

I first wiped and restored to JB #2 because that was just a couple days before the problem started - still there.

I then wiped and restored to JB #1 and the problem was still there even though this nandroid was made 5 days before the problem started.

So, then I wiped and restored to ICS from the 17th and it seems to be fine.

So what could go wrong that would make a functioning nandroid backup stop working correctly after wiping and restoring to it?

---------- Post added at 09:54 AM ---------- Previous post was at 09:13 AM ----------

Ok, so I've just installed Vicious CM10 JB v4 and so far it is working beautifully.

IDK WTF is going on...
[Samsung Galaxy Nexus] Guicrith:
The contents on the sd card maybe dalvik cache.
[Samsung Galaxy Nexus] chjade84:
I wouldn't think anything stored in there would cause touch screen issues, but maybe the dalvik - though that wasn't wiped between the JB -> ICS restore that fixed the problem.

I don't know, I'm not a dev - just trying to help pinpoint where the problem code lies.
[Samsung Galaxy Nexus] RogerPodacter:
I just think you didn't notice it before, or didn't use the phone in such a way as to trigger the bug. But I started this thread on 4.0.4 so it definitely existed then for me. A nand backup can't carry over any bugs, it literally puts every single file back to the state of the backup. So the bug must have been there then.
[Samsung Galaxy Nexus] chjade84:
Well I definitely didn't not notice because the phone is on the verge of unusable when it happens and screen lock/reboot does nothing to help. It was so bad and only confined to the lower 1/3 that I had assumed it was a hardware malfunction.

I know of the multitouch bug in 4.0.x but I hadn't heard of this issue exactly. Since nandroid puts everything back exactly as it was, why would it be working fine when I made the backup but not be fine after restoring said backup? It seems like it would have to be a problem in an area that nand wouldn't touch.... but I thought that was nowhere...
[Samsung Galaxy Nexus] RogerPodacter:
That's strange it almost seems like a different issue. I don't think my bug was only on the bottom third of the screen but the entire screen, which gets fixed by locking the screen. Maybe you do actually have a hardware issue?
[Samsung Galaxy Nexus] chjade84:
But it got fixed with a 4.1.1 flash! :victory::confused:

Maybe I'll go start my own thread about this issue with 4.1.1 and partial responsiveness, specifically. This was the only good thread about it I could find that was close though.
[Samsung Galaxy Nexus] aeoveu:
There may be truth to that statement. When I did a logcat, it gave me a few dalvik errors here and there (my log was awfully messy so it took me ages to figure out... I may have it wrong, but dalvik DID report some errors.

And Google Now was also active - there were some velvet.apk strings in the log. I don't think that's got anything to do with this, but... its a dalvik issue.

I could paste the whole dalvik again - I just don't know how to trim it so that only the relevant portion remains visible.

sent from my mini tractor
[Samsung Galaxy Nexus] BrUhNiGGs:
I have had this issue with every version of android 4.0.2, 4.0.3, 4.0.4, 4.1, 4.1.1

with my first Gnex. I am now im on my replacement Gnex and get the same exact issue. I am still debating whether it is a software or hardware issue. A VZW tech told me to get another replacement as it has never happened to his phone. If my second replacement gets the same issue then it just has to be a software issue. But the thing is, it happened from the start of Gnex...
[Samsung Galaxy Nexus] claud_face:
Had this issue. Completely left after full wipe and installing version 4 aokp jellybean.

Feels great again!!
[Samsung Galaxy Nexus] BrUhNiGGs:
Same way that happened to me when I flashed Faux kernel. It was gone for a while. Then it slowly haunts you back.
[Samsung Galaxy Nexus] shrijith1:
Have had this issue ever since I got my GN. I think everybody has this issue and it should not be a hardware issue, but something to do with memory leak or stuffs like that. The thing is it doesnt happen all the time, or maybe I dont notice it all the time. People who dont face this issue, perhaps dont notice it or the screen gets locked/unlocked frequently.

Like somebody mentioned, I am also able to reproduce this issue after installing System Tuner and clicking on events and scrolling around. How to make this heard by Google ?
[Xoom Q&A, Help & Troubleshooting] Yuccaman:
[Q] Cordy & DungeonDefenders - Full Versions or the same as those on the Play Store ?

Ok,

Finally got round to starting to tidy up my Xoom, using Titanium to remove some system apps I don't use / want....

For Cordy and Dungeon Defenders, is there anything special about them, i.e are they the full versions or the same versions as you can get from the Play Store ?

Tried Cordy and it wasn't really my cup of tea, but might keep it if it's a full version (I suspect not mind you).

Cheers,

Rob
[Xoom Q&A, Help & Troubleshooting] akhu:
I have played cordy on the original os, honeycomb. I beat the game and sometime between then and the ics update, there are new levels that are "pay to play." Since the game came free when I bought my Xoom, I had hoped that any updates or new content would be free as well. Now I wish I could uninstall the game, but it seems to be integrated, like dungeon defenders.
[Xoom Q&A, Help & Troubleshooting] Yuccaman:
Well, I can uninstall System apps via Titanium Backup. I think there are other apps out there that can do the same, but I've been using Titanium for far too long now to look for anything else :)
[Asus  Eee Pad Transformer Prime] Mekrel:
Hi all,

When installing content from the Play Store and then switching to another application such as the browser, the system completely pauses when the notification centre at the bottom of the screen changes to "Installing x application...." i.e. when the application is being written to the data partition.

Now, this issue existed on my HTC Desire but didn't exist on my Galaxy Nexus or Galaxy SII both of which use EXT4 as their file systems. Running the mount command on the Transformer Prime, I can see it's also using EXT4.

What gives with the pause when an application is being written to storage? Can anyone confirm they experience the same? Do custom roms fix this issue?

For reference, I installed Temple Run to double check this issue existed before posting, so try that application to install if you wish to check for yourselves.
[Asus  Eee Pad Transformer Prime] reNeglect:
Supposedly either Asus cheaped out on our storage chips or the drivers really suck. There was a thread about how the sd card performs pretty bad when compared to other android devices.
[Asus  Eee Pad Transformer Prime] leppie:
This is normal. Multi-core process scheduling is clearly not a strong point of the Android OS.
[Asus  Eee Pad Transformer Prime] Mekrel:
That's the thing, it can't be normal as my Galaxy Nexus does not suffer from the same bug, even when it was on Android 4.0.2. The Galaxy SII also didn't when on Android 2.3.x.

At a guess, it's down to one or a mixture of things (again, I stress this is a guess):

Poor choice in mount flags

Tegra3 - I know it doesn't have the best CPU out there

Poor quality memory/storage
[Asus  Eee Pad Transformer Prime] demandarin:
its because priotrity is given to downloads from the market. you can install an app in developement section called ATP tweaks. then change the default noop(which overall is the best) to like a deadline I/O scheduler. this should relieve the slowdown you seeing while donwloads from market happening. there are also other schedulers you can choose from of you want to experiment. but the stock one is the best regardless of market slowdown. those downloads just getting priority over everything else so it'll download and install faster.

---------- Post added at 12:40 PM ---------- Previous post was at 12:37 PM ----------

Actually Tegra3 does have the best/most powerful CPU in the tablet market today. nothing out now, in tablets, beats it quad core 4+1 CPU. then add in the fact we can already overclock to 1.6, 1.7 & 1.8Ghz already and nothing is touching the tegra3 in Prime right now. Tegra3 CPU smokes new Ipad CPU. Tegra3 has a good gpu also but new Ipad GPU is more powerful, due to it new high Res. display needing most of the power.
[Asus  Eee Pad Transformer Prime] Mekrel:
Well I don't buy the scheduler point because that just wouldn't make sense. Installing from the market doesn't require such importance/attention, I would much rather browse the web whilst applications update in the background. In fact, the video's of this issue posted by me here, show the Galaxy Nexus installing Temple Run quicker in my opinion.

The Prime is supposed to be better than the Galaxy Nexus on all fronts in terms of performance but so far, web browsing and multi tasking is better on my Nexus (which is completely stock). The web browsing experience on this tablet is absolutely shocking, it's pretty much a case of waiting for pages to respond or waiting for the "Browser is not responding" message.

I've done the paperclip reset, linux cold boot mode and factory reset. I'm sad to say that I'm regretting this £500 purchase. I'm not moaning for no reason, I would rather love this tablet and fix these issues as there's nothing else on the market Android tablet wise worth getting. However, I can't live with this unacceptable performance.
[HD2 Android NAND Development] smokin901:
I am starting this thead for miui v4 translation. Aim is to make translation files available for all possible languages. This is too much of work for single person, hence calling others to help with translation.

*******UPDATE*********

Looks like we do not need to de-compile apps for strings all the resource are available here

https://github.com/MiCode/patchrom_miui/tree/ics/src/packages/apps

I am attaching simple batch script to de-compile all the apk.

before running this make sure you have

JDK 1.6.x and above

ApkManager Download from here View attachment 977437

enough free space

Already translated rom in your language(If you are lucky) else you will have to do it from scratch

How to De-Compile

Extract attached Apkmanager zip file to a folder

Download miui rom and extract it to a folder

copy framework-res.apk and framework-miui-res.apk from system/framework to place-apk-here-for-modding in apkmanager folder

Install framework with following command

apktool if framework-res.apk

apktool if framework-miui-res.apk​

Extract and copy all the apks from system/app in folder place-apk-here-for-modding

Run decompile.bat