Database Users

[Q] a guide to "non-convoluted android game programming"?

this question is actually about a small network of things: what the default android framework permits, how users use it and what engines can do.
after getting into android programming, it soon seemed to me that the android framework would require me to manage a lot of things i simply don't want to put up with for a simple game (e.g. i don't care about managing intents, creating xml-layouts and stuff like that... slap a couple of images on the screen and i'm fine - well... basically), i started looking for game engines.
after almost a month of research and tests (with default framework, andengine and libgdx), i finally whipped up a little prototype of the game i want to program using libgdx in just two days.
but then i noticed something...
the following issue might make the last third of this post irrevelant:
this game runs at 70% cpu usage on my desktop. even though i would only need to render on user input (it's a puzzle game). so i'm guessing it would use 20 times (or whatever) the battery of the phone it actually should.
since it seems to me "render on demand" isn't possible with libgdx, i figured i'd take another stab working with the default android framework and hope that this doesn't redraw like crazy even though it's not needed.
if such a thing is simply impossible, please tell me and i'll just keep on working with libgdx.
now, the most compact open source game example to learn from that i found is this:
http://code.google.com/p/asqare/source/browse/#svn/trunk/a2
after i tried it out and studied the code, i was stunned by how much stuff is being handled for this very, very simple game (pretty much as simple as mine). so i counted the lines of code... ~4200! while my libgdx prototype has roughly 800. sure, it doesn't have a preferences menu, no about screen and doesn't handle what happens on things like pause/resume but even with those things i highly doubt i'd get anywhere near that amount of code.
so:
IF it is indeed possible to produce a full-screen android app that draws images only on demand, is it possible to do that in a less convoluted fashion than in that 4200 line example?
i'm hopeful that this guy has simply overdone it and i've just been looking in the wrong places for slim examples.

Fyi I did not read 100% of your post, but I think I can help you out.
Imo do not waste your time with game engines. If you are serious about game dev then learn opengl. Its worth it.
With the glsurfaceview you can ether render on demand or as fast as possible. Also as with all opengl u have full control over what is rendered. If need be I can provide an example but it will have to wait a few days.
Sent from my MB860 using Tapatalk

actually, i've learned opengl in the past (but forgotten a lot already - didn't use those skills much) but a) i'll only do 2d games anyway and b) opengl isn't really the problem. getting to where i can actually render things is. and engines allow you to focus on gameplay/rendering without dealing too much with the whole setup and management of things.
i don't feel like libgdx takes control away from me, since i can still use all the opengl-commands i want. and i will definitely look up glsurfaceview and see how it fits into what i currently have. thanks!!
btw - i'm not really "serious". i'm a fulltime artist who happened to have learned about eight years of programming in the past and just wants to try to make a little extra on the side. and create some games i'd like to see but simply aren't out there yet.
and i don't want to spend more time programming all the management nonsense around it than the gameplay itself and working on the design.

I wouldn't rely on the cpu usage on the desktop. The emulator isn't efficient at all...

libgdx is a multiplatform engine, so that cpu usage is based on the desktop-version.
but it does use continuous rendering and can't be switched to on demand. tried to extend the classes of the engine and adapt them so that it renders in on demand for the last three hours without success...
but i've found a neat blog post on the android developers website called "The Simplest GLSurfaceView Application" and hope that i'll be able to find my way from there. after all, i now already at least have a nice full screen canvas with just 54 lines of code... that's something i did not expect i would ever see happening.

sefe

[redacted]

