Database Info

Question ROM IceColdSandwich

Hi,
I've got problems after installing IceColdSandwich ROM v.8.3 AOKP, and as I'm a newbie I'm unable to post to the correct section.
When I write messages, sometimes the keyboard doesn't respond and I have to hit many times the same character to get it written, and sometimes I get the character next to the one I hit.
Another problem is : from time to time, when I write a text, after some time the words are no more written in the text section, but they appear only in the keyboard suggestions section.
I had first the BlindIce ROM and the keyboard problems were permanent, so I changed to ICE DS ROM with Sense 3.6, there was no problem but as I hate HTC Sense, I changed to IceColdSandwich. The keyboard problems came back but very less compared to BlindIce...
Could you help me to fix these problems ?
Thanks.

May low ram? Close unnecessary apps in the background. Try switching keyboards.
Sent from my Nexus 7 running Froyo.

Adine said:
Hi,
I've got problems after installing IceColdSandwich ROM v.8.3 AOKP, and as I'm a newbie I'm unable to post to the correct section.
When I write messages, sometimes the keyboard doesn't respond and I have to hit many times the same character to get it written, and sometimes I get the character next to the one I hit.
Another problem is : from time to time, when I write a text, after some time the words are no more written in the text section, but they appear only in the keyboard suggestions section.
I had first the BlindIce ROM and the keyboard problems were permanent, so I changed to ICE DS ROM with Sense 3.6, there was no problem but as I hate HTC Sense, I changed to IceColdSandwich. The keyboard problems came back but very less compared to BlindIce...
Could you help me to fix these problems ?
Thanks.
Click to expand...
Click to collapse
i also have experience that, solution: select force closed in scrolling cache, and never use oc, governor, i have notice this when the rom is newly installed, no prob at all but when i try to OC thats when this happen, also in games the touch always release your hold so i cant even enjoy my game, and have to switch rom

I tried closing all unnecessary apps in the background and switch keyboard, but the problem persists.
I selected force closed in scrolling cache, but what does "OC" mean ?
Thanks

Adine said:
I tried closing all unnecessary apps in the background and switch keyboard, but the problem persists.
I selected force closed in scrolling cache, but what does "OC" mean ?
Thanks
Click to expand...
Click to collapse
try to install the rom again, full wipes, then first thing you do is to force closed scrolling cache, OC means over clocking, dont enable this feature in performance tab, or simply dont do anything in performance tab in rom control

Think that this problem is due to a full wipe needed. When you install a ROM, even an update of it, it's very very advisable to do te full wipe, first data, cache and if you want dalvik.This will solve some issues and save battery life (sometimes?). Moreover, if your battery is doing weird things you can do wipe battery. Read some posts about it.

Hi,
I did everything you told me but there is still the problem with the keyboard. I tried with a game and I had problems with the touchscreen too...
Is there anything else I can do ?
Thanks

Looking for help with a butt-slow stock 4.1.1 Nexus S

