Related
Sky maps worked wonderfully when I first got my tablet a few months ago. However, flashing custom roms seems to have royally screwed up the tilt sensors (I have tried multiple different roms, nothing seems to address it). Compass is okay, but X and Y axes are reversed (i.e. it pitches when it should roll, and vice versa). This happens in both landscape and portrait.
Anyone run into this before, or have any idea how to proceed?
playing SpeedX 3d the tilt sensors worth great, playing table labyrinth where you have to roll the ball through the maze to reach the other side is totally FUBAR, the sensors are opposite of each other which makes it impossible to plays.
So with my finding it works fine with some games and terrible with others.
I noticed the same issue on the a100.
SoHaunted said:
playing SpeedX 3d the tilt sensors worth great, playing table labyrinth where you have to roll the ball through the maze to reach the other side is totally FUBAR, the sensors are opposite of each other which makes it impossible to plays.
So with my finding it works fine with some games and terrible with others.
Click to expand...
Click to collapse
Admittedly, I haven't tried it with too many other apps, but those that I have are problematic (sky maps and several sensor-reading apps). It's frustrating because it used to work just fine with sky maps.
Which version of HC are y'all using, 3.1 or 3.2.
On 3.2 I'm having no problems at all.
Just wondering?
Check out "GPS Status" app on the market, it has an option to calibrate the pitch and roll sensors, maybe you just need a calibration..
It will also show the actual pitch/roll values which may help.
kiwi_mat said:
Check out "GPS Status" app on the market, it has an option to calibrate the pitch and roll sensors, maybe you just need a calibration..
It will also show the actual pitch/roll values which may help.
Click to expand...
Click to collapse
"A Tilt Labrynth" also has a built in calibration tool as well
If I'm not mistaken, those calibration utilities only affect the program that they're part of - they don't have any effect on global settings.
[Edit: I'm using 3.2 (Taboonay 2.1b), though the problem was also present on several other 3.1 and 3.2 roms]
I'm running Skeye and Mobile Observatory on my A500 and havent noticed any problems at all with the x/y axis' being off. Honestly, I haven't paid that much attention since I also have both programs installed on my phone and mostly use it instead since I can mount it to my scope for push-to guidance. But just locating Polaris and other well known objects seem to be spot-on. May want to try another program and see if that fixes the issue.
fasteddy86 said:
If I'm not mistaken, those calibration utilities only affect the program that they're part of - they don't have any effect on global settings.
[Edit: I'm using 3.2 (Taboonay 2.1b), though the problem was also present on several other 3.1 and 3.2 roms]
Click to expand...
Click to collapse
as that maybe true it would help people figure out of the calibration is off on the tablet. if the calibration is off then we can look into why its happening in stead of what apps are having the issues
Timelord83 said:
as that maybe true it would help people figure out of the calibration is off on the tablet. if the calibration is off then we can look into why its happening in stead of what apps are having the issues
Click to expand...
Click to collapse
Well there's no question that my sensors are off. The only apps that work are those that come bundled with a calibration function. There's a long-standing defect logged with elgoog about the fact that there's no easy way to calibrate, but they've not addressed it yet.
I know some phones come with a calibration function, and others at least have files where one can change the values...
Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Shissu said:
Hello, i installed http://forum.xda-developers.com/showthread.php?t=1906507 kernel, adn i wanted to test FastMode.
And i noticed than is useless, because i have horrible ghosting effects - it's hard to read anything in browser.
It's normal?
Click to expand...
Click to collapse
The initial ghosting occurs (at least in fastmode2.apk) because the apk does not perform 1 full screen refresh after the start (yet).
Try to lock and than unlock the device after starting fastmode2.apk.
The other reason may be that you have 'NoRefresh' installed and it autostarts on boot.
Never use both NoRefresh and FastMode at the same time.Kill one or another using TaskXP (or similar apk).
Edit:
Yeah. I have checked it. Applying 1 full refresh helps a lot. (you can also try do display a white full screen image to get the same result).
If you have time you can edit the source of fastmode2.apk. I won't do this during this week for sure.
osowiecki said:
Applying 1 full refresh DOES NOT helped me.
Click to expand...
Click to collapse
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Mnurlan said:
I do not mean any offence but FastMode2 does the trick but with terrible ghosting. Nevertheless thanx to osowiecki
Click to expand...
Click to collapse
What I meant by performing a 1 full refresh :
1. you can see extensive ghosting
2. I push the lock button, the screen blinks (full refresh)
3. After unlocking there is no (a little) ghosting effect.
It would be nice to force fullscreen refresh after fast mode gets activated.
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Mnurlan said:
Alas, That is not an acceptable solution for me (still poorly readable), I think the only way to get the NST working with normal resolution is to rollback to factory settings and install the FW with which this mode is working.
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
"lurk moar"
stock image 1.1 for CWM
https://code.google.com/p/nst-recovery/downloads/detail?name=nook_1_1_update_cwm.zip&can=2&q=
Also..why not use NoRefresh then?
Both modes work on kernel v166.
Mnurlan said:
Now I realize that there is no way of getting any FW earlier than 1.2.1. I am stuck.
Click to expand...
Click to collapse
1.1.2 FW straight from B&N
Also..why not use NoRefresh then?
Click to expand...
Click to collapse
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Mnurlan said:
Yes, agree, I am a "lurk more" and thank you for the link - I would never be able to find it myself. We, Russian speaking people, used to say "to make someone's nose pointed in the right direction" . The only thing is I am not sure now that downgrading the FW is the right thing to do as they say that the performance was improved in 1.2.1.
I've tried every NoRefresh I could find, even some NoRefreshToggle-debug2.apk, they seem to be having no effect whatsoever so far.
2 straygecko - link seems to be incorrect. Thank you nevertheless.
Click to expand...
Click to collapse
What do you mean by "no effect"?
You should run NoRefresh once (it starts it's deamon), then you run in the second time to get results.
By default the contrast options are set to "auto". Go to "NoRefresh Settings"->"Contrast Settings" and select "appear always".
Add shortcut to NoRefresh to 'quicknav' bar or any other place that you can always reach on the screen.
NoRefresh works only within the application that it was started with. When you change the focus to another apk, it stops.
If you are on stock kernel and 'NoRefreshToggle-debug2.apk' does not work, that means you don't have FW 1.2.1 installed.
Seems like I've now got a bricked device, neither Noogie, nor CWM can help - my PC doesn't "see" my NST anymore and I can't replace the uImage, the NST itself is working now, but this means I will not be able even to restore it to a saved image:crying:
A day later I've found out that for some reason my desktop PC ("floortop") refuses to "recognize" my NST (although "sees" it alright without Noogie or CWM), then I have managed to replace uImage on my NST using my son's laptop, yet FastMode is not working, same as NoRefresh, FW 1.2.1 (I'm positive), FastMode2 works fine but resulting view renders it useless.
Update: 26.04.2013 - NoRefresh is working, but the resulting resolution renders it also almost unusable. Just delivering my SitRep, not whining. Installed kernel 166 with CWM.
dots
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
eraycr said:
I have same problem in addition dots. I tried different software versions(1.1.0-1.2.1), different root methods(nook manager, touchnooter, minimal touch) and also different kernels with all variations. But no change. Screen resolution is awful because of dots and ghosting. What the wrong?
View attachment 2413476
View attachment 2413477
View attachment 2413478
Click to expand...
Click to collapse
Same here, try many kernels.
I thought it was normal operation of this modification. Oo
Well, I'm late to the party, having generated an apparently useless post here. But I agree with you all who are underwhelmed with the screen appearance using either of these two mods. I like the sprightly Android performance of the NST in FastMode, but there really is a lot of visual "noise" on the screen. NoRefresh is even worse on my Nook. I can hardly get an image at the beginning, the screen is almost an all white overlay so the contrast buttons don't do me any good because I can't see much through the white film (sort of like a bad cataract!). Scrolling a bit gradually brings in a fractured image and by the time the app has closed.
I've tried disabling the NoRefresh app entirely to see if FastMode would work better. No deal. Same poor image quality. Nothing like some of the YouTube videos I've seen.
FW 1.21, kernal 166.
But who knows? At least multi-touch is nice.
I know someone brought up this bug before, and someone else also offered a temporary fix for it. I just wanna keep this issue alive since the MAIN reason why I spent 500 plus clams for this tablet was for the S-Note note taking application. Reason: I have a year of weekly meeting notes I accumulated using my Note 2, and want to keep them, and keep adding to them.
The issue: The auto-brightness feature is flawed when entering a s-note. Not entering the app itself, but actually going into a past s-note that was previously written. The tablet would become at full brightness.
The temp fix: Before you enter S-Note, turn off auto-brightness from the pull down notification menu. Put the tablet in 40% brightness, then enter S-Note.
I don't want to sound like I'm hating on Samsung. I love my Note 10.1 2014 edition. I just wish this top-of-the-shelf tablet, that supposed to be better than iPad, had this issue fixed prior to selling the tablets.
Try Lecture Notes, I gave up on S note
Auto brightness is useless. Don't use it.
Have you tried "Note Anytime"??
It even syncs notes between devices....
Enviado desde mi GT-N7100 mediante Tapatalk
lawalty said:
I know someone brought up this bug before, and someone else also offered a temporary fix for it. I just wanna keep this issue alive since the MAIN reason why I spent 500 plus clams for this tablet was for the S-Note note taking application. Reason: I have a year of weekly meeting notes I accumulated using my Note 2, and want to keep them, and keep adding to them.
The issue: The auto-brightness feature is flawed when entering a s-note. Not entering the app itself, but actually going into a past s-note that was previously written. The tablet would become at full brightness.
The temp fix: Before you enter S-Note, turn off auto-brightness from the pull down notification menu. Put the tablet in 40% brightness, then enter S-Note.
I don't want to sound like I'm hating on Samsung. I love my Note 10.1 2014 edition. I just wish this top-of-the-shelf tablet, that supposed to be better than iPad, had this issue fixed prior to selling the tablets.
Click to expand...
Click to collapse
I also bought this tablet just for using S-Note, the bug is unfortunate
Search for "Lux" in the play store (sorry, I can't link it since my account is new) - this application gives brightness detection and control.
I turned off the native brightness detection (the Lux program seems to work better anyways)
Now, my S-note detects brightness properly.
jonleez said:
I also bought this tablet just for using S-Note, the bug is unfortunate
Search for "Lux" in the play store (sorry, I can't link it since my account is new) - this application gives brightness detection and control.
I turned off the native brightness detection (the Lux program seems to work better anyways)
Now, my S-note detects brightness properly.
Click to expand...
Click to collapse
Yeah Lux Brightness control works great, just disable the native brightness control. You might need to tweak the Lux brightness values initially but is very easy and once set it works fine.
Installed Lollipop last night and a few things that I found are working/not working. Let's get a list going here.
1. H+ icon no longer shows up. (ATT)
2. Feels like a new phone performance wise.
3. Home Launcher App no longer seems to work. (https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en)
Cast screen option is now available in the notification pull down, but it still doesn't recognize the Chromecast.
ART uses a lot more space for apps, so a microSD card is now a must. Probably why Moto added it.
Camera doesn't seem to have any improvements. Not worse, but I'm not seeing anything better either.
Sometimes specific apps (like Skype for example) don't seem to use both speakers leaving the sound very quiet.
Screen pining option in security is awesome
Sent from my Galaxy Nexus using xda premium
Hey, I'll paste the questions I leaved in a thread I created but doesn't seem so popular:
First and foremost, I'm curious about the new memory management in this Release. As you can see in this threads 1 XDA Thread 2 (Official Motorola Forums one) the problems with RAM management in KitKat were MASSIVE.
- How do you feel it is as of right now? It's still there? It's a little better?
- How does the CPU respond? Could you run an Antutu Benchmark to compare with KitKat?
- I know it's a little early to ask, but I'm curious about Project Volta. Do you notice more battery life?
Click to expand...
Click to collapse
THANKS !!!
jarbro said:
Installed Lollipop last night and a few things that I found are working/not working. Let's get a list going here.
1. H+ icon no longer shows up. (ATT)
2. Feels like a new phone performance wise.
3. Home Launcher App no longer seems to work. (https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en)
Click to expand...
Click to collapse
Have noticed performance improvements? Such as better memory management, improved responsiveness, faster app loadings etc. ?
On 4.4.4, I can't run Facebook and Chrome simultaneously without one getting kicked out of memory
jarbro said:
Installed Lollipop last night and a few things that I found are working/not working. Let's get a list going here.
1. H+ icon no longer shows up. (ATT)
2. Feels like a new phone performance wise.
3. Home Launcher App no longer seems to work. (https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en)
Click to expand...
Click to collapse
What about battery usage? Does the application optimizing occur at every boot?
ksuuk said:
What about battery usage? Does the application optimizing occur at every boot?
Click to expand...
Click to collapse
100% at 8am. Was down to 10% around 2:30PM after heavy usage. Definitely not real world use. Mostly playing around with Lollipop.
Application optimization does not happen at boot like it did w/ ART on 4.4.4.
I'd like to note, it took my phone nearly 45 minutes to upgrade from 4.4.4 > Lollipop.
jarbro said:
100% at 8am. Was down to 10% around 2:30PM after heavy usage. Definitely not real world use. Mostly playing around with Lollipop.
Application optimization does not happen at boot like it did w/ ART on 4.4.4.
I'd like to note, it took my phone nearly 45 minutes to upgrade from 4.4.4 > Lollipop.
Click to expand...
Click to collapse
It would appear your lolly got well and truly licked...
L LLIP P
Can you test some more things, like a benchmark or something just to see, and more impressions about the lag of open the menu?
I waded through all the spam and robotically dubbed crap on YouTube, and FINALLY found someone who's actually bothered to make a brief video... so here it is:
Has anyone else noticed not being able to access the camera from the lockscreen on Lollipop?
My thoughts on Lollipop 5.0:
-Booting the phone takes about 30 seconds. I have a lot of apps on the SD card, and they take a while to become available. Perhaps 2 minutes. I had to move a lot of apps to the SD card to get room for the update, so I can't compare before and after times for finding apps on the SD.
-When the phone was updating to Lollipop it said it optimized 105 apps. It does not optimize on every boot. I'm pretty sure apps on the SD card were not optimized based on number of apps.
-Music (Pandora and Play Music) still stops playing in the background when I launch some apps. The suspected 'memory leak', memory management problem, or whatever the cause, has not been fixed. So no apparent change there.
-If I create an app folder with apps on the removable SD, those apps still do not reappear in the folders when I restart the phone. No change.
-App-specific notifications are awesome. I have 'Subway Surfers' on my phone because my kids like the game. I hate getting notifications every day for an app I don't even play. I have disabled notifications for that app. Definate positive change.
-I use an app called 'Notification Toggle' to add toggles for skipping tracks, camera, battery life with numbered %, turning on wifi and cell data, etc. The Cell Data toggle doesn't work any more, it takes me to a screen that can be used to turn on/off data roaming but not data all together. Hopefully that will be fixed. The notification screen update already gives me another option (see my next comment).
-The pull-down notification menu can be pulled down again to show some settings that partly replace the 'Notification Toggle' app I just mentioned, including turning cell data on/off. It's a nice feature. I wish it were customizable. Definate positive change; it doesn't quite replace 3rd party apps for me, but that's part of the Android customizable experience.
-It takes longer to unlock. The unlock pattern/code input has been replaced by notifications, you need to swipe up before unlocking. Minor change but definitely not an improvement for me.
-Stability and responsiveness are good. I haven't noticed any lag but I don't remember noticing lage on 4.4.
-Battery life? I'm a compulsive phone charger, so I don't know yet. I like the new battery life screen. It shows charge over time like it used to, and it also shows projected battery life. It says I have 10 hours left, after using the phone for about an hour looking at settings, locking/unlocking the phone while on WiFi streaming Pandora.
-Lockscreen notifications have the following settings:
Show all notification content will show content in new text messages and what is playing on Pandora or Play music; in Play Music it lets me skip to the next song without unlocking; I can't change tracks in Pandora from the unlock screen. Annoying change for me.
Hide Sensitive content in Notifications lets me know I got a text but doesn't show the message; I can see what is playing and skip tracks in Play Music but not Pandora
Show Nothing shows... nothing.
I wish I could select which apps would show their content on the lock screen; in my mind what I am playing in Pandora is not nearly as sensitive as what texts I receive.
If I get a text and there are multiple notifications on the lock screen, or if I get more than one text,it won't show the content of the texts. No scrolling to fit more notifications (like the notifications shade). So if you have a lot going on, lock screen notifications become sort of useless, and that's when they might be the most useful.
I used to be able to press the power button and skip to the next pandora track from the unlock screen. Two actions. Now: (1) I press the power button, (2) swipe up, (3) enter the unlock pattern, (4) open Pandora, and (5) skip to the next track. Convenience has suffered.
People will have different opinions, but for me personally the whole lock screen experience is a step backwards. I think there are some simple fixes that could make it very good, and I hope this is a bad start to a good feature (i.e. waiting for 5.0.1).
Memory leak/bug is still there Oh god why
@mike_ekim
can you check if the usb otg bug is still there?
mike_ekim said:
-It takes longer to unlock. The unlock pattern/code input has been replaced by notifications, you need to swipe up before unlocking. Minor change but definitely not an improvement for me.
Click to expand...
Click to collapse
Thanks, I asked if this was the case in another thread, nice to have it confirmed but wasn't the answer I wanted.
From my impression the KitKat lockscreen is perhaps better for people like us (it is for me), you can easily see your notifications but not see any content just the icons at the top, music playback controls are easily accessible and the pattern/PIN is displayed without a swipe.
thisisjason said:
Has anyone else noticed not being able to access the camera from the lockscreen on Lollipop?
Click to expand...
Click to collapse
I can get to the camera app from the lock screen without unlocking, take pics from front and rear camera, shoot video, and view the gallery pics/videos I took from THAT LOCKED SESSION ONLY. I can't see all the other pics/videos on the phone.
A minute later I accessed camera without unlocking the phone again. I could NOT see the pics that I took a minute ago with a locked phone. In other words, if I take pics with a locked phone those new pics are still private, as long as I turn off the screen again. Maybe that's the default Lollipop behavior, but I'm glad it works that way.
Edit: the phone wants to back up the photos that i took with the screen locked. I need to look into this. I deleted those pics i.e. I selected 'delete everywhere'. If someone takes pics with my phone, will they be backed up to online folders/tools that I share? I'm just a simple caveman lawyer, your new technology frightens me. I just copy/save my pics manually, so I don't even understand how backup works. I'm pretty sure backup was turned backup off in Jelly Bean.
Another edit: The Photos app says that backup is for 'my eyes only'. As long as no one can take a pervy pic with my locked phone and share it with the world, I'm ok. Because we all know how safe pics on our phones are.
bhavin192 said:
Memory leak/bug is still there Oh god why
@mike_ekim
can you check if the usb otg bug is still there?
Click to expand...
Click to collapse
Sorry, I don't have a thumb drive or otg cable handy. I never heard of the problem till you mentioned it, I guess I don't use thumb drives with my phone.
Different subject:
I connected the phone to my computer with USB debugging turned on, and I got this driver error:
Device driver software was not successfully installed
Motorola ADB Interface X No driver found
It's an old problem and looks like getting the error is expected, but I'm busy at work and can't be bothered to look into it for now. File explorer from the PC works fine. I have other android toys, I don't like messing with my main phone so I don't need ADB anyways. I honestly think I've never even put this phone into USB Debug before today.
mike_ekim said:
I can get to the camera app from the lock screen without unlocking, take pics from front and rear camera, shoot video, and view the gallery pics/videos I took from THAT LOCKED SESSION ONLY. I can't see all the other pics/videos on the phone.
A minute later I accessed camera without unlocking the phone again. I could NOT see the pics that I took a minute ago with a locked phone. In other words, if I take pics with a locked phone those new pics are still private, as long as I turn off the screen again. Maybe that's the default Lollipop behavior, but I'm glad it works that way.
Edit: the phone wants to back up the photos that i took with the screen locked. I need to look into this. I deleted those pics i.e. I selected 'delete everywhere'. If someone takes pics with my phone, will they be backed up to online folders/tools that I share? I'm just a simple caveman lawyer, your new technology frightens me. I just copy/save my pics manually, so I don't even understand how backup works. I'm pretty sure backup was turned backup off in Jelly Bean.
Another edit: The Photos app says that backup is for 'my eyes only'. As long as no one can take a pervy pic with my locked phone and share it with the world, I'm ok. Because we all know how safe pics on our phones are.
Click to expand...
Click to collapse
Thanks, weird that it's not working for me. If I restart the phone, it will work the very first time I'm on the lockscreen and swipe into the camera, but on subsequent attempt I get a black screen with the icons for switching between front and back cameras and for shooting video, but none of the controls work.
thisisjason said:
Thanks, weird that it's not working for me. If I restart the phone, it will work the very first time I'm on the lockscreen and swipe into the camera, but on subsequent attempt I get a black screen with the icons for switching between front and back cameras and for shooting video, but none of the controls work.
Click to expand...
Click to collapse
Interesting, that's an inconsistency between out phones. I can enter, exit, and re-enter the camera app repeatedly without unlocking the phone, turn the screen off and on again, and use the camera again without unlocking.
---------- Post added at 12:36 PM ---------- Previous post was at 12:23 PM ----------
One more thing: the home screen redraw issue still happens, but less often. For example I just used chrome browser briefly, went home and the screen didn't redraw. Same with Play Music.
I loaded Clash of Clans, collected some gold/elixir, donated some troops, went to home screen and the screen had to redraw. Exiting a lightweight game like 2048 does not cause the home screen to redraw (so far). Overall the home screen seems to redraw less often.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
One more thing: the home screen redraw issue still happens, but less often. For example I just used chrome browser briefly, went home and the screen didn't redraw. Same with Play Music.
I loaded Clash of Clans, collected some gold/elixir, donated some troops, went to home screen and the screen had to redraw. Exiting a lightweight game like 2048 does not cause the home screen to redraw (so far). Overall the home screen seems to redraw less often.
Actually, another one more thing:
In settings-->developer options-->Process stats: I got the message "device memory is currently critical" I killed a few apps (including Play store, play music, all the Motorola apps) and got 403 MB ram available. Settings is using 70MB, Notification Toggle is using 3MB, Swipe is using 26MB. I went back to Process Stats and it now says 'Device memory is currently normal". Sorry, I didn't take not of how much memory was available before killing apps.
---------- Post added at 12:56 PM ---------- Previous post was at 12:45 PM ----------
Reboot:
Unlock screen 50 seconds after pressing power
Widgets active 1 min 15 seconds after pressing power
Apps on SD available in app drawer 2 minutes 30 seconds after pressing power. I have 36 apps on my SD card, it's a 16GB card with 5.4GB available (lots of media) and I believe it's a class 4 or class 6).
On boot I had 408MB ram free. After killing some apps I have 453 MB free; settings using 70MB, Swype 24MB, and Google Search 15MB. MotoCare using 15MB and if I kill it it just restarts. I don't know if Settings always uses RAM or if I get that RAM back when I exit Settings.
How much more space does ART take?
You can try ART on KK... but on my XT1068 Dalvik 2.6Gb free space / ART 2.0Gb free space.
I updated my phone yesterday.
It's now faster. The lollipop is so beautiful.
The only problem is that yes I can't see
H+ icon anymore. Does anyone know what ?
Sent from my XT1064 using XDA Free mobile app
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