Some cool ideas there. A few comments (posted here because I don't see a way to leave feedback on the site):
1) I'd put the Charms bar on press-and-hold of a button, probably Search (which doesn't currently have any Hold action assigned). Double-tapping is an action that literally nothing else on the Windows Phone OS uses, and especially a button that is sometimes capacitive and sometimes physical (depending on phone model) it's not something I advocate adding now. I like the idea a lot, though, especially for its tie-in with Win8. One thing to add to the Charms bar though: as on Win8 (where it shows a bunch of status info when you open Charms), the Status Bar at the top of the screen should be always visible when showing Charms.
2) There's already a way to get to the task switcher; while it's OK to have multiple methods for achieving the same goal, it seems like there might be something more useful to do than duplicating functionality through a more round-about approach.
3) There should be a more visible cue about the notifications center. Either have something drop down from the top (perhaps a "you have <X> notifications" bar with an appbar-like pull indicator?) or add a button specifically for notifications (two-level Charms bar? Move it to the right edge of the screen? Not sure how best to handle that).
4) I know the whole "swipe down to close an app" thing is very commonly requested, and comes from WebOS, and vaguely resembles Win8, and... I still don't know if I want it. Closing an app is pretty close to literally never needed; backgrounded apps are not generally allowed to use any system resources (they may hold onto some RAM, but the system will take it from them if a foreground app needs it). Closing an app the "usual" way - by switching to it if needed, and then tapping Back until it goes away - also works, although it's more actions. My biggest concern would be that right now, it's not really possible to ever do the wrong thing on the task switcher view. Closing an app, though, is a destructive behavior - you lose the app's current state - and is something that would need to be carefully implemented to make sure it never happens by accident... or perhaps make it optional entirely.
5) The Xbox Music feature looks pretty good, although the drop-down switch between Albums/Songs/Artists/etc. might be a bit too... background. Also, the really basic problems of the new UI - things like songs getting duplicated when they exist both on the phone/SD card and on the "Music Cloud" - really need to be addressed. Highlighting the Search thing - I know you mentioned it earlier with global search, but it's good to have more focused search capabilities too - as the current lack of Search in the music app is a Problem.
6) "Windows and Windows Phone share the same store" is way, way more complex than anybody might be realizing. Leaving aside the fact that most Windows Store apps aren't written for the resolution or aspect ratio of Windows Phone and would therefore possibly look kind of crappy if they were usable at all, and the fact that app models of the two OSes are pretty different (for example, Windows Store apps are allowed to request filesystem access and are required to implement the Settings charm, while WP apps have neither of those things), the APIs are just different. WP8 can use a sort-of-subset of WinRT (the API for Win8 apps) but it's not the same thing (and Win8 can't run WP7 apps at all, not even close). Finally, there's the issue that even the most powerful WP8 are half as powerful as even the lowest-end WRT tablets, and that's going to make a lot of things that perform fine on things like Surface RT be unacceptably slow on a Lumia 920 and impossible to run on anything with lower specs.
7) IE11 is coming for sure. The sync feature would definitely be nice. I'd also like to see some version of (desktop) IE's feed reader (shared with desktop Outlook) get integrated into WP8.
8) Integration with photo services, in the same way as other parts of the phone are integrated with Facebook and LinkedIn and Twitter and so on... that is an excellent idea. Come to think of it, Facebook pictures are already integrated (a feature I never really use) so adding others should definitely be possible. It would be cool if apps could integrate that kind of stuff without explicit OS support, but that may be aiming too high.

Thanks for the good feedback!

Hmmm, concept by who?

that'd be me.

