1. Download the #1 Android News App:   EarlyBird - News for Android
    Dismiss Notice

Touch Screen SensitivitySupport

Last Updated:

  1. amaranthine

    amaranthine Well-Known Member

    Just swapped my Optimus V for an Optimus Elite (White) and it's been good so far, except for one issue I've run into with the touch screen not registering taps as well as my old Optimus V. It's not an issue that pops up often, but shows up a bit more than with the OV.

    Usually I just have to re-tap the screen and it'll work, but it's a bit annoying. I also noticed I have to be more precise with my tapping, or else it won't register (like for on-screen buttons). Sometimes it has to do with some lag on the phone responding, but sometimes the initial tap just didn't register. I feel like I had a wider tapping range for things like on-screen buttons with the OV than the OE.

    I'm running Harmonia with giantpune's kernel, OC to 1612 mhz (smartassv2) and have left the original screen protector on it (just like with my OV).

    I was wondering if there's anything I could do to increase touch sensitivity (app or programmatically-wise without plain removing the screen protector) or if this is normal behavior?

    I haven't run into any other issues so I'm debating whether this is something worth exchanging the phone over.

  2. Artine

    Artine Well-Known Member Contributor

    Both the Tagged and Sleipnir ROMs have increased touch sensitivity tweaks, you may want to give those a try, but I do remember touch screen lag/sensitivity being an issue at one point in time. Otherwise, you could look into doing some build.prop and init.d edits (but again, some of these are already done) that you can find on XDA :)
  3. amaranthine

    amaranthine Well-Known Member

    I initially flashed Sleipnir but went back to Harmonia because I prefer to have all the stock apps available and not replaced with alternatives. Does Tagged retain the stock apps?

    I didn't use Seipnir long enough to make a judgment on any touch sensitivity improvement.

    I have a friend who owns a Black OE on stock which seemed more touch sensitive , so it makes me wonder if another OE will help, but at the same time I might run into new issues or see no improvement at all since it appears that each OE may have various issues of their own.

    I will look into editing build.prop and init.d, but given that I even avoid adb due to lack of expertise, I'm hesitant on messing around too much and bricking the phone.
  4. Artine

    Artine Well-Known Member Contributor

    It was actually returned back to stock in 2.3.7 (with the exception of the Mms.apk, turns out I missed that this time around), and Tagged does have stock as well. It could very well be that you might have received a worse OE than your friend, but it'd be hard to say. You don't have to use ADB either (honestly, I haven't since using the jcase root method). As long as you make a Nandroid backup, you should be fine and not worry about bricking your phone (you could even then, but that's only if you're messing around with something not /data, /cache, or /system).

    Also if you're going to use init.d, the only ROM with working init.d support is actually Sleipnir since we got that figured out (Harmonia and Tagged are both missing a modified install-recovery.sh that, with the proper permissions, allowed init.d scripts to actually run). But if you'd rather not use it, I'd be happy to attach the file and the line in the installer for you to get it working correctly for you :)
  5. amaranthine

    amaranthine Well-Known Member

    Does missing the mms.apk mean no MMS support? I'm welcome to give Sleipnir another try as long as it has the stock apps.

    That would be very helpful! Not sure exactly what I would with it, but it wouldn't hurt to try and figure it out.
  6. Artine

    Artine Well-Known Member Contributor

    No, the Mms.apk is still in the build, it's just different than an earlier build which was unintentional. Some stock apps are missing, some are included, it's been completely debloated and that means that things like Gmail and Maps would have to be added in manually if you wanted it, but given a number of factors (including very frequent updates, and that not everyone uses these apps or has their own alternatives), some stock apps were removed. However, their once-upon-a-time-replacements have been changed back over to stock (with the exception of the Mms.apk in 2.3.7, for aforementioned reasons). The goal is pure stock, that shouldn't be outdated once an app that some people use and some do not use gets updated. So anything extra, aside from the apps mentioned in the OP (which are easily uninstallable), you would have to add manually. This is to prevent the most headaches. All in all, I would wait for v2.3.8, which may get released tonight.

    As promised, the modified install-recovery.sh file is included in this post. The appropriate line for the installer is as follows:
    Code (Text):
    1. set_perm(1000, 1000, 0755, "/system/etc/install-recovery.sh");

    Attached Files:

    amaranthine likes this.
  7. amaranthine

    amaranthine Well-Known Member

    I'm really only concerned about the stock apps that I can't download from Google Play. It's fine that maps and wallet are removed, but I'm looking for things like contacts, calendar, calculator, clock, email, stock browser, etc. Once I saw that Sleipnir 2.1.4 eliminated the stock browser (which I kind of want around) I decided against keeping it.

    I will wait for v2.3.8 though and give that a try.

  8. Artine

    Artine Well-Known Member Contributor

    Those have all been brought back :)
  9. amaranthine

    amaranthine Well-Known Member

    The Sleipnir ROM appears to give a minor boost to touchscreen performance, although not enough for me to say it 100% solved the issue for me. It seems that occasionally there is just a lag in response that I associate with not registering. Sometimes the phone just came out of waking up and needs to get going. Other times I'm just picky about it making hit a button exactly where it is on screen to work. It's not perfect, but the Optimus V was CPU limited anyways, so that touches and swipes were registered rather late at times.

    The Optimus Elite shouldn't have that similar issue since it's CPU is better, but this might be a defect of the phone screen. It's bearable, although not ideal.
  10. sneaky_1

    sneaky_1 Well-Known Member

    Try bumping up the minimum cpu frequency to 368, and make sure your on the smartass v2 governor and noop I/o scheduler.
  11. Dark One

    Dark One Well-Known Member Contributor

    Actually I would try interactive instead of smartassV2. You will get less lag but worse battery life.
    amaranthine likes this.
  12. sneaky_1

    sneaky_1 Well-Known Member

    Agree, those are the only two that give me no lag on my elite. I've had good results with other interactive governors on my other android devices but the elite doesn't like them.
    amaranthine likes this.
  13. amaranthine

    amaranthine Well-Known Member

    Thanks for the suggestions, I've started using interactive and noop for now and again see a bit of responsiveness improvement (especially in games).

    I've also discovered that the somewhat bulky case I have on the phone might be limiting my range enough that I miss the "sweet spots" of the buttons on the screen, making it seem like the phone is unresponsive when in fact I just don't hit the button right. A bulky case wasn't as much an issue on the Optimus V because the screen was small, but the Elite has a bigger screen that actually makes it a bit wider and more difficult to hold in one hand.
    sneaky_1 likes this.
  14. amaranthine

    amaranthine Well-Known Member

    I've noticed that the interactive governor (and interactiveX) do improve the screen sensitivity, however at the expense of battery life it seems. Right now I lose about 50% battery in 7 hours, but I may need to optimize JuiceDefender and figure out other ways to conserve battery life. It certainly is somewhat worse than with the Optimus V, but given I've overclocked it to twice it's stock CPU speed I guess that is the trade off.
  15. Artine

    Artine Well-Known Member Contributor

    On normal use I get 60 hours of battery life from 100 to zero. Losing 50% in 7 hours is good for stock, but rather dismal.
    Also, can I just say this: the screen sensitivity is awesome. It's sensitive enough that I can use regular leather gloves, and still use the screen with precision. I would call that pretty sensitive. Any more sensitive than that and I'd be worried the thing is going to shock me or something :p
  16. amaranthine

    amaranthine Well-Known Member

    What settings do you use to achieve that? (I've seen the JuiceDefender settings in the Sleipnir thread.) I guess it would also depend on what you do with the phone to get that sort of longevity. I will surf the web, stream audio, do some GPS mapping (not necessarily all at once, but will stream audio and surf at the same time occasionally) and I'll lose 15% in an hour. This is usually over 3G. I'll be on the phone for 2 hours and lose 20%.

    The screen sensitivity in merely bearable, I'm just tremendously annoyed when I have to tap something twice (or three times) to get it to respond, which happens a few times daily. Like I've said in the past, sometimes it's lag on the CPU, sometimes it's just the screen not registering it, which is just odd.

    I can live with it if I have to, and the general responsiveness (minus the touchscreen) is great. The phone just flies compared to the OV, and it's great not to micro-manage the app space. Those two are worth it alone (as long as you don't run into issues keeping the $25 plan).

    I'm tempted to give another Elite a try to see if I get a better touchscreen, but I'm hesitant in case the swap to another Elite will screw up me keeping the $25 plan (which has happened to some people).
  17. Artine

    Artine Well-Known Member Contributor

    All of those things are very intensive on the battery, and that would be considered moderate to heavy use (gaming as well). As far as those sensitivity issues, even on my new replacement I haven't had those problems (or at least don't notice them if they're there) and it registers touches just fine for me. The problem also could be if you're using a screen protector of some kind, and I am not. And as far as battery life is concerned, the JuiceDefender configuration in Sleipnir, in addition to just the smartassV2 governor and DroidWall. That's about it.
    amaranthine likes this.
  18. amaranthine

    amaranthine Well-Known Member

    True. I have raised the underclock of my CPU to 468 mhz, it's possible it was too underclocked and that's why it keeps lagging.

    It's very possible I may exchange my White Optimus Elite for a black one, after trying my friend's Elite's (black) for a while (where I never run into the lag and unresponsive touch issues I have with mine...and he runs it on stock!) it could drive me batty to keep mine at this point.

    Now I just have to figure out how to return everything to stock. Is there a thread or link somewhere that could help me get it back to stock and unroot, while wiping all my data off the phone? Should I do the factory reset from the Sleipnir ROM? Would wiping the /data and /cache partitions and flashing the stock ROM be sufficient to wipe my data off the phone?

    I haven't figured out the un-rooting and removing custom recovery parts yet. Some research indicates I might not be able to unroot it or restore stock recovery, but it may not matter.
    DsyMnapTic likes this.
  19. Artine

    Artine Well-Known Member Contributor

    This is probably what you're looking for :)
    amaranthine likes this.
  20. amaranthine

    amaranthine Well-Known Member

    Upon further tests with my friend's OE, the screen sensitivity is a bit of a wash between the two. It's a bit more finicky than my OV, but the OE doesn't have the lag that would make the OV take its time responding to some taps. I figure it worth living with since it acceptable 90% of the time (I'm just a perfectionist).

    I've run into some odd Bluetooth+Wi-Fi issues with some headsets (and not others), but since that is a rare use case for me it shouldn't be an issue.

    I can't wait until we can get some Cyanogenmod to try on the OE.

Share This Page