unofficial kang cm9 question - Xoom Q&A, Help & Troubleshooting

Hi all, just installed the new 1/16/12 cm9. There was a post in the developer thread indicating that this version breaks face lock. Just wanted to pass along my experience. I did not have this issue. Facelock is working great. I did a full wipe data/dalvik/cache using the rogue cwm.
The only issue i Seem to be having is with the browser and ics browser plus. They seem very slow to respond to loading pages, and entering text (like searching in Google). Has anyone else experienced similar problems? I did not see this problem when I was on EOS nightlies build 36. Any suggestions or information would be greatly appreciated.
Also I did flash the latest gapps that was posted with cm9

Good to hear 1/16 did not break facelock for you.
I can confirm that 1/15 Kang did have oddities around certain apps closing. For example, if you close Google Currents, Youtube, B&N Nook, Kang 1/15 would pause before closing the apps (minimized). Browser and others did not exhibit this issue.
As for your specific issue, 1/15 did not have browser load or other performance issues. IMHO, 1/15 had full functionality except for those apps closing.
There are some visual artifacts in "Burn the City" game where the screen would intermittently flash on 1/15.

Same here (Installed CM9 from 1/16 with new GAPPS). No issue with the browser lagging. Did you wipe/reset your data before installing CM9 and GAPPS? If not, try wiping, then install the ROM and immediately install the Google apps (make sure you have the latest from 1/18 which is version 5.2) after the ROM without rebooting in between. Then reboot at the end. Hope this helps.

Overall 1/16 Kang is smooth. But I've had some weird app closing issues but only a few (Google Currents, B&N Nook Reader, YouTube).
When you're in the App and press HOME, the Xoom shrinks upper and lower by 1/3 and then waits for about 1/2 a sec then minimizes/closes.
On some games like "Burn the City" it causes intermittent screen flashing.
Other apps seem to run fine. Have other people seen this too?
Tempted to restore to stock and flash the official release.

Let me us know how it goes with the official release. BTW I saw on the Development threads that there's a rooted version of the official release that can be installed via Recovery so you won't need to return to stock first (saves a few steps).

reboot isues
my xoom ever since th 26th update has had restarting issues not all the time bout 4 times in a 24 hour period every time i update i wipe everything and start over but im still having this issue updating to the 29th update today i hope this fixes it has anybody else had this issue

Related

[ROM][BETA 4.0.3][Evervolv-ICS-2.1.0-01MAR-HeroC]