The sync of bookmarks from Desktop IE to WP IE has already been confirmed for a future version of WP. They didn't say which one exactlly so it might take until WP Blue.
I personally don't like the idea of having the icons in the settings - at least not at the end, just looks kinda weird. Perhaps it would work better if you put them in front and aligned them properly on a grid.
Camera settings actually return back to the defaults when you relaunch the Camera App (and didn't save your changes as defaults).
As for the charms bar - I like the idea of a universal sharing and search feature but I don't particularily like the implementation of it with the charms bar on Win8 and I really don't see it work well on WP.

I like it but MS always let's its users down and dismisses the best ideas and concepts. WP will go now where higher that where it currently is now because of MS's ignorance. The next 2 updates for Luminas that includes the Amber and the GR2 or whatever its called don't really bring much to WP at all; who cares about another clock on the screen or data sense? Or more camera tricks...? Really now!!

@sinister1: Does that post really help? Come on, there's no value in just being negative everywhere.
Also, you call Microsoft "ignorant", but I guarantee that they know far, far more about the smartphone market than you do. If you want to be persuasive, you need to come up with arguments that have more substance to them than effectively just calling MS names.
@KlausWidraw: I think I'm with StevieBallz on the suggestion to have the Settings icons be left-aligned; they do make the items easier to identify, but having a consistent horizontal position to look for them at would help. That said, the ability to re-order the options would be huge; I use some all the time (like Cellular, which is annoyingly just off the bottom of my screen) and others not at all (like "lock screen", "tap+send", or "theme") once I've set them up initially, and would like them out of the way to make room for the options that I care about.

GDR2/Amber as well as GDR1 before it and GDR3 after it are mere maintenance releases. No one expects an Update from Android 4.2.0 to 4.2.1 or 4.2.2 to bring major new functionality. No one expects updates from iOS 6.0 to 6.1 to bring major new features. Somehow everyone (contrary to all reporting on those topics) expects those maintenance releases in WP to do just that. Really new functionality will only arrive with WP8.1/Blue and this has been known pretty much since the WP Blue name first appeared in leaks.
GDRs mainly serve the purpose of fixing some bugs and enabling new hardware functionality that is required for device launches. It has been the same with WP7. There were updates like Tango that served to enable LTE. GDR2 now mainly serves to enable the new capabilities that Nokia required for their Lumia 925 and Eos Camera phones and to keep Google Mail usable. GDR1 was mainly bugfixes, GDR3 will enable new hardware like even higher resolution screens.
Amber then is bundled with the GDR2 update rollout but IS NOT a WP update. It is a device specific capability update like we have seen them by all OEMs in the past.

If there are two things I would change about WP (from a user perspective) those are:
1) A clock tile that updates real time, like the HTC one (srsly want one).
2) Battery saver profiles that let me choose what i want to remain active (bluetooth, wifi, mobile data, background tasks)
That's about it.
From a developer point of view, things are very, very different xD

GoodDayToDie said:
@sinister1: Does that post really help? Come on, there's no value in just being negative everywhere.
Also, you call Microsoft "ignorant", but I guarantee that they know far, far more about the smartphone market than you do. If you want to be persuasive, you need to come up with arguments that have more substance to them than effectively just calling MS names.
@KlausWidraw: I think I'm with StevieBallz on the suggestion to have the Settings icons be left-aligned; they do make the items easier to identify, but having a consistent horizontal position to look for them at would help. That said, the ability to re-order the options would be huge; I use some all the time (like Cellular, which is annoyingly just off the bottom of my screen) and others not at all (like "lock screen", "tap+send", or "theme") once I've set them up initially, and would like them out of the way to make room for the options that I care about.
Click to expand...
Click to collapse
Sorry for being so negative but this is really how I feel and what's wrong with that? I know that not everyone will agree with my views or me with views of others but my negative feed back is feed back just like positive feed back is also feed back. I'm pretty sure that you have your gripes with other things.
I'm just feed up that devs come up with some of the brightest ideas and MS simply ignores them. Tell me what is so hard for them to open the OS just a little more for people to be creative? Seriously? Now the truth is the best substance. And of course if you still don't agree with me that's okay; I won't hold it against you because those are your opinions and the way you feel. Please don't take any of my rants personal as all they are, my personal opinions.

