I'm not sure if it has something to do with SMOLED in general, or if it's particular to the Nexus S, but I'm noticing oddities with the screen. Can't be sure if it's software related, or if it's hardware related.
There are two things. One, it sometimes doesn't register presses, even when an icon is clearly pressed; the orange highlight that surrounds an icon is clearly seen but it doesn't launch the app. It requires a second touch. I'm guessing this is mostly software related, but either way, it's disappointing to see Android like this (or, if hardware related, sad to see SMOLED like this).
The 2nd thing is, the screen seems problematic for the complete opposite reason sometimes. Has anyone ever hovered their fingers over the screen without actually touching it? Sometimes it'll register presses this way. I'm guessing this is hardware related? Either way, I have no doubt this causes unintended screen presses, and might go a long way in explaining typos and frequent errors that occur when typing quickly where your fingers glaze over the screen (like I often see double letter hits, like tthis or thiss - very annoying).
Not sure what the deal is, whether it's software or hardware contributing to these two oddities/problems - or a combination of both. Either way, these two things can make the Google Android experience feel second rate.
Additionally, I think this goes a long way in explaining my frustrations with typing on Android. Missed space bar presses are particularly frequent, resulting in words likethis; while other times, double hits occur, per my example above (like tthis or thiss). Again, it detracts from the overall Android experience and can be frustrating when thumbing out long messages.
The first issue might be related to the Launcher you're using. Are you on stock launcher or did you install something else like ADW or Launcher Pro? If you're on a third party, try it back on stock, or dig into the settings for your 3rd party launcher and see if there are tweaks you can turn on/off that might impact it. I know ADW has a "keep in memory" toggle; stuff like that is what I'd play with.
The other problem is something I've seen several people mention in here. I'm not sure I notice it or not, BUT, I just read this interesting article yesterday, which suggests to me that the screen is ultra-sensitive to touch. The article authors are amazed that they can use the back of their fingernail, or even wear gloves and still register touch on the screen. Other phones aren't so sensitive.
It seems they did something to increase the capacitive touch sensitivity, and perhaps a bit too much. Hopefully it can be software fixed.
The NS is such a lovely device, but it's got it's fair share of quirks, both hardware and software that really mar the experience for many. I love the phone, but am still considering returning it when my 30 days is almost up.
distortedloop said:
The NS is such a lovely device, but it's got it's fair share of quirks, both hardware and software that really mar the experience for many. I love the phone, but am still considering returning it when my 30 days is almost up.
Click to expand...
Click to collapse
I agree.
As for the launcher, I am currently using ADW because there are a slew of glitches and issues with the stock launcher, including the unresponsive issue I wrote about in my OP. ADW Launcher is unquestionably more reliable, smoother, and stable.
It's unfortunate the experience with the Nexus S can be so polarizing: sometimes the screen is not responsive, and other times, too responsive.
And I have to reiterate, the experience typing on this phone (and on Android in general) remains a particular sore spot for me.
distortedloop said:
I'm not sure I notice it or not, BUT, I just read this interesting article yesterday, which suggests to me that the screen is ultra-sensitive to touch. The article authors are amazed that they can use the back of their fingernail, or even wear gloves and still register touch on the screen.
Click to expand...
Click to collapse
No kidding. I don't have to actually touch the screen at all. Just hovering the tip of the finger 0.5mm over the screen is enough. Which is not really a problem, because it's quite difficult to do that.
I have found the same issue with the screen, it is very sensitive to touch. As for the bad selection and typing errors, I think that is more more likely software related, try a different keyboard?
Sent from my Nexus S using XDA App
Corvidd said:
I have found the same issue with the screen, it is very sensitive to touch. As for the bad selection and typing errors, I think that is more more likely software related, try a different keyboard?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I'm currently trialing Swiftkey. It is impressive the few times it works to perfection, but this is usually a rare occurrence. More often than not, I'm still having to type out my words, however, perhaps it's still "learning" how I type. For now, I feel like the experience is actually slower than manually thumbing out messages because you're so busy concentrating on picking the correct predicted word. In some ways, it's counter intuitive to messaging quickly. I have until the end of the month before the trial expires, so we'll see if the experience is improved.
Prior to that, I was using either stock keyboard, or Smart Keyboard Pro. Both have their positive and negative issues, but those two offerings are as good as it can be on Android, it seems. Which is to say, it's disappointing. I have many typing woes. I have to say, the typing experience pales in comparison to typing on iPhone/iPod touch devices. I can type far more confidently and smoothly on an iPhone than I can with any Android device I've used so far. I'm hoping, one day, when Blindtype is implemented, this will change.
I didn't like swiftkey, and don't understand its popularity, having to check the scrolling bar for which word i wanted slowed me down. I agree that the typing accuracy on an iPhone is superior to android devices, there are many things I don't like about the iPhone keyboard but the accuracy is very good.
Have you tried Swype? I believe the beta is now open to all to try, google it, as its not in the market. Failing that, apps like Shapewriter (when it becomes available again) and SlideIT keyboard are other similar options. Or if you want to go all-out weird with text input, try 8pen.
i found the same bugs
and my guess it has to do with the Concave design, that throws off the screen calibration.
on the SGS, the touches are 110% accurate
you just hover your finger on top, and the work
Corvidd said:
I didn't like swiftkey, and don't understand its popularity, having to check the scrolling bar for which word i wanted slowed me down. I agree that the typing accuracy on an iPhone is superior to android devices, there are many things I don't like about the iPhone keyboard but the accuracy is very good.
Click to expand...
Click to collapse
Agreed. However, I'm trying my best to give Swiftkey ample opportunity to grow on me, and as I said, when it actually predicts your words accurately, it's quite intuitive, but this happens rarely. Most of the time it guesses incorrectly and you end up thumbing in almost all the letters to a word anyway. Swiftkey slows me down too and I, ironically, end up taking longer to type out messages. Like you, I'm too busy making sure it's predicting correctly the next words I want to say. In many ways, it's counter-intuitive.
And it's a shame Google didn't set itself apart from Apple's keyboard. They could/should have included custom auto-corrections, etc.
Have you tried Swype? I believe the beta is now open to all to try, google it, as its not in the market. Failing that, apps like Shapewriter (when it becomes available again) and SlideIT keyboard are other similar options. Or if you want to go all-out weird with text input, try 8pen
Click to expand...
Click to collapse
Thanks for the suggestions. Yes, I forgot to mention I have the Swype Beta. Swype is quite fun and often impressive, but like Swiftkey, I find it cumbersome when I'm trying to type 'personal' words like unique names of places, or uncommon lingo and words, etc. Plus, when you start getting into long words, Swype becomes difficult to track. Perhaps I just need more practice, but ultimately found it slower than thumbing it out. I have tried a few other options, like the one where the keys change sizes depending on predictions, and even 8pen (novel, but no thanks), but nothing seems capable of accurately mimicking the iPhone/iPod Touch typing experience. Anyone who has typed extensively on both platforms will know the difference.
I would just like to be able to thumb out messages minus the odd errors and mis-presses/unregistered presses, or the overly sensitive presses. Smart Keyboard Pro remains the best choice, in my opinion, but even that has hiccups and my aforementioned problems. It's probably a combination of software and hardware that is contributing to my typing woes.
Blindtype, please hurry.
I don't have problems with it not registering presses, but it certainly is sensitive. Depending on conditions, you can register a press by hovering your finger 1-2mm off the screen surface. This has rarely bothered me, but if you keep your fingers very close in while you're typing, yeah, I can see it being really problematic.
EDIT: Actually, Android Central posted a short article and video just this morning about how you can use your Nexus S with certain types of gloves on in the winter cold because of this.
zorak950 said:
I don't have problems with it not registering presses, but it certainly is sensitive. Depending on conditions, you can register a press by hovering your finger 1-2mm off the screen surface. This has rarely bothered me, but if you keep your fingers very close in while you're typing, yeah, I can see it being really problematic.
EDIT: Actually, Android Central posted a short article and video just this morning about how you can use your Nexus S with certain types of gloves on in the winter cold because of this.
Click to expand...
Click to collapse
Right, you are. I mention about the hovering finger thing in the OP.
AllGamer said:
i found the same bugs
and my guess it has to do with the Concave design, that throws off the screen calibration.
Click to expand...
Click to collapse
But my understanding is that the actual touch screen itself isn't curved...?
onthecouchagain said:
But my understanding is that the actual touch screen itself isn't curved...?
Click to expand...
Click to collapse
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
zorak950 said:
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
Click to expand...
Click to collapse
Yes, that makes sense.
Not sure if I'm liking what I'm hearing. If the screen is indeed too sensitive and is the cause of my typing woes, I don't suppose there's a way to dial it down via software, is there?
onthecouchagain said:
If the screen is indeed too sensitive and is the cause of my typing woes, I don't suppose there's a way to dial it down via software, is there?
Click to expand...
Click to collapse
I don't know enough about how the technology works to answer that authoritatively. I'm curious too, though.
onthecouchagain said:
The 2nd thing is, the screen seems problematic for the complete opposite reason sometimes. Has anyone ever hovered their fingers over the screen without actually touching it? Sometimes it'll register presses this way. I'm guessing this is hardware related?
Click to expand...
Click to collapse
I've had this happen to me a couple times. I could see how its annoying, but I'm coming from a nexus 1 where you could mash the screen at times and nothing would happen so its nice to have a sensitive screen.
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
distortedloop said:
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
Click to expand...
Click to collapse
I agree. Voice input is very good with the S, much better than it was with the N1.
Smart keyboard pro is also a good one.
distortedloop said:
I don't see that I've mentioned it in this particular thread, but I have in others, so forgive me for repeating myself, but for short messages I really find the best solution is to just use the voice input.
Not to dismiss the need for an accurate, fast, easy to use keyboard, but I think Voice Actions and Voice Input are one of the absolute best features of Android that don't get a lot of attention.
I won't say Voice Actions has changed my life, but it's definitely changed the way I do several things (like to-do lists), and how I interact with my phone.
edit: Another good keyboard is Better Keyboard, it lets you see where you hit the keys to help train yourself on it; not sure it's any more accurate than the others though.
Click to expand...
Click to collapse
Yes, I've attempted to use Voice Actions, especially while driving. Usually it gets what I want to say correct, but unfortunately, it doesn't always get the person I'm trying to send it to correct. In fact, it never does. Same is true for when I'm not driving. So I end up having to cancel the command and type it out anyway.
I bought Better Keyboard long ago. It was one of the first third party keyboards I tried. I found the experience atrocious (at the time, it lacked true multitouch. If you think stock keyboard missed letters... you should try BK!). My understanding is that multitouch is implemented now, so perhaps I'll give it another try.
Edit: Also, Smart Keyboard Pro offers touch points and calibration to help you see where you mistype and to calibrate it to your typing style. These features help, but there's no mistaking that the phone (softward or hardware?) often misfires or misses presses altogether. Problems that appear like tthis or thiss or whenever it misses a space bar press (despite the space bar clearly being highlighted on the keyboard) resulting in words likethis are far too frequent and have nothing to do with pressing accuracy.
zorak950 said:
Yeah, but what that basically means is there's a different thickness of glass between the touchscreen and your finger at different points on the screen. I don't claim to know much about capacitative touch technology, but that seems likely to make for a much touchier sensitivity calibration than a traditional flat screen.
Click to expand...
Click to collapse
exactly... too much empty space in between, that's why the areas around the edge at the bottom are harder to register
Has anyone else run into this problem? Care to list such apps?
Google Music's interface is much different on the Note than it is on an S2 (at least for me). Where on the S2 artists, albums, etc are displayed in a long list of names, on the Note they are displayed in a long list of thumbnails of the artist, album, etc. This layout would make sense on a full size tablet and horizontal scrolling but it is very inefficient on the Note. Also much more taxing on the hardware (not that the Note is lacking in this department though). I would much prefer the S2's layout to quickly find an artist or scroll through the list.
Swiftkey X gives a warning when installed saying the phone version is incorrect for this device (the Note), use the tablet version. However, skipping the warning is not detrimental and the phone version works perfectly on the Note (have not tried the tablet version).
I assume this has to do with the resolution of the Note and apps confusing it as a Full Size Tablet. Anybody else seen this problem? On what apps? Workarounds?
JoyR2 said:
Has anyone else run into this problem? Care to list such apps?
Click to expand...
Click to collapse
I don't know if it's a 'problem'.
I don't necessarily like it with certain programs (some games are a bit painful to play), but I don't consider it a bug or anything.
It's a matter of detected screen resolution and how the app decides to use it. I don't see any workaround for it, unlike windows where you can use a selected resolution.
It would be nice for there to be an option to set screen resolution.
I imagine there are some people interested in the note because they want the larger size (larger icons/text/buttons/etc) but not necessarily the higher resolution. You can't always set that.
- Frank
it has full tablet resolution so it should run like that
kromosto said:
it has full tablet resolution so it should run like that
Click to expand...
Click to collapse
Ya, I know. But for some apps it really is not optimal. Just trying to get a feel for how many apps are going to encounter this "problem" (for lack of a better word).
Use spare parts to make the adjustment
Sent from my ADR6400L using xda premium
Plume thought that my note was a tablet. However the support team gave me a corrected version and said that it will be sorted in their next release
i have seen a lot of threads about the touchscreen being unresponsive and have pretty much tried everything from disabling currents sync to editing the build.prop (cant remember exactly what the settings were but they were supposed to increase touchscreen responsiveness)
i have tried stock rom, cm10.1, smooth rom etc but using the touchscreen is still a pretty crappy experience
basically, the inertia of swiping up and down is near non existent. it takes me a million swipes just to get back to the top of a webpage.
its not as bad in non web browser apps such as reddit sync or facebook but its still there
ive tried every browser known to man (chrome is nearly unusable, firefox beta is the best, dolphin is ok) and theyre all pretty bad, my galaxy s1 is better than this.
is it possibly a bad unit or is this just how the nexus 7 is?
Without seeing what you are observing, it is hard to know if there is a problem with your tablet, or if you have unreasonable expectations. (You didn't *quantify* what you meant.)
This page:
https://www.kernel.org/pub/linux/kernel/v3.x/
is 2203 lines long, but I can scroll the length of the page in either the AOSP browser or Chrome from top to bottom with three FULL swipes. (Portrait orientation, CM10.1 Nightly ROM, no tweaks afaik)
Hope that helps you figure out if there is a problem with your unit.
It's just how it is. It's very sensitive to touch, so when you scroll down (with your thumb as if you were on the phone), sometimes it picks up the last drag before lifting your thumb to reposition as a stop. And they can't say, "Oh, it's because Nexus 7 is bigger than your phone! So you have to swipe a further distance!" because my 7" Galaxy tablet and even the HP Touchpad (10") hacked with Android has better touch experience and scrolls nicely with smooth inertia to the bottom or top of the page depending on how fast you swipe.
Everyone swipes differently, and I think those who swipe with our thumbs at an angle are the ones that are really noticing this. So yeah, Nexus 7 touchscreen sucks for people like us. You can see many threads about this if you search "nexus 7 inertia" or "nexus 7 scrolling" etc. It is quite crappy but I've become used to it some. Looking around for something better, though.
Can somebody please tell me whether it is possible to use the yotaphone 2's EPD as a (small) display to do some basic word processing outdoor out in the sun? I.e. to attach a keyboard/mouse to it (e.g. via bluetooth), to open some simple word processing app or even sthg like google docs, and then to just start working.
I have actually been looking for quite some time for some way to do this and I can't for the life of me understand why there aren't better solutions out there. I am always pleasantly surprised when I type notes on my Kindle Paperwhite. Of course it's a lot slower than on an LCD, but I am not a fast typer anyway, and I could live with some lag - if that's the price I'd have to pay to finally be able to work outside. I have thought of the Raspberry Pi x Kindle solution (but you can only type on sthg like vim); of ebook readers with an open OS that you can attach a keaboard/mouse to (like Onyx Boox that runs on Android 4.0 - and I'm still thinking about that); or of an e ink monitor (too expensive). But it is time for me to change phones, and if this works, I might actually consider it.
If anybody has any experiences or thoughts or - better yet - videos to share on this, I'd be very grateful... Thanks!
-Stephan
I haven't tried this personally, but I am fairly certain that this would work. Android supports bluetooth keyboards. The only limitation would be that you have to use mirrored mode, because there are no proper word processing apps made native for the EPD. Plus the system might not enable external keyboard for EPD apps only. Not sure on the latter though, I don't have any bluetooth keyboard/mouse to test this with.
Jeopardy said:
I haven't tried this personally, but I am fairly certain that this would work. Android supports bluetooth keyboards. The only limitation would be that you have to use mirrored mode, because there are no proper word processing apps made native for the EPD. Plus the system might not enable external keyboard for EPD apps only. Not sure on the latter though, I don't have any bluetooth keyboard/mouse to test this with.
Click to expand...
Click to collapse
Thanks Jeopardy. Can you (or anybody else) tell me whether there is an active developer community working on those EPD apps? And also - if you have to use mirrored mode, does this mean you have to open the phone and the AMOLED screen has to be 'on'? On can all of this just stay in the 'background'? And does mirroring to an additional lag beyond the usual - and much slower - e-ink refresh rate? If anybody has any first-hand experience with this, I'd really be curious... Thanks!
sdspieg said:
Thanks Jeopardy. Can you (or anybody else) tell me whether there is an active developer community working on those EPD apps? And also - if you have to use mirrored mode, does this mean you have to open the phone and the AMOLED screen has to be 'on'? On can all of this just stay in the 'background'? And does mirroring to an additional lag beyond the usual - and much slower - e-ink refresh rate? If anybody has any first-hand experience with this, I'd really be curious... Thanks!
Click to expand...
Click to collapse
Well there are some developers, myself included, working on EPD applications. But not a lot. There should be more once Yota releases the device in USA around mid-August.
Mirrored mode does not need the color screen to be turned on. Of course behind the scenes it will wake up the system to similar state as if the AMOLED screen was on, but that's handled automatically. This means more battery use, but you should get a lot more out of it than using the color screen, especially on static apps like word processors which don't update often.
You can handle everything from the EPD. You can, for example, create a shortcut on the EPD for a word processing app, which will automatically enable mirroring and open that application. The lag on EPD when mirroring should be about the same as on native EPD applications, but of course you will notice it more because you can easily compare it to the non-laggy color side. There's only a few extra algorithms for turning the color image to nice greyscale, and some logic for creating additional "flashes" to fix ghosting when switching between apps etc. Should be fine for word processing, especially on external keyboard, provided you can write without constantly checking which letter you just pressed. The refresh rate on the EPD is about 8 frames per second, or one frame every 0.12s.
If you're seious about outdoor word processing may I suggest a rooted Nook Simple touch? It is small and light and a fraction of the price of a Yotaphone... as well as having a much bigger screen! You can pick these up for around 40GBP in good/new condition and although it will be a fair bit of messing around with rooting you are unlikely to come totally unstuck, and there is a lot of support on XDA to get you help if you do. With the NST device, you use the OTG USB mode to attach a bluetooth dongle, hard wired full sized keyboard or whatever to your desire. Pop over to the NST forum and there are many threads on this topic, but to whet your appetite here's someone who is doing that with a solar panel to power the setup!
http://forum.xda-developers.com/nook-touch/general/nook-simple-touch-solar-power-t3068849
Is there any way to increase the screen sensitivity on the T280? I've only found one mention of the issue after thoroughly searching Google, with no suggested fix.
I'm comfortable with modifying system files such as build.prop and such, I just have no idea where to start!
The issue:
This screen is really slow to pick up touches, especially from a stylus.
When swiping (eg for pattern unlock) contact is often broken.
Even using my finger, when selecting text it's difficult to move just one letter at a time.
In handwriting/drawing apps, resulting text is extremely angular and jagged.
Here's what I've tried:
Changed "mouse sensitivity" in the settings (minor improvement)
Used 2 different screen calibration apps (minor improvement)
Installed debloated ROM (only one available; no improvement)
Removed some unnecessary system apps (will be removing more to free up space....)
Disabled settings that affect device speed such as animations
Several different stylus types (the most expensive work worst )
So, is anyone else finding this an issue? Is there a fix I don't know about? Is/are there a kernel tweak or something that will speed up screen response time?
I bought this tablet in part so I could use it for handwriting input using a stylus on a larger screen than my teeny S5. Unfortunately, the screen response is far too inconsistent and ...well, slow than I'd expected.
PushyPhoenix said:
Is there any way to increase the screen sensitivity on the T280? I've only found one mention of the issue after thoroughly searching Google, with no suggested fix.
I'm comfortable with modifying system files such as build.prop and such, I just have no idea where to start!
The issue:
This screen is really slow to pick up touches, especially from a stylus.
When swiping (eg for pattern unlock) contact is often broken.
Even using my finger, when selecting text it's difficult to move just one letter at a time.
In handwriting/drawing apps, resulting text is extremely angular and jagged.
Here's what I've tried:
Changed "mouse sensitivity" in the settings (minor improvement)
Used 2 different screen calibration apps (minor improvement)
Installed debloated ROM (only one available; no improvement)
Removed some unnecessary system apps (will be removing more to free up space....)
Disabled settings that affect device speed such as animations
Several different stylus types (the most expensive work worst )
So, is anyone else finding this an issue? Is there a fix I don't know about? Is/are there a kernel tweak or something that will speed up screen response time?
I bought this tablet in part so I could use it for handwriting input using a stylus on a larger screen than my teeny S5. Unfortunately, the screen response is far too inconsistent and ...well, slow than I'd expected.
Click to expand...
Click to collapse
Unfortunately the drivers or the touchscreen hardware itself for the T280/T285 is not that good. I have a drawing app that I created myself and the touch event update rate is so slow it creates jagged lines. Best case is that it is a driver issue and we can fix it in the kernel, worst case the hardware just sucks and it is what it is. On my OMNIRom 6.0.1 SM-T285 device touch response is actually ok, it is the update rate and precision of the touch which is a problem.
Thank you so much for the quick reply, and for understanding what I mean.
jedld said:
On my OMNIRom 6.0.1 SM-T285 device touch response is actually ok, it is the update rate and precision of the touch which is a problem.
Click to expand...
Click to collapse
Congrats on getting most of the bugs out of that ROM! It was SO disappointing to read the "fine print" on your OMNIRom and discover I couldn't use it, as it looks pretty sleek, but you're helping others immensely with your work.
jedld said:
Unfortunately the drivers or the touchscreen hardware itself for the T280/T285 is not that good. I have a drawing app that I created myself and the touch event update rate is so slow it creates jagged lines. Best case is that it is a driver issue and we can fix it in the kernel, worst case the hardware just sucks and it is what it is.
Click to expand...
Click to collapse
Hooray for drivers being a possibility! There's something can be done about that!!
Do you find that the lines aren't quite as jagged running OMNIRom as with stock?
How would someone find out whether it's the hardware or the drivers?
Are the differences between 280/85 so extreme that I can't try anything on my own?
Is there anywhere I can "sign up" for testing any new tweaks or ROMs or kernels?
(Update on the issue: I ran the "screen calibration" test again and it says it's taken another 10ms off the response time. Not sure if I'm imagining it but it feels as if it's actually faster...)
I was also thinking, would the DPI have anything to do with the jagged appearance? Between this tablet and the 2 others I was looking at (both Galaxy - previous 7-inch and 9-inch) those had much better DPI ...or am I thinking of resolution? Those aren't the same thing, are they? In any case, it's worth checking into whether fiddling with the DPI might do any damage.
Do you find that the lines aren't quite as jagged running OMNIRom as with stock?
Click to expand...
Click to collapse
I think it is just as bad
How would someone find out whether it's the hardware or the drivers?
Click to expand...
Click to collapse
We will need someone to tinker with the kernel sources to found out. For the SM-T280 someone is working on making the kernel sources work. Unfortunately, though annoying it isn't really on the top of my list right now.
Are the differences between 280/85 so extreme that I can't try anything on my own?
Click to expand...
Click to collapse
Devs working on the devices are actually surprised that there are more differences as expected for two devices that share the same family name.
Is there anywhere I can "sign up" for testing any new tweaks or ROMs or kernels?
Click to expand...
Click to collapse
I just go through xda for my testing.
I was also thinking, would the DPI have anything to do with the jagged appearance? Between this tablet and the 2 others I was looking at (both Galaxy - previous 7-inch and 9-inch) those had much better DPI ...or am I thinking of resolution? Those aren't the same thing, are they? In any case, it's worth checking into whether fiddling with the DPI might do any damage.
Click to expand...
Click to collapse
Based on the software codepath, DPI shouldn't really affect touch performance.
I wound up returning it and picking up the 7" Galaxy Tab E Lite (SM-113), which seems to suit my needs much better. While it's much more limited in some ways - no custom ROMs, limited to KK4.4.4, same small internal storage issue - the screen response is WAY better and I can get around the annoyances (largely - no, SOLELY - due to all the things this forum has taught me over the years. :highfive:
jedld said:
Based on the software codepath, DPI shouldn't really affect touch performance.
Click to expand...
Click to collapse
You were right. But it was fun to play around with! And I learned a few things in doing so.
We will need someone to tinker with the kernel sources to found out. For the SM-T280 someone is working on making the kernel sources work.
Click to expand...
Click to collapse
I sure hope that someone figures this out soon because it's a pretty sweet little tablet, otherwise, and I can't be the only one for whom this is a deal-breaker.
Unfortunately, though annoying it isn't really on the top of my list right now.
Click to expand...
Click to collapse
I totally appreciate that your time is valuable, and thank you immensely for taking the time to respond.
Similar issue
Hi,
Was wondering if anyone with these issues also experienced this: While the tablet is on, when watching something for instance, if the touch screen isn't used for a bit (say over 30 seconds) when I first press it it doesn't respond at all, to get it to wake up I have to press quite firmly, usually several times, before it starts working. Once it does respond I can use a much lighter touch so it doesn't seem like a screen protector or overall sensitivity problem, it's as if the screen goes into some kind of sleep mode becoming much less sensitive.
Anyone know about this/how to fix it?
Much love,
Tom