Database Info

[Q] Force close loop with Launcher pro as default

Hello, This is my first post. I have the vanilla GTAB with the 2 updates that were automatically loaded last Dec. & Jan. I frequently get force closes. Today when I booted the gtab, I had it connected to my pc, but I clicked 'hide' at the activate usb prompt. Then the usual force close occured in Launcher pro. At the same tiime there was a prompt that said something like "which app to use for this action" 1) desktop or 2) launcher pro. Since I thought I already set this to Launcher pro, I selected Launcher pro, and (this is the important part, I think) I checked the box to make this the default action. I had done this before so I didn't give much thought to it.
Well, the device immediatel began looping between to 'force closes' that look similar: 1) The application LancherPro (process android.acore) has stopped unexpectedly. Pleas try again; and then the second half of the loop is 2) The process android.process.acore has stopped unexpectedly. Please try again.
Note that in #2 it doesn't refer to LauncherPro.
I rebooted the ddevice and it immediately goes into the same loop.
Is there any way out of this? I can't help thinking it is caused by making the failing app (Lpro) the default action. How do I get the prompt back? Or have I bricked this gtab?
I was able to activate usb support between loops, so I have backed up all my data to my pc (whew!), but I can't get the device to do anything on it's own, other than loop. I do not have a recovery file or any of the suggested clock??? utilies. This is a completely vanilla device. Therefore booting with recovery (power + vol +) just comes up and enters the same loop.
Sorry if this is long winded, but I want to hear any advice before I follow Viewsonic cust support's instructions to ship it to them for a hardware reset. TIA, -Jim

Try Fix Permission in the Recovery. I face this problem every now and then and could not find a better permanent solution . Its really painful at times. It usually happens when my Gtab awakes from a long sleep (like remaining in standby for overnight).

I just experienced the same problem the other day. It is my third time with all the loops and force close and android.process.etc.etc. Unfortunately the GTab with the stock OS has this troublesome issue. I followed the instructions to install clockworkmod (CM) restore to stock with the 3389 mods, and now when it happens I boot into CM and first try and clear the cash and if that dosen't fix the problem then I do the wipe data/ factory reset option which is a pain, but if you have backed up everything you are back up and running with everything restored in less than 15 minutes. Do a quick search and you will find the CM solution to get your tablet back.
Hope this helps! I think everyone who has this device has gone through it. I guess for the price what can you expect, $799 for a XOOM without flash or $350 for the Gtab with flash and some issues. There is always a trade off.

Thanks VERY MUCH for the replies. So minardml, it seems you have done the factory reset yourself. Is there instructions for this online? You took the back off the unit to do it? I will search for the CM solution. Also, kshwetabh, you are right it had been several days since I used the gtab. Could you explain how to "try fix permission in the recovery?"

newbieJim said:
Thanks VERY MUCH for the replies. So minardml, it seems you have done the factory reset yourself. Is there instructions for this online? You took the back off the unit to do it? I will search for the CM solution. Also, kshwetabh, you are right it had been several days since I used the gtab. Could you explain how to "try fix permission in the recovery?"
Click to expand...
Click to collapse
@newbieJim, before wiping cache or factory resetting try Fixing permission option. It always works for me.
1. Reboot system into Recovery (Shutdown. Press and hold Volume Up(+) button and press Power button.
2. Select "advanced" ( scroll the options using Volume up/down button). Press Home button when on "advanced" option
3. Select "Fix Permissions".
This will take a while (depending on the packages/apps installed). Note that you will not see any progress bar. Once complete simply reboot.
Hope this helps . I don't know how the system looses permissions but somehow it does.
-------------------------
kshwetabh
NexusOne [Cyanogen 7| Desire HD| MM Cyanogen 7| Looking for 720P mod]
GTab [Vegan latest]
http://kshwetabh.wordpress.com/

Sorry if I led you to think that I took the back off as I did not do that. The options that I was refering to are in the menu of clockworkmod. If you haven't found the fix I was talking about (installing CM) post again and when I get home later today I will see if I can find it. I think I may have bookmarked it on my laptop.

I just keep the home button prompt on. it seems to prevent 90% of FCs and also improved the screen lag i was getting.
it may be another step, but it's less of a pain the the ass in the end.

Once again thx to all. I will attemp recovery again, but I don't have high hopes because, as I said, the loop happens even in recovery (or safe) mode. IOW, I cannot get to any menu or screen.... Only the loop. I do not think I can install any new app., but I will try tomorrow when I return.

[A700] Update destroyed touch screen response

OK so I downloaded & installed the latest OTA update (RV23RC03; 1.057) with the power mode choices, and it has completely destroyed my touch screen response! I previously had ZERO problem with this- every key press registered on both the original ROM and the 1st update. Since the latest update, everything takes 2 or 3 presses, sometimes VERY firmly, many times still without registering. This totally sux
Is anyone else having this issue? I should note that I do have a matte screen protector on; this previously caused NO problems.
Is there an easy reasonably safe way to revert back to the 1st update (RV07RC06; 1.029)? A link and/or instructions appreciated. Thanks.
Acer, are you out there? This exact issue occurred with my A510 on its 1st update, after which it became nearly unusable for me. Since it was < 30 days I was able to return it. No such luck this time. Why are these updates doing this? It's driving me nuts!

No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.

More specific instructions
Itchiee said:
No issues with touch on update. It seems to be running better actually.
Try to completely reset thru recovery with wipe data maybe.
Click to expand...
Click to collapse
That's so amazing. I went from no problem at all, to I can hardly use this any more; only thing that changed was the update.
Can you please be specific about how to reset through recovery. (Step-by-step if possible) and how to wipe data.
Thanks.

You can reset data thru settings/privacy but you will lose everything and start fresh.
I'll check on the other method later on for you.
Also turn up touch sensitivity in settings/display if you haven't...
Edit - it appears that the stock recovery doesnt have those options.
You can still reset by inside ICS like above, or...
Factory Reset:
WARNING: reset will start immediately
Volume button (one dot) and Power button, once buzzes release power button and then toggle the rotation switch on and off a few times

Yes of course, I have set screen sensitivity to high. I think I'd rather go back to 1st update, rather than wipe everything (I do have a backup but it's still a hassle). I can't believe no one else is having this problem.
Any idea how to revert to last update?

