Database Info

[Q] Oxygen 2.2.1 on Nexus S 4G

I was running this ROM for a couple of weeks with no issues. All of a sudden if I reboot my phone and the second I unlock it I get a launcher FC???? Is anyone else getting this? I cleared davlik cache a few times with no luck. I even did a factory reset to reinstall and same issue. I really like this ROM too because of the them engine and all.

Have you tried fixing permissions in ROM manager or in recovery?
Also, what kernel are you using?
Sent from my Nexus S 4G using Tapatalk

fixing permissions?? sorry but I have no idea what that is referring to. I was using the kernel that came with the ROM and I believe that it's Netarchy. I even flashed Math's 5.5 and 6.0 kernel but that didnt help.

unomedmen1 said:
fixing permissions?? sorry but I have no idea what that is referring to. I was using the kernel that came with the ROM and I believe that it's Netarchy. I even flashed Math's 5.5 and 6.0 kernel but that didnt help.
Click to expand...
Click to collapse
To fix permissions, reboot into recovery, click on "Advanced" then "fix permissions"
If you can get into ROM Manager you can open the app and click on "Fix Permissions"

Dam, I just finished installing petes ROM 8/19 and setting everything up lol. I really like the oxygenROM so I'm willing to try that. I will have to go thru recovery since I cant even get to the homescreen when I boot.
Do you know if this actually helps? I mean from experience.

I figured out what was causing the FC's. I downloaded a few CM7 themes from the market (basic white, honeybread) and these were causing the issue. I just setup everything again and downloaded Pure Red theme and no FC after a number of test reboots.
Sweet!

Cm10 camera issues

Is there a fix for the camera issues in the latest build. Since 1012 build, I'm experiencing lots of reboots and my phone get stuck all the time when I'm using the camera. I have tried every build since then up until the latest 1108, including the latest gapps. All of them get my phone stuck or reboot. Please help
Sent from my One X using xda app-developers app

etai-ab said:
Is there a fix for the camera issues in the latest build. Since 1012 build, I'm experiencing lots of reboots and my phone get stuck all the time when I'm using the camera. I have tried every build since then up until the latest 1108, including the latest gapps. All of them get my phone stuck or reboot. Please help
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I haven't had that problem since before the two EXPERIMENTAL builds. Most of that time I've been using the leaked 4.2 camera, but I did use the stock camera a few times with no issue. I would try doing a clean install (wipe everything) of the latest nightly, if you haven't tried that yet.

etai-ab said:
Is there a fix for the camera issues in the latest build. Since 1012 build, I'm experiencing lots of reboots and my phone get stuck all the time when I'm using the camera. I have tried every build since then up until the latest 1108, including the latest gapps. All of them get my phone stuck or reboot. Please help
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Haven't had that problem. The only issue I have with the CM10 camera is the high pitched whine you get when recording video. Seems to go away if you have headphones pulled in while recording?
No reboots though. I did notice that the default kernel for ViperXL rebooted a few times per day until I changed "Keep Wi-Fi on during sleep" to "Always." I know that's not related to the camera, but that was a problem when I was running MIUI on my Desire and fixed the reboots on my One XL in ViperXL.
- Joel

lauterm said:
I haven't had that problem since before the two EXPERIMENTAL builds. Most of that time I've been using the leaked 4.2 camera, but I did use the stock camera a few times with no issue. I would try doing a clean install (wipe everything) of the latest nightly, if you haven't tried that yet.
Click to expand...
Click to collapse
I already did a clean install, with factory reset, and even formatted the sdcard. Didn't help.
Further more, I'm experiencing lots of reboot with the latest nightly (ever since the EXPERIMENTALs). Playing a game for a few minutes, reboot. Surfing the web for a few minutes, reboot. Opening skype, reboot. But the reboots are not consistent, sometimes it happens and sometimes it does not.
All I wanted is a stable JB experience, and I know CM10 is still in beta, but still, I have too much problems.

yeah, I've had the same high pitched whine issue. also, my camera is unable to record in 1080p, the files just never save

Unfortunately, Android keyboard has stopped

I installed CM10 on my AT&T HTC One X and can't type anything as the keyboard keeps crashing. I've searched all over the net for a keyboard to install but everything like Swype requires you install it from the phone directly which I can't type on. Does anyone know of a solution to this crashing issue or somewhere that I can get an alternate KB?
Here's the issue, the keyboard keeps crashing and the home button doesn't work either.. the phone just vibrates when I press it. I installed the CM10 nightly build plus the gapps-jb-20121011-signed.zip GAPPS. I've been searching all over and search keeps breaking on xda so I can't find much on here right now.
-Keith