This is now considered a beta version of Ice Cream Sandwich for the HeroC. Please keep all comments/communication about this ROM in this thread, and keep the Development thread clean for people actively working on the ROM.
No guarantees that anything will work, or that your phone will not be turned into a brick or a toaster. Please backup if you value what is currently on your phone.
You can use this with or without gapps. If you load them both on the initial setup, be sure to select "Setup Wizard" when the system first comes up.
In its current state this ROM with GAPPS needs around 155M in /system. I am currently running firerats at 160/20 just to be safe for testing purposes. I would recommend at least 155 for system.
There are some obvious places where we can reduce the size, but that will come as we continue to refine and move forward. Performance in not great, but overall it is fairly functional. Gapps are just some a minimal version to get Market working.
THIS ROM TAKES A LONG TIME TO BOOT (ESPECIALLY FIRST BOOT).
Boot animation has been added in 26NOV version. Please be patient.
This is a work in progress and there remain many Opportunities for Improvement (the gentle euphemism for Defects).
Working (at least for me):
Touchscreen
Trackball
Phone
Data
WiFi
MMS
Audio
Bluetooth
SD Card
Market
GPS
Gallery
Boot Animation
LatinIME Keyboard
Prediction/Dictionary
Network Stats (Data Usage)
Headsets (Audio Jack & HTC 11 Pin)
Not Working:
Camera
Gallery2
Graphics Acceleration
TBD (Lots of other stuff)
25-NOV-2011 Initial Alpha release
TeamICS-4.0.1-25NOV-HeroC.zip
26-NOV-2011 Update with working GPS. Disabled broken qcom egl so that Google Maps works (slowly). FIXED LINK
TeamICS-4.0.1-26NOV-GPS-HeroC.zip
28-NOV-2011 Updated kernel for better alignment with ICS. Lots of additional updates. Updated to fix wifi issue (wlan.ko replacement)
TeamICS-4.0.1-28NOV-NEWKERN.zip
01-DEC-2011 Updated kernel to support network stats (Data usage). Modified LatinIME to show entire keyboard. Synced with CM/AOSP repos.
TeamICS-4.0.1-01DEC-HeroC.zip
06-DEC-2011 Updated with test fix for random app crashes (phone, exchange, popups, etc.)
TeamICS-4.0.1-01DEC-HeroC.zip
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Fixed trackball. Replaced Gallery2 with older Gallery for the time being. This has major changes to the source base and limited testing, so backup is recommended.
TeamICS-4.0.3-18DEC-HeroC.zip - Currently offline while resolving some issues
18-DEC-2011 Updated to latest AOSP/CM 4.0.3 source base. Update from earlier post to add audio driver fixes, and su updates that restore Superuser functionality.
TeamICS-4.0.3-18DEC-HeroC-AUDIOFIX.zip - Currently offline while resolving some issues
20-DEC-2011 Back to 4.0.1 for the time being, until 4.0.3 issues can be resolved. This version has all of the standard fixes including radio/data, trackball, and audio. Also includes Gallery instead of Gallery2.
TeamICS-4.0.1-20DEC-HeroC.zip
22-DEC-2011 Minor update to include fixes for Headset (Audio Jack) and Dictionary/Prediction.
TeamICS-4.0.1-22DEC-HeroC.zip
25-DEC-2011 Add basic Bluetooth functionality. Additional testing in progress. Classification changed to Beta, as all major functionality is working except for Camera and Hardware Acceleration.
TeamICS-4.0.1-25DEC-HeroC.zip
01-MAR-2012 Integrating development with Evervolv team. Brings alignment with ICS 4.0.3 development.
Evervolv-ICS-2.1.0-01MAR-HeroC.zip
GAPPS
You can use the latest ICS Gapps from here. Or other Gapps of your choice.
FAQ / Fixes
DATA ISSUES
If you are having issues with Data try the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
If you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
KEYBOARD ISSUE
Attached below is a replacement keyboard that doesn't have the bottom row off-screen. This is just a quick hack to get a functional keyboard. After some clean up and testing, I will include it in the releases going forward. Just replace the existing /system/app/LatinIME.apk with this one for the time being.
Reserved 2
This is also reserved for later use.
Nice.
Sent from my HERO200 using XDA App
I've got work in an hour........ so here we go, I'll let you know what happens.
whoa man, already? YOU GUYS ARE AWESOME!!
p.s- happy thanksgiving btw!!
edit:btw downloading it right now,, going to give it a go
---------- Post added at 10:45 AM ---------- Previous post was at 10:03 AM ----------
hmmm after the HTC screen, i get a black screen showing nothing. Plugged the charger and shows charging light.. Still waiting for it, it's been like 3 minutes. im on 170 40 mtd settings. K nvm it setup just appeared. For those that are trying, wait for it.
EDIT: K been messing around with it (sorry for all these edit, just trying to prevent a lot of posts and I am awake this late so might as well show some heads up) but problems I found
1) Keyboard is half (missing space bar and the alt function)
2) Screen orientation is choppy
3) Im missing the actual market app, might be firerats issue
I found a pointless feature.. but using the trackball brings up a cursor lol didn't know it'd do that. Making it "click" u have to press the ball then scroll quickly rather than just keep clicking the ball.
Thank you ICS Team. Other than the items listed in the OP, I cannot get data to work. Phone is stuck on No Service and every few minutes will jump to roaming and then back to no service. If I try to call a number with the dial pad, the dial pad disappears after I press send, I assume this is because I have no cell signal. Could not test google apps due to no data. I was still able to play with the home screen, widgets, etc.
@ Majin101, my keyboad seems to be working ok, I do have the market app but haven't tried to use it yet. I am not using firerats mod. If anyone else tries to flash this, make sure you wait a few minutes for the rom to boot as mentioned in the above post. You will see a blank screen but it will eventually boot.
This is going to be a great rom. If you use a different keyboard you also get space and alt to show up.
Findings.
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair
Freeroot said:
Okay, Seems nice. There is no bootscreen, so be patient, when setting up, choose "setup wizard"(this is kind of a no brainer, but you never know). Alright:
1. Data isn't working, I changed the roaming settings, but it didn't help.
2. As mentioned in an earlier post, the keyboard is missing some keys.
3. I do however have the market application. I used the gapps in the op and am using firerats 160 40
Really amazing work. The fact that this is even running on my hero amazes me. And they thought it would have trouble with eclair
Click to expand...
Click to collapse
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?
jaybob413 said:
Data is working well for me with the following settings:
"Data enabled" checked
"Data roaming" unchecked
"System select" Home only
Try that, and if you still have issues with data, please capture the output of "adb logcat -b radio" from boot to completely booted and post it to pastebin or equivalent.
Click to expand...
Click to collapse
Alright, that did the trick. Really nice work.
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
rizdog23 said:
As i was installing in cwm i got an error stating "random offset: 0 x 150" yet the rom still installed. Any ideas as to what this was/is?
Click to expand...
Click to collapse
I got the same error. It booted just fine and I thus ignored it. Would be nice to know though.
For those that want to fix the keyboard, just download ics keyboard from market. For those that cannot download from market, use root explorer to go into "cache" and create a folder named "downloads", for those that want to increase scrolling speed etc., flash the TweakZ.zip found in the android general forum here at XDA. I would also recommend setCPU.
I also got Random Offset 0x1ba. Once rebooted, HTC screen showed up then black screen. I waited 10 min but it looked frozen. So I pulled the battery. Then I accidentally formatted my SD card and the fun was over.
Sent from my HERO200 using Tapatalk
The "random offset" comment has to do with the flashing of the kernel. I'm not entirely sure but I think it has to do with the way the boot.img is packed. Should be harmless though..
Good to see you'll got this thing running though.
Sent from my PG86100 using Tapatalk
Another feedback!
pros
1) Ive been texting sending and recieving just fine no problems (havent tried mms)
2) Made calls talked fine (although my face kept hitting the end button..)
3) Installed swype, texting is fine now and changed the dictionary too english to get rid of those red lines under the words
4) Also increased pointer speed to just use the trackball if needed
other bugs:
1) Noticed that some of my notification doesn't make a sound or plays
2) When I play music its coming through the ear piece speaker rather than the back speaker
3) google map fails to login
Darn looks like I have to go back to CM7.1. People try to call me but my won't won't tell me someone is calling and their isn't any sound either. Also the gallery app opens but doesn't show pictures and apps are missing from the market but thats probably a build.prop issue.
-------
Just flashed without mtd and it seems to be working better. I'm receiving calls and can hear my sound now.
Great job guys! Running for about an hour and besides the above mentioned bugs, I've noticed one more.
When I put the phone on the charger it becomes unresponsive and the screen goes dark. No way to wake the phone nor is the charging led on.
The only way I can charge the phone is to do a battery pull and boot the phone while on the charger.
mines charging and im still able to use it?
Very Impressive, to say the least!
*note for the development team - you are the F-ing man!!!!