sinister1 said:
I'm just feed up that devs come up with some of the brightest ideas and MS simply ignores them. Tell me what is so hard for them to open the OS just a little more for people to be creative? Seriously?
Click to expand...
Click to collapse
I have to agree with you on this one. There are some understandable things for security's sake, but its ridiculous how complicated it is to customize Windows Phone 8 or even WP7. With WP7, you could only have a static lockscreen (ignoring LockWidgets from WPH) and couldn't set a custom text notification sound (besides MS' and HTC's.) I could add a custom ringtone, but it was a pain to do, period. With WP8, its a tad easier. You can just copy and paste ringtones, lock screens are customizable, and alarm can be customized as well, as well as the battery percentage can be pinned to the lockscreen/start screen. But compared to the other 3 platforms (Andriod, iOS, and now discontinued Symbian) could virtually anything could be changed. I remember when the 7.8 Beta was out and there were swapped fonts in the roms. Its something that no one had even thought about modifying until it was an issue.
I do have to say the native apps ability is appreciated, but it seems that Interop is still an issue (except I have no idea how problematic it still is). I do have to say I don't know much of whats been going on, due to jumping ship getting Verizon's Trophy late in the game (like when I first signed up here) and then finally moved to WP8 with their 928. So I'm kinda in the dark as to what has been added from the GDR1, Nokia's supposed Amber update, whats in GDR2, future FM support, ect. I really just wish that MS would be a little more verbal about whats in WP8's updates. They were bad with WP7 and they aren't any better now.
Another feature that MS is completely missing is Xbox Video. Seems stupid for them to say their experience is coherent between all their devices when its clearly not.

Can u guys tell me ....which phones will get windows 8.1 update .????
Sent from my HTC Explorer A310e using xda app-developers app

Some people don't like customization.
Customization comes with the cost of performance. I had an android with "customization" and whenever i "customized it" it became really, really, really slow.
In order to even have customization working, the system has to waist a lot of CPU cycles on stuff like checking 1000000000000000 settings to figure out what it should render next, swap a gazillion artifacts from storage to memory etc etc.
I want my phone to do what I tell it to do. I don't give a damn about more customization than it already has, and so are 99% of all windows phone users, whom increase in numbers day by day.
If you are going to give feedback disguised as QQ, then you should head over to microsoft's site and make your voice actually count. You complaining here all day, on a freeking developer/hacker forums, will not help!
Windows 8.1 blue will probably loosen up the developers a bit, if they are going to implement all our suggestions. Which will come for all windows phone 8 phones.

