CM7 RC1 issue... - G Tablet General

So I know this is the wrong place to post this, but I "cannot post to the dev forum" due to low post count...nice...
anyway...
Installed CM7 RC1 for 1.2 BL (actual package: "update-cm-7.1.0-RC0-smb_a1002-KANG-signed -clemsyn-bl1.2.zip") along with google apps (package: gapps-gb-20110613-signed.zip) and was running fine for a few days. A little while ago my gtab when to standby (just as it had many many times over the last few days), and when I pushed the power/standby button nothing came back...okay, I thought...no biggie... hold the power button down for a few secs to power down, push the power button again to power back up...gtab boots back up to home screen, but all my widgets fail to load and instead show soemthing like 'problem loading widget'...okay, I say, reboot once more...and here's the rub...after that reboot, now stuck at three birds - cannot even boot into recovery (I have CWM installed). (but I -can- boot to APX)
So...other than re-flash wiping everything out...is there anything else I can do?

Oh...and fyi... the only change made between the previous standby and this last standby was that I moved a few apps from 'phone' to 'sdcard' (Netflix, and two others that I cannot remember).
But I am wondering if the lock up occured more from having to hard power down during standby or if it was due to moving my three apps to sdcard....

You don't happen to use another Launcher ? I had this issue before but no more after sticking to stock launcher.

Actaully yeah, I was using Launcher Pro - but had been since minute one of installing the ROM...as well as the ripple lock...
Sounds like CM7 RC1 doesn't like Launcher Pro...

So...anything that I can do other than re-flash? not a huge loss...just time...

nm - i just re-flashed and will try with the included launcher for a few days.

So...interestingly enough...I re-flashed with tnt 1.2 pre-installed with cwm, re-intalled CM7 RC1, re-installed gapps, only wiped the cache part, removed all broken widgets, and re-added widgets, and now it is all back...i let it standby a couple times and it comes back no prob...so it would seem that the issue might be related to the hard power off (long power button push) (coupled with something else going on in the background maybe)...fun, fun...lol

Co to tablet settings and make it so the gtab wakes from sleep with the volume buttons. Also, the problem loading Widgets thing just happens sometimes. Especially if you have 2 launchers installed on your tab.

Related

[Q] HTC Desire "appears" as if it has the home button stuck, since a recent update

[Q] HTC Desire "appears" as if it has the home button stuck, since a recent update
One of our HTC Desire is exhibiting very weird behaviour since a recent update (couple of days ago). It only affects one of the phone, the second one is working fine, both were updated within the same day.
** I will try to post the software version on the next post, I think it's triggering the "No outisde link for new user" error, even though there is no outside link!
This phone only started playing up about a day after the update, not immediately. It sometimes wake up on its own and bring up the "Recent Apps" screen, as if you have long-pressed the Home key. It then switches wildly between that screen and the zoom out (helicopter view?) view of all the home screens. Initially I thought it is hardware problem and the phone is 'screwed' but I think it's more software problem, since it can work normally sometimes.
The wild screen switching made it impossible to use the phone and because it is working constantly, it gets hot and drains the battery. The problem started to get worse when we plugged it into a PC to sync and it started to go crazy. Since the screen switching so wildly, I can't get into the menu to soft reset or turn off the phone properly. So had to hard reset it, and done that more than half a dozen times.
We did have an issue when we first downloaded that recent update, both phones didn't have enough space, so the install crashed out. We freed up more space and both phones appear to have installed the update fine. Well, until a day or so after, one of the phone started playing up.
At the end, I found that if I held down the optical cursor button (very hard work), it seems to hold off the wild screen switching. I can then sort of use the phone as per normal, so that I can join WiFi and change settings & install apps etc.
I noticed that the Rosie Utility is always showing on the "Recent apps" screen. I've never seen that on a normal "Recent Apps" screen before. Not knowing what it was, I googled and learnt that it's the SenseUI. I then compared the SenseUI info with AppKik and the crazy phone is showing a different size 1.9MB (laterly 2.0MB) whereas the working phone is showing 3.0MB, althought both said HTC Sense Version 1.0 com.htc.launcher.
So I figured something must have gone wrong with the SenseUI Launcher and hence it's doing crazy thing. So I downloaded couple of other launchers, LauncherPro and ADW Launcher. They initially seem to work then all of a sudden the crazy screen switching will start and they will get worse. It seems worst if I left it on the main home screen, if I was in an App, it sometimes stay calm for a while.
In frustration, I thought I will backup my SenseUI (rosie.apk) from the working phone using Appkik and then install it on the faulty phone, but the install failed. Probably because it's being used. Tried switch the default launcher to LauncherPro, still the same. May be it needed Root access to replace? So I rooted the phone with UnRevoke3 (after a long struggle getting the correct ADB working) but still can't install the rosie.apk.
Anyhow, after rooting the phone, it mysterously settled down. I could use the phone normally for quite a while, then it started again. Although not as crazy and only intermittently. Haven't used the phone later part of today, so not sure what it's doing at the moment. When I tried the phone this morning, I stumbled across an option to un-update the senseUI, so it's now supposedly switched back to the factory default (Eclair 2.1??) version? The info from Appkik is stil lthe same though.
My question to the experts are ...
1. Can I 'update' just the latest Rosie.APK since the phone update said I already got the latest and no more updates available. ? If so, where and how?
2. If not, can I download a working copy of Rosie.apk from somewhere, and how do I write that over the existing 'possibly' faulty version?
Any help will be greatly appreciated.
HTC Desire "appears" as if it has the home button stuck, since a recent update
Attached is the TXT file containing my HTC Desire Software Version details.
For some unknown reason, it won't accept my post if I had the text from this file in the body of the post. It keeps bringing up the error about no 'outside' link for new user.
Update: If I "Cleare Default" on SenseUI in the App2SD settings, then it appears to stop the Screen Switching, but the Home button stops working altogether, the rest of the home screens appear to work normally though. Very weird. I think the problem is definitely to do with corrupted Rosie.apk (com.htc.launcher) .
Hi,
In case it helps anyone else, my home and menu button on an hd desire became intermittently broken in that they would stop working for days.
I followed this and did a clear data on the rosie utility and they work fine now.
Whoop whoop!