[Q] EaglesBlood AOSP

Recently installed EB 2.5 (nightly 05-07) w/ harsh kernel, and have a couple of questions/possible bugs... was wondering if anyone else has seen these issues:
- CWM (5.0.0.7) buggy from app: eg, fails to backup current ROM, cannot browse backups, etc. Runs fine in recovery, but not so hot in app
- Brightness settings. Auto doesn't seem to work, and the 50/75/100 settings are all the same
- AnTuTu sometimes doesn't do so well with SD I/O test (hangs up, then gives up)
Lastly, I know that the camcorder is a known issue w/ ICS due to shortcomings w/ LG. But I seem to remember someone mentioning a workaround w/ a third-party app. I just can't seem to find the post that I read it on... any help??
Overall, I thought I would be a little skittish about moving from CM7 to ICS, but this build is great!! Thanks to the devs!
TIA
jmgustin said:
Recently installed EB 2.5 (nightly 05-07) w/ harsh kernel, and have a couple of questions/possible bugs... was wondering if anyone else has seen these issues:
- CWM (5.0.0.7) buggy from app: eg, fails to backup current ROM, cannot browse backups, etc. Runs fine in recovery, but not so hot in app
- Brightness settings. Auto doesn't seem to work, and the 50/75/100 settings are all the same
- AnTuTu sometimes doesn't do so well with SD I/O test (hangs up, then gives up)
Lastly, I know that the camcorder is a known issue w/ ICS due to shortcomings w/ LG. But I seem to remember someone mentioning a workaround w/ a third-party app. I just can't seem to find the post that I read it on... any help??
Overall, I thought I would be a little skittish about moving from CM7 to ICS, but this build is great!! Thanks to the devs!
TIA
Click to expand...
Click to collapse
VideoCam Illusion is the app you looking for.
jmgustin said:
- CWM (5.0.0.7) buggy from app: eg, fails to backup current ROM, cannot browse backups, etc. Runs fine in recovery, but not so hot in app
- Brightness settings. Auto doesn't seem to work, and the 50/75/100 settings are all the same
Click to expand...
Click to collapse
CWM from the app and CWM in recovery are two different things. Anything CWM related you will want to do in recovery.
The brightness thing is a known issue, but I'm not sure what the deal is with that. Something about the sensor I believe. A miracle that it works at all... or something like that.
With the whole CWM thing you need to reboot into the recovery that way and just bypass the ROM manager app all together. And the backlight issue is being worked on but no solution has been presented yet.
jmgustin said:
Recently installed EB 2.5 (nightly 05-07) w/ harsh kernel, and have a couple of questions/possible bugs... was wondering if anyone else has seen these issues:
- CWM (5.0.0.7) buggy from app: eg, fails to backup current ROM, cannot browse backups, etc. Runs fine in recovery, but not so hot in app
- Brightness settings. Auto doesn't seem to work, and the 50/75/100 settings are all the same
- AnTuTu sometimes doesn't do so well with SD I/O test (hangs up, then gives up)
Lastly, I know that the camcorder is a known issue w/ ICS due to shortcomings w/ LG. But I seem to remember someone mentioning a workaround w/ a third-party app. I just can't seem to find the post that I read it on... any help??
Overall, I thought I would be a little skittish about moving from CM7 to ICS, but this build is great!! Thanks to the devs!
TIA
Click to expand...
Click to collapse
i have the same rom and and kernel and i already back up and everything with no issues different is i have clock mod rec 5.8.1.3 i just use rom manager to rename file