@mcosmin: The conecpt the you trade performance for customization really isn't true. Yes, the phone could eke out a trivial amount of better performance by hardcoding its UI styles, but they don't do that. Things like accent colors, background colors, text styles, etc. are all stored in the registry; you don't have to modify a single line of system code to modify or create themes of your own, and they'll run just as fast. Other forms of customization, such as replacing some of the builtin libraries with custom ones, might be slower in certain circumstances, but only if the custom library either added new features (not just new customizations, but actual functionality that wasn't present before) or is simply very poorly coded. The first of those is a tradeoff, the second is easily fixed if people just share their source code.
@sinister1: It's not that I don't agree with you - I do, in fact, and frequently quite vociferously - I just don't see what value you're adding to this conversation by proclaiming it. This thread is to discuss mockups of UI changes to WP8, not to complain about OS lockdown in WP8 and Microsoft's apparent unwillingness to implement some requested changes.

GoodDayToDie said:
@mscosmin: The conecpt the you trade performance for customization really isn't true. Yes, the phone could eke out a trivial amount of better performance by hardcoding its UI styles, but they don't do that. Things like accent colors, background colors, text styles, etc. are all stored in the registry; you don't have to modify a single line of system code to modify or create themes of your own, and they'll run just as fast. Other forms of customization, such as replacing some of the builtin libraries with custom ones, might be slower in certain circumstances, but only if the custom library either added new features (not just new customizations, but actual functionality that wasn't present before) or is simply very poorly coded. The first of those is a tradeoff, the second is easily fixed if people just share their source code.
@sinister1: It's not that I don't agree with you - I do, in fact, and frequently quite vociferously - I just don't see what value you're adding to this conversation by proclaiming it. This thread is to discuss mockups of UI changes to WP8, not to complain about OS lockdown in WP8 and Microsoft's apparent unwillingness to implement some requested changes.
Click to expand...
Click to collapse
And how many people do you think will be able to do proper customization? Windows Phone shouldn't be Android with squares instead of rounded edge widgets.
And solid colors like the ones WP uses will always be faster than a image on the background, or some sort of gradients or whatever they they propose to have around the phone.

How many people will do "proper" customization? As many as want to. Who are you to say what is or is not "proper" for how I want my phone to look?
Of all the things wrong with Android (the battery drain due to background services not exiting automatically, the more stuttery UI on all but the highest-end phones due to poorer optimization, the ability for malicious apps to send premium SMS completely invisibly to the user, etc.) you choose to pick on the customizations? Nobody is suggesting that we want Android with WP-like tiles; in that case we would have bought Android phones and installed one of the several Metro-style home screen customizations. On the other hand, if I want a Windows Phone with "rounded edge widgets" and am willing to put in the effort to develop them, I see no reason I shouldn't be allowed to.
WP uses the graphics processor for its UI. Those "solid colors" are just textures like any other. A gradient, an image, a partially translucent image... they're all the same to the GPU. The performance cost would be unmeasurably small.

GoodDayToDie said:
How many people will do "proper" customization? As many as want to. Who are you to say what is or is not "proper" for how I want my phone to look?
Of all the things wrong with Android (the battery drain due to background services not exiting automatically, the more stuttery UI on all but the highest-end phones due to poorer optimization, the ability for malicious apps to send premium SMS completely invisibly to the user, etc.) you choose to pick on the customizations? Nobody is suggesting that we want Android with WP-like tiles; in that case we would have bought Android phones and installed one of the several Metro-style home screen customizations. On the other hand, if I want a Windows Phone with "rounded edge widgets" and am willing to put in the effort to develop them, I see no reason I shouldn't be allowed to.
WP uses the graphics processor for its UI. Those "solid colors" are just textures like any other. A gradient, an image, a partially translucent image... they're all the same to the GPU. The performance cost would be unmeasurably small.
Click to expand...
Click to collapse
It's not about the GPU.
It's about the CPU. The more complex the image is, the bigger the size, the more time wasted for CPU to process it.
Add to that the fact it needs to purge/load from memory several times a day (in the case of a background wallpaper for startscreen), and the performance loss and battery drain is suddenly no longer unmeasurably small.

You're talking about a difference of microseconds. Not milliseconds, microseconds. Several times a day. And telling me that this is *not* below the noise threshold of any measurement system we have today, never mind human perception?!?
Also, consider people who use apps (with their own tiles, not just system tiles that are mostly blank and therefore rendered as mostly a solid color) on their lock screen. You know, the whole "meet <person>" advertising campaign Microsoft has been running for this OS? Those app tiles take just as long for the CPU to decode and send the texture to the GPU as the customized tiles we're talking about here...
Except, customized tiles aren't even the point. If you don't want to customize your tiles because saving a few millionths of a second per day - a saving which will never amount to a whole second over your entire lifetime, much less that of the phone - you don't have to. The rest of us want features; customization is merely one of those features. It gets a lot of discussion because:
A) It's an obvious feature to have. MS advertises personalization. People like being able to change how things look, be it their clothing or their front yard or their Windows background. For some reason, though, they can't change their Windows Phone background.
B) It's really, really simple to implement. I mean, there are tons of third party apps, some rather sophisticated, to do this. Microsoft doesn't have to jump through the crazy hoops that we did, and they have the documentation on how the OS works as well.
c) It really does not affect performance. There's no cost. Look at the custom themes and custom system tray icons and so forth on WP7, and try telling me with a straight face the percentage by which it impacts performance to use them.

