Develop Bugs

Car Home acting like a VIRUS! Need Help!

Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!

I have the same thing. silly thing keeps poping up. trying somethings if i get it to stop ill let you know. let me know if you get it to stop

Go into a roms zip file, find carhome apk, delete it and wipe and flash. I'm not sure if this will work since I don't know if you have to change the code too
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo.

Or use Root Explorer and go to /system/app and delete it there. I never used it anyway.

I had that same problem on that rom
I found 2 carhome apk's in my system apps. I deleted both but then had fc's.
So I'm curious off you find a solution
Swyped from a galaxy far far away......

thanks i tried that did not work. just done got a older nan backup and put it ok it seems ok for now.
thanks m8

car home is a virus
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)

robenever said:
i tried. i lookd into the roms, cm7 rc1 n rc2 n none of them have it. i figured if i delete the car home apk off gapps.hdpi.zip file it would work.. since thats the only other place its located in. nothing. it still pops up. i being dealing with thins for the last week. i did everythin. clean factory wipe, went from cm7 to cm6 in all the versions available. n nothing. car home still pops up.
other known issues that i think might be connected;
calls are answered with speaker on.
when usb is connected, the notification does not give you the option to mount sd (only in cm7 rc1 n rc2)
Click to expand...
Click to collapse
gapps.hdpi.zip? WTF? Quit running your own GApps. Wipe everything, get RC2, flash 20110307 GApps and go from there. Solves all problems.

Not sure if this will help you much but I had this same problem once and ended up unrooting my phone and even then it did it so I went into a sprint store and they replaced it free of charge.

crakerjaks said:
Even after uninstalling it with titanium backup,root explorer and native android in menu it keeps popping up in notification bar with these ill-effects:
It closes out any apps or programs I was using!
It automatically puts me on speaker when I make or receive calls
Screen orientation cannot be disabled
Screen lock cannot be disabled
Volume is lowered when playing music
stays at the same volume and cannot be adjusted.
Some suggestions were to disable automatic startup and bluetooth in Car Home's menus when it pops up, I did not see such option. Now the menu does not pop up anymore, only the steering wheel icon pops up in notification bar to let me know its here to make my day a living hell again. Everyday, Every Hour, Every minute. I've done full wipe,cache,dalvik, and reinstall of cm6 6.1.2 and it just wont GO AWAY! Please HELP!
Click to expand...
Click to collapse
i flashed to Sense then updated PRL, then Profile. Then i flashed back to CM6 its bn working eversince

i rather make my own gapps n take my chances than just sit here n do nothing. however, i am working unrooting my phone and rerooting it again. if that doesnt work.. then its back to the sprint store

I did a full wipe and reflashed CM7 RC2 along with the gapps that came with it, and so far no problems *knocks on wood*.

I had this problem and found that the culprit was pocket lint lodged in the phone's usb port--grounding out one or more pins.
I read a post about a guy who made his own car dock cable by grounding pin4, auto-triggering car home, like the real evo car dock, whenever he connected his cable.
I got thinking and grabbed out my jewlers loupe and saw some crud at the base of the usb jack. With the battery removed I got a slender sewing needle and bent the tip slightly with a plires to make an "r" shaped hook.
I gently scraped around the bottom and edges of the usb jack on the phone with the needle and pulled out a years worth of greazy lint crud that literally wedged against the pins, no doubt grounding out one or more of them, thus kicking up the car dock shenanigans. Seriously, a lot of lint.
Once the dock issue showed up, prior to cleaning the jack, the car home app showed up EVery time i plugged in usb.
I havent seen car home nonsense at all since cleaning out the jack.
prior to cleaning i called sprint having read about others doing the same. Without much hassle they sent me a warranty refurb (with 2.3.3 installed) to replace mine,
With a clean jack, i can send them back the refurb and keep mine as is.
hope this helps

So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect

slackard said:
So cleaning the USB jack solved the Car Dock app nonsense, that app is no longer popping up. However at present the phone is still defaulting to Speaker Phone ON for outgoing and incoming calls.. Will try reflashing etc later on to see if it has an effect
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1107759
A story of how I fixed this problem over a month ago. Refer to post 5.

It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App

