So I just got the gTablet from Sears today and the thing is great. I love it.
I immediately flashed VEGAN onto it without updating the original SW. That thing sucked, but now that I have loaded it all the way I wanted it I get the lag we are all talking about but then I also get a reboot quite often. Meaning it must shut down on its own then when I go to wake the gtab it has to start again.
Is this common with VEGAN b4 or is this unique?
If not what could I do to fix it?
TIA
there is a thread about this just below this one.
here it is.
Thanks. I read some of that but didn't think it had too much about the reboot issue I'm having. I'll read more into it!
webby_s said:
Thanks. I read some of that but didn't think it had too much about the reboot issue I'm having. I'll read more into it!
Click to expand...
Click to collapse
I think they are related issues webby_s. I think the CPU gets stuck in a slowdown and either misregisters a power button press duration or simply can't seem to get the screen back on. I have had this happen from time to time with all the ROMs, but I have the lagginess on wakeup much more with Vegan beta4 than with beta3.
My recommendation, if this is something that annoys you and you'd like to help us out, is to flash Vegan ROM beta3. You may or may not need to wipe user data - I'd go ahead and try without wiping first.
See if the issue is still as frequent on beta3 and let us know. Would definitely be helpful feedback.
I could probably try that out. I'll see if I have the time today!
Related
hello xda members
i have install froyo fx06 bundle here
my problem is sometimes the phone freeze. i read the entire post to find the solution to fixed that. then i found the only solution is to install init at here . can someone make a tutorial how to install that. i mean the step by step tutorial.
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
R^7Z said:
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
Click to expand...
Click to collapse
i don't know how to use ADB or terminal. actually this is my first time heard that. hehe
Some say it isn't that difficult while others have a difficult time trying to understand English, much less speak/type it(like myself ). If you feel up to it, you can start by reading HERE. Unless someone else has this simplified elsewhere. If that were the case and I knew of it, I woldn't be pointing you in this direction.
Thank you for trying to help me.
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
hotsmusic said:
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
Click to expand...
Click to collapse
and i think it's not because flax cable because this problem only happen when i use froyo fx06.
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
R^7Z said:
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
Click to expand...
Click to collapse
Thank you for trying to help me. actually i have try to set my phone in airplane mode to test if the problem because operator/service provider , but the problem still the same. it's not freeze because i still can fell it vibrate when i touch the screen only the display not show up.
about gingerbread. i have read that gingerbread is android 2.3 and froyo is 2.2 right? but why many people like to use froyo then gingerbread? if gingerbread have any problem. sorry if i asking to many question.
I'm not 100% on this but I think it has something to do with the fact that the porting is still in alpha phase for our devices. If anything, this can be looked at as good or bad. Good, that we have gotten this far and it seems our devices are pretty much stable. Bad, that this might be as good as it gets for a while. You have to weight the options of a faster port(in terms of stability) but less complete(in terms of functionality) or a more complete port but not quite as fast. I remember when we first got FroYo, it seemed like a complete mess. It took till the third release (FRX03) for stability to take place(noticable) because the devs were trying to figure out what caused the instability. When it's all said and done, the end user experience is all that most are looking for. When this is the case, it's difficult to say what should be done. Wait till it becomes more stable or try to come up with work arounds. Troubleshooting can get you so far until you require more understanding of what affects what. Hopefully, I have bored you out of your mind and that this makes things clearer as to what you can do to help!
thank you for your kind to help me. i have change to gingerbread but it have same problem like froyo. then i tried to hard reset then reinstall froyo and change the kernel. now it working great without problem except camera not working . maybe because i change the kernel htc-msm-linux-20110214_200559-package.tar . but it's ok for me. i will wait till new release.
You must have the similar issues some others have (on foreign carriers/other than USA based) Now, I'm not saying this is the problem just that others that have a similar issue, are on those carriers. There have been updated kernel packages that include the camera fix but I would suggest a little more reading into what you need to do, to ensure that you aren't causing the issue you are experiencing now.
Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!
Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8
adam_deluxe said:
Here we go:
As of update 1.1.7 of mike1986's Android Revolution ROM I experienced a strange issue:
My phone just randomly turns off at least two times a day. I'm not talking about a reproduceable error, since my phone only showed an unresponsive black screen (waking it up by pressing the power button didn't work, too), when I was carrying it in my pocket. I thought at first it was an SOD issue like with the early Android builds for the HD2. But today my phone just literally turned off before my own eyes while I was checking my mail. I wasn't even able to turn it on anymore without performing a battery pull. I was confronted with this issue the third time just a couple of minutes ago. I even did a full wipe and reflashed the ROM (I know, I'm just a Junior Member, but trust me, I know how to this properly), before this happened - again.
Should I just revert to an older version of the ROM or wait for an update? I don't want to just sit around and do nothing about it.
Any help is much appreciated!
Click to expand...
Click to collapse
Hi,
This is a kernel issue.
Try flashing the kernel in my sig using CWM.
Dacoit said:
Please search the Android Revolution Thread before posting next time.
A lot of people are having these issues. Just install a different kernel and that should fix the problem or go back to 1.1.5 or 1.1.6. I'm waiting for 1.1.8
Click to expand...
Click to collapse
I did. Thing is, I'm still a Junior Member, so I'm not allowed to post the experience I had or ask questions about it. I know, it's a ROM-specific question which belongs in the thread of the aforementioned ROM, but asking someone out of the to post it for me would have been about just as much annoying. Still, I'm sorry.
Still, it seemed somehow that no one reported the exact situation, as there were different solutions proposed. But - as I said - I couldn't even add anything to the discussion, since I'm not allowed.
I hope, it didn't disturb you too much.
Regards
Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
EDIT: The UI runs pretty smoothly now and my WIFI and mobile data are not lagging anymore. It MUST have been the kernel.
adam_deluxe said:
Thanks for the quick (and hopefully helpful) reply.
I have to wait and see, if it works for me, but if you say so, there must be something true about it.
Anyway, thanks again!
Regards
Click to expand...
Click to collapse
Hi,
It worked for me,and I've had no black screens since.
Yes, reverting to RC Mix 2.3 solves many glitches IMO. Should do the trick while waiting for a better version.
The skyrocket is a fantastic phone I'd have to say, except for this: Probably once a week (been happening more often recently), my phone would randomly turn off (or sometimes I would just reboot it) and after it starts up and all, I get the stupid force closes that DON'T GO AWAY! Now I've figured out how to fix this, Just reflash the ROM, but that takes awhile and im sick and tired of losing all my stuff that backing up doesn't back up. Is there any easier fix to this or just keep reflashing every time that happens? I'm on 2.3.5, was running Alien 3 (now ICS, which I've had no problems with [so far...]), aaaand I believe that's it. Thanks.
Gfrt94yn said:
The skyrocket is a fantastic phone I'd have to say, except for this: Probably once a week (been happening more often recently), my phone would randomly turn off (or sometimes I would just reboot it) and after it starts up and all, I get the stupid force closes that DON'T GO AWAY! Now I've figured out how to fix this, Just reflash the ROM, but that takes awhile and im sick and tired of losing all my stuff that backing up doesn't back up. Is there any easier fix to this or just keep reflashing every time that happens? I'm on 2.3.5, was running Alien 3 (now ICS, which I've had no problems with [so far...]), aaaand I believe that's it. Thanks.
Click to expand...
Click to collapse
This IS an issue alot of people are having......search the threads a lil more. you will see threads dedicated to this like THIS ONE
http://forum.xda-developers.com/showthread.php?t=1386234
Thanks! this just happened to me again but hopefully its the last... I didn't even think about looking in the general section! I just checked the dev and q&a
Hi All
kinda directed @sbdags (sorry again champ i cant post in development thread) but for some reason after a little use of the ROM the touch screen becomes unresponsive and stops working completely for like a few minutes sometime a lot longer. keyboard attached works like a charm, thank god otherwise im stuck =/
comes good after a hot boot, but have also done cold boots and fixes the issues but does come back every now and again.
i did a complete wipe and also using that4+'s kernel (no dirty wipe). but has been happening the last 2-3 versions but havnt thought anything of it.
has anyone come across this issue? is there something that im missing?
Cheers
DuckDodger70 said:
Hi All
kinda directed @sbdags (sorry again champ i cant post in development thread) but for some reason after a little use of the ROM the touch screen becomes unresponsive and stops working completely for like a few minutes sometime a lot longer. keyboard attached works like a charm, thank god otherwise im stuck =/
comes good after a hot boot, but have also done cold boots and fixes the issues but does come back every now and again.
i did a complete wipe and also using that4+'s kernel (no dirty wipe). but has been happening the last 2-3 versions but havnt thought anything of it.
has anyone come across this issue? is there something that im missing?
Cheers
Click to expand...
Click to collapse
Never heard of that happening. Did he reply to you?
jt1998 said:
Never heard of that happening. Did he reply to you?
Click to expand...
Click to collapse
DuckDodger70 said:
Hi All
kinda directed @sbdags (sorry again champ i cant post in development thread) but for some reason after a little use of the ROM the touch screen becomes unresponsive and stops working completely for like a few minutes sometime a lot longer. keyboard attached works like a charm, thank god otherwise im stuck =/
comes good after a hot boot, but have also done cold boots and fixes the issues but does come back every now and again.
i did a complete wipe and also using that4+'s kernel (no dirty wipe). but has been happening the last 2-3 versions but havnt thought anything of it.
has anyone come across this issue? is there something that im missing?
Cheers
Click to expand...
Click to collapse
Never happened to me but perhaps there may be some apk that consumes all the resources, it strikes me that you can try to see what is consuming the resources of the tablet, for example, through the free apk COOL TOOL because you can see the% of CPU in use well as the available memory or the process that consumes more resources......
Try one of the other kernels from my kernel installer to eliminate that first please.
I've seen this happen once when advanced wifi settings was set to always on with power or whatever it was. It never came back though.
sbdags said:
Try one of the other kernels from my kernel installer to eliminate that first please.
I've seen this happen once when advanced wifi settings was set to always on with power or whatever it was. It never came back though.
Click to expand...
Click to collapse
@jt1998 yeah he did see the last post
@morgan39 thanks for that ill give it a go
@sbdags yeah figured you might say that, ill have to give and other kernal a go when i get home tonight.
thanks for the input guys, much much appreciated!!!
i know its a small donation @sbdags but all i could afford for right now =/
much appreciation for all your work and help!!!
DuckDodger70 said:
i know its a small donation @sbdags but all i could afford for right now =/
much appreciation for all your work and help!!!
Click to expand...
Click to collapse
Wow! Thanks mate! I really appreciate that.
sbdags said:
Wow! Thanks mate! I really appreciate that.
Click to expand...
Click to collapse
no problems at all mate
Just thought id give you a quick update so far no good with 3 out of 5 kernels, both _that's and your stock kernel having the issue and just about to try one of Hundsbuah's beta kernels and see what happens.
its no major issue to me actually gives me an excuse to actually do a cold boot every so often, since i never turn my tablet off.
Cheers
So since about 2 days ago the phone just start freezing. Sometimes it just restarted randomly, but mainly freezing at least every 5 minutes. The power button alone wouldn't turn it off no matter how long I held it. Always have to use Pwr+Vol Down to reboot.
I put up with it because I've been busy, but finally tried wiping cache - no profit. Tried safe mode - no profit. Factory reset- negative profit. After the reset it just seems to restart a bit more often but in general it freezes less, making the timing seem even more random.
This happened when I first got it (used). It was restarting due to the fresh 7.0 update. So a factory reset fixed it and it was smooth sailing for like 3 months or something. I know there was a minor system update a few days ago but those dont usually call for a factory reset. I tried it anyway and it just didnt work. I had actually even tried uninstalling all the app updates from the night before it started happening. but safe mode couldn't even fix the problem so I guess that was moot.
Software version: G920VVRS4DQE1
Stock everything - I dont hack my daily drivers at all
Android 7.0
Mainly I'd like to know if Im alone. A fix would be great but I'm hoping it's not specific to my device. If it's a hardware issue I'm gonna give it a swift toss down the stairs and maybe deliver a nasty curb stomp to it right afterward.
Any advice?
I'm running into the same exact issue. Same build, and am running out of ideas.
Lathorus said:
I'm running into the same exact issue. Same build, and am running out of ideas.
Click to expand...
Click to collapse
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.
sawyerbenjamin said:
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.
Click to expand...
Click to collapse
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Same for Verizon. I guess I'll just hold out, using a backup phone, until a new update hopefully fixes it.
Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Gonna go ahead and revive this. It seems to work fine when the sim card is out. I recommend you see if it's the same with you. I've charged it up before work multiple times before work days and come home from to see that it never restarted. I was able to test this using the fingerprint feature; it isn't asking me to use pattern like it does after boot.
No one else is chiming in but, since we're both on Verizon, I'm having a feeling that it's directly related to the SIM/carrier.