So finally, after 2 months of barely being able to pick up my tablet because of work, I've been able to start playing around with building again. I've been able to build CM with that's kernel inline, and with some preinit scripting it runs great except for two issues.
First, and probably easiest to solve, I can't get any of the reboot commands to work. Regardless of hitting power off or reboot recovery, the tablet simply reboots. If it was happening in a language I'm more familiar with, I'd think it's not passing a variable to whatever controls the shutdown routine. But, I don't know if that's the issue or even where to look.
The second problem is more annoying and perhaps harder to diagnose, I have random screen blackouts. Things will continue to run in the background, but the screen goes dark. Hitting the power button will bring it back, and promptly lock the screen (apparently hitting the volume button also works as I just found out). It happens intermittently, I could go for an hour with no issues, and then have multiple blackouts over the course of the next 10 minutes. Makes it difficult to get a logcat when you never know if it's going to happen.
So I turn to this wonderful community for help once again. Anyone have any thoughts on what to try?
Thanks in advance,
Psudeke
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Related
First off, just want to say thanks to all of the developers who are making the gTab a wonderful experience.
However, there are some issues with the tablet. I want to know if these are fixable via software updates, or if my tablet is faulty.
Before I begin, here is some info:
-I'm currently running Vegan beta 4, but I tested for all of these issues in beta 3 and TNT lite 2.4. These ROMs also experience the issues I'm about to mention unless noted otherwise.
-I have cwm .08 installed.
-My model number is UPC300 .
-I only use this tablet with a 32-bit Windows 7 machine (it may not seem relevant, but it could explain two issues...maybe).
-I have not done anything related to Nvflash.
Ok, here is my list:
1. When I wake the tablet from sleep mode, occasionally the "Device options" window pops up. It's as if the tablet thought I held the power button, instead of pressing it. Someone raised this question before, but no one really gave an answer. He ended up exchanging it, and it solved the problem. Here is the thread: http://forum.xda-developers.com/showthread.php?t=867702. I tested this on Vegan beta 4, beta 3, and TNT lite 2.4. Beta 3 did not give me this problem, but I may not have tested it extensively enough.
2. When I plug the tablet into my Windows machine, the PC makes the "connected" sound. However, when I put the tablet in sleep mode while connected, the PC makes the "disconnected" sound. After a short while, the PC makes the "connected" sound again. It continuously goes through the "connected" and "disconnected" sounds, and it seems to be random. I tried to reproduce the symptom various ways to find the cause of it, but to no avail. It's easy to reproduce, but the cause is unknown.
3. When I put the tablet in sleep mode, the soft buttons still remain active for about a second. If any of these buttons are pressed right after the screen is turned off, it turns the screen back on. This isn't too bad, but it gets worse. It seems that the soft buttons become active randomly while in sleep mode as well. Plugging the the tablet into a computer provides some insight to the problem. Issue #2 proves that this issue is not truly random. When the tablet is connected to a PC, and is in sleep mode, it randomly connects to the computer. When it randomly connects to the computer in sleep mode, the soft buttons are active and can turn on the screen (although, it takes a few tries). What's strange though, is that the tablet still thinks the screen is still off. When the power button is pressed, the screen abruptly turns off, and then it turns back on, and shows the lock screen. Can anyone else try and replicate this problem for me?
4. When I disconnect the gTablet from the computer, it occasionally thinks that it is still connected to the computer. I can even "mount" the internal SD card. I have not tested this with TNT lite 2.4 or beta 3. I will test it out later.
5. I'm probably just being nit-picky here, but when I turn the screen off and then on again, the screen immediately wakes up from sleep mode. However, the screen turns off for a second, and then it turns on again. All three ROMs I tested suffer from this issue...is it just my tablet?
6. I've seen some people with the same problem (http://forum.xda-developers.com/showthread.php?t=855821), but with no solution (that I know of): When the gTablet is in sleep mode for about ten minutes or so, it randomly shuts off. It's happened on all of the ROMs I have tried...clueless as to what the cause could be.
These 6 problems are tempting me to exchange the gTablet, if not return it. If all of these issues are common, but fixable via software, I'll be patient and wait. But...if these issues are common in all of the gTablets, I might just return it. I really don't want to, because these problems seem really small, but they are very annoying (Lets also consider the lag-on-wake and inaccurate battery readings...both fixable by software, but there is no definite solution to both of these problems yet). If exchanging the tablet would fix all of these problems, then that would be great. Any help would be appreciated!
Javier78,
Nice job to document the issues you are seeing with the gtab. As an avid follower of this forum, I can say that many of us have seen the issues you reported. I don't think anyone is ignoring that there are issues like this, but I believe most will agree, the pros very much outweigh the cons. I think many of the folks who purchased the gtab know they are early adopters of the Tegra 2 hardware, especially on the 10" tablet.
Now that the source is available to the community, I expect to see a lot of changes in the coming weeks. I fully expect these issues (which I believe many are software related) to be resolved. I look forward to builds running on Gingerbread and Honeycomb.
Butch1326 said:
Now that the source is available to the community, I expect to see a lot of changes in the coming weeks. I fully expect these issues (which I believe many are software related) to be resolved. I look forward to builds running on Gingerbread and Honeycomb.
Click to expand...
Click to collapse
Yeah, I guess I should wait a few more weeks before deciding whether to exchange the tablet or keep it. Hell, a kernel that supports NTFS drives came out a few days ago! Thanks for your input.
After updating to 3.2, I noticed that the touch screen has a ton of bugs. I used this program to check the inputs (I can't post links now due to forum restrictions):
Multitouch visible test
Basically if I scroll from far left to far right (Asus logo on the top left of my view), there is always a cutoff somewhere on the screen.
I never or hardly ever notice this problem when I'm in 3.1.
Any ideas on how to fix the problem? Or is it just 3.2 that has this and I should go back to 3.1?
Help is totally appreciated. Thanks!
Update:
Sent in the TF to Asus (to Ontario Canada) on August 9, 2011
Received it back from Asus on August 29, 2011 via UPS
Problem: they only reloaded the OS and did NOT test the touch screen so I have the exact SAME problem... Requesting RMA again
Can you grab a video of the issue?
Plonk it on youtube and then stick the url on here.
Cheers
Video is at youtube:
www(dot)youtube(dot)com/watch?v=ukdzYMKYtFE
Basically a portion of the screen does not respond to touch, and the classic turning screen on and off does not fully solve this problem.
had this problem before 3.2.
my screen have only small places..quarter of inch, random places.
noticed this only after rooting. and with some kernels more than others.
have you rooted?
No root. All stock since I am too lazy to do anything other than install apps, view video and manga.
blastdabomb said:
Video is at youtube:
www(dot)youtube(dot)com/watch?v=ukdzYMKYtFE
Basically a portion of the screen does not respond to touch, and the classic turning screen on and off does not fully solve this problem.
Click to expand...
Click to collapse
Quality vid there, top notch.
Have you tried a hard reboot?
And a restore to factory default settings?
For some reason that sounds sarcastic there... but the video was taken by a Desire HD so it's not that good quality. It conveys the point (I hope).
Haven't tried hard reboot or factory default settings because that would mean I have to reinstall stuff and re-setup things like gmail.
Lol dude, i wasnt being sarcastic, for some reason i was expecting some half-assed effort.
Hard reset shouldnt wipe your data.
Hard Reset:
Unplug the power cord and shut the unit off and Press and Hold the power button and the "Down" volume button together for 6-10 seconds and let them both go. After a few seconds you should see a couple of shapes in the middle of the screen called "Wipe Data" and "Android". Wait a few more seconds until the term "Cold Boot" appears in the list near the top of the screens and just press and release the "Down" volume button again and let it reboot. If you own the dock be sure and do this with the dock connected.
Sorry man, I guess my sarcasm detector is pretty off today.
I tried the hard reset and the same problem persists. I will have to see how this can be fixed though (I see that many people have similar problems though).
Thanks for your help =)
might be worth giving asus a tinkle and see what they say.
Hi all - my TF700 has been solid for about 9 months, but this past weekend the touchscreen started getting wonky and now it will work for 5-10 seconds and then not register any touches, until the power button is toggled to put it to sleep and then wake up and go through the process again. In my research, it appears as if this can be addressed through recalibration of the Touchscreen.
However, I don't even know if that's possible with my current stock/rooted setup. I did try booting into recovery, but I saw the RCK/Android/Wipe Data prompts, and didn't want to go anywhere without knowing what each would do. I'm guessing maybe the Android button, but I'm not sure.
Is there an easier way to recalibrate the touchscreen without doing a factory reset, or going to a new ROM yet?
Thanks!
This may be a hardware problem with the digitizer going bad. I would contact Asus, they probably will recommend a factory reset and you should try that anyway.
But a custom rom will not take care of this problem - at least I do not think this is software related....
Good that you are still under warranty!
FYI:
RCK will boot into the stock recovery which will not do anything unless you have an update file downloaded somewhere on your storage - it'll just show you an Android falling over with it's belly open a ! triangle. Scary if you don't know what it is! LOL
Android will boot you back into your system. This is a so called 'cold boot' and you could try that. I doubt it'll help, but it won't hurt either.
Wipe Data does exactly what it says. You better have everything you care about backed up before you execute that command.
You use the Volume Down button to navigate between the icons and the Volume Up to execute.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Hmmm. after enabling Developer mode (so I could d a Titanium backup), I decided to enable the touch sensing, and what I've found is that it appears as if there is a spot in the northeast quadrant (while holding vertically, with buttons on the right/dock connector on the left) that gets stuck in the 'touched' sense (the little dot sticks, and in the kindle reader, it acts like the text is selected).
Sometimes it gets unstuck when pressing the power button to sleep, and then re-logging in via the lockscreen code I have set. Sometimes it doesn't. I guess I'll contact support and see if I can capture it on video with my phone.
Pyperkub said:
Hmmm. after enabling Developer mode (so I could d a Titanium backup), I decided to enable the touch sensing, and what I've found is that it appears as if there is a spot in the northeast quadrant (while holding vertically, with buttons on the right/dock connector on the left) that gets stuck in the 'touched' sense (the little dot sticks, and in the kindle reader, it acts like the text is selected).
Sometimes it gets unstuck when pressing the power button to sleep, and then re-logging in via the lockscreen code I have set. Sometimes it doesn't. I guess I'll contact support and see if I can capture it on video with my phone.
Click to expand...
Click to collapse
Pyperkup,
Did you ever resolve this issue? I'm experiencing the Very same issue on my TF700T.
Thanks
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
calvinb1 said:
Pyperkup,
Did you ever resolve this issue? I'm experiencing the Very same issue on my TF700T.
Thanks
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Had to send it in on warranty.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Hey everyone, I'm a fairly new OPO user myself here as well; I received mine back in early-mid October, and have had it since then.
But oddly enough, for the past two weeks or so, the following issues have surfaced and has become more frequent, and prominent than ever. For all the fellow OPO-users out there, I was wondering if anyone else has come across the same issue(s) that I've been going through... Unfortunately I really haven't had the time to look up any solution methods and whatnot with two young'uns whom are extremely demanding of my presence... All. The. Time.
So I thought that if I compiled my little list here, hopefully some kind soul will reach out to me with answers (or at least, the direction to where I could find those answers) and make my day just -that- much lighter.
Now just to mention the main points : NO, I have NOT rooted my phone, and YES, I DID install the OTA update, and currently my CM version is the 11.0-XNPH38R.
~~~~~~~~~~~~~~~~~~~~~
a) sometimes, my OPO screen will absolutely REFUSE to turn back on, after I've put the phone to sleep. nothing i do can get the screen to turn back on again - unless it decides it finally wants to. (it's got a mind of its own, this thing... and it's just as stubborn as I am. UGH.) i try double-tapping the screen several times (i've turned that feature on) and i try pressing the power/wake button, or holding it down, ... but zilch. this will usually last up to 10~15 minutes. (after 5~10 minutes of trying to bring it back to life, I just give up and let it be.) when the screen DOES end up turning back on, it's either flashing the "power off/reboot/accessibility" menu several times (probably from me trying to mess with the physical power/wake button) then finally respond to my 'backspace' on-screen keys, or the home icon, returning me back to the proper lockscreen it's supposed to show. ANOTHER way it ends up FINALLY responding, is that the phone will vibrate in short sequences of two, maybe three times and then it will initiate the rebooting process. then everything starts working fine again. i don't recall having ever done anything to trigger something like this to happen, either...
b) the keyboard (the stock Android keyboard) randomly will NOT work; by that I mean, when I am in a messaging app, or any other app that requires a person to TYPE WORDS ON, the keyboard DOES show up, (along with the suggestive bar just above it) and when I try to type, all the usual things will occur; the letter I happen to press will pop-up in response to my tap, and in the suggestive word bar above, it will start showing me the possible word combinations possible based on the sequence of the letters I type, but nowhere do I actually SEE on the SCREEN/message bar/etc. any letters or characters popping up. this issue too, will happen out of nowhere and will last about 15~20 minutes as well. usually what fixes the problem (as annoying as it is) is if I shut down/turn on, then reboot the phone a couple of times to get the keyboard to actually start working again. but there MUST be an easier method to fix this (and all my other issues) !
c) the stock camera app; this issue actually started occurring within days - just under a week of actually getting the shipment of the phone to my place. I was testing out the camera functions, the usual, then suddenly, I would get booted out of the app, and a message saying "The Camera cannot be used at this time" will pop-up as a result. (although, what was even STRANGER, was for a while, (for about 2-3 days) I was receiving a totally different message that didn't even make any SENSE: it said something along the lines of "the camera could not be connected to the device at this time" or "the camera has been disconnected from the device"... i don't even know HOW a camera can "disconnect" itself from the phone, but apparently it CAN.) with this issue, there was absolutely NOTHING I could do to start making it work again. it was non-functional for three, four days straight (no word of a lie) then just for the hell of it, I decided to open the camera app again, and boom, it was working. that didn't last long, though... then suddenly after opening the camera, there would be a prolonged black screen on the phone that wouldn't go away, and I couldn't select any options whatsoever... then when the camera finally started "working", i tried taking a picture - i thought that it would work, since nothing was indicative of it NOT working... but alas, such was not the case. when i went into gallery, to browse through the photos I had taken, they were not there at all, and the photos i had thought were taken weren't actually taken at all.
Asides from that, and some occasional (frequent) crashes while using the phone, I'm not feeling too frustrated by it. (I guess I just have an effin'-load of patience.) Still, I would greatly appreciate any thoughts or suggestions about this dilemma of mine, or providing me the key to all of the answers to these stupid bugs.
Thanks for all those who took the time to read my lengthy post. :fingers-crossed:
-- MK.
I've gotten no help from ZTE themselves - they want me to do a factory reset and didn't even bother to read what my problem is. This is with the stock ROM for a ZTE Blade 10. I touch the power button and the screen doesn't stay off, instead turning on every time I move it (in the same vein as a "Lift to Wake" problem). This burned a huge hole in my battery the first day I had it, butt dialed a couple of people by opening my Contacts on its own, swiped important notifications away (including texts and reminders), and played with apps. I've managed to stabilize it some by tweaking some settings, but I haven't found a setting that disables this entirely.
I have screenshots of my settings in a second post, since I'm not allowed to post them in the original post.
Worth noting is that I have a custom lockscreen app, HiLocker, for which I set a five-second timeout. It does not seem to be the app, since the problem still presents itself when I disable it. Ergo, I either have to choose between changing that to instantly locking (thus making me enter my pattern again when my screen times out, even if I'm in the middle of using the phone) or keeping as is and dealing with this problem. I don't want this to be a choice. I want this five-second thing, but I want the power button to be absolute and keep the screen off until I push it again. My phone doesn't seem to understand something so basic: That's what the power button is for.
Does anyone know if there's a solution for this? Any pointers would be appreciated, thanks!
I hope this works.
https://i.imgur.com/uwdn8V5.png
https://i.imgur.com/aqd16Ko.png
https://i.imgur.com/RuhrvAV.jpg
Bump. Seems I can do that every 24 hours, and it's on the bottom of the page, so...
Still seeking any feedback. Anyone have any idea, or do I need to flash a ROM for the first time in half a decade?
One last try... can anyone help me?