[Q] What should the power button do?

Hi all, I'm one of the "new to the gtablet world thaks to Woot" crew. First, thanks for what you all do here, it's a great resource.
I've managed to install the TnT Lite v4.3.0 wthout any problems and everything seems to be running well. My question is, when i hit the power button on the side, it shuts the tablet down and to turn it back on i have to hold the power button down and it has to go through the entire boot process.
Maybe thats what it is suppose to do, but being used to my iphone i imaged it would just turn off the screen and hn bring back up the lock screeen whn it was pushed again. Am i wrong or did i do something wrong when installing? Is it a setting change?
I know this question may be dumb, I'm not as tech-ignorant as this post may make it seem.
Thanks again.
A long press on the Power button should power it up. Once it's gone through the full boot cycle, a short press on the Power button should put it into sleep mode. When in sleep mode, another short press should bring it back to wake mode. A long press on Power while the gTab is fully awake should bring up a dialog box that asks what you want to do, go into Airplane Mode, Shutdown, etc. If you choose shutdown, you'll get another dialog box that asks you to confirm with a yes/no.
I am using the Stock Enhancement so maybe it works differently from yours but mine has functioned this way consistently from the time I got it, even before I loaded the Stock Enhancement.
did you try to press the "power" button lightly. when you press it lightly, it should just turn off the screen. If you press the power button and hold it for a sec, you should see a popup choice (shutdown, sleep, air mode, etc). I agree that the power button is a little sensitive to me as well and I have been using mine for 3 months and it is getting a little bit "wear".
So, it is just my solution, and it may or may not work for you. Since you are running tnt lite (not working on Vegan rom). You can download an app from android market called "Tap Tap App" power button (free)
https://market.android.com/details?id=net.maicas.android.wsleep&feature=search_result
and it will place a icon to your screen or notification bar. It basically turns off your screen, and you can press the volume buttons to turn the screen back on. I have been using this solution for a month now, and have no issues so far.
I'm pushing the button very lightly, and it appears to shut the machine down, or makes it unesponsive. Then I have to hold it down for quite a while to get it to do anything, which makes the machine reboot. When i hold down the botton (when the machine is on) I do get the options, and can put it ito sleep mode that way, and then a light touch will turn it back on. But obviously this is not the way it is suppose to run.
Is there a way to reinstall TnT or shoul i try one of the other ROMS?
Actually I think that is a problem with 4.30. If you install clemsyn's kernel it should fix it. Pershoot's may work too but I only tried clemsyn's.
It sounds like a sleep-wake issue. Like wall_fodder said, you can try to install Clemsyn or pershoot kernel. before you do install the kernel or reflash it, make a backup through clockworkmod and use titanium to backup your apps and data.
I am using 4.2.5 and very stable. Yes, you can reflash it with 4.2.x or vegan 5.1 through clockworkmod.
tyy10002 said:
It sounds like a sleep-wake issue. Like wall_fodder said, you can try to install Clemsyn or pershoot kernel. before you do install the kernel or reflash it, make a backup through clockworkmod and use titanium to backup your apps and data.
I am using 4.2.5 and very stable. Yes, you can reflash it with 4.2.x or vegan 5.1 through clockworkmod.
Click to expand...
Click to collapse
thanks, is there a step by step on this someplace?
hey all, thanks again, i restarted it in recovery mode and now everything works fine, nothing new installed or changed. Thanks so much...
I heard mixed results about 4.3.0 and sleep. For me, it works (as well as others). But some have reported issues. I'm not sure why that is -- maybe a data wipe is needed?
fyi, the recover reboot only helped the sleep issue for about two presses of the sleep button. However, I installed the Clemsyn kernel through Clockwork Mod and now it works great (after several tests). I had installed tnt 4.3.0 and 4.3.1 directly without CWM. So installed CWM on top of tnt4.3.1 then installed Clemsyn. Probably not the correct way to do it, but everything is working right now.
Lots of hail marys from this newbie while i was doing it though.