kelkin said:
I installed CM10 on my AT&T HTC One X and can't type anything as the keyboard keeps crashing. I've searched all over the net for a keyboard to install but everything like Swype requires you install it from the phone directly which I can't type on. Does anyone know of a solution to this crashing issue or somewhere that I can get an alternate KB?
Here's the issue, the keyboard keeps crashing and the home button doesn't work either.. the phone just vibrates when I press it. I installed the CM10 nightly build plus the gapps-jb-20121011-signed.zip GAPPS. I've been searching all over and search keeps breaking on xda so I can't find much on here right now.
-Keith
Click to expand...
Click to collapse
Try rolling back to the most recent stable version.
The new JB keyboard crashes on me whenever I try to save anything, but I'm running it on a Sense rom.

iElvis said:
Try rolling back to the most recent stable version.
The new JB keyboard crashes on me whenever I try to save anything, but I'm running it on a Sense rom.
Click to expand...
Click to collapse
I tried the last stable version too with the same results. Not sure why it keeps crashing on me :/
-Keith

kelkin said:
I tried the last stable version too with the same results. Not sure why it keeps crashing on me :/
-Keith
Click to expand...
Click to collapse
So you can't even interact with the "Select input method" dialogue in the notification pane? Because you should be able to remotely install a new keyboard through Play. Then once it's there, you can switch in the notification pane.

I'm having the same issue. Tried installing CM10 coming from CleanRom. Did a wipe before install.
Not only keyboard for me, home button doesn't work correctly and I cannot launch the browser.
Went back into recovery, flashed CM10 again, preformed not only a factory reset but also did a "system" wipe.
rebooted and things were fine.
rebooted back into recover and installed gapps, things are hosed again.
reproduced on gapps 4.2 and gapps-jb-20121130-signed.zip

phattychops said:
I'm having the same issue. Tried installing CM10 coming from CleanRom. Did a wipe before install.
Not only keyboard for me, home button doesn't work correctly and I cannot launch the browser.
Went back into recovery, flashed CM10 again, preformed not only a factory reset but also did a "system" wipe.
rebooted and things were fine.
rebooted back into recover and installed gapps, things are hosed again.
reproduced on gapps 4.2 and gapps-jb-20121130-signed.zip
Click to expand...
Click to collapse
Same here.. Browser won't open, home and recent apps key don't work also... glad it isn't just me.. So you're fine if you don't install gapps?
-Keith

iElvis said:
So you can't even interact with the "Select input method" dialogue in the notification pane? Because you should be able to remotely install a new keyboard through Play. Then once it's there, you can switch in the notification pane.
Click to expand...
Click to collapse
I can't even log into my google account, I can't get a keyboard to appear to type with.

OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.

phattychops said:
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
Click to expand...
Click to collapse
I can't seem to find Wipe "System" in the Factory Reset. The only options I am given to wipe are the data and cache which I have tried doing and afterwards reinstalling CM10 and GAPPS-jb-20121011-signed.zip yet the "Unfortunately Android's Keyboard (ASOP) has stopped working" still pops up

I know you have tried one of these but ill quote what Inflatedtitan gave to me when i had the same problem.
"Sounds like there could be a few problems so were gonna go with the most popular ones lol..
1. Sounds like you didn't wipe everything in twrp before you flashed. Make your you always wipe cache, dalvick, factory reset, and system. Then flash Rom followed by gapps.. then reboot
2. Have you restored from a titanium backup? If so, make sure next time its ONLY user apps.. if you restore system apps and data, think of your system settings from one Rom clashing with the system files from your new Rom. They won't play nice together. Only backup and restore user apps+data
3. If the above steps were taken correctly, I would delete the Rom.zip from phone. Maybe download using a different browser. Chrome browser is notorious for corrupting roms.. you could have had a bad download
Sent from my HTC One XL using Tapatalk 2"
With these steps I got my ROM working so maybe it could help you.

The issue y'all are having is coming from the newest gapps. Install a older gapps and you will be up and running. I had the same issue on my tab 7.0 and hox and reinstalling new gapps worked
Sent from my One X