google apps are force closing

exhibit II with Peach Sunrise 2.04 ROM
I have been rolling peach for about two weeks. Upon reboot I get “the application google services framework (process com.google.process.gapps)has stopped unexpectedly… then all other apps google related force close. Dolphin and opera browsers force close as well. How can I fix this?
Try clearing Google Play Store app data as well as Google Framework Services in: settings>applications>manage applications>(find both and select "clear data"), see if that helps things...
Sent from my SAMSUNG-SGH-I747 using xda premium
it happened to me the gapps was FC every sec... i solved the problem installing the gapps again with CWM... remember to chose the right gapps file.... it happens to me while i was trying to change DPI screen size with LCD Density on JB, the market fix crashed gapps and they were FC every sec as i said... maybe installing new gapps over CWM can help you : D
Rafael Aparecido Camilo said:
it happened to me the gapps was FC every sec... i solved the problem installing the gapps again with CWM... remember to chose the right gapps file.... it happens to me while i was trying to change DPI screen size with LCD Density on JB, the market fix crashed gapps and they were FC every sec as i said... maybe installing new gapps over CWM can help you : D
Click to expand...
Click to collapse
I will try that, I will have to wait untill i get home as I am at work. Its killing me! I feel lost and naked without a working phone!
@Apex_Strider I did what you said... it seemed to help for a few min. Then back to FC....
weigel294 said:
I will try that, I will have to wait untill i get home as I am at work. Its killing me! I feel lost and naked without a working phone!
@Apex_Strider I did what you said... it seemed to help for a few min. Then back to FC....
Click to expand...
Click to collapse
Yeah, I'd say try a new Gapps package file and flash in CWM, also might not hurt to select the "fix permissions" option under advanced in CWM as well...
Sent from my SAMSUNG-SGH-I747 using xda premium
Exhibit + Peach Sunrise + Go Launcher = eventually many apps Force Close => Repeat ag
I've searched the forums and can't find a solution that fits my problem.
I bought a Galaxy Exhibit II with Monthly4G - love the form factor, accessible battery, expendibility (compared to big $$$ phones).
TMO default load was very unsatisfactory.
I flashed it to Peach Sunrise 2.04, ran V6 supercharger and the phone became what it should be - a good performer.
I also loaded go launcher.
I thought it was stable and just installed apps, updates, etc as I wished (you know like I did on the iPod for 6 months before committing to the android platform.)
For the second time the phone just melted down - starts getting all kinds of random Force Closes - reboots don't help.
I also tried clearing all cache and davlik, uninstalling google play updates.
However, the problem is also affecting some core services and almost any app I start on demand - including backup apps!
I had recently installed some updates and three wifi teathering apps (to make teathering easier). On one of the reboots go launcher went through it's setup several times (I know there was an update recently).
I am really enjoying the android platform and this inexpensive phone - but I really don't want to be reflashing it every 4 weeks.
Here are my questions:
Q1) Does anyone recognize my combination of software or a specific software as causing general instability (Peach Sunrise + Go launcher OR Wifi Tether utils that require root)
Q2) Is there a way to trace what causes the instability? (In my day job I use detailed tracing utilities on Windows to find problems with Apps / OS). I found catlog - but didn't have it installed and can't get it installed now.
Q3) Could I be getting hit from a virus or hacking? (I am running "Lookout" antivirus)
Q4) Does anyone else have this challenge of persistent reflashes required?
I'm not expecting to be hand held here - but when I search "Force close" with any combination I get a lot of information that ends with the solution of reflashing. If that is the only solution I can't be reflashing every month.
Thanks for any help.
I have this problem. So far, I can only find a temporary fix. Flashing anything or clearing cache or dalvik cache in Recovery mode temporarily fixes this problem.
I only get this problem when I'm using Instagram though. I don't know why.
I have this problem on my samsung exibihit 2 4g after flashing it back to stock because of the problem with sending texts while on data. And now none of my apps are working. i had to switch phones because i cant ecen text on it now. If anyone has a fix gor it please message me your suggestions. Thank you
This seems to be Talk crashing. I get the same FC message. I have to login manually to get Talk online again. Anyone else notice that