tnerb123 said:
It's actually a hardware issue. There is a circuit on the EVO board that is fried. Of course sprint won't acknowledge this but have seen it happen on other phones.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My circuit board fried, then fixed itself?
I would be interested in where you got this information from.

Sprint does acknowledge this. I have the same issue and thought i solved it by cleaning the USB jack--not so.
I was just in the sprint store the other day with my faulty phone and after some digging the tech found a bug report titiled something like "speaker phone always on" in their bug database. Recommendations in that bug report were to clean usb leads and if that doesnt solve, replace the phone.
Sprint offered to replace mine without too much hassle and shipped a refurb overnight, but the new phone came with gingnerbread and is therefore unrootable (at the time of this post), so i started looking for another solution--to disalbe the dock features entirely.
I came across the app NoDock, which loads a kernel module that interupts communication between the dock sensor and the OS, preventing the dock & speakerphone shenanigans.
I dug around in adb shell a bit and found the kernel module being loaded by the NoDock app.
Its located in /data/data/com.nothize.free.nodock/files/ and titled "nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko"
I was able to load this module by hand as SU in adb shell with the following:
#su
#insmod /data/data/com.nothize.free.nodock/files/nodockm_2_6_37_4_cyanogenmod_01388_g0374804.ko
I will work on moving this module out of the NoDock app directory and see if i can get it to load on-boot without needing the timelimited APK. No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
I already sent the gingerbread phone back to sprint and will stick with this solution for the time being.
Hope this helps anyone with similar problems.

Well you're not offending me, you're just thinking in a different way than I'm and (if) you haven't leave any destructive comments about it.
What the app worth is really the kernel module.......the app interface however, provides settings that may serve other use cases.
I wrote the kernel module myself, but not ripped off from anything else, so you cannot say that you are not willing to pay for just the "app" that loads the kernel module. In fact, you're paying the novel ideas and the novel kernel module too that took most of the time for the research to make it works for various phones including S2. You can read more if you have visited my website. So if you got the knowledge and skills, as I've already documented how I am doing this, you should be able to write your own kernel module.
The free trial app was a free app a long time ago......until I felt offending by some "free version users". They emailed me for support, they left silly comments, complains and complains out of a reason. I lost my hope to them while the paid users have so much better quality.
And you're lucky to extract the old free trial version....IIRC, the expire has been introduced to the kernel module too since some version.
slackard said:
No offense to the app's author, just not interested in a pay to play 'app' that loads simply loads a kernel module that can be loaded with a simple script etc or by hand.
Click to expand...
Click to collapse

I had the same issue. Turned out that my issue wasn't a piece of pocket lint in the USB jack (which DOES cause the same issue)....instead it was a bent pin in my charger. I bought a new charger for $3 on Ebay and I have never had the issue since then. Common sense tells you that if you've gone through all avenues of software issues and the problem is still recurring then you need to start looking at physical aspects of the phone. In this case, the device that triggers car home automatically......aka the USB port and anything connected to it.

[Q] No DInc2 Earpiece Audio - Speakerphone works fine