Someone in a german android forum mentioned that it help on his device after the update to set the sensitivity to the lowest setting and then back to middle or high.

I tried playing with sensitivity settings, turning on/off,resetting and no luck.
I actually found the ROM from before the update on this website and flashed it as update.zip with vol +power. It worked, I now have 1.029 back and touch screen works perfectly. I'm sorry to lose power management but i think I'll stay where I am . Don't ask me about a Jellybean update; I'll want it but after this I'll be afraid to try it. If anyone has an explanation for this i'd love to hear it.

[Q] Screen On Issues

I just made a bunch of mods and now I'm having trouble getting the screen to turn on. Here's what I did:
1) Unlock boot loader (Used Android Toolkit)
2) Root (Same kit as above)
3) TWRP (Same as above)
4) Installed center clock mod (This one)
5) Installed smaller DPI nav bar (This one)
6) Installed 4-in-1 reboot (This one)
After all were finished, once my screen turns off, I see it kind of light up again (though still blank) and if you press the power button, the lock screen flashes on for a moment and then automatically shut off again. All the way off. A brief moment later, I seen the screen come back on but blank.
I read there was a possible compatibility issue between the center clock and small DPI mods so I removed them. Still have the issue. I can't see how the 4-in-1 could affect the screen.
Any ideas? I search but couldn't find anything close to the issue.
Thanks

Here's a video. Hopefully the screen off but really on glow comes thru the vid.

I had too many issues so wiped back to stock.
The toolkit has a few bugs.
The center clock and small DPI nav bar apps had compatibility issues.
I was not able to revert back to stock with the 4-in-1 app.
Apparently there are still some issues with the toolkit ver 1.1. From my little investigating, I think there's a simple typo in the programming and it's looking for an older version of SuperSU (1.65 vs 1.69).
I'm back to stock, unlocked and rooted. Screen/display works.
I have no idea what broke or how it broke but it's back to normal now.

Turns out my issue was with Light Flow. Not sure on the exact steps to get this to happen. But after 2 wipes and one rebuild without any restoring, I can get the issue to duplicate.
I personally believe it has something to to with being rooted and having the app use rooted options.

[Q] long/short press not working on android phone

When I do a long press to move or delete an app/icon on the home screen, nothing happens - no wobble or options - nothing. They did flash momentarily when I first got the phone. I am also unable to move apps or widgets from the app menu. However, touch seems to work just fine for everything else. I have done a full device reset, a general reset, and have tried different launchers. Any suggestions? This is android 4.2.2 and the phone is rooted. Probably hardware but am hoping. Has anyone run across this?

[Q] Only in Actual Operating System, Phone Refuses to Unlock

Hi Everyone! This is my first forum post anywhere (I'm used to looking at these forums, but not asking questions), as this issue has me completely stumped.
The issue is that every time the Nexus 5 (32 GB - White) is started, no matter what ROM I use, the first screen always works just fine. However, if I were to hit the power button to lock the device, it doesn't unlock. If I hit the bottom arrow, it will immediately lock the screen; when it gets to the "Select Wifi Network" screen, the screen unlocks. At that point, hitting the power button will show a glimpse of the screen, then immediately lock.
If I am in either Clockwork Recovery, or TWRP recovery, there are no issues at all. The issue is only present whenever I am actively in an operating system.
Things I have tried so far: using fastboot to copy over Google's stock images back. They all replicate the issue as well... I was on Android L Preview, and started noticing the issue. First thing I did was try to fastboot the image of the 2nd to latest image (the latest one had knocked out the front facing camera for some reason... lol). I have tried both Clockwork Recovery and TWRP as alternate recovery options and tried to sideload CM 11, and that didn't do anything. I have tried clearing any partition to clear it.
Well, after all of this, I called Google, and they told me I had voided my warranty, so I decided to go ahead and open up my phone to check for any damages, and the water indicator on the inside of the phone was set off (pink). However, there wasn't any damage except for some corrosion (sweat, I am pretty sure), but that which could be found was removed.
I'm at a complete loss. Is there a reason the recoveries would work flawlessly, but the OS fails when you try to use it? Is there a way to truly nuke the entire storage device on the inside, recreate the partitions, reinstall recovery, and maybe have a completely wiping any trace of the OS? It feels like something might be staying in all the erases I have done.
Thanks much for the help in advance!!!