Team EOS 4.2 MR1 01192013 nightly

Experiencing crashes in various apps. New to this revision.
EOS4 173 - Xoom Wingray
I am also running EOS4 011913 (173) nightly, and I've been experiencing lag in almost every animation - launcher, notification pulldowns, desktop switches, and especially the app drawer opening and closing. These problems were mostly able to be mediated with a combination of a third-party launcher like Nova, and some gentle adjustments to the System/Performance settings in EOS Control Center.
But I digress. My biggest problem is that there is noticeable audio lag, almost everywhere in the system. Music starts a split second after I hit Play, games' sound effects happen just after the events (Jetpack Joyride is atrocious about this one), and most aggravatingly it seems to be cumulative; running an app longer makes the lag worse. Music and videos don't seem to have it quite as bad as games, but it's still noticeable.
I tried to isolate the problem (wipe everything, reflash, try apps without changing anything first) and it's still recurring, as badly as before. I don't want to give up on EOS yet, but to my knowledge after diligent Googling I am the only person who seems to be suffering this sound delay problem.
It is my sincere hope that the devs will pick up on this two-post thread, or that someone more qualified reports this problem somewhere more noticeable.
-K
--EDIT
"Stock" EOS4 173 was still having the audio lag with all the settings default (and I would hope that none of the settings, which are mostly for the interface, would create this lag), but some other users (whom I'd like to thank, but can't) suggested adding the boot.img (kernel) from CyanogenMod 10.1's latest nightly into the .zip for this, and it seems to have worked like a charm. It remains to be seen if the problem will resurface with prodding into the settings (which I'd really like to do!) again, but there it is.
donrull, I don't know if your problem would be fixed by using the different kernel, but it seems to have fixed a multitude of problems for other users
I noticed the same lag in launcher when I still had the Xoom with EOS4, but I kindda found another workaround(there is a set of tweaks mentioned in the main EOS thread which is a little too much modification for me) to that.
The last option in Power options will hide both the status bar and navigation bar, with those bars gone, launcher just becomes "butter" again.
I then used GMD gesture for all the actions and it was much more acceptable to me, hope this helps with the launcher lag for you too
I wanted to return to weigh in on my trial and error process, in the hopes that it helps someone else:
In this order:
Wiped /data, /cache, and the Dalvik cache via CWM Touch Recovery.
Flashed the 'stock rooted' JB 4.1.2 to get root, something that was missing before. I don't honestly know if it'll help these issues, but it seemed relevant that I hadn't done that yet. Worth noting, the stock rooted ROM has the absolute smoothest launcher/desktop/app drawer animations I've seen, even over the stock OTA 4.1.2.
Wiped /data, /cache, and the Dalvik cache via CWM Touch Recovery. (Always, between all flashes.)
Flashed the lastest EOS nightly (20130126-174), followed by the latest Gapps package (20130105). Launcher/desktop/app drawer lag was back, and my earlier mentioned SEVERE audio lag (almost half a second) was back, on the keyboard and in apps.
Nova Launcher with 'Fast/Fast/Jelly Bean' animation settings and all the animation settings in Dev Options set to 0.5x was, and remains, the best-looking solution to the launcher lag. App drawer still has a slight, but noticeable, lag, even with only stock apps inside. Switcher lags, sometimes severely, even when entering or exiting a less intensive app like Google Play Music.
This audio lag, though: It appears to be isolated to EOS's updated Tiamat kernel, as it was fixed (as mentioned earlier) by replacing it with the latest from CM10.1. This fixes the audio lag and slightly alleviates the notification bar pulldown lag, but the launcher/desktop/app drawer still needed Nova to seem close to 'butter' again. This also disables OC, the kernel doesn't support it but EOS's settings will still 'let' you, minus the 'lagfree' governor showing up; the only noticeable effect is about 100MB less available RAM at all times, and choppiness in places as a result.
Mentioned earlier, but the audio and video lag I tested BEFORE I started messing with settings like OC; even a brand-spankin'-new flash of this ROM suffers from it. Mentioned this too, I was using Jetpack Joyride to test, because its sound effects are very punctual. Tried some other apps, they suffer the same lag but I guess it isn't as noticeable. (Fruit Ninja you can hear the fruit being tossed AFTER you see it.) No messing about with the settings seemed to alleviate it, which is why I tried the kernel swap.
So basically where I'm at now is either stock-rooted 4.1.2 that looks and sounds gorgeous, but it feature-barren, or EOS's 4.2.1 that technically runs faster, but looks choppy and awkward and sounds about a half second off at all times, or EOS + CM10's kernel, that splits the difference, still suffering the animation lag and the lack of OC, but with OK audio. After five days of messing with this on 173, and today's struggle on 174, I'm about ready to give up on being 'satisfied' with EOS. I really hope this lengthy post reaches someone who can do something about it, since I am not enabled to post in development forums and cannot privately message anyone just yet.
Edit: the 'stock rooted' update is 4.1.2, not 4.1.1 as I posted previously. This seemed like kind of an important oversight.