So I have the i9020T (from Wind in Canada). I enjoyed running CM9 nightlies on it, but then Jellybean came along and I went nutso over it (like so many others). I flashed back to stock ICS, and then ran the OTA update on it to JB.
My experience has been disappointing. It was unfathomably slow. It was running-Windows-7-on-a-Pentium-III slow. The new UI and features are glorious, but I need a lot of patience if I expected to use them. I'm talking about delays of around 5 seconds to start an app, switch apps, or even open the app drawer, 2-3 seconds lag when bringing up the keyboard, and 5-10 seconds to bring up Google Now.
I automatically decided to nuke everything and start from a clean slate. I grabbed the 4.1.1 stock image from Google, then formatted /system and threw it on. After the initial setup, and before I even got to rooting the thing (never mind restoring from Titanium), it was still muscle-atrophyingly slow.
I ended up just restoring all of my apps and data, and using it as-is, figuring this is what I should expect from an older device. Yet everyone online raves about how much faster JB is than ICS on the Nexus S. Either you're all trolling me really hard, or I'm doing something very wrong.
Here's some more gory details:
Like I said, I wiped /system before loading the new image. I did it on the phone using Clockworkmod recovery, then used fastboot from my computer to load the image. I did not wipe data or cache, because I figured the whole image-writing thing would be obliterating all my stuff anyway, but perhaps I was wrong?
I've been playing with the CPU usage overlay, available in the Developer Options. First off, I have no clue what the different colours mean or what scale those bars represent, but I can tell you my load is typically 2.0 (even just sitting there idle with the screen on), all the way up to 15 or so if I'm trying to do something like use Chrome while listening to Google Play Music. system_server is always the top process, and its bar is always 3-4 times bigger than the next, with the sole exception of loading up Google Play Music, in which case the mediaserver process holds the top spot with a fairly long bar. ksmd, com.android.systemui, surfaceflinger, and com.android.phone are always running, but only ksmd even has a bar long enough to be visible. Other processes pop in and out, and of course they start going willy-nilly when I actually start using apps and switching between them.
There have been a handful of times where an app will die while I'm in the middle of using it, and 2-3 times the phone has outright rebooted itself.
So there's my story. Can someone tell me if I'm just plain doing it wrong? Perhaps there's a guide on how to completely sterilize the phone before loading the stock image? Or perhaps my hardware is broken? :-/

I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.

Cool... I'm looking into it, and can't find any directions whatsoever on what I should download or how to install it. I'll keep digging, though. Thanks!

While I am not sure what is causing your issue I can confirm that stock jb should not be performing like you are describing. Except for loading up Google now. That does take some time but even that once its loaded runs OK.
Did you clear your SD card? If not back that up to a computer and wipe it. That's all that I can think of and it may actually fix it.

At first I noticed painfully slow speeds as well. Changing my min setting to 200 helped so much! I've heard the the Interactive governor is amazing with JB in terms of speed. You could try that out.
Nexus S. (GSM i9020a)
Paranoid (1.97 - 4.1.1)
Matrix (CFS - 22.5)
Ondemmand (1000/200)
Deep Idle (On - Deadline)

I've just flashed Air Kernel (I just picked one of four options, I don't know what the heck "blue color" means), then set the governor to smartassv2, and so far it feels snappier. I'll have to keep using it to see if it's the solution I need. Thanks to all who've made suggestions so far!
Sent from my Nexus S using xda app-developers app

If your phone is going crazy slow it could be a number of things like apps could be slowing down the phone in the background or the phone might be trying to sync. You could backup all of your apps and then wipe your phone fully it should speed it up quite a bit and then you can restore each app 1 by 1 to determine if its a rogue app causing it. But if you can't be arsed to do that and wipe then just try and flash Thalamus kernel and see what its like if you set the governor to interactive on that it should go crazy fast.
Sent from my Crespo using xda premium

Please provide clear advice Nexus S so slow on Jelly Bean
ronnygunz said:
I was with you there, trying to figure out why everyone thought it was so fast and I was being left in the dust. Google Now in particular was painful to interact with. I downloaded and installed Air Kernel, which seemed to help a little bit but then I switched the CPU governor from "ON DEMAND" to "SMARTASSV2" and it was like night and day. It's flying and I'm satisfied.
Click to expand...
Click to collapse
I can see there are many 'fixes' for slow running devices on Jelly Bean. However, I have no idea:
1. how install Air Kernel or where to get it from
2. How to change the CPU governor from "on-Demand" to "SMARTASSV2" or where to download this from
Please can someone give me the complete idiots guide to getting my Nexus S running properly again??
THANK YOU

There are a million guides on this forum for all of this. If you don't know how to flash a kernel or adjust CPU speeds, you need to familiarize yourself with these things and understand the risks. First off, try cleaning your phone up. Take all your important stuff off your external storage, and do a factory reset. My Nexus S never ever ran slow, even on stock.

Have you tried a more simple but fast kernel like marmite 4.2 from bedalus? Give it a try.

Upgraded to ICS, now wat?

was on gingerbread. waited and waited for the OTA updated. ended up rooting. ice cream sandwich update came out and couldn't get it OTA. used Kies and installed the update. finally, now have ICS. lost root access. so anyone out there with the official ics? recommend what to do now!