I finally decided to root/s-off/ROM last week, and after following the many excellent guides around I got to a place where I liked the features and speed of the ROM I settled on (Incredible 2 HD 4.something).
Here's a breakdown of what I passed through to downgrade/s-off/root/recovery/ROM:
Friday
Downgraded from 2.3.4/Hboot0.98. Successful.
Installed CWR, su, busybox. All well.
Boot once into stock VZW GB 2.3.3.
Grab full nandroid backup of "stock" 2.3.3 as a failsafe.
Back to CWR 5.0.2.0. Installed CM7 / gapps. All still well. I wanted Sense back, so hunted for a good candidate ROM.
Settled on Incredible 2 HD from themikmik.com
Initial flash acted like I wasn't rooted (CWR .zip install said (bad) when I selected the ZIP. md5sum is perfect, so it's not a bad copy. Battery pull later and a few full wipes, install is fine.
Saturday
Inc2HD ROM is really sluggish so I decide to nuke it from orbit and start over again.
I grab the Super Wipe script and run.
Reinstall DInc2HD ROM.
Rom is very responsive, acting much better.
Start reinstalling all my apps again.
Deal with the stupid problem of sms messages from VZW (http://www.droid-life.com/2011/06/2...age-from-vzwnmn-here-is-how-to-stop-them/]fix detailed here[/URL]).
Receive and place several calls as normal throughout the day.
Gradually reinstall apps only as I need them. Keeps down the clutter
Sunday
Receive and place several calls as normal throughout the day.
Gradually reinstall more apps only as I need them.
Getting to a good state with apps re-authed and reinstalled. Decide to grab another nandroid checkpoint backup.
Backup is fine, resume normal daily use.
Monday (today)
[*]Alarm goes off as intended (yay - I have 'Clock' back after being missing on my phone since 2.3.3!)
[*]Listen to some spotify paired to my car on the drive into work
[*]Colleague calls me .. and I can't hear him. I figure it's a bad connection so I call him back. Still can't hear him through the earpiece. As a quick test I switch to speakerphone, I can now hear him.
I figured this was a one-time thing, but start test calls to DInc2 from my desk.
Damn - earpiece isn't passing any audio. Speakerphone toggle gets me audio, as does plugging in my 3.5mm earphones.
I then test other apps I know I can toggle to playback through earpiece, and no dice (Google Voice, etc). All I can hear is a very very faint buzz while a call or playback should be coming from the earpiece. When I hang up, the faint buzz in the earpiece goes dead again.
Made sure bluetooth radio was off to rule out pairing to other devices (though I haven't re-paired since wiping anyway). No wifi radio on either. All alone with the mobile network radio.
Now I know I've done a lot to the phone over the weekend, but I can't find any common cause of what might have happened between the last good call I placed on Sunday evening and today (Monday). Phone sat all night charging on my nightstand. No physical damage or anything like that.
Thinking this may be a ROM or app issue, I bounce back to my known-good snapshot of the 2.3.3 stock ROM. Problem persists - crap.
To further rule out, I full wipe and install CM7.1.0.1 from scratch just to get another baseline. Still no earpiece audio - getting frustrated!
Whatever it is, it isn't exhibiting signs of being a ROM or app issue because it persists full wipes (wipe/cache clear/dalvik wipe, and another pass even with the super-wipe script).
Yes, I've checked basics like making sure In-Call Volume is not muted. I've also installed Audio Manager to make sure there's not some lurking audio volume problem. All sliders maxed before, during and after test calls.
Uninstalled any audio-related app to attempt to remove any hold on audio output. But recall here - it's following across ROMs and wipes, so this is just busy work.
Logic says then that either
I hit some rare bug?
The process of mucking around with recoveries, ROMs, and other lower-level items has flipped a bit somewhere that will persist full user-space wipes/partitions/formats.
it's faulty hardware (which I have a hard time believing, but stranger things have happened!) This would just have to be horrible timing.
Searches on here and other sites don't bring up too much for the Incredible 2 and this kind of earpiece issue. There's a passing mention of a "silent audio bug" here, but doesn't seem relevant (nor much detail given).
I've grabbed output 'c:\> adb logcat -v time -b radio > alogcat.radio.txt' while making a call and switching between earpiece (default) and speakerphone. No really good clues there. Changes in logging verbosity didn't show too much of interest. I'll pastebin it after I scrub my phone number out if anyone's interested.
So after the wall of text ... anyone have any ideas?
I'm in it to win it with this, so I'm not unrooting and warrantying this pig I'm due for a new phone but there's nothing I want other than to just have my DInc2 back working.
I'm off to keep searching. Wondering if there are other debug-level tools/switches via adb that'd let me poke at devices, but I'm guessing those interfaces may not be as readily exposed as I'd like.
Thanks in advance all.
tl;dr - Incredible 2 earpiece randomly stopped working, but speakerphone and headphones still output phone call audio fine. Follows across wipes/ROM installs. LOLWTFBBQ?

I hate to say it, but your earpiece is probably broken... U may have smashed it with your keys in your pocket (did that on og dinc)...
Sent from my Incredible 2 using xda premium

If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Sent from my Incredible 2 using xda premium

faehsemc said:
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Click to expand...
Click to collapse
Fair enough. I hadn't ruled out full-on hardware failure I just found it to be the least-likely of the candidates.
I had to replace the speaker in my original Incredible, so I figure it can't be too much tougher to do in this one. I'm going to exhaust some other troubleshooting first (my wife has a functional stock DInc2 that I want to compare some logcat output from, see if anything stands out when making a standard voice call).
I'm always careful to change ONE thing at a time then test to make sure my variables are where I expect them to be, so this one threw me. I'll post back with results, and hopefully get my earpiece back .

OK, I ordered a replacement earpiece and replaced it. This did not fix the audio. I tested both the original earpiece and the new earpiece before installation by using a low speaker-level source and confirmed that BOTH actually work fine and produce sound as expected.
While the phone was disassembled, I made sure all contact points were good for the earpiece. This isn't a physical problem.
So, this takes me back into the software/firmware/radio arena.
And more specifically, in order to persist all wipes and reinstalls, this has to be something below.
I'm going to use adb to flash a radio (I think there's one newer than the one I have installed, something.622? Not down at bootloader to check right now).
If this doesn't do it, anyone want to buy a DInc2 for parts and dev?

The newest radio is .1111 before that .722
Sent from my Incredible 2 using xda premium

Good call on the 1.09.01.1111 firmware. I found and flashed that instead of .722.
No effect unfortunately.
So next I'm thinking that perhaps whatever kernel I brought with me from the first ROM flash could have jacked something up in terms of audio modules or packages. It's a long shot, but I'm going to grab something like nc2_2.6.35.14#21-2.3.4.zip (non-AOSP) and flash that.
Now that I have ruled out actual hardware failure, I'm just too stubborn to give up on this .. open to productive ideas on things to check, methods to troubleshoot or rule out, etc. TIA.

What about Tue hardware connection from the speaker to phone itself? I don't know much of the board on the phone so I can't give you ideas of where to test, but if you can see where the leads go I would say follow it
Sent from my Incredible 2 using xda premium

Right. I disassembled the phone again late last night and traced back to the extent I could follow. I didn't find anything glaringly obvious or bad.
Also of note, if I'm in a super-quiet room and keep the earpiece near me with no call in progress, I hear literally nothing. As soon as a call is initiated, I hear a very faint "sputtering" sound from the earpiece (original or new earpiece), which means the symptom here clearly impacts either speaker.
So something upstream from it ... whatever pathway sends audio to this device isn't getting instantiated properly? That'd make me look to the kernel or driver to understand what pathway does work when routing audio output to the rear speaker that doesn't properly route it to the earpiece for the same call.
Recapping for my own sanity:
- Physical causes == none seen, mostly ruled out via disassembly and inspection, earpiece replacement with known-good part and known-good reassembly.
- Radio == upgrade to .722, .1111 and back to .622, no change.
- ROM == not likely culprit (problem persists any ROM replacement)
Can't fight off the nagging feeling that the act of starting down the road to S-Off + su + rooting did something here.
Given that there are guides to un-rooting (don't think you can un-S-off per se though, right) I may give that a shot since this phone is essentially a guinea pig now. Going to see how far down this rabbit hole I can go.
While I'm stewing on that does anyone have links to android filesystem reference material? I'm thinking the high-level relation between things like bootloader, recovery partition, user-space filesystem and on which levels I can address these with tools like adb. I want to try to understand if some bit could have been flipped at a layer lower than what flashing a ROM or kernel can recover, but perhaps higher than a baseband radio flash. Knowing where all these live and how they interrelate sounds interesting to me. Then I can form a better working theory on what could cause the stupid problem I'm having and if it's plausible to be in software/firmware somewhere.

There is an unrooting guide on YouTube. I find it hard to believe its software, but I work on a radar weapon system that has proven me wrong many times... But if you have flashed multiple roms then the kernel would've been reflashed atleast once and if you are doing a full boot and system wipe, whatever drivers previously installed would have been overwritten... I'm leading to believe there is a shorted componant on your board and because the voltage is so low on these, there moght not be any visual evidence. Unless u have schematics of what voltage is applied where, there isn't a way to test most of them. Especially if the gates are set to be low when applied, vice highs. I would s-on factory reset and of that doesn't work, its hardware
Sent from my Incredible 2 using xda premium

Agreed. I work with enterprise hardware/storage/cluster systems, so I'm driven by nature to root cause this silly thing - but yeah, occam's razor seems to say here that it's just a really stupid coincidence that some random component failed just at the time I began making other changes. And I can't let it go
This is even more frustrating to me because I always make a point to introduce only one change at a time then test the outcome!
After poking through the SDK/reference guide about AudioManager, I was reminded that GV has access to the earpiece audio path. While I could just make test calls in/out, this saves me from burning minutes in the process.
As a quick-and-dirty workaround (for anyone who may stumble on this in the future), you can use Google Voice to act as an internal earpiece playback test tool.
Install and then go to settings and tell it to play back via the earpiece by default and not the speaker. Then (assuming you have voicemails to play), attempt playback. You can toggle between the two audio outs in a much quicker way than I've seen in any other app. Works close enough for me to serve as a test tool as I make discrete changes as I go through troubleshooting.
Maybe there are other media playback apps that'd offer a toggle to the earpiece for playback (but why?), though I didn't look. Seems like the AudioManager reference guide implied that the earpiece was a more "protected" audio path than the speaker (but that's likely just for actual carrier network voice calls).
Cheers,

I'm really getting a kick troubleshooting.. I've been recruiting for a year and a half now.. miss working on gear.. one and a half years left and back to my ship... Can't wait
Sent from my Incredible 2 using xda premium

I actually doubt it's your ROMs --- I'm running latest unmodified vz gingerbread and all of a sudden about 5 days ago I could no longer get earpiece to function - my only guess is something shorted out because of an off-market USB charger that I got 3 of for 7 dollars off Amazon...
Anyways, I had the same sorta flutter that you seem to hear when on a call and there should be sound... and otherwise silence when silence is expected... anyways I replaced it with a brand new earpiece and EXACT same issue is happening still.
Not sure whats up but this may be the world telling me to use my Bluetooth headset more anyways... I'll post if I find anything that fixes it, but I ain't gonna hold my breath given how few ppl seem to be experiencing this issue.
Good luck

[BUG] Screen Sensitivity Issue-Lag (4.0.4-4.1.x)

Problem summary
Known cause (might be others): selecting an app from the Recents list (Task Switcher)
Temporary fix: turn the screen off, then back on
Workaround: avoid using Recents list (you can use a 3rd party task switcher instead)
How to test: open Messaging, hit Home, hit Recents, select Messaging from the list. Your screen will be less sensitive until you turn the screen off and back on. You can view the pressure by going to Settings -> Developer Options -> turn on Pointer Location. This will allow you to see the Prs of each tap in your status bar. Normally your lightest taps that register will show anywhere from 0.28 to 0.32. However, after this bug is activated, you will mostly get values over 0.40 for your light taps. This is actually a very noticeable increase, especially when trying to type quickly.
Please report any other known methods to "activate" this bug. After re-assigning my Recents button to a 3rd party app (I'm using Simple Task Switcher), I haven't seen this bug at all. It seems that a couple of people have seen it produced by something other than Recents, but they haven't narrowed it down (or reliably reproduced it on purpose).
Please star this issue officially so Google can fix:
Link is http://code.google.com/p/android/issues/detail?id=29734
Note: Downloading & using Screen filter application from play store, with brightness set to

Your hands are really dirty or really dry. Try moisturizer or something.

Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.

Hehe yes this s gonna be a difficult one to confirm. But it is definitely not dirty hands. To clarify, a quick press of the power button to lock then unlock completely fixes the issue. Same fingers suddenly register perfectly. This is driving me nuts as the phone is not even usable right now. Literally.

@rbiter said:
Been using my screen for almost hour straight now. No issues.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
ios 6.2 doesnt get issues.

I don't know about your other experiences, but as far as the browser goes I have the same scrolling effects as you do. I think this is how it is meant to be. They tightened the scrolling a lot and I kinda like it. Before one small flick would send me across the whole page, which was kinda annoying. Just my preference.

I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.

I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.

My wife had this issue once.
It was the third party launcher she was using.
I don't think its a matter of touch sensitivity dropping, its a matter of the system just being too slow to really work right.
It was ADW EX, fwiw.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Lol that is hilarious. You forgot the step where its the OS that actually processes the input data, so in that process, a ton of problems can arise.
And personally, since 4.0.4 I have also been experiencing a "similar" issue. When scrolling down (and only down), I experience a kind of "lag" like if it only registers the swipe movement half an inch lower. Its not a big deal, but still an issue.
Edit : What he explains as "pressing very hard" is most likely the fact that when you press harder you actually cover more surface, so the amount of extra input data can definitely impact the behavior.

I had issues for a few hours after the 4.0.4 update, where my softkey buttons weren't responding. Thankfully, it seems to be fine now, but it was a cause for concern.
Sent from my Galaxy Nexus

gokpog said:
I'm not having this problem. It would drive me crazy too. Been using my phone alot over the past two days and I didn't run into this problem even after almost 1h of continuous surfing. Also a few checkpoints of Shadowgun didn't trigger it.
But you can confirm your problem if you enable "cursor position" in the dev options (hope that's what it 's called in english). "Prs" and "Size" should need a lot more than around 0.30-0.40 to register your touch if you have the problem you describe.
Click to expand...
Click to collapse
Thank you my friend, I should have thought of this; now I have numbers to confirm this. So with cursor option enabled I can get down to 0.30, managed 0.28 once. However when the bug starts, I can confirm that I cannot get below 0.60. It just refuses to register that input for some reason.
I lock the screen, 1 second is all it takes, and now it registers down to 0.30 again and all touch works properly. Its almost like some type of memory leak issue is the way it feels to me. It only starts happening after a few min of use.
Its definitely an issue now that I can see the pressure numbers. The question is what the hell can I do about it. I flashed aokp29 with the latest 4.0.4 ota merged in, problem still occurs. I'm gonna try stock 4.0.2 or 4.0.1 just to see. Thanks.

I have never had much luck upgrading Linux versions. That's why I start fresh every time with Android. Lol
Sent from my Galaxy Nexus using Tapatalk

Before I start digging, anyone know specifically which driver controls the touch input? I'll try looking thru github.
Also I was on stock 4.0.1 prior to this. So this could be normal behavior for everyone but everybody is used to it since nobody stayed on 4.0.1 like me. Cause I can easily say this is difficult to notice if you aren't paying attention. The question is, why does locking the screen temporarily change it back...

I can confirm some of what you are saying..sometimes when I'm browsing the scrolling tightens up..I lock the phone then unlock it and it is smooth again..doesn't happen all the time tho..doesn't bother me but I've noticed it
Sent from my Galaxy Nexus using XDA

I can also confirm. This morning I found the Swiftkey was lagging on Facebook. Something like the phone did not receive the touch. Then I rebooted and now it is ok.
I did not get this issue on 4.0.2 and I don't install anything new on 4.0.4.
The way I installed 4.0.4 was from the official factory image, so my phone is fresh! I reinstalled all apps manually as well. Nothing fancy apps.

I know this is my first post, but I can definitely confirm this issue.
I use my Galaxy Nexus for development, so the screen is always on. The sensitivity goes down very quickly.
My phone was an International GNEX that I loaded the US firmware on and then I flashed the OTA 4.0.4 update.

kristovaher said:
I am sorry that you're experiencing this, but 4.0.4 has nothing to do with this. 4.0.4 is just software, Galaxy Nexus is not a pressure-sensitive device, it is merely touch-sensitive. Which means that software gets an analogue signal from the touchscreen, either 1 or 0. It has no 'range' of sensitivity, so it cannot decrease in sensitivity in software (if it did, then it would not work at all).
This is entirely hardware issue and I suggest either making sure your screen is clean, your screen protection thing (if you use one) isn't acting up or if your hardware has become faulty (have you dropped it recently?).
If problem persists then return under warranty.
Click to expand...
Click to collapse
Just to point out, the phone is all digital. It does not get an analog signal from touching the screen. Also to that point you said analog but then described digital with the 1 and 0

Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.

TechNoir said:
Has anyone affected tried going between 4.0.2 and 4.0.4? To check the possibility of a driver or some related value changing.
Also, if not fixed by going back to 4.0.2, this could be due to current leakage from somewhere causing the touch to not work properly. I've seen it on other capacitive touch devices, though mainly when a non-compatible charger is connected. When you shut the screen off, the charge causing the problem/interference with the touch is temporarily dissapated, but then comes back after you use it again. Probably very unlikely in this case, unless Google changed something in the touch driver that makes it more sensitive to interference, which in turn messes with actual input from fingers.
Click to expand...
Click to collapse
Its possible. I was on 4.0.1 so perhaps this issue originated in 4.0.2 but I never noticed since I didn't update then. I can add that I did multiple wipes and clean flashes, and also tried both aokp 28 and 29 (new 4.0.4 ota merged), and happened on both.
I'll post what I just sent to arbiter which gives more insight.
From my extra testing under normal use my light touches register 0.28-0.33. Especially on swipes, the end of the swipe registers 0.28 as the finger travel breaks contact with the screen giving that swipe extra input which pushes the swipe motion further extra boost. When the bug starts the touch swipe won't even break 0.38-0.40, and that extra swipe data is lost resulting in the end of the swipe data points being excluded and swipes travel half the distance.
This gets exacerbated on the keyboard when fast typing light pressed. Its so bad it frustrates my face off cause typing just ceases to be possible. Such a difficult issue to diagnose.
Click to expand...
Click to collapse
Yes my face literally flew off!

[Q] GPS navigation + Rain Storm = Not good :(

If you can't guess what happened from my title, then let me elaborate.
When leaving a nightclub in camden last saturday night, I whipped out my phone to navigate to the bus stop when the heavens bucketed it down on me. Well shortly after getting on the bus and texting my flatmate to see if they are still up and want a game of COD, the screen starts flickering and the contrast went all weird and I lost my mobile signal. So rebooted the phone, still the same (at this point the brain still hadn't clicked that it could have been water damage). So I decided that I should reinstall the rom whilst on the bus, still the same (mine is rooted and running Liquid Smooth beta 3.2). It was only when the phone felt particularly warm at the back that it occurs to me that it's water damage so that was when I decided to take the battery out.
Anyway, now that I've set the scene and the background story, the problem I have now is that the camera doesn't work and I've tried multiple camera apps. All I get is a grey screen, the camera icons doesn't work and I get a message saying "Gallery isn't responding". At the same time Gallery sometimes work and I can't view any videos via MX Player or play anything on youtube (the menu and links are still there though). And my mobile signal just drops to nothing and I have to reboot.
Any ideas on what I can do? I've done the following:
Hardware reset and reflash my phone
Tried different versions of LiquidSmooth Rom
Made sure I'm using the correct version of Gapps
Attempted to run Z-Device Test to no avail, the app just hangs
I've let it dried
Cleared the cache, enable/disable gallery
Cleared the cache on Media Storage app
Used multiple camera apps
Tried to use the camera in the lock screen (just get a black screen)

Since it's water damage I cannot imagine flashing anything will make a difference.
Should have immediately pulled battery and put it in rice asap.
Always a good idea to keep a small plastic bag in your car/bag/briefcase for just that situation.

Yeah.. I had hopes someone in the forum would go, "That doesn't sound like water damage, you can fix it by doing this". Sigh.... It's amazing how one hardware fault can affect things like youtube whilst everything else is fine.

I'll keep my fingers crossed for you that someone will see this and know of another possibility.

[Q] GS2 Boot Vibration became intense, rattly, almost violent

I've been running CM10 stable for most of my time with this phone. Flashed CM10.1 Stable as soon as it was released recently. Everything was smooth and I encountered no problems. My one gripe was the lack of USB mass storage, so I attempted to enable it via this terminal command fix.
It didn't work, and instead caused me to lose all network service. I wiped/reflashed CM, and restored through Titanium Backup. All was well and back to normal.
Starting around yesterday, however, I noticed that the phone's vibration upon booting was much more intense than usual. It lasts for about half a second but is incredibly loud (regardless of surface it is on or if it is in my hand or pocket) and when placed on a flat surface causes the phone to move around for the duration of the vibration.
I tried wiping data, cache, dalvik, fixing permissions, and finally flashing the device back to stock ICS through Odin. When running stock, I changed the Sound>Vibration Intensity settings to zero for ringtone, notifications, and vibrate on screen tap. Results are the same.
This problem doesn't really impede my use of the phone, only really causes some annoyance upon booting and has me worried that this activity might break the vibration mechanism in the phone (as I said, it is REALLY intense).
Does anyone have any idea what is going on with my phone?

There's a bee stuck in your phone

JesusWazBlack said:
There's a bee stuck in your phone
Click to expand...
Click to collapse
I really wish it were that simple

Lol sorry but are you sure its a problem or just normal vibration. It might also be a hardware issue where unless you can open up your phone or get a new one you might be outta luck