so I really need thumb keyboard, or for that matter anything other than the stock keyboard. in cm7.0.3 (fresh wipe), literally as soon as I switch to any keyboard other than the stock keyboard, it instantly force closes and continuously keeps force closing until i switch back to the stock keyboard. the same thing happens on the latest nightly build (86). anyone else had this issue?
things tried that didnt work:
thumb keyboard is installed in system/app
tried clearing the data on thumb keyboard
fixed permissions in CWM.
re-partitioned to 2048 / 0
did You try to clear data and cache on thumb keyboard? or to move it to system/app instead of user apps?
I already moved it to the system/app folder (it wont let me even come close to use it unless its in system/app). and I just tried clearing the data (there wasnt any cache to clear) and nothing changed.
You might want to fix permissions in clockworkmod. That will often fix recurrent force closes.
raphenucleus said:
You might want to fix permissions in clockworkmod. That will often fix recurrent force closes.
Click to expand...
Click to collapse
fixing permissions did not fix this problem. gahhh I really like CM7 but I NEED thumb keyboard.
Funny that you are having such troubles. With CM7 and other built form scratch type of ROM's, I have never had issues with Thumb Keyboard. I don't even need to put it in system.
Maybe try a fresh format and reinstall of your rom. Maybe even nvflash to stock and repartition the SDCARD. I know it seems extreme, but that will probably work bc soo many people use thumb keyboard on CM7 and its variants.
I'm running CM 7.0.3 on one of my gTabs and also installed Thumb Keyboard straight from the Market without any tweaking or moving it to this folder or that folder and it works fine for me.
ramerco said:
Funny that you are having such troubles. With CM7 and other built form scratch type of ROM's, I have never had issues with Thumb Keyboard. I don't even need to put it in system.
Maybe try a fresh format and reinstall of your rom. Maybe even nvflash to stock and repartition the SDCARD. I know it seems extreme, but that will probably work bc soo many people use thumb keyboard on CM7 and its variants.
Click to expand...
Click to collapse
I nvflashed to stock, but it went into a bootloop for some reason. I was able to nvflash clockworkmod on it so I was able to save myself from being bricked but after that, I wiped and re-partitioned but still no dice. here is the error line from the log:
W/dalvikvm( 1607): No implementation found for native Lcom/beansoft/keyboardplus/BinaryDictionary;.openNative (Ljava/nio/ByteBuffer;II)I
D/AndroidRuntime( 1607): Shutting down VM
W/dalvikvm( 1607): threadid=1: thread exiting with uncaught exception (group=0x40015560)
I/Process ( 1607): Sending signal. PID: 1607 SIG: 9
W/KeyCharacterMap( 1596): No keyboard for id 0
W/KeyCharacterMap( 1596): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
really? no one else has this issue???
Related
I've been experiencing multiple ANR's so I tired to run an adb logcat and all i get is a scrolling "failed binder transaction". From what I can find, by searching, it has to do with rogue applications... I'm very new to this stuff, but I dont want to just ask for an answer or someone to hold my hand, I am here to LEARN.
If someone can help me understand what or where to look I would appreciate any type of help.
CLIFF NOTES:
(problem)
Market stuck loading or FC and ANR's
(what i've done)
-search
-wiped
-reformat ext3 partition
-cleared dalvik cache
-re-flash
-re-download
-Nand-BU, manually and through recovery
-run "fix_permissions"
(what I am running on the phone)
-Cyanogen 3.9.7
-Cyanogen 1.4 recovery
-8 gig Class 6
(what I am looking for)
-help
-to learn
-understand adb and fastboot better
-to be able to help others and myslef in the future
I'd also like to add I can run 3.8.6.1 completely STABLE. Once I flash 3.9.7 the everything reverts???
If you need me to give more info/backstory to my problem or have questions, links or answers I will appreciate it.
Thanks in advance,
Jay
Agh... good one. And you've done all the steps required. Send a log to Cyan (pm him) he should be able to help you.
In the mean time, try doing this
Flash last stable configuration that you had (make sure there's no theme)
Download 3.9.1, wipe, flash 3.9.1 and WITHOUT wiping flash 3.9.7.
From there, drop in console and clear your dalvik-cache and reboot.
Do you have comcache or linux-swap running? I would disable those as well for the time being until u stabilize
Good luck... let us know how it turns out.
Actually this seemed to work pretty well. last time I got results like this was when I wiped the EXT3 partition. Seems to be holding. I will report back later today and tomorrow morning. Thanks Borodin... I owe you considering you're the only one who has tried to help on this board. If you'd like me to donate something to any dev on your behalf let me know! Even if it ROM breaks again the offer still stands!
UPDATE: I can actually browse the market, but when I click to DL, it doesn't prompt into the notifaction bar.
Any takers on this one??? Market not prompting DL's to start
All~G1 said:
Actually this seemed to work pretty well. last time I got results like this was when I wiped the EXT3 partition. Seems to be holding. I will report back later today and tomorrow morning. Thanks Borodin... I owe you considering you're the only one who has tried to help on this board. If you'd like me to donate something to any dev on your behalf let me know! Even if it ROM breaks again the offer still stands!
UPDATE: I can actually browse the market, but when I click to DL, it doesn't prompt into the notifaction bar.
Any takers on this one??? Market not prompting DL's to start
Click to expand...
Click to collapse
@ All~G1 thanks for pointing me to this thread and even i had your problem..for me sometimes random times it wouldn't just download the app n show in the notifications bar but when i restart the phone it would automatically pop up the download n finish it off
and for me the market isn't even able to open..i just think that i screwed my database tho...even the browser has got same error .../databases/browser.db is null
For me probably a wipe would work but want to know if this is a bug in the rom or the app pls ?am going to skool right now so i'll come back n try to wipe n update the post
[highlight]NOTE: Am posting below my original post that i posted in the cyanogen rom thread[/highlight]
hey guys...i din update my g1 for a long time...just upgraded from 3.6.7.1 to 3.9.7 today i did the backup from the app backup for root users n everything went fine...i restored them after having done a wipe and installing 3.9.7 but market gimmes me a fc and it seems that assets.db din get restored...everything else got restored fine(sms,call log,etc)...i saw the error from the log which is below..i tried to browse the /data folder via astro but couldn't.
Code:
08-07 15:55:59.593 I/ActivityManager( 1378): Starting activity: Intent { action=android.intent.action.MAIN categories={android.intent.category.LAUNCHER} flags=0x10200000 comp={com.android.vending/com.android.vending.AssetBrowserActivity} }
08-07 15:55:59.683 I/ActivityManager( 1378): Start proc com.android.vending for activity com.android.vending/.AssetBrowserActivity: pid=3317 uid=10006 gids={3003}
08-07 15:56:00.103 I/ActivityThread( 3317): Publishing provider com.android.vending.SuggestionsProvider: com.android.vending.SuggestionsProvider
08-07 15:56:00.353 E/Database( 3317): sqlite3_open_v2("/data/data/com.android.vending/databases/assets.db", &handle, 6, NULL) failed
08-07 15:56:00.363 D/AndroidRuntime( 3317): Shutting down VM
08-07 15:56:00.363 W/dalvikvm( 3317): threadid=3: thread exiting with uncaught exception (group=0x40019a68)
08-07 15:56:00.373 E/AndroidRuntime( 3317): Uncaught handler: thread main exiting due to uncaught exception
08-07 15:56:00.553 E/AndroidRuntime( 3317): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.vending/com.android.vending.AssetBrowserActivity}: android.database.sqlite.SQLiteException: unable to open database file
p.s trying to restore again with backup for root users failed...any suggestions please??
Would just pushing the file via adb or terminal work guys ??
The browser too fc's n gives me this error in logcat n followed by a bunch of other stuff
Code:
sqlite3_open_v2("/data/data/com.android.browser/databases/browser.db", &handle, 6, NULL) failed
@ All~g1 I read somewhere that sometimes the notifications dont come cuz of the gtalk service not logging in and stuff....so once check that too...hope tat helps....
[highlight]update on my condition:[/highlight]
i wiped it completely again and just when restoring deleted the files that werre causing the trouble i.e the asses.db n database.db n everything is fine...sorry about the posts guys if caused any problem with all the postings...hope this helps some1 else...
Dare{D}evil said:
@ All~g1 I read somewhere that sometimes the notifications dont come cuz of the gtalk service not logging in and stuff....so once check that too...hope tat helps....
[highlight]update on my condition:[/highlight]
i wiped it completely again and just when restoring deleted the files that werre causing the trouble i.e the asses.db n database.db n everything is fine...sorry about the posts guys if caused any problem with all the postings...hope this helps some1 else...
Click to expand...
Click to collapse
Did you erase .db manually or just by wiping??? if you did do it manually what was the commands you used to do so?
:::UPDATE:::
I finally broke down and used my barnd new sd card and to my amazement I have not seen one FC, ANR and my market is FLYING. I hope I dont jinx myself since its only been an hour. I figured it was worth a shot so worse case scenario get a new card.... I'll update again tomorrow!
All~G1 said:
Did you erase .db manually or just by wiping??? if you did do it manually what was the commands you used to do so?
Click to expand...
Click to collapse
just by wiping...then restored using backup for root users.....
Just an FYI.... before you guys wipe completly, try going into app management and clear the data from application that causing troubles (like market or google talk). A lot of times that will fix the problem and you will not have to set up your phone all over again. Also, if you it has anything to do with google - clear "google apps" data as well. Yeah, you will have to sign-in again but it's better then re-setting you phone again.
all~g1: if you feel like donating -donate to whoever is your rom builder (JF, cyan) I don't care. It seems like everyone is expecting donation for every little thing they do so I don't want to be behind I have a very limited knowledge though so I'd prefer to keep our pro's happy.
I don't always check these forums, you can gtalk to me if you have any problems
borodin79 a t g m a i l . com
Good luck.
I found that whenever I flash an updated ROM or apply some themes that quite a few of my apps stopped working and had to be re-installed, especially private apps. The fix has always been re-install. This drove me nuts as some of the apps required a reboot (i.e. mobiledefense) I took a look at my logcat and saw an error (sorry, don't have exact as I figured it out after closing the logcat) regarding a mismatch between odex and dalvik cache. I went through and deleted my app-private/*.odex files. They ALL started working without a reinstall. I have since gone through and removed all of my .odex files and have created a script to do so in assuming this could happen again.
I had a hard time figuring it out because it wasn't all apps, just some. What I discovered was the userinit.sh and user.conf here as a default set this:
odex_auto=1 # perform auto create or del odex for applications installed or removed within 3 days
So it would create .odex files within the parameters outlined. I've since turned it off.
I know .odex has something to do with optimization, and I noticed they are not re-created at any noticeable time. My question is, are there any detrimental effects from deleting them? Will it decrease performance or have any other ill effects on the applications?
If it actually helps performance, I can delete and rebuild them after I do a flash that has this issue. I just don't know if it is worth the effort.
Thanks for any input that may be coming!
Usually there isn't a problem deleting odex files since the system recreates them anyway, but on a similar note, instead of doing that, since you run latest Cyan recovery..go into console mode and type "FIX_PERMISSIONS", it should fix the force closes issues you may be having. This basically fixes the mismatch issues you may be having.
prash said:
Usually there isn't a problem deleting odex files since the system recreates them anyway, but on a similar note, instead of doing that, since you run latest Cyan recovery..go into console mode and type "FIX_PERMISSIONS", it should fix the force closes issues you may be having. This basically fixes the mismatch issues you may be having.
Click to expand...
Click to collapse
Thanks Prash. I've tried fix_permissions from the recovery console and even the new and improved one here previously, which I think is now integrated into Cyanogen's build with no luck. That's when I decided to look a little deeper. I don't know if it was a timing issue with the userinit being set the way it was, but deleting them always worked.
Question from this then for curiosity's sake. When do they get recreated? I have rebooted, updated (maybe not re-installed) numerous times and still don't have any new ones since disabling it in the userinit script.
I also remembered and re-found this, where Cyanogen himself said "Don't .odex your apps, it's a waste of time.".
So, I guess I'll start blowing them away Thanks!
Sorry to start a thread on this but I couldn't find a simple enough answer for how to fix this in windows.
I tried to install smart keyboard, and I removed the original LatinIME.apk. When I put it back in everything was back to normal originally. I then tried to install smart keyboard again(which didn't work again), and when I go to put the original LatinIME back in the system/app folder it won't take.
I tried pushing it on adb and came up with a stale nfs file handle error. Anyone know a fix on windows?
I had the exact same thing when putting better keyboard on my NC. Using a Mac I did a repair on the adb mounted drives of the NC and that fixes the stale NTSC handle error.
So, after having installed the last few iterations of COS-DS (April 21st through May 1st) I cannot seem to get ADW EX installed or any other custom home application. It always ends with that the application cannot be installed. Yoshi RC6 and 7 haven't had this same issue and honestly I've never encountered it before. I've tried fix permissions, wiping caches, switching install location.
I also notice in the thread someone makes brief mention to this, but is replied to by Roalex as being fixed in the latest rom. (which at the time was April 26th)
Any Help?
Igneo676 said:
So, after having installed the last few iterations of COS-DS (April 21st through May 1st) I cannot seem to get ADW EX installed or any other custom home application. It always ends with that the application cannot be installed. Yoshi RC6 and 7 haven't had this same issue and honestly I've never encountered it before. I've tried fix permissions, wiping caches, switching install location.
I also notice in the thread someone makes brief mention to this, but is replied to by Roalex as being fixed in the latest rom. (which at the time was April 26th)
Any Help?
Click to expand...
Click to collapse
I would think that is happenning becuz u have the default install location in sd-ext, so try installing it in the sysytem memory
As I noted, changing install location doesn't work. In fact, I don't use Sd-Ext and don't have the partition on my sdcard
Igneo676 said:
As I noted, changing install location doesn't work. In fact, I don't use Sd-Ext and don't have the partition on my sdcard
Click to expand...
Click to collapse
Try doin a fresh install, wipe everything and reflash the rom.
EDIT: Before u do that. There is a known bug that still installs apps in the phone memory even though you set the ext partition as the default install location, so they wont install, they will only install if they are installed in the sd card. Are you sure you have an Fat32 partition and ext4 partition on your sd card?
did u click allow moving(COSsettings/Application)?
As I noted, I've tried reflashing the rom (I've done it multiple times for for each of the older and newer versions of the rom that I specified). Furthermore, I stated I don't ever do SD-EXT, the partition simply does not exist for my card. I find it buggy and nasty and quite frankly I should never need it if I have a responsible amount of apps for my phone.
One of the requirements for the rom is to have a ext 4 partition.
Sent from my HTC Dream using XDA App
number of reasons an app can't install
COS sets market d/l cache to /data/download
this could be the problem
when an app installs it looks at free space on data, and then takes away 10% of the total size
so assuming you don;t use custom MTD you have total data size around 90mb
adw is about 1mb (just over)
so 9 + 1 + 1 = 11
we add adw size twice because cos d/l the temp file to data
do you have enough space on data?
it could be something else
I use ADW Ex , and it was fine with COS
BUT I installed without wiping data
(later I deleted /sd-ext/data and /sd-ext/system to start fresh I use Firerat's ddb )
either way ADW Ex ran fine
how are you installing?
a logcat of what happens during install would be nice
I made a todo list
logcat is on it
I want to write a one stop guide to bring everyone up to speed on tools like adb, logcat, fastboot and compiling maybe throw in a totally basic Linux vm to do it all (some license issues with that , so don't hold me to it)
short version
adb logcat > alogcat.txt
cheat version
http://wiki.cyanogenmod.com/index.php?title=Logcat
should be enough
Many thanks, to pawitp, FaultExeption, Jt1134, be18 and all the other people who commit to gerrit. without these, this rom wouldn't be possible
you can find the official website for this projekt here
http://www.hellybean.com/index.html
you'll find download links and faq on this site.
IRC channel:
http://webchat.freenode.net/?channels=hellybean
Install instructions:
coming from any other rom:
- make sure to have gingerbread bootloaders
- flash zip
- reboot recovery
- flash zip again
- flash gapps
if you are coming from a previous version, older than 08/28 your data will get wiped due to new partition layout!
coming from previous version:
- flash zip
Additional changes, compared to cm10.2 (this list might not be complete):
- facebook sync integrated
- option to enable high end gfx effects
- possibility to activate and customize navigation bar
- aokp clock (right/center, custom color, big/small am/pm, display weekday)
- misc settings in settings menu
- added possibility to change the colors of the statusbar toggles
- added option to enable/disable coloring of toggles
- added option to display a small bar below the toggles as indicator for toggle state
- possibility to change quicksettings tile background color
- added pie control from slim roms
- added app sidebar from chameleon os (unfortunatelly it still seems to be a little buggy...wip)
- alternate default app picker (from aokp)
- removed cm stats
- removed cm updater
- lockscreen seethrough
- possibility to change color of lockscreen text/pictures
- customizable "long press back to kill" timeout
- added HALO
- more options for rebing the hardware keys
- build.prop mods
- TRDS (The real Dark Slim)
- ...
Click to expand...
Click to collapse
Can we please keep this thread clean?
If you like Der's work, hit his Thanks button. Please refrain from posting like "Thanks", "Great ROM" or "Can't wait" These types of post just cause clutter and cloud the real questions like about wifi, the God forsaken GPS, Devil OC/UV settings,....
We have a great group here who know proper "Net-iquette", but there has been a rather large influx of new users too.
Good luck and Happy Flashing.
New ROM online here
Sent from my Olympus via Hermes.
...sorry if I'm the party-p**per but it's something I wish to know about the new version (if it is fixed or going to be). It's a long standing bug which has often driven me crazy. I've written about it in the other thread but let me restate it here and the possible workarounds that kinda work but (which) are far from elegant. Anyway here it is:
In both the 0817 and 0828 that I've tried it is there (and probably it was from the start), it's the duplicating effect that media scanner has over my media. That's to say that every time I reboot it re-adds my media, creating (false) duplicates which disrupt my music player but also the gallery. Of course an obvious work-around is to use apps which use their own SD scanner or (worse yet) to delete the "media provider"'s cache before each and every reboot.
Since smartphones -though- are almost primarily for media consumption I would prefer an actual fix to this problem. It does not belong to the "popular" bugs (bad GPS etc), but it is a bug I don't often see discussed and I think it deserves part of the limelight. Anything approaching to a fix would really "untie my hands" for one...
BTW thanks for the great rom
@guy above me
It probably isn't in the bugs list because not too many people have suffered from it.
Did you do a complete wipe before flashing 828
Sent from my SGH-T959 using Tapatalk 2
Steve - thats been a random bug since ICS and maybe even before. Try some file maintenance on your SD card. Delete the Lost.dir on your internal SD, and the .thumbnails folder in your DCIM folder. Also, maybe try backing up your important data from both the internal and external sd, format them both, then load your data back onto it. That problem always seemed to stem from cache files. I personally have never seen it, but I run basic file maintenance before every flash, it takes just a few minutes, and saves a ton of headaches.
I`m coming from 817.....So just flash allinone zip. No GAPPS? Just curious before i flash.
Guitar100 said:
I`m coming from 817.....So just flash allinone zip. No GAPPS? Just curious before i flash.
Click to expand...
Click to collapse
I needed to flash gapps because of the partition swap. So back up your apps because they will be wiped.
Sent from my Olympus via Hermes.
What about the Battery?? My battery drains too early. I can't use 1.5 hours at a stretch!!!
Sent from my SGH-T959 using xda app-developers app
Br1cK'd said:
Steve - thats been a random bug since ICS and maybe even before. Try some file maintenance on your SD card. Delete the Lost.dir on your internal SD, and the .thumbnails folder in your DCIM folder. Also, maybe try backing up your important data from both the internal and external sd, format them both, then load your data back onto it. That problem always seemed to stem from cache files. I personally have never seen it, but I run basic file maintenance before every flash, it takes just a few minutes, and saves a ton of headaches.
Click to expand...
Click to collapse
The problem seems to be on/in my external SD alone. I've formatted it before reinserting it, also I installed the version that I have now (0828) coming from stock, so I thought my starting point was a clean sheet... but no, the problem came back to haunt me, I dunno maybe my micro-SD is dying, I'm hoping that it ain't. Thanks for the reply though...
On the lighter side of things; If anyone misses the MIUI V4 like-UI
http://forum.xda-developers.com/showthread.php?t=1853132
released about a hour ago
-When you first install it might crash System UI- Just press home button and it should be back in a few seconds.
Stevethegreat said:
The problem seems to be on/in my external SD alone. I've formatted it before reinserting it, also I installed the version that I have now (0828) coming from stock, so I thought my starting point was a clean sheet... but no, the problem came back to haunt me, I dunno maybe my micro-SD is dying, I'm hoping that it ain't. Thanks for the reply though...
Click to expand...
Click to collapse
Do you have access to another microSD to try, and see if the problem repeats itself on a different card? Its worth a shot, and could let you know if its the card or not.
How to choose vc or cmc when flashing? old version only make a devil/voodoo_color works. But it seems like not working in new versions.
dddtc2005 said:
How to choose vc or cmc when flashing? old version only make a devil/voodoo_color works. But it seems like not working in new versions.
Click to expand...
Click to collapse
From OP.
DerTeufel1980 said:
Install instructions:
if you want the rom to be installed with voodoo color kernel instead of the default one, just create a folder called devil at your sdcard, and place an empty file named voodoo_color in this folder. Then just install the rom as followed below
Click to expand...
Click to collapse
I have had one bug come up on the latest build, 0901, wondering if anyone can verify. Exchange Services keeps crashing on my corporate email account. Anyone else run into this on the latest build?
Here is a logcat, if it help at all DT.
Code:
W/dalvikvm( 7890): threadid=13: thread exiting with uncaught exception (group=0x40a7f300)
E/AndroidRuntime( 7890): FATAL EXCEPTION: ExchangeService
E/AndroidRuntime( 7890): java.lang.NullPointerException
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.collectEasAccounts(ExchangeService.java:560)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.access$600(ExchangeService.java:107)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService$AccountObserver.<init>(ExchangeService.java:665)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.run(ExchangeService.java:1973)
E/AndroidRuntime( 7890): at java.lang.Thread.run(Thread.java:856)
I/BufferQueue( 412): BufferQueue: minUndequeued=2
W/ActivityManager( 3817): Duplicate finish request for ActivityRecord{40ea6a38 com.android.email/.activity.Welcome}
omnifarious said:
From OP.
Click to expand...
Click to collapse
Thanks, this works for version 0901 again. but failed for version 0830.
battery seem to be a major issue I am not sure why. I flashed 9/1 an hour go and I had the battery fully charged, other then doing the required updates and setting up my apps, I left it on alone, an hour later i notice my battery status was 76%...Android System seem be utilizing it mostly. I hope there is a solution.....other then that everything seem to be pretty smootth. It was little choppy at first and it got smoother the more i played with....
Br1cK'd said:
I have had one bug come up on the latest build, 0901, wondering if anyone can verify. Exchange Services keeps crashing on my corporate email account. Anyone else run into this on the latest build?
Here is a logcat, if it help at all DT.
Code:
W/dalvikvm( 7890): threadid=13: thread exiting with uncaught exception (group=0x40a7f300)
E/AndroidRuntime( 7890): FATAL EXCEPTION: ExchangeService
E/AndroidRuntime( 7890): java.lang.NullPointerException
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.collectEasAccounts(ExchangeService.java:560)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.access$600(ExchangeService.java:107)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService$AccountObserver.<init>(ExchangeService.java:665)
E/AndroidRuntime( 7890): at com.android.exchange.ExchangeService.run(ExchangeService.java:1973)
E/AndroidRuntime( 7890): at java.lang.Thread.run(Thread.java:856)
I/BufferQueue( 412): BufferQueue: minUndequeued=2
W/ActivityManager( 3817): Duplicate finish request for ActivityRecord{40ea6a38 com.android.email/.activity.Welcome}
Click to expand...
Click to collapse
When that happens I clear the app data.
Sent from my Olympus via Hermes.
nht48823 said:
battery seem to be a major issue I am not sure why. I flashed 9/1 an hour go and I had the battery fully charged, other then doing the required updates and setting up my apps, I left it on alone, an hour later i notice my battery status was 76%...Android System seem be utilizing it mostly. I hope there is a solution.....other then that everything seem to be pretty smootth. It was little choppy at first and it got smoother the more i played with....
Click to expand...
Click to collapse
I haven't flashed 09012012 yet so I don't know if it still utilizes the KA7 modem. If it does refer to this post:
http://forum.xda-developers.com/showpost.php?p=30966626&postcount=1255
iKoolkid said:
When that happens I clear the app data.
Sent from my Olympus via Hermes.
Click to expand...
Click to collapse
I tried that, also fixing permissions, clearing out the accounts, even pushed the exchange2.apk from 0817 which worked great to my recollection.