After about a week of owning a gtablet I couldn't resist the call to root. I just flashed tnt lite v4.2.0 and later tonight I'll try the v4.2.4 Supp. Easy as pie so far.
Flashing a new rom on these tabs just opens them up so much. I only waited four hours to flash ours, but that is because it took that long to charge the battery
Related
The tendency for the GTab to reset to the viewsonic birds screen when awakened is making the the device useless to me. I'm used to using my Droid Incredible for a while, then putting it to sleep, and later picking it up and continuing where I left off.
When I set the GTab down, I have to count on it restarting on waking, which means I might as well power it down. Not every time, but often enough, and the longer it sits, the more likely it is to crash,
What is your experience?
I have run into that with various different roms. I don't know why. I was on VEGAn 3 and it didn't happen. I just updated to VEGAn 5.1 and it's happening. I am thinking about reflashing back to stock and starting over to see if it makes a difference.
I have this issue with VEGAn 5.1 but not stock rom.
I experience it also but not as often as any of you. I'm on vegan 5.1. A fix wild be nice.
Scott
vegan 5.1?
I was also running vegan 5.1. I had tried different kernals, but always 5.1 as the os. Interesting. I am now back to stock (ugh), and it has not reset on wake once. Which roms do not seem to have this issue?
I have been seeing this the last couple of days. Stock 3389 with the performance pack.
Just crashed from overnight on stock. My wife also has one, still on stock that has never crashed. I am strongly suspecting there IS a hardware issue with some of these gtabs.
Mine reset 3 times tonight on wake-up using Vegan 5.1
It seems to happen if left idle for longer periods of times, like maybe more than an hour or so. Now I'm back on Stock 3389 to see if it still happens.
I have the issue everytime on Vegan 5.1, but not 3 or TNT Lite 4. Same issues on two tabs. I love Vegan, but switched back to TNT because it's so annoying. TNT Lite 4 is very stable in my experience.
jmdearras said:
The tendency for the GTab to reset to the viewsonic birds screen when awakened is making the the device useless to me. I'm used to using my Droid Incredible for a while, then putting it to sleep, and later picking it up and continuing where I left off.
When I set the GTab down, I have to count on it restarting on waking, which means I might as well power it down. Not every time, but often enough, and the longer it sits, the more likely it is to crash,
What is your experience?
Click to expand...
Click to collapse
Using VEGAn 5.1, I experience the same problem. If I let the device idle for more than an hour or so, it seems to restart instead of coming out of standby mode.
Hey don't get me wrong, it's better than the old lag-on-wake issue, but it definitely limits the usefulness of the tab.
Out of curiosity I upgraded to Clemsyn's TNT 10.9.8 kernel (http://forum.xda-developers.com/showthread.php?t=895825), but am still having the same issue.
I am now using Vegan 5.1 and Pershoot's latest 2.6.32.28 - VFPv3_FP - Gtab/Zpad kernel, with everything wiped clean, and it has all but eliminated the problem.
Jim
Both my tabs now do it on TNT Lite 4.0. Very frustrating... this is my biggest complaint right now. I guess I need to go back to older roms.
Has anyone tried to debug this or give VS support a call (since I saw it on Stock (w/ the performance pack of course))?
have any of you tried using the volume buttons to wake it rather than the power button. Mine likes to flash on and off when i press the power button to sleep as my fingers like to find the back and home button when im holding it with one hand to press the power.
Also, ive heard that the "power on" length, and reset press and hold length are really short on vegan 5. try just jabbing the power button and not pressing it till you see it do something.
Mines on 5.1 and i dont really ever have it reset, but Im aware of these 2 and usually either jab the power button, or use the volume button
jmdearras said:
I am now using Vegan 5.1 and Pershoot's latest 2.6.32.28 - VFPv3_FP - Gtab/Zpad kernel, with everything wiped clean, and it has all but eliminated the problem.
Jim
Click to expand...
Click to collapse
Thanks for this info. Yesterday I restored my backup of Vegan 5.1 and then installed Pershoot's latest kernel and haven't had the reset on wake problem since. It appears to have fixed the problem for me.
So do you think this could be resolved by going to Vegan or simply Pershoot's kernel?
Could you that have fixed this issue, post the exact version of the kernels you are running? I have tried 4 different versions, but still can't get it to wake without reboot.
Thanks
Gudy
I have a replacement phone that was sent to me because my original phone suffered from random shutdowns (on both the stock, but rooted ROM and on custom ROMS) and was within the affected IMEI range. When I got it on Friday I immediately flashed Cog 4.0 and then 4.1 on it. Woke up Saturday morning and it had shutdown during the night. Restarted and it shutdown again within 10 minutes. Restarted and about 3 hours later it shutdown again. Restarted and it shutdown again within the hour. Four random shutdowns in less than 18 hours when I had only 4 shutdowns in 2 months on my original phone. Upon checking, the replacement phone is also in the same IMEI range. Grrr.
Decided it was going back, called AT$T and arranged for another replacement to be sent and voiced my displeasure that they would send a phone within the same IMEI range. I Odin'ed the replacement back to stock and did the Kies update to 2.2 just for fun. The phone was up and running for 24 hours on stock Froyo without a single random shutdown. This morning I flashed Andromeda on it, again, just for fun and because I wanted to test the GPS compared to Cog 4.1. The Andromeda GPS is amazing, locks in less than 10 seconds, sees more birds, gets closer accuracy and holds lock better. Unfortunately, the phone had a random shutdown within an hour. Restarted and it shutdown again within 10 minutes.
Two different custom ROMs, same problem with random shutdowns. Not sure what the relevancy is, but there's obviously something not right if I can go 24+ hours without a shutdown on the stock, unrooted ROM and no more than an hour on a custom rooted ROM.
Been waiting all day for the battery to completely die so G Tab could lose info in temporary memory, as Viewsonic tech support suggested, to see if I can bring my damaged device back up after a bad firmware flash.
It has been 10 hrs, had it on all day. First it was just stuck on the bird screen with lights on non-stop then it went to powering down occasionally. A proceeded on to, after about 8 hrs, to where I would have to push the power button to give it juice to stay on for about 30 secs at a time. That gradually went down to about a second. After 9 1/2 hours went down to waiting 10 minutes pushing the power button and the G Tab still would pop on. In any event it is still stuck on the bird screen and not fully booting. I sure hope this helps with the process of bringing her back up. She never booted the firmware flash.
Fyi nvflash could have had you up and running in minutes (assuming you could get the drivers working right away) there are multiple posts in the dev forum on how to set it up.
This has already been mentioned, but hopefully this points you in the right direction.
Follow this link to download the stock update.zip.
hxtp://forum.xda-developers.com/showthread.php?t=842000
To use nvflash follow the following instructions listed at.
hxtp://forum.xda-developers.com/showthread.php?t=861950
Don't forget to replace x in hxtp links i sent you with t.
Roadzero said:
Fyi nvflash could have had you up and running in minutes (assuming you could get the drivers working right away) there are multiple posts in the dev forum on how to set it up.
Click to expand...
Click to collapse
Took me over 4 hours last night to get the correct drivers.
Once I got past that took about 15 minutes to get my G Tab running TnT Lite 5.0
Roadzero said:
Fyi nvflash could have had you up and running in minutes (assuming you could get the drivers working right away) there are multiple posts in the dev forum on how to set it up.
Click to expand...
Click to collapse
Been trying since last night over 24 hours ago. Read most of the articles. My tab is not recognizing inputs. I'm on Win 7, 64 bit with nvidia drivers on my system from my graphics card and such. Not showing any of the usb drivers I loaded to nvflash. Tried every method posted on this site and then some. For some it is easier than others depends on what equipment you are working with. That was my first resort.
My G Tab after more than 12 hours, still powers on an amazing device.
Cannibul said:
Took me over 4 hours last night to get the correct drivers.
Once I got past that took about 15 minutes to get my G Tab running TnT Lite 5.0
Click to expand...
Click to collapse
God bless you to the poster who posted the useable Win 7, 64 bit nvidia usb file. Finally she came back up!
Yes, I did search, and I didn't see anyone else reporting with this particular badness, so here we go.
Where I'm at now:
If I try to power up my Charge, the SAMSUNG logo appears, and stays there. A long time. This morning, it stayed there the whole time I got ready for the shower, showered, and dried off.
I am able to use PST to flash it; the downloader comes up when the battery is pulled, and I flashed the rollback to EE4 that p3droid provided from TBH. But it still won't get past the SAMSUNG screen.
It won't boot to recovery--just shows that damn SAMSUNG screen.
How I got here:
Not sure. I was running the stock ROM with the voodoo lagfix kernel to make it go faster, which has been fine for the last few weeks. I had experimented with TBH's GB leak, but had reverted back, as that's not quite ready for prime time (I was too used to the goodness of CM7 on my OG DROID to settle for such a work in progress).
Last night, I pulled the Charge out of my pocket, and it was dead--the battery was drained, which seemed very odd.
I plugged it in and a large, empty battery icon appeared--so far, so good. I had to move it to a different outlet, and when I did, a crazy display of lots of little jiggily battery icons appeared, filling the screen. The screen proceeded to morph, slowly, into a bunch of light-colored lines--but apparently the battery is charged, 'cause now it'll show that SAMSUNG screen for a long, long time, as described above.
I'm guessing I need to take it in and get a new one. Any other ideas?
Thanks--
Similar thing happened to me last night. Just would go to samsung screen, kept taking out battery and retrying and still got stuck there. I ended up flashing humble 1.2 and it worked and now its fine. Hope it helps, Good Luck!
I would try flashing one of the Odin roms or flashing back to stock ED1. If that doesn't work... I'm out of suggestions.
I used PST instead of Odin, but the same idea. I'll try Odin instead, see if that makes a difference.
Looking at Humble 1.2, which certainly looks interesting, but as he points out, start with a more or less stock EE4...and I'm trying to get back to that, first.
Thanks--
EDIT: Same results with Odin, no matter what I tried to flash.
Took it to the VZW store, a replacement's being shipped to me overnight.
Thanks again for your suggestions, hoping this doesn't affect anyone else.
Does this still happen to anyone else? It happens to me quite often (almost once a day now) and it's getting very annoying.
By the way it's when the screen goes off and sits after about 30mins and when I go back to use it, it wont come back on unless I hold the power button for about 5 secs to boot it back up.
I never had a SOD problem. Not with stock Honeycomb and not with custom roms.
Did you root our Transformer and trie custom rom or do you whant to stay on stock rom?
Sent from my Transformer TF101 using Tapatalk
Not rooted!! Stock since day 1
I had it all the time with my 3.1 stock, 3.1 stock rooted/cwm'd. I have not had it happen since I updated to 3.2, but I also put Prime 1.7 immediately after the 3.2 update, so I can't say if it's 3.2 or prime that fixed it. I'm on day 3 with prime 1.7 so I suspect it's gone, but SOD probably occurred every couple of days. So not 100% sure it's gone, fwiw.
Ugh...it's already happened twice today...I'm beginning to think I have a defective device...I love my tab but its getting annoying. It stopped for a while after 3.2 but it's back with a vengeance