Related
My Gtab has intermittent wake from sleep failures, where it then resets on the next button push. You can tell it's going to fail because you see a flash of the "desktop" the instant you push the button, then it goes dark. Next push gets you the birds!
Is this unique to my tablet?
running Vegan B5.1, but it has happened on other Roms.
Jim
Not unique. I get a similar thing and I'm running VeganTAB b5.1. Usually it doesn't shut right down, but occasionally it does. I also get lag when putting it to sleep. The screen seems to have two stages. First it blacks out for about a second, then it turns off. The only problem is that the digitizer seems to still be active for that one second so if I brush the screen or buttons it wakes up. Not a big issue, but a little annoying.
Prof-KOS said:
Not unique. I get a similar thing and I'm running VeganTAB b5.1. Usually it doesn't shut right down, but occasionally it does. I also get lag when putting it to sleep. The screen seems to have two stages. First it blacks out for about a second, then it turns off. The only problem is that the digitizer seems to still be active for that one second so if I brush the screen or buttons it wakes up. Not a big issue, but a little annoying.
Click to expand...
Click to collapse
Well, the cold resets are annoying, everything I had open is gone. You do not get the resets?
jmdearras said:
My Gtab has intermittent wake from sleep failures, where it then resets on the next button push. You can tell it's going to fail because you see a flash of the "desktop" the instant you push the button, then it goes dark. Next push gets you the birds!
Is this unique to my tablet?
running Vegan B5.1, but it has happened on other Roms.
Jim
Click to expand...
Click to collapse
EXACTLY the same symptoms and problems here too, I've seen this on both the ZPad and TNTL 3.0 ROMs, do I'm pretty sure it's not limited to just the Vegan.
Justin
Turbo4V said:
EXACTLY the same symptoms and problems here too, I've seen this on both the ZPad and TNTL 3.0 ROMs, do I'm pretty sure it's not limited to just the Vegan.
Justin
Click to expand...
Click to collapse
Thanks. I was more concerned it was limited to my hardware! Software can be fixed.
Hi, i had the same issue and changed the endbutton behaviour in spare parts to "home, then sleep". Haven't had the problem since then. Maybe worth a try.
jmdearras said:
Well, the cold resets are annoying, everything I had open is gone. You do not get the resets?
Click to expand...
Click to collapse
I don't get the resets often. They happen, but almost every time it wakes properly it seems to register a second button press and brings up the power menu. Not a big deal because I can just cancel out of it, but it's definitely strange.
DaMan said:
Hi, i had the same issue and changed the endbutton behaviour in spare parts to "home, then sleep". Haven't had the problem since then. Maybe worth a try.
Click to expand...
Click to collapse
Ah, great suggestion DaMan. I think the kernel issues sometimes causing this problem were fixed with our lagfix. But there's still some slightly flaky behavior with the Power button. Changing the Endbutton behavior as you suggested in Spare Parts seems to reduce the tendency for the power button to bring up the shutdown menu when waking up, which I believe is the root cause of this problem.
Everybody should change that setting.
DaMan said:
Hi, i had the same issue and changed the endbutton behaviour in spare parts to "home, then sleep". Haven't had the problem since then. Maybe worth a try.
Click to expand...
Click to collapse
I tried that, but it did not seem to help.
anyone else have any ideas how to fix this annoying problem?
Hi guys,
I read about the keyboard isssues the transformer had. Like battery issues, trackpad issues, etc. For some of these issues it has to be send to Asus.
Recently I got one from a mate in the US, and I'm in China, so assume I cannot be helped in China (seriously, its next to impossible to get after market help in China).
So, are there firmware updates that resolve these issues before they become apparent, or do I really need to send it to asus for modification? Or have Asus addressed some of these issues already in the docks? If so, from what S/N onwards is this the case?
the one real issue is the dock prevents the tablet from going into deep sleep. so if you don't have battery issues with the dock, you don't need to modification. this "fix" however requires that you send the dock to asus.
i don't know what other issues you're talking about (you might want to be more specific)...but the only other consistent complaint with the keyboard is the lag when using in stock browser. this is a software issue, and not one with the dock.
Sent from my Transformer TF101 using Tapatalk
ok, thx. So deep sleep, is this doen automatically? is that the problem, or is it also present when I short-click the power button to switch off the display?
For teh other issues, yes, i think it was related to lag, an inresponsiveness. but if this is in-browser, an dnot a dock issue, then I'm not concerned.
i'm a bit confused what your question is.
if you're asking about how deep sleep works, then yes, the idea behind it is your TF will automatically go into it after a period of non-interaction, or if you press the power button.
unless of course you have an older dock...which prevents that from happening.
if you're asking if the fix is done automatically, no. you have to send the dock to asus because the fix is a hardware installation.
Sent from my Transformer TF101 using Tapatalk
ok, that answers my question. I always use the power button to switch teh screen off.
I have a problem with my dock : after putting the tablet into sleep with the power button while docked, I close the netbook. As soon as it is closed the screen lightens on (so it's no more sleeping and will undoubtly suck up on battery).
I think I already read a post about someone having the same problem, but I can't find it.
Just noticed it. No idea why. I turned the tablet off/on a couple of times but that didn't do anything. Any ideas?
The motor might be dead. Have you tried toggling it under sound?
The 700 I got from Best Buy, a C7, haptic was dead out of the box. Had to take it back.
Factory reset didn't fix it either. I'm hesitant to exchange it because I don't have any of the other issues people are complaining about with this one but might with another. What a pain in the ass.
Does it vibrate when you power on or off? It should at least do that, if it does, its working. If you don't feel anything its toast.
Makes me mad too cause the one I had, everything was great except haptic. I didn't want to wait for another one so just took the refund
NeoMagus said:
Does it vibrate when you power on or off? It should at least do that, if it does, its working. If you don't feel anything its toast.
Makes me mad too cause the one I had, everything was great except haptic. I didn't want to wait for another one so just took the refund
Click to expand...
Click to collapse
Yeah, it vibrates when turning on/off. The tablet has been set to 'vibrate on touch' since day 1. Mysteriously that doesn't seem to work anymore.
after seeing this thread i just checked mine out. The haptic feedback is really really weak. I cant really feel it unless i am paying really close attention. On my prime it is noticeable, for sure.
I powered down and back up as suggested and got the standard 1/2 second buzz associated with those actions.
Maybe something in the update neutered the feedback? Is anyone's really pronounced?
stunya said:
after seeing this thread i just checked mine out. The haptic feedback is really really weak. I cant really feel it unless i am paying really close attention. On my prime it is noticeable, for sure.
I powered down and back up as suggested and got the standard 1/2 second buzz associated with those actions.
Maybe something in the update neutered the feedback? Is anyone's really pronounced?
Click to expand...
Click to collapse
Mine was totally fine, pre and post update, until I think late yesterday? The only thing I can think of, and I really hope this has ZERO to do with my issue, is that I had left my stylus laying across the screen for a short period of time. I think while it was resting on the screen it was registering touches repeatedly and maybe this screwed up the feedback mechanism? I know it was registering because the webpage that was showing was zooming in and out frenetically until I picked the stylus back up.
stunya said:
after seeing this thread i just checked mine out. The haptic feedback is really really weak. I cant really feel it unless i am paying really close attention. On my prime it is noticeable, for sure.
I powered down and back up as suggested and got the standard 1/2 second buzz associated with those actions.
Maybe something in the update neutered the feedback? Is anyone's really pronounced?
Click to expand...
Click to collapse
IMO this tablet is considerably more hefty than the prime. I think its because of the form factor that doesn't transit vibrations as well.
Sent from my PG86100 using Tapatalk 2
I'm just going to live with the broken haptic feedback. None in stock locally to make an exchange, and I really don't want to go thru the rigamarole of shipping it back, waiting who knows how long for a replacement, and then possibly getting one with other issues.
I got no haptic feedback at all since I got the Infinity. There's no screen locking sound either. I guess there should be one anyway?! The settings for these aren't affecting to anything at all.
jdeoxys said:
IMO this tablet is considerably more hefty than the prime. I think its because of the form factor that doesn't transit vibrations as well.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
i messed with mine all day. i am on the fence about sending it back (though prob not). it transmits a decent amount of feedback every 2-3 times, then 1-2 time where it is barely noticeable. I did the same set of testing with the prime...it too has a weak signal every 2nd or 3rd time, but it is still stronger than "regular" on my infinity.
I am going to see what others say, but i might have to agree with you on the transmission of vibration. If i hold it up to my ear, its definitely trying to do something...just not communicating it well.
Where is this "vibrate on touch" option? I can't find it anywhere. Are you talking about "Vibrate on keypress" for the Android keyboard? As long as you get buzz during the turning off and on, you at least have it functional.
alienedd said:
Where is this "vibrate on touch" option? I can't find it anywhere. Are you talking about "Vibrate on keypress" for the Android keyboard? As long as you get buzz during the turning off and on, you at least have it functional.
Click to expand...
Click to collapse
settings/sound/system - vibrate on touch.
its more for say a long press when adding a widget or icon...etc
stunya said:
settings/sound/system - vibrate on touch.
its more for say a long press when adding a widget or icon...etc
Click to expand...
Click to collapse
Hmmm. I don't get any feedback from that. Messed with some widgets and icons - nothing. Maybe its one of those things that didn't get checked by QC?
Ooookk...after reading this thread went to check my. Also no haptic feedback even if I check it from the settings...this is strange.
I never noticed haptic feedback.
After reading this thread I checked all the settings and I didn't get anything.
Except the one when you switch it off....
I'm using swiftkey.
So I checked the settings there.
It was activated but no haptic feedback.
But in swiftkey you can change the duration as well.
I set it to 60 and now I get haptic feedback.
So the hardware seems to be OK in my case.
I was getting decent haptic feedback when typing, backspacing, hitting the home key, arrow key, home screen, whatever, before it stopped working. I also tested out swiftkey from the app store and was able to turn up the haptic feedback setting when typing, but still nothing from screen touches etc. This has to be a hardware issue, right? Then again, why would this function work, then stop working, but then sort of work (at least on the keyboard side) when using another app?
I made an assumption that this problem manifested when I left my stylus on the screen causing the screen to bug out as if it were be touched rapidly and repeatedly. Because store exchanges are impossible at this time and I'm ~1.5 weeks from my 30 day return window I decided to order another one, and then set up an RMA for this one to go back and be credited; assuming that my replacement doesn't have any other issues. I couldn't justify letting this go considering the cost of this thing and the fact I've only had it a couple of weeks.
How about the screen locking sound? Should there be one?
Actually there is a very very faint audio feedback for touch that I'm able to hear with headphones in a totally quiet place. It disappears when unchecking the setting.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Jack Daniel's said:
I never noticed haptic feedback.
After reading this thread I checked all the settings and I didn't get anything.
Except the one when you switch it off....
I'm using swiftkey.
So I checked the settings there.
It was activated but no haptic feedback.
But in swiftkey you can change the duration as well.
I set it to 60 and now I get haptic feedback.
So the hardware seems to be OK in my case.
Click to expand...
Click to collapse
If you change the duration of the regular Android Keyboard under its "Advanced Settings" you can get the vibrate on keypress to work. The duration is initially set too short for the vibrate mechanism to fully buzz. I changed it from 1 ms to 100 ms and I get definite (but not powerful) jiggle.
johannesr said:
How about the screen locking sound? Should there be one?
Actually there is a very very faint audio feedback for touch that I'm able to hear with headphones in a totally quiet place. It disappears when unchecking the setting.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
I can get a faint locking sound. Can't hear anything for interactions outside of typing though.
stray_pube said:
I was getting decent haptic feedback when typing, backspacing, hitting the home key, arrow key, home screen, whatever, before it stopped working. I also tested out swiftkey from the app store and was able to turn up the haptic feedback setting when typing, but still nothing from screen touches etc. This has to be a hardware issue, right? Then again, why would this function work, then stop working, but then sort of work (at least on the keyboard side) when using another app?
Click to expand...
Click to collapse
I just checked all of the boxes under the sound feedbacks. I can get some haptic from the back and home buttons but still nothing for widgets and such. Can't really notice any sounds from those though. Perhaps an update lowered the values for the feedback and that's why your initial problem happened? Dunno.
alienedd said:
I just checked all of the boxes under the sound feedbacks. I can get some haptic from the back and home buttons but still nothing for widgets and such. Can't really notice any sounds from those though. Perhaps an update lowered the values for the feedback and that's why your initial problem happened? Dunno.
Click to expand...
Click to collapse
The problem didn't start happening until 2 days ago. The update has nothing to do with it. The last fix I tried to do was a 'cold boot'. I can't get that to work and yes, I followed the instructions posted on another forum and in YouTube videos. I hold down power and volume simultaneousy for up to a minute and nothing happens, other than locking it up and I have to stick a paper clip to reset it.
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.
This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.
I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet
I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.
I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:
I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet
Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.
So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk
Hi guys,
I thought is was a good idea to put Update related stuff into a separate thread.
So here we go
First question from my side, Can i stay rooted/xposed/selinux off for updating successful or do i need to Reset it? I dont really need root
Issues: I have brightness changing a lot and quickly, may it be an effect of doze?
Sent from my LG-D802 using Tapatalk
---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------
It doesn't sense the magnetic cover, it interprets as touch so, instead of going off screen, it increases brightness!
Sent from my LG-D802 using Tapatalk
Gianni said:
Issues: I have brightness changing a lot and quickly, may it be an effect of doze?
Sent from my LG-D802 using Tapatalk
---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------
It doesn't sense the magnetic cover, it interprets as touch so, instead of going off screen, it increases brightness!
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I have no problem with screen brightness changing or the on/off function from the magnetic cover, and have great battery life after the upgrade to marshmallow. My tablet had not been rooted and I am using a generic cover.
Sent from my Nexus 6P using Tapatalk
The adaptive brightness is a "feature" of the Asus software Vivid Display, it attempts to change the brightness of the screen to somehow compensate for the darkness of the content. There is nowhere to turn it off. It does my head in, i was able to disable it with root before the update, and with the Marshmallow update you can use the debloater tool. Disable packages called VisualMaster and Splendid, that seems to fix it.
mrbeardy said:
The adaptive brightness is a "feature" of the Asus software Vivid Display, it attempts to change the brightness of the screen to somehow compensate for the darkness of the content. There is nowhere to turn it off. It does my head in, i was able to disable it with root before the update, and with the Marshmallow update you can use the debloater tool. Disable packages called VisualMaster and Splendid, that seems to fix it.
Click to expand...
Click to collapse
Good to know, I will experiment. Usually I keep auto brightness and twilight app for the night, they may be conflicting too.
It's personal, but I hate vivid display [emoji4]
I solved the magnetic cover, the option is on setting but was defaulted to off
Sent from my LG-D802 using Tapatalk
What kind of battery life are we getting including screen on time?
For my use l was already satisfied with jb battery performance, and I don't see a great improvement.
But speed increment is very visible, I would say 20/30%
Sent from my LG-D802 using Tapatalk
Hello! How can we have multi user support on M? Thx
PG
One issue I have is that there are certain (non-media consumption) instances where the tablet will not automatically turn off the screen even though it is supposed to time out after 30 seconds of inactivity. Not a huge deal but since we are sharing...
macallik said:
One issue I have is that there are certain (non-media consumption) instances where the tablet will not automatically turn off the screen even though it is supposed to time out after 30 seconds of inactivity. Not a huge deal but since we are sharing...
Click to expand...
Click to collapse
My kids have some games that do that, more than likely the game has a permission to Keep the screen awake, you might be able to deny this permission now with M installed. I haven't upgraded their tablets yet but once I do I will check for that permission.
My big issue also relates to brightness. I use on screen alerts so that the screen lights whenever I get an alert. The problem is that with MM the screen dims just before it times out and turns off. I think it did this in earlier versions of android but with MM the dimming effect is so great that the screen is unreadable. This problem occurs even with auto brightness off and with the screen plenty bright...except for the few seconds before it turns off. Any ideas on if this can be fixed would be appreciated.
wxman123 said:
My big issue also relates to brightness. I use on screen alerts so that the screen lights whenever I get an alert. The problem is that with MM the screen dims just before it times out and turns off. I think it did this in earlier versions of android but with MM the dimming effect is so great that the screen is unreadable. This problem occurs even with auto brightness off and with the screen plenty bright...except for the few seconds before it turns off. Any ideas on if this can be fixed would be appreciated.
Click to expand...
Click to collapse
I don't get what are the screen alerts, but screen dimming and shining at random happens too.
I think we should be waiting the obvious update in a couple of months
Sent from my LG-D802 using Tapatalk
Gianni said:
I don't get what are the screen alerts, but screen dimming and shining at random happens too.
I think we should be waiting the obvious update in a couple of months
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
The random screen dimming has been happening since I bought my tablet last year. It hasn't been fixed & probably never will.
Sent from my VS980 4G using Tapatalk
Update: Can't write to OTG USB drive; Nook FC; FBReader FC
Mm is a mixed bag for me, to the point where I would go back to rooted LP with Xposed if I could.
Biggest issue is that I can no longer write to an OTG drive. I'd prefer to use the SD card as internal storage and use OTG on the relatively rare occasions when I need to move files. I can read the OTG Ok, but not write. It doesn't seem to be a drive or cable issue; I've tried multiples of both.It *does* seem to be a MM issue, because my phone (LG G3, unrooted) has the same problem.
Second issue is thst both the Nook reader app and FBReader crash. Both work OK on other MM tabs (granted, they are rooted) and on my LG G3 phone (bone stock).
Just venting!
Update: the OTG issue is not as bad as I indicated. ES File Explorer Pro is a lot fussier than the ASUS native file manager. Once I grant access via the file manager, ES seems to read and write OK. I finally got FBReader to work by uninstalling the Premium version, installing the free version, and then upgrading again to Premium. Now the Nook issue is the only remaining problem, and I can work around that by stripping the DRM from my books using Calibre in the PC so I can access them via FBReader.
tjupille said:
Mm is a mixed bag for me, to the point where I would go back to rooted LP with Xposed if I could.
Biggest issue is that I can no longer write to an OTG drive. I'd prefer to use the SD card as internal storage and use OTG on the relatively rare occasions when I need to move files. I can read the OTG Ok, but not write. It doesn't seem to be a drive or cable issue; I've tried multiples of both.It *does* seem to be a MM issue, because my phone (LG G3, unrooted) has the same problem.
Second issue is thst both the Nook reader app and FBReader crash. Both work OK on other MM tabs (granted, they are rooted) and on my LG G3 phone (bone stock).
Just venting!
Click to expand...
Click to collapse
In mine is even worse: it mounts the device but looks empty, will try different cases and apps
Sent from my LG-D802 using Tapatalk
I tried it again. Even with the MM update, there is severe battery drain while powered down. I charged to 100%, powered off and unplugged. Two days later booted up and battery shows 64%. Meanwhile my NEXUS N7 was turned off for 6 days and still shows 98% charge when booted up. Intolerable. No more Asus products for me.
Sent from my P01MA using Tapatalk
wtherrell said:
I tried it again. Even with the MM update, there is severe battery drain while powered down. I charged to 100%, powered off and unplugged. Two days later booted up and battery shows 64%.
Click to expand...
Click to collapse
Wait. You said you powered it down and then later "booted up." So the unit was off, as opposed to sleeping? If so, then the problem isn't related to the OS, 'cause the OS isn't operating.. It's your battery. It's self-discharging too fast.
Is there MM update for CN version?
Hi all, i,ve just read that there is a MM updates for Z580CA, and it said we need to download it manually (not OTA) . But when i checked to the asus website there is only updated firmware for WW and JP Version,
So.. is the CN Version will have the updates soon? ( i don' know if it possible to change SKU, but i've read the update can only applied to a same SKU, ex, WW to WW)
tjupille said:
Mm is a mixed bag for me, to the point where I would go back to rooted LP with Xposed if I could. ...
Click to expand...
Click to collapse
Check the parent thread for this as there is a way to revert back to LP.
Sent from my P01MA using XDA Labs
PMikeP said:
Wait. You said you powered it down and then later "booted up." So the unit was off, as opposed to sleeping? If so, then the problem isn't related to the OS, 'cause the OS isn't operating.. It's your battery. It's self-discharging too fast.
Click to expand...
Click to collapse
Exactly. Battery or a short circuit. But it seems a short would have other, more disastrous consequences. Since it doesn't really fit this thread I am asking a moderator to move to the appropriate one.