chandrew said:
was on gingerbread. waited and waited for the OTA updated. ended up rooting. ice cream sandwich update came out and couldn't get it OTA. used Kies and installed the update. finally, now have ICS. lost root access. so anyone out there with the official ics? recommend what to do now!
Click to expand...
Click to collapse
I'd flash a ROM. I recommend CM10 to have Jelly Bean! There are a lot of ROMS in the dev section. Go choose one. Make sure you flash a recovery!
Sent from my CM10 Blaze

I'll second the recommendation to go to a JB based rom.

any convincing wins for the JB release? as i am pretty content with what i have on ICS. everything has been smooth so far, nothing buggy at all.
improvements todo: root, remove bloatware, get wifi tethering to work (currently broadcasts signal but devices cannot connect - says connection is unsuccessful)
here are my screenshots (if i should get something else):
1. Lock screen - I noticed the text notification that appears turned black in ics, which i like. it just blends in with my lock screen wallpaper. going for the simple dark black wallpaper for longer battery life? i guess haha
farm9.staticflickr.com/8250/8453732470_8826585926.jpg
2. Screen 1 - man that weather widget that comes with Eye in the Sky is the best weather app! plain simple
farm9.staticflickr.com/8251/8453732494_45cd46759f.jpg
3. Screen 2 - My home screen with a black google search bar that came with ics, yay! also using Widgetsoid with those widgets that i happen to use quite often.
farm9.staticflickr.com/8381/8453732504_333f2afecf.jpg
4. Screen 3 - Well more Widgetsoid action going here. This is my utilities section. I just decided to turn my regular icons into the widgetsoid theme. The weather is actually USB tethering now here. I am enjoying the sound recorder and flashlight of easy access.
farm9.staticflickr.com/8385/8453732484_e8fef3b090.jpg
so yep, recommend widgetsoid and eye in the sky. AND I AM A NOOB ON XDA CAN'T POST LINKS OR PICS

Swype is a little slow in messaging for some reason. A weird icon appears every time at the top of notifications indicating 'Swype in use' so that may be making swype a bit more laggy. ANYONE EXPERIENCE THIS? this new icon appears in ics and not gingerbread. what about JB?

There is the Tweaked ICS rom also if you do like ICS. It's already debloated and optimized. The Swpye icon can be diasbled in the swype options.
Also you can disable most the bloatware now that you are on the stock ICS. Go to settings > apps > select "all" and disable what you want (if it can be).
As for JB, they are all pretty good (bug free). I'm currently using Slim Bean 3.1 with the inverted packages, but you really can't go wrong with any of them. Try them and find out. But you still have to flash CWM and make a backup with it first thing.
GL and enjoy.

Romman0 said:
There is the Tweaked ICS rom also if you do like ICS. It's already debloated and optimized. The Swpye icon can be diasbled in the swype options.
Also you can disable most the bloatware now that you are on the stock ICS. Go to settings > apps > select "all" and disable what you want (if it can be).
As for JB, they are all pretty good (bug free). I'm currently using Slim Bean 3.1 with the inverted packages, but you really can't go wrong with any of them. Try them and find out. But you still have to flash CWM and make a backup with it first thing.
GL and enjoy.
Click to expand...
Click to collapse
Whoa didn't know you can disable apps, nice!

chandrew said:
Whoa didn't know you can disable apps, nice!
Click to expand...
Click to collapse
Some may need to have the updates uninstalled first, it's in the same location.

it seems like i was able to do a lot of stuff already without rooting. thanks to the disable app feature in ICS, it is pretty much like titanium backup. ended up bypassing the built-in hotspot check and can tether wifi.
well, i ended up rooting. so what am i to use root features on?
guess i can only think of AdFree. also, i can permanently remove disabled apps. anything else to take advantage of root access?

