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.
Related
The other day, I hit the power button on my touch pro, and the screen didn't come on. I did a soft reset, and it started working again. Now today, the same thing is happening, but a soft reset isn't helping.
The screen's back light comes on, the LEDs on the buttons come on, and the phone seems to be working fine. I hear all the sounds, including the HTC sound while it is booting, and the new message sound, but the screen stays black. It still recognizes touches, it just doesn't show an image. I want to do a hard reset, and will if I can get it to come one one more time, but its been about a month since I backed up my contact list. Lesson learnt there. I'm afraid it might be a hardware problem since I don't see anything while its booting either.
Anyone know if this is a known hardware issue with the touch pro? The phone is less then 3 months old, and I've been real careful with it. I haven't dropped it from more then 2 feet, and even that was onto carpet. Its the Verizon version if that makes a difference, and I'm running one of the NFSFAN roms. Its not the newest one, but rather the one posted on October 19th. I doubt its the rom, though, as I've been using it for around 2 months with no issues.
EDIT: Ok, I went into the bootloader to see if it was hardware of software. I figured if it was hardware, the screen would be black, and if it was software, it would be the rainbow. Sure enough, the screen stayed black. Hit the reset button, and the screen actually came on! Go figure. Went to do a backup, and the screen literally crapped out on me while I was watching it. Definitely a hardware problem.
similar with Touch HD... kinda
I've been having a similar problem with my Touch HD. The problem is very intermittent though and is sometimes hard to reproduce. The screen and phone will be working fine then once in a while when I push the power button to lock the phone, I'll unlock it and the screen stays black. I know that the phone is still on and even unlocked because pushing the buttons at the bottom makes the phone vibrate. The only consistency in reproducing the problem happens after I do something major on the phone such as making a phone call, browsing the internet, sometimes charging the phone. Other than that, I can sit here and push the power button all day and it'll come on and off with no problems. When the screen does go black I've taken the battery out repeatedly as well as repeatedly rebooted the phone until it comes back on. I've tried doing hard and soft resets to no avail. I've tried deactivating "turn off backlight if device is not used for" and "turn off device if not used for" without any resolve. After this I've even left the screen on (disabled backlight off) to see if it flickers or shows any sign of being faulty and it seems to be fine. I'm currently on Dutty's HD WM 6.5 Leo R5 WWE rom, but this has happened with two other roms (NRG, LIA). Other info include:
OS: 5.2.23016
Manila: 2.519192828.0
Radio: 1.14.25.24
Protocol: 52.64.25.34H
I guess the only consistent software has been my radio. Please help! Any advice would be awesome. I've tried google search and xda search without much help. Thanks
Over this past week the back light for my Nexus S 4G appears to randomly shut off. Right now it has happened about 5 times and when I need to use it right then, preventing me from just stopping to investigate what may be causing this. The screen still comes on allowing me to quickly unlock using the pattern and then restart by holding down the power button. The one time I was able to investigate a little I was navigating into the settings menu when the screen just went blank. I pressed the power button a few times and could see the hardware buttons below lighting up as if the screen was on but that was it.
I'm currently running Slim Bean (Android 4.2.1) Beta and will be trying another rom but wanted to see if anyone else may have encountered this issue before I bring it up with that thread.
Yeah experienced this too in most 4.2 ROMs that I've tried. Some people say it's a bug with the auto- brightness settings but I don't buy it since I don't really use auto-brightness but still get the error. I'm back to 4.1.2
Glad to hear. I was becoming worried I had some hardware that was failing.
I will turn auto brightness off and see how it goes.
Thank you
So it has happened quite a bit since my last post. Even with auto-brightness turned off. I'm blaming this bug for my alarm not continuing after I snoozed it a few times. (I know they are unrelated but its just really annoying).
It happened again about ten minutes ago and I managed to output a bug report feature on 4.2.1. Not sure if it is of any use to anyone. Message me if you would like it.
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
Hi everyone, as the title says, i've been having some problems with my surface RT (from the first generation) that I bought 2 days before the Pro was released in 2013 xd
First, a while ago, a year I think, my Vol - button stop working, I don't know why, but it just doesn't work until now. *
Second, I've been realizing that the speed and the fluently have decreased, or in other words, some lag has started to appear, even if I restart the tablet. Do the ARM version of windows suffers the same problems than its x86 counterpart? I mean, that it gets slower and slower as time goes by?
And third, and the most important, for a week or two, the right edge of the screen, doesn't respond to touch, so I can't open the charms bar or press "x" to close desktop apps, unless I use a mouse. It is like an inch wide or maybe less and involves all the "height" in landscape, but when I touch that place, the screen detects it like if I'm pressing either its left or exactly at the right edge. Curiously, it is intermittent, sometimes it works fine like it should, and in others it just doesn't work. Also, sometimes it goes crazy, and that sectors act like if i'd pressing and moving my five fingers all across that area, and I have to press the lock button for make it stop.
*I didn't mention it, but my Vol + button is starting to work weird too, I have to press it several times for make it "return to life" and response.
Well, the touchscreen problem is the one that worries me the most, but due to it is intermittent... could it be related to software instead of hardware? Could it be solved?
Thanks in advance for the answers.
Regards (I always doubt if this is the correct word for the expression that goes here xd)
Edit: I forgot to mention it, but i have win 8.1
If you haven't deleted the recovery partition, you can "refresh" the tablet to restore it to a like-new-install state. That should clean up any actual decrease in speed (as opposed to mere perception of the same).
The hardware issues sound like, well, like hardware issues. You can't really do much about those except get the thing serviced; it's not very user-repairable.
I thought that using the recovery to restore it to its original state will be the option, but is anyone else getting similar issues? I was thinking that maybe the problem was an update, because I have them programmed to be installed automatically, and maybe I didn't notice it.
I guess i'll do the "refresh" after I backup my files on December for vacations if this problem doesn't disappear by itself.
This is getting weirder :S, now I can't open some modern apps, they stay forever with the loading icon in the center, this occurs for example, in the store app or In the news app, but weather or desktop (luckily) work fine.
Hi there,
I have been struggling with a problem the last few days, and have been reading quiet a lot. I got two old Nexus 5 phones, one had a broken screen, the other one had the display glitching problem - related to the flex cable. So I opened them and put a working one together out of both.
So far so good, everything seems to be working, with one exception: Once I press the power button, the screen goes black like its supposed to. If I wait long enough and try to wake the phone, its not responding. The only thing that helps is long-pressing the power button to hard reboot it.
So I did read a lot, about the power button malfunctioning and the batteries dying on the Nexus 5. I ruled out the power button problem and its working like it should. I ordered a new battery, which is not perfect, but has an estimated of 1800 mAh. I monitored the voltage of the battery with different apps, even logging them to see what happens right before the shutdown - but everything seems normal. So this could not be the problem either.
I am currently running the latest LineageOS, but I experienced the same problem running the latest factory image google released for the phone. I even tried different kernels. So I thought, it might not be software related. But since it always happened when the phone starts to enter the deep sleep , I tried to google some about this and found the SOD ( Sleep of Death ) problem for the Nexus 4. Since I was out of ideas, I installed an App called "SOD Killer", which creates a wake lock preventing the device from sleeping. Et voila - the problem is gone.
I could not find discussion on the internet relating to the nexus 5 concerning the sleep mode and the phone dying once it goes to sleep. Am I missing something here? The SOD Killer wake lock solution is a good temporary fix, but I would like to get to the grounds of this.
Does anyone have an idea what could be causing this strange behavior? Thank you in advance,
joha
What I forgot to mention is that once the phone is connected to a power source, the problem does not appear. That is also the reason why I wont get any logs via adb. ;p
I will try to get some logs with an APP and root once I get home - maybe there is some information about the problem causing this strange behavior.
I managed to get a log while the phone died when it wanted to activate sleep mode. But I am not that good in figuring out what in the log might be pointing in the direction of the failure. Any ideas?
I dont like the
Code:
09-21 12:11:51.977 E/BatteryStatsService( 786): no controller energy info supplied
parts in there. What might be the problem here?
Thank you so much in advance!
Does no one have any idea? I guess its hardware related somehow, when the phone tries to enter deep sleep. Anybody out there that knows, what the phone is actually doing when entering deep sleep which might be causing it to die / become unresponsive? Any idea is highly appreciated - I love that phone.