Same Problem Over Here
majortaylor said:
The issue y'all are having is coming from the newest gapps. Install a older gapps and you will be up and running. I had the same issue on my tab 7.0 and hox and reinstalling new gapps worked
Sent from my One X
Click to expand...
Click to collapse
hi all i have sucessfully installed cm10 on my samsung galaxy s i9000
but i forgot to install gapps.
after installing gapps i just cant type anything it keeps telling me unfortunately andriod keyborad has stopped working.
what do i do?
what version of gapps can install for CM10 Stable?

xdagee said:
hi all i have sucessfully installed cm10 on my samsung galaxy s i9000
but i forgot to install gapps.
after installing gapps i just cant type anything it keeps telling me unfortunately andriod keyborad has stopped working.
what do i do?
what version of gapps can install for CM10 Stable?
Click to expand...
Click to collapse
Ask in the I9000 forums
Sent from my HTC One XL using xda app-developers app

phattychops said:
OK,
Factory Reset and wipe "System"
Install CM10
Use gapps from 1011 - gapps-jb-20121011-signed.zip
Things are working.
Click to expand...
Click to collapse
I had the same problem as others here, keyboard would stop working as soon as my One X started. The above fixed it. I only wiped System, did not Factory Reset. Make sure you're using the above version JB Gapps.

I've seen this issue when I accidentally forget to wipe something. I've found I have to wipe, flash previously working Rom, THEN go back, wipe and install new rom.
Sent from my HTC One X+ using xda app-developers app

[Q] Pac 4.3.0 Aosp Keyboard has stopped

Hello, I thought I'd try to post this here to see if any one else is experiencing this issue. I am running PAC 2.3.0, the 8/20/13 release. I have my tablet updated to the 4.2 boot loader via Version US_V10.6.1.15.3, and flashed this with TWRP 2.6 after wiping system, data cache and dalvik. After flashing the rom and the most current gapps (8/12/2013) every thing boots fine. Then I get to the setup screen and there is an error message displaying the AOSP keyboard has stopped.
I hit ok then try to enter my wifi password and some error just flickers too fast to see. I attach the keyboard dock and still no luck for typing. The home and other keys seem to function properly. After skipping through the setup I notice that the choose keyboard lay out notification in the status bar, but when choosing it the error message pops up that Settings has stopped. I have downloaded this twice onced on my pad and once from the pc. Nothing seems to be diffrent.
I know that this is still early in the game for 4.3 but, I can't be the only one experiencing this. I haven't seen any other posts on this, so if any of you out there have any ideas I am all ears. Thanks in advance.

It happened to be, but only when I tried swiping. What you are experiencing seems to be a bit more complex.
Are you able to install a different keyboard, like Go Keyboard?

I haven't tried that. I'll give it a shot.
Sent from my TF300T using XDA Premium HD

That happened to me as well but I flashed again,the rom and gapps and it worked fine

mikep2323 said:
That happened to me as well but I flashed again,the rom and gapps and it worked fine
Click to expand...
Click to collapse
I will give it another try.
thanks!

JakaraRuus said:
I will give it another try.
thanks!
Click to expand...
Click to collapse
I tried again last night. I did a dirty flash over 23 with a dalvik and cache wipe and a re-flash of the latest gapps. same deal. Then I tried with a full wipe and flash of the rc1 from 8/25 same thing except now it tells me who to blame when the keyboard stops. lol.
I have a d2vzw galaxy S III and it give the same keyboard error. So it isn't just our build.
*I found a solution a while ago, but have been too busy to post. I downloaded the official PA gApps for 4.3. Problem solved. The gApps on goo.im were form 4.2.2.*
Admin please close

[Q] System UI has stopped.. after updating to CM12

I have seen this error around on the forums a little but have not seen any answers so I thought I would try here since I have a Oneplus One. I am using TWRP to wipe and flash the latest (Jan 20th) CM12 rom plus the full gapps. I was on CM11 before this. After it boots up and goes to the setup screen it gives me an error "Unfortunately, System UI has stopped." You click ok but it just pops up again. It is possible to get through the entire setup by hitting next fast in between pop ups, but once it finishes it still pops up.
Tried wiping again and reinstalling, but got the same error. Rebooted a bunch, made no difference.
I suppose I can go back to my restore, but was hoping to try out CM12
Any ideas?
Thank you!

Think it's just a problem with this particular build (20th). I had the same issue. If you're really desperate you could try a slightly older build 18th or 19th and see if they work. I'm just gonna wait a few days and hopefully it'll be fixed
Sent from my One A0001 using Tapatalk

facing the same situation
I am facing the same situation today!!

Same here reverted back to 19th build