If you go to a Jellybean based rom, most of them have button light notifications. "What is that?", you may ask...
The blaze doesn't have an LED to visually notify you if a call came or a message came...sure, the screen can activate when the call is coming, but if you're in the other room and don't hear it, or if the phone is on silent and you don't see it, you'll never know about it until you actually check your phone by turning on the screen...
Which many people do INCESSANTLY.
Button light notifications can enable the back/home/voice/settings LED to light up so you can be notified of it. It's nice to have.
Also, Google Now works by default with JellyBean, no funny business required. I had Google Now on rooted ICS and I liked it, but the only one that works on ICS for our phone is of course a much older version of Now, and it doesn't support certain features.
Google now is great, check it out on youtube or something.

This might get asked a lot but how is the battery life on JB??
For ICS, I'm currently charging about once every 1.5 days. I usually charge it at night, sometimes I can skip one night and charge it the night after. Sometimes I do use the phone a lot during the day and need to charge it within the next night, maybe even within half a day, but rarely. Sometimes I just charge it at work, so ~1.5 days. To get the 2 days worth, I'm usually Airplane mode-ing it when I'm definitely not going to be looking at my phone, such as at work except for breaks - I can probably go 2.5 days like this, but I still charge at 2.
How does JB compare?

This is from cm10

jbats said:
This is from cm10
Click to expand...
Click to collapse
That must've been the nightlies back in November huh lol
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

[Q] Updating cyanogenmod 10 to 10.1

I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?

kylepont said:
I just wanted to be sure that I am going to do this right.
Do I just go Settings > About phone > CyanogenMod updates > then download 10.1 and it will do all the work for me? Or do I have to make a nandroid backup (going to do that anyways), wipe cache and dalvik, flash boot.img then flash the rom?
Also, how stable is 10.1? Any known bugs?
Click to expand...
Click to collapse
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Sent from my One S. Please hit thanks if I helped.

zaak00 said:
The automatic updater will not work. At least if you're S-On. So flashing through recovery is the way to do it (wipes and boot.img flashing as usual also ofc). I believe flashing CM10.1 over CM10 might work without factory reset, but prepare for stuff not working and flashing it again with proper wiping.
Give it a go! It's not too hard to go back to CM10 if it doesn't please you.
Click to expand...
Click to collapse
This will be a tl;dr story so only read it if you can be bothered...
I did the automatic update, then as soon as it downloaded I had to run for the bus (one a bloomin' hour). I was then stuck on the htc splash screen for about ten minutes, did a soft reset, went into recovery, went back to CM10, restored the backup, not a problem. Then got home, pushed 10.1 onto the phone, flashed the new boot.img, then flashed CM10.1 and restored backup again. Worked fine. Then I had to try three different Gapps because two of them didn't actually work, and it was agonising that the website that I got them from only had an upload speed of around 0.4Mbs. But flashed that now, and everything works fine (although I had to delete and re-download NatWest and Play Music).
zaak00 said:
Bugwise I'd say CM10.1 is absolutely ready as a daily driver. Wifi tether doesn't work when screen is off (same issue is with CM10). Performance is a bit lower than with CM10. You'll see some screen tearing when scrolling and switching home screens and in some games with intense graphics.
Click to expand...
Click to collapse
Spotted a couple of bugs immediately. Syncing with facebook simply does not work (I only wanted contact pictures for caller IDs). Obviously the clock bug, but I know how that is fixed. Haven't had any screen tearing yet, and since Orange only give me 750MB there is nooooooooo way that I am going to use tethering, so that won't bug me. CM10.1 has fixed the music player bug, where the first song I play would take around 30 seconds to play, if I chose another song then it would restart the previous song, play that for five seconds, then play the selected song, and if I paused a song it would then start playing again for a couple of seconds after five seconds of being paused. That was irritating. Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...

kylepont said:
Noticed it seems to be a fair bit more RAM heavy than CM10, but I miss the settings button on the top of the notification bar, that tiles thing just seems to take to long for my liking...
Click to expand...
Click to collapse
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Sent from my One S using Tapatalk 2

usaff22 said:
You can also swipe down with two fingers, or set a specific area that opens the Quick Settings immediately, in Settings
Click to expand...
Click to collapse
Already knew about the sections thing, but because I'm right-handed every time I wanted to look at a notification I got settings, and setting it so that the settings open on the left side just seems a bit weird. I didn't know about the two fingers thing, and I like that, cheers.

[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