[Q] Force Close Issues on GS2 w/ AOKP - General Questions and Answers

I am on the newest update of task650/ktoonsez AOKP for ATT GS2. The update is from 7/3 and it was working fine until last week or so. It no longer lets me use the Lockscreen options. It force closes every time I try to access it. The clock and wifi mess up occasionally too. I tried wiping/reflashing but it didnt seem to help for long (either that or I didnt wipe/reflash correctly). Any suggestions?

Related

[Q] G Tablet Cyan7.0 Market will not open

I have had my Viewsonic GTab for about 4 days now, and have probably wiped and reinstalled a half dozen mods trying to get a fully functioning Android Market. The closest I have come has been able to come only has gotten me the Market icon. But it opens a white screen which rapidly closes itself. I installed Cyanogenmod7 back to back with gapps-gb-20110307-signed.zip
After installing GApps the whole system becomes extremely buggy in general, including the home button not working. I am not concerned with that though.
I have tried many walk throughs but the vast majority of them are related to the less broken Market that you can at least semi-access.
I scoured through this and other sites looking for guidance before resorting to posting, so I hope I didn't overlook a thread that was related to this exact problem.
Regards,
Sacrifusion
Im having the exact same problem. Gmarket not force closing and homebutton not working within cyanogen
Anyone find the solution? I have had may Gtablet for months working great until yesterday. I am running CM7 daily release 5/24/11 and everything was working fine, added netflix mod to build.prop and ran it for a about a week no issues but now market opens then closes. Any help?
oncouch1 said:
Anyone find the solution? I have had may Gtablet for months working great until yesterday. I am running CM7 daily release 5/24/11 and everything was working fine, added netflix mod to build.prop and ran it for a about a week no issues but now market opens then closes. Any help?
Click to expand...
Click to collapse
You have some incredible timing buddy. After weeks of my gtab just sitting in my bag, today I decided to pop Gingerbread on it w/ a fully operational Market and it's running smoother than I have ever seen it. But, I did run into a skirmish with Netflix (MOD 2) that semibricked it for a half hour. Wound up playing many back to back games of beat the clock as it would reboot after making it to the home screen for a few seconds before I was able to make it to the app manager fast enough to uninstall it. I know there were probably simpler ways to go about it, but I'm running on only a few hours of sleep.

[Q] New Market Force Closes!!

The new market updated on my phone yesterday. It force closes every time I use it and it takes about 4 opens to download anything. It also stalls other programs and then shows the force close error box.
I am rooted with EE4 debloted with Peanut Butter and Jelly Time. No other mods (except recovery of course).
Any ideas?
Did you try to clear data under settings/applications?
Yes. Did that more than once.
anyone find a fix for this, I'm on stock Rom and its doing the exact same thing to me. Frickin annoying

[Q] Anyone experiencing apps closing on Slim Beam 7.2 2012.09.04

Hello everyone,
I installed the CM 7.2 based ROM from this thread [ROM][GB\ICS\JB][2012.09.04]Slim-CM7,CM9,CM10,AOKP.
It works fine but in about 2 months I experienced a weird behaviour.
When using the phone (it always happened using FB application but it could be just a coincidence) a message comes up and the all the running applications close.
From that point on, even after a reboot, every application I try to launch... closes immediately.
The only (that I know) way to exit this situation is to restore to default settings and so I have to reinstall everything.
Any suggestion?
Thanks
maxi2570 said:
Hello everyone,
I installed the CM 7.2 based ROM from this thread [ROM][GB\ICS\JB][2012.09.04]Slim-CM7,CM9,CM10,AOKP.
It works fine but in about 2 months I experienced a weird behaviour.
When using the phone (it always happened using FB application but it could be just a coincidence) a message comes up and the all the running applications close.
From that point on, even after a reboot, every application I try to launch... closes immediately.
The only (that I know) way to exit this situation is to restore to default settings and so I have to reinstall everything.
Any suggestion?
Thanks
Click to expand...
Click to collapse
Nobody is working or developing on CM7 sources anymore. Switch to CM9 or CM10 or Slim Bean 3.1.
I recommend CM9 if you don't want random Force Closes, 'cuz it's yet the most stable ROM for our device.
CM9 installed!
Thanks for the tip and have a nice day.

[Q] Similar problems with all JB ROMS. is it a hardware issue?