Team EOS 4 trials and tribulations

I wanted to post this somewhere besides the short, dead-end thread about someone else's struggle with apps crashing under EOS4.
This is not exactly a question nor an answer, just information that I really hope reaches the devs who can do something about it.
In this order:
Wiped /data, /cache, and the Dalvik cache via CWM Touch Recovery.
Flashed the 'stock rooted' JB 4.1.2 to get root, something that was missing before. I don't honestly know if it'll help these issues, but it seemed relevant that I hadn't done that yet. Worth noting, the stock rooted ROM has the absolute smoothest launcher/desktop/app drawer animations I've seen, even over stock.
Wiped /data, /cache, and the Dalvik cache via CWM Touch Recovery. (Always, between all flashes.)
Flashed the lastest EOS nightly (20130126-174), followed by the latest Gapps package (20130105). Launcher/desktop/app drawer lag was back, and my earlier mentioned SEVERE audio lag (almost half a second) was back, on the keyboard and in apps.
Nova Launcher with 'Fast/Fast/Jelly Bean' animation settings and all the animation settings in Dev Options set to 0.5x was, and remains, the best-looking solution to the launcher lag. App drawer still has a slight, but noticeable, lag, even with only stock apps inside. Switcher lags, sometimes severely, even when entering or exiting a less intensive app like Google Play Music.
This audio lag, though: It appears to be isolated to EOS's updated Tiamat kernel, as it was fixed (as mentioned earlier) by replacing it with the latest from CM10.1. This fixes the audio lag and slightly alleviates the notification bar pulldown lag, but the launcher/desktop/app drawer still needed Nova to seem close to 'butter' again. This also disables OC, the kernel doesn't support it but EOS's settings will still 'let' you, minus the 'lagfree' governor showing up; the only noticeable effect is about 100MB less available RAM at all times, and choppiness in places as a result.
Mentioned earlier, but the audio and video lag I tested BEFORE I started messing with settings like OC; even a brand-spankin'-new flash of this ROM suffers from it. Mentioned this too, I was using Jetpack Joyride to test, because its sound effects are very punctual. Tried some other apps, they suffer the same lag but I guess it isn't as noticeable. (Fruit Ninja you can hear the fruit being tossed AFTER you see it.) No messing about with the settings seemed to alleviate it, which is why I tried the kernel swap.
So basically where I'm at now is either stock-rooted 4.1.2 that looks and sounds gorgeous, but is feature-barren, or EOS's 4.2.1 that technically runs faster, but looks choppy and awkward and sounds about a half second off at all times, or EOS + CM10's kernel, that splits the difference, still suffering the animation lag and the lack of OC, but with OK audio. After five days of messing with this on 173, and today's struggle on 174, I'm about ready to give up on being 'satisfied' with EOS. I really hope this lengthy post reaches someone who can do something about it, since I am not enabled to post in development forums and cannot privately message anyone just yet.
EDIT: The 'stock rooted' update is 4.1.2, not 4.1.1 as I had posted previously. This seemed like kind of an important oversight.

Categories

Resources