[Q] MIUI 1.6.17 - Freeze with new lockscreen after reboot!

So I updated my MIUI rom yesterday to 1.6.17. Everything worked fine, and I got one of the beautiful lockscreen to work (the five way one). It was a bit laggy, but it worked.
But now in the morning, I reboot my phone, and when I try to unlock it with the new lockscreen, it freezes! I tried opening one of the apps instead of unlocking, but that also didn't work. I tried waiting, didn't work. It's odd because when I move the unlock button (you have to move it to one of the icons, 4 apps and 1 unlock icon), it isnt laggy at all. But when it hoovers above one of the icons, and I lift my finger, it freezes. After that, the screen won't turn off, except if I press the power button, but then it wont turn on. When I press the power button along with both the volume buttons, it vibrates, sometimes more times quickly in a row.
I've also tried wiping cache and dalvik cache, also didn't help.
I'm running MIUI 1.6.17, with the stock 2.3.4 Jame Bond kernel. It has been told to me that MIUI runs best with no custom kernel, but I really wanted Voodoo Sound. This kernel worked fine.
I've seen one guy with the same problem.
mousse04 said:
I tried to apply some of the new lockscreens but each time I reboot, my phone freeze when I want to unlock it :-( !!!!!! Anyone else?
Click to expand...
Click to collapse
What should I do?
Yeah, i had the same problem It's a bug in the new lockscreen. Don't use it until it's been fixed.
Here's two solutions. [1] [2]

Four Soft Keys "stuck"?

Hey,
I've been flashing roms to my Nexus S (Rogers) since I got it last May. All 2.3 stuff (Usually NSCollab) until the last month or so, when I started playing with ICS. This seems to be an issue only with the ICS roms I've flashed - thought admittedly, I've only tryad Cyanogen and Nexus MV (Cyanogen-based)
It seems my search key gets "stuck" from time to time. Sometimes, it acts as though I'm long-pressing it... other time like I'm tapping it repeatedly. When this happens, the touch-screen still reacts normally (I can pull down the drawer, type messages in and so on) - but I can't tap back or home or the menu key. Usually (though not always), putting it to sleep for 10 seconds or so will fix this.
Anyone have any ideas what's wrong? Maybe something to try troubleshooting that I haven't thought of?
Thanks
..

Screen won't turn on after screen timeout

I've recently picked up my new Infinity and I've noticed that after the screen times out (I've set it to 30 seconds), it won't turn back on after I press the power button. Sometimes I have to press it numerous times before it will show the lock screen; other times, I've had to press the outer button down to reboot it.
Is anyone else having this issue or know what the issue is?
I have "same" problem and is driving me crazy. Did a cold boot, did a factory reset (through cold boot and through OS) - didn't help.
When my pad is in a locked/sleep state for longer time, it doesn't wake up anymore. It is draining battery as a sponge, but doesn't receive e-mails etc...so it could be it freezes or the wifi is off.
This problem is usually reported with a fact that one has enabled to turn off wifi when in sleep state (prime forums)...
My case:
- i had set wifi to never sleep
- i fiddled with build.prop and i think only after that the problem emerged (i mention this because there is a setting about sleep/wifi thing)
- i have restored orginial build.prop
- i have tried to set wifi to turn off in sleep
- i switched back to never sleep
- i coold boot, factory reset
Nothing helps anymore.
It is better with the Power Fx widget i think.
It happens less regulary, but it still does and I also don't know what else to do.
Some are reporting there is a bug in 4.0.3 ICS - but i don't know.
I think this is not a HW issue, and i refuse to do so
Hopefully JB update will solve this, too.
BTW: as i mentioned in my other topic on this matter, i am pretty surprised that factory reset didn't change my bootanimation and some other stuff on the system folder. Because of this fact i think factory reset will not help with this problem as it seems it leaves some things intact, which could also mean that if there is something wrong with SW it just doesn't overwrite/change it and that's why the problem is still here (broken file, changed file, cache...i don't know).
If this problem persist for a week or so and if there is still no JB update i will probably just go and install the latest update manually, which i think should overwrite all files. But, not sure.
Please if anyone has any idea on what is going on....
I have this same issue. It usually occurs after long periods of being idle and I pick it up to use it, hit the power button to wake it up, and it just doesn't wake up.
I have to hold the power button + vol down button to restart it.
Sometimes it'll happen when I just put it to sleep too or after short idle periods.
It's somewhat embarrassing when in public using it and randomly have to reboot; it also did it once when I was in class taking notes, thankfully SuperNote saves as I go.
Any ideas what the cause is? I'm only rooted, no custom recoveries, ROMs, kernels, etc. I'm running the stock ROM .26

Categories

Resources