Pretty much every time I flash a JB ROM my infuse is fine for a few days. Sometimes even a week. Perhaps a bit laggy, but I guess that's expected given the outdated hardware.
Then eventually I start getting having these two issues
1) random shut offs - in this case the phone sometimes will not boot unless I pull the battery and put it back in.
2) or an error that reads something like "unfortunately System UI has stopped"
I can press "okay" and then get the error again over and over. I can only get out of it by pulling the battery, or holding the power button down.
I did go back to GB for a while and did not have any of these problems.
All my apps are installed from the play store, not restored from a backup. I do not overclock or undervolt.
I'd simply blame hardware, except I don't seem to have problems with GB.
This has always happened to me as well. I would say that its due to incompatibility with JB. Wasn't so bad on ICS but I found that on JB I would be reflashing after only about 2 weeks because it got so bad.
-Sent from that.... you know.... thing that sends these things-
DarK_DemoN said:
This has always happened to me as well. I would say that its due to incompatibility with JB. Wasn't so bad on ICS but I found that on JB I would be reflashing after only about 2 weeks because it got so bad.
-Sent from that.... you know.... thing that sends these things-
Click to expand...
Click to collapse
Try Paranoid Android 4.1.2 pa_infuse4g-2.53-04NOV2012-152548 . I have been using that with no issues except the Video camera being crap (photos just fine though), and you have to toggle wifi on and off to get it working. 4.2.2 roms don't work that well on really any phone I have tried even the Gnex I own had issues. I upgraded from AEON straight to Paranoid Android using their upgrade steps listed on their page. No problems no errors didn't even loose my IMEI.
I have tried the newest 4.2.2 roms from liquid, Cyan, and paranoid android. 4.2.2 roms acted badly for me in general I can't remember if I ever got that exact error. I Keep on wiping and going back to my 4.1.2 PA nandroid backup. I kinda think it might be a general 4.2.2 issue dunno.
Also saw this on the latest Beanstalk out 4-10 (so I think you should stick to 4.1.2 roms which of course don't get updated anymore)
Trouble Alerts/Workarounds:
Status bar/Notification Drawer - There seems to be a bug with the 4.2.2 status bar/notification drawer freezing. It is happening on numerous phones at random and there is not a fix available yet. Workaround - Numerous ways to workaround this issue, but easiest in my opinion is to go to settings - system settings - PIE - Enable/Disable PIE. This restarts systemUI and unfreezes the status bar.
Does anyone know what sh means? Android os is destroying my battery life.
Sent from my SGH-I997 using xda app-developers app
Use cpuspy
Sent from my SGH-I997 using Tapatalk 2
I hope you have now the latest JB ROMS update, and every thing is working fine.
I hope you have now the latest JB ROMS update, and every thing is working fine.
for me, Beanstalk latest build 1.205 is working awesome, battery life is like i do not need to charge for two days.
Yianaki said:
Try Paranoid Android 4.1.2 pa_infuse4g-2.53-04NOV2012-152548 . I have been using that with no issues except the Video camera being crap (photos just fine though), and you have to toggle wifi on and off to get it working. 4.2.2 roms don't work that well on really any phone I have tried even the Gnex I own had issues. I upgraded from AEON straight to Paranoid Android using their upgrade steps listed on their page. No problems no errors didn't even loose my IMEI.
I have tried the newest 4.2.2 roms from liquid, Cyan, and paranoid android. 4.2.2 roms acted badly for me in general I can't remember if I ever got that exact error. I Keep on wiping and going back to my 4.1.2 PA nandroid backup. I kinda think it might be a general 4.2.2 issue dunno.
Also saw this on the latest Beanstalk out 4-10 (so I think you should stick to 4.1.2 roms which of course don't get updated anymore)
Trouble Alerts/Workarounds:
Status bar/Notification Drawer - There seems to be a bug with the 4.2.2 status bar/notification drawer freezing. It is happening on numerous phones at random and there is not a fix available yet. Workaround - Numerous ways to workaround this issue, but easiest in my opinion is to go to settings - system settings - PIE - Enable/Disable PIE. This restarts systemUI and unfreezes the status bar.
Click to expand...
Click to collapse

Display stops working, mostly, on second boot after installing non-stock.

I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
what's the last 3 characters of your bootloader version?
heldc said:
I've got an odd problem with my p900. If I install any lollipop ASOP ROMs, the first time I reboot after initial install, the display mostly stops working. The first boot works fine, I go through the setup wizard, set everything up, and the tablet works and displays fine as long as I don't reboot.
Specifically, what will happen if I reboot is that the tablet will go through the normal boot, and get to the point when the wallpaper and status bar will come up, but no homescreen icons or anything. Then after a while, about 2-5 minutes, the display will go black except for the status bar. I can pull down the notifications drawer from the status bar, and it will display, as will the quick settings, but anything I tap to try to interact with will seemingly just do nothing. If I have 'show touches' on, then touches will display properly, anywhere on the screen, but they seem to do nothing. I've tried trebuchet, google now, and adwex, the home app doesn't seem to make a difference.
The problem first began in I want to say october, when I flashed a CM12 nightly update. I unfortunately no longer remember which nightly I was on nor which I flashed to. I of course immedately tried to flash back to the previous nightly when I discovered the problem, but it did no good. It took me a while to figure out the pattern to the problem after it first occurred, as I often don't reboot the device for a long while after a first install. I don't have a lot of spare time to devote to sitting down and just focusing on trying different things, so it wasn't until president's day weekend that I tried what I *thought* would fix it, ODINing back to stock and installing the latest CM12.1. Clearly that didn't work, or I wouldn't be posting.
I've tried the 20151104, 1029, 1006, and 0910 CM12.1s from http://forum.xda-developers.com/gal...nt/rom-cyanogenmod-12-lollipop-5-0-1-t2971945. I've also tried Civz lollipop, pacman, and resurection remix. Anything not stock based has the problem. I tried running stock, but I've been running CM since G1 days, and I just can't stand stock, even the stripped down and modded versions. It just doesn't work right, and I can't get used to it, even after forcing myself to use it for several days.
I've never encountered such a weird problem, and I can't seem to find anyone else having a similar problem. I have no idea how to troubleshoot this beyond what I've done already. I'm currently running thompatry's Cm12.1 20160212, having not rebooted after the initial install, and it's running mostly ok, but I live in dread of my battery dying, and of course I can't install any xposed modules like xprivacy or multiwindow, which is bothersome. I have the wifi only US model, v1awifi, and I'm currently running TWRP 3, tho I was on TWRP 2.8.something when the issues first started happening.
Click to expand...
Click to collapse
Have you tried changing kernel? I mean in the case of civz lollipop rom you do get an option of 2 different kernels try choosing the opposite to the one you had chosen before. Thank you, hope it helps.
I won a year ago 2 Note Pro, one works flawlessly while the other is slow af and it has the same issue that you speak about. If I stay on stock everything is good more or less (sometime little slow), but if I install Lineage or any other Custom Rom is too slow and has the same issue you speak.
I changed both batteries, but nothing to do. If anyone knows, text please.
Thank you!

Categories

Resources