GoodDayToDie said:
You're talking about a difference of microseconds. Not milliseconds, microseconds. Several times a day. And telling me that this is *not* below the noise threshold of any measurement system we have today, never mind human perception?!?
Also, consider people who use apps (with their own tiles, not just system tiles that are mostly blank and therefore rendered as mostly a solid color) on their lock screen. You know, the whole "meet <person>" advertising campaign Microsoft has been running for this OS? Those app tiles take just as long for the CPU to decode and send the texture to the GPU as the customized tiles we're talking about here...
Except, customized tiles aren't even the point. If you don't want to customize your tiles because saving a few millionths of a second per day - a saving which will never amount to a whole second over your entire lifetime, much less that of the phone - you don't have to. The rest of us want features; customization is merely one of those features. It gets a lot of discussion because:
A) It's an obvious feature to have. MS advertises personalization. People like being able to change how things look, be it their clothing or their front yard or their Windows background. For some reason, though, they can't change their Windows Phone background.
B) It's really, really simple to implement. I mean, there are tons of third party apps, some rather sophisticated, to do this. Microsoft doesn't have to jump through the crazy hoops that we did, and they have the documentation on how the OS works as well.
c) It really does not affect performance. There's no cost. Look at the custom themes and custom system tray icons and so forth on WP7, and try telling me with a straight face the percentage by which it impacts performance to use them.
Click to expand...
Click to collapse
Don't compare the WP7 theme mods and stuff like that which were made by hackers that knew what they were doing.
If Microsoft allows this officially on the marketplace, it will be flooded by poor apps.
Anyway, we seem to not be talking about the same thing. We should let it rest.

EPD x keyboard = outdoor word processing?

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

[Q] Laggy screen response/sensitivity on T280

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

Nougat Screenshots

anyone who did the nougat update, can you post some screenshots? i am debating whether to do the upgrade or leave well enough alone. one post mentioned that th recent apps window was sub-standard. any other good and bad?

mark2573 said:
anyone who did the nougat update, can you post some screenshots? i am debating whether to do the upgrade or leave well enough alone. one post mentioned that th recent apps window was sub-standard. any other good and bad?
Click to expand...
Click to collapse
Yeah, I'm curious as well..i want to know if this update is going to be worth it

I did update to Nougat. My use is very limited but I find battery timing much improved and multi window is way better.

first of all - if you're satisfied with your device as it is don't update! It (unfortunately) doesn't get any better. They removed two important features - at least for me. There are no floating apps anymore - so if you want to use the small version of (for example) the google play music player while you're browsing you will have to use the splitscreen with dramatically decreased space for your browser left. So basically this means less convenience for you. The other thing is the (absolutely) useless "recent apps" view. In the past the whole screen was used by displaying the apps as tiles - now you only see them in the (for big tablet screens) useless card view.
Sorry - i always hate it when something really good just gets abandoned and replaced by something far inferior
I also found out, that manufacturers of 10"+ Tablets are encouraged to implement the native Android N freeform mode - so why has lenovo left this out of their update? I hope it gets back on the device with a later update.
P.S.: Android 7.0 CDD states that:
Device implementations with screen size xlarge SHOULD support freeform mode.
In the parlance of this CDD, there appear to be three levels of endorsement: SHOULD, STRONLY ENCOURAGED, and MUST. SHOULD is the weakest of the three, but it is still an endorsement.

NiffStipples said:
first of all - if you're satisfied with your device as it is don't update! It (unfortunately) doesn't get any better. They removed two important features - at least for me. There are no floating apps anymore - so if you want to use the small version of (for example) the google play music player while you're browsing you will have to use the splitscreen with dramatically decreased space for your browser left. So basically this means less convenience for you. The other thing is the (absolutely) useless "recent apps" view. In the past the whole screen was used by displaying the apps as tiles - now you only see them in the (for big tablet screens) useless card view.
Sorry - i always hate it when something really good just gets abandoned and replaced by something far inferior
I also found out, that manufacturers of 10"+ Tablets are encouraged to implement the native Android N freeform mode - so why has lenovo left this out of their update? I hope it gets back on the device with a later update.
P.S.: Android 7.0 CDD states that:
Device implementations with screen size xlarge SHOULD support freeform mode.
In the parlance of this CDD, there appear to be three levels of endorsement: SHOULD, STRONLY ENCOURAGED, and MUST. SHOULD is the weakest of the three, but it is still an endorsement.
Click to expand...
Click to collapse
Thanks buddy. I think I'm better off skipping this update.

Wrong, wrong, wrong
NiffStipples said:
first of all - if you're satisfied with your device as it is don't update! It (unfortunately) doesn't get any better. They removed two important features - at least for me. There are no floating apps anymore - so if you want to use the small version of (for example) the google play music player while you're browsing you will have to use the splitscreen with dramatically decreased space for your browser left. So basically this means less convenience for you. The other thing is the (absolutely) useless "recent apps" view. In the past the whole screen was used by displaying the apps as tiles - now you only see them in the (for big tablet screens) useless card view.
Sorry - i always hate it when something really good just gets abandoned and replaced by something far inferior
I also found out, that manufacturers of 10"+ Tablets are encouraged to implement the native Android N freeform mode - so why has lenovo left this out of their update? I hope it gets back on the device with a later update.
P.S.: Android 7.0 CDD states that:
Device implementations with screen size xlarge SHOULD support freeform mode.
In the parlance of this CDD, there appear to be three levels of endorsement: SHOULD, STRONLY ENCOURAGED, and MUST. SHOULD is the weakest of the three, but it is still an endorsement.
Click to expand...
Click to collapse
First of all, updates are really important for android devices in general. And especially for manufacturers like Lenovo which is known to let their product outdated pretty early. Personally, I'm impressed this time they updated to Android N even before schedule, and I'm hoping they continue releasing updates not to let this amazing product die.
As for the features you talk about:
1) floating windows in freeform is natively supported in android N and just need to be enabled in developer options (one of the last entries under App category). You can install "Taskbar" app to launch all of your apps in window mode by using the native method, and resize them as you like by dragging on the bottom-right corner (which previously was not possible).
2) It is true that Task manager with tiles view was a more clean way to switch between apps on this device, but the needing of double-pressing the TAB button when alt-tabbing beween apps, always made it uneffective and uncomfortable to me. Now ALT-TAB switch between apps just flawlessly as in a standard computer. Hence, i'm really happy with that.
3) I find overall performance have gotten slightly better with the recent N update: i can notice that in the UI and in games too! other users on other threads are talking about a slightly better battery performance too, so it seems like they optimized the hardware support somehow.

morrolinux said:
First of all, updates are really important for android devices in general. And especially for manufacturers like Lenovo which is known to let their product outdated pretty early. Personally, I'm impressed this time they updated to Android N even before schedule, and I'm hoping they continue releasing updates not to let this amazing product die.
As for the features you talk about:
1) floating windows in freeform is natively supported in android N and just need to be enabled in developer options (one of the last entries under App category). You can install "Taskbar" app to launch all of your apps in window mode by using the native method, and resize them as you like by dragging on the bottom-right corner (which previously was not possible).
2) It is true that Task manager with tiles view was a more clean way to switch between apps on this device, but the needing of double-pressing the TAB button when alt-tabbing beween apps, always made it uneffective and uncomfortable to me. Now ALT-TAB switch between apps just flawlessly as in a standard computer. Hence, i'm really happy with that.
3) I find overall performance have gotten slightly better with the recent N update: i can notice that in the UI and in games too! other users on other threads are talking about a slightly better battery performance too, so it seems like they optimized the hardware support somehow.
Click to expand...
Click to collapse
Thanks for the suggestion of taskbar - i've already tried it before and imho it's just not that convenient as a rom included solution. Beside the fact that you would have to use an unnecessary extra app for a native android function, it's not really intuitive in it's handling - but i have to admit, that every user will see that different depending on their needs My question is just why lenovo hasn't implemented this standard feature in a neat and handy way?
Speaking of different user needs/requirements - i've personally never used the Alt-Tab combi on my tab. In my daily use i use it most of the time in tent mode without the keyboard.
As to the performance - i didn't really noticed a change here. But in my opinion it was already really snappy before the update so maybe i can't rate that improvement. Maybe the animations between app switches got nicer but it's possible that i deactivated them before the update by myself - so nevermind

Guys, can somebody upload Noughat update otapackage?
I do not have a device but i need this to borrow graphic drivers.

After update to Nougat, battery drain in idle status doesn`t happen anymore. After a day idle, it takes only like 1-2% of battery. At least it is worth to me.