Last night I installed Enom's 2.11.3 ROM, GApps, and a blackbar circle battery theme (just the notification bar, not a system wide theme kind of thing). I also moved dalvik cache to /cache and enabled old style apps2sd.
Reinstalling apps, most worked fine, but several failed, and most importantly, K9 Mail won't reinstall.
When I try to install from the phone (from card, Market, etc) logcat has the following:
D/PackageManager( 486): Scanning package com.fsck.k9
I/PackageManager( 486): /data/app/com.fsck.k9-1.apk changed; unpacking
D/installd( 468): DexInv: --- BEGIN '/data/app/com.fsck.k9-1.apk' ---
W/dalvikvm( 1377): partial write in inflate (8152 vs 32768)
W/dalvikvm( 1377): DexOptZ: extraction of classes.dex from /data/app/com.fsck.k9-1.apk failed
W/installd( 468): DexInv: --- END '/data/app/com.fsck.k9-1.apk' --- status=0xff00, process failed
E/installd( 468): dexopt failed on '/data/dalvik-cache/[email protected]@[email protected]' res = 65280
W/PackageManager( 486): Package couldn't be installed in /data/app/com.fsck.k9-1.apk
If I try from adb:
1257 KB/s (1235200 bytes in 0.959s)
pkg: /data/local/tmp/k9-3102-release.apk
Failure [INSTALL_FAILED_DEXOPT]
Anyone have any ideas? Googling I've gotten the idea that it needs an odex file, but why is it failing for this ROM or configuration, and what can be done about it? Several results I found mentioned full filesystem (/system, /data, dalvik cache, etc) but those are all fine.
Okay so Enom answered in his thread on this as well, suggested I don't restore everything from Titanium so I didn't, but I'm still having problems specifically with Nook, AndroZip, and who knows what else... I've installed about a dozen random apps off the market with no problems but these two fail same as the original post.
Anyone seen this before or have an idea what might be going on?
After JesusFreake was so kind to chat with me, his opinion was that the problem was a disk full or permissions. /cache was 100% after moving dalvik-cache there, so seems like a lot of apps installed /cache is not big enough.
I wiped the system, enabled apps2sd, set up the system and my apps again, did not move dalvik-cache, and so far I've had no problems with the apps I normally install, the above apps, or any others I've tinkered with.
Hopefully my weekend experimentation helps someone else down the line.
Hi there,
Since upgrading to CM6, using a stock or custom rom, using stock, wildmonks or pershoot kernel my logs are almost overflowing with these errors:
Code:
E/JavaBinder( 120): !!! FAILED BINDER TRANSACTION !!!
These result in services, many of them system services, failing. Occasionally a soft boot will occur if it's an important service.
I can't seem to diagnose these issues further but I'm certainly not the only one experiencing them.
Any insight?
Shameless bump.
Anybody?
As certain Pandora users on this board may know, Orbot never works on Enomther's rom, but runs fine on CM and presumably stock (haven't tested stock). Orbot cycles between "Starting Orbot" and "Could not start Tor process", does this twice, then exits.
It appears to be failing at findProcessId(TorServiceUtils.java:68).
The tor log reveals:
1. "Orbot is starting"
2. "got tor proc id: -1" (i'm guessing -1 is an error flag)
3. "Couldn't start Tor process"
It then says "checking for an existing tor process", then quits on error.
I guess it can't find the tor background service.
Edit: I think the tor service isn't starting, even though Orbot thinks it did. Might have something to do with iptables or something.
Logcat: http://pastebin.com/6GESYFmm
I'm not a dev, but is there a simple solution to this? Is there something obvious I can change in the Orbot source, maybe I can compile my own client.
Thanks guys.
You're not connected to WiFi, right? Using cellular data?
See if you receive the same warnings on CM6:
09-25 04:29:38.433 W/ORBOT ( 1990): Unable to get proc id for: /data/data/org.torproject.android/tor
09-25 04:29:38.433 W/ORBOT ( 1990): java.lang.NumberFormatException: unable to parse 'app_61' as integer
Other than that, the error dump is binary - not much to do with it...
Context:
- T-mobile G1
- CyanogenMod 6.1.0-DS
Whenever I try to launch GTalk, the application starts and then instantly closes itself. I tried looking at the phone using LogCat in Eclipse and got the following line:
06-05 17:00:55.967: E/talk(710): signInAccount: failed to get GTalk connection!
What can I do to make GTalk work?
I've already tried:
- Rebooting the phone
- Reinstalling the Google Apps ZIP
... logging in with your Google account?
Sent from my Gingerbread on Dream using XDA
How would I log in? The phone already has a Google login for my account; that's why it can get my e-mail and contact information.
I'm seeing this same issue with CM 7.2.0.1 on an HTC Desire (GSM). I'd only recently (about a week ago), upgraded from a CM 7.1, but gtalk had been working for a while since that upgrade, it stopped working yesterday with the "closes very quickly after starting" behaviour.
Full logcat excerpt for an attempt (fresh after a reboot to install the latest gpapps as I'd not done that before, assuming Google Play would have updated all necessary):
Code:
I/ActivityManager( 173): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.talk/.SigningInActivity bnds=[0,732][96,800] } from pid 277
I/ActivityManager( 173): Start proc com.google.android.talk for activity com.google.android.talk/.SigningInActivity: pid=937 uid=10058 gids={3003, 1015}
D/szipinf ( 937): Initializing inflate state
I/ActivityThread( 937): Pub com.google.android.talk.SuggestionProvider: com.google.android.talk.SuggestionsProvider
D/dalvikvm( 937): GC_CONCURRENT freed 412K, 51% free 2765K/5639K, external 0K/0K, paused 3ms+6ms
D/ViewConsistency( 937): AbsListView [email protected] enabled= true
D/ViewConsistency( 937): AbsListView [email protected] enabled= true
D/GTalkService( 261): AcctMonitor.auditGTalkConnections: not starting any connections since shouldTryToConnect is false
I/ActivityManager( 173): Starting: Intent { dat=content://com.google.android.providers.talk/accounts/1 cmp=com.google.android.talk/.SigninActivity } from pid 937
W/GTalkService( 261): blockingCreateGTalkConnection failed due to low storage!
D/dalvikvm( 261): GC_CONCURRENT freed 490K, 49% free 3290K/6407K, external 0K/0K, paused 3ms+14ms
E/talk ( 937): signInAccount: failed to get GTalk connection!
W/InputManagerService( 173): Window already focused, ignoring focus gain of: [email protected]
I/ActivityManager( 173): No longer want com.android.providers.calendar (pid 503): hidden #16
W/ActivityManager( 173): Duplicate finish request for HistoryRecord{40b9e8e8 com.google.android.talk/.SigninActivity}
Note that was an in-place upgrade from 7.1.? and I'm constantly fighting with low phone internal storage on this device, although right now it shows 11MB free.
[SOLVED] Bad default partition sizes ?
It seems likely now that this was just one symptom (also had Twitter app Force Closing, Google Reader unable to auth/connect, Browser Force Closing etc) of the bad default partition setup on an HTC Desire.
I managed to get S-OFF and then use the 'CM7r2' partition setup from alpharev.nl (I've too few posts to be able to post actual links) and so far everything's working without issues. Basically the default setup has a /system way too large for CM7's needs, and using that space in /data instead gives a lot of breathing room whereas with the default /data kept on filling and causing apps problems (and, yes, this was with as much as possible APP2SD'd).
It's possible I could have solved this using SD-EXT (partition your SD card to have 2 partitions, one of ~1GB for SD-EXT, the rest for SDCARD as usual), but I didn't try that.
Athan said:
It seems likely now that this was just one symptom (also had Twitter app Force Closing, Google Reader unable to auth/connect, Browser Force Closing etc) of the bad default partition setup on an HTC Desire.
I managed to get S-OFF and then use the 'CM7r2' partition setup from alpharev.nl (I've too few posts to be able to post actual links) and so far everything's working without issues. Basically the default setup has a /system way too large for CM7's needs, and using that space in /data instead gives a lot of breathing room whereas with the default /data kept on filling and causing apps problems (and, yes, this was with as much as possible APP2SD'd).
It's possible I could have solved this using SD-EXT (partition your SD card to have 2 partitions, one of ~1GB for SD-EXT, the rest for SDCARD as usual), but I didn't try that.
Click to expand...
Click to collapse
Since I have no idea what you mean by "S-OFF" or "CM7r2", could you post the search engine keywords you used to find the instructions to use the 2 things?
S-OFF is 'security off'. It refers to a HTC phone feature where some bits of the boot sequence can't be changed whilst it's on, so you need to go from S-ON to S-OFF in order to then be able to change that part of the boot sequence. This I did using the 'AlphaRev 1.8 HBOOT reflash utility' from alpharev.nl , I applied it using VirtualBox to boot the image.
A small guide to doing this is at: http://forum.xda-developers.com/showpost.php?p=8590461&postcount=31
In turn that part of the boot sequence is where you can tell the following part that the partition table has been changed.
The 'CM7r2' simply refers to "CyanogenMod release candidate 2". Note I mentioned with regards to changing partition layout it when referring to the alpharev.nl site which contains the necessary files to change the partition setup. Just put alpharev.nl into your web browser's address/search bar to go to the site (again, I can't link because THIS site only lets you after a certain number of forum posts, the minimum of which I've not yet reached).
Hope this helps.
So you are saying that alpharev made a patched bootloader that won't check for secure flags on the g1 or you just posted in e wrong thread?
Sent from my Nexus 7 using xda premium
Ah, sorry, I forgot I originally posted about the GTalk problem in a forum not about the HTC Desire, which is what I have.
Still, anyone having such an issue may still find it's due to 'bad' partioning of their phone, whatever the model. The same basic problem may apply: /data is too small, such that it (near-)filling causes apps to randomly fail, both in the manner GTalk can (closes as soon as it opens without being able to auth, logcat suggests some problem with authing), or just simply force closing.
If your phone has enough storage that a change of partition sizes (with the HTC Desire the method I outlined reallocated some un-needed space from /system to /data) will result in a larger /data without compromising functionality then it may solve such issues.
Hi all,
after days of searching the web I hope maybe someone here can help me.
I try to encrypt my Galaxy GT-I9305. My Rom is currently "S5 Elite Lite v3.1" but I also had this prob with CyanogenMod.
So here is what happens:
I start encryption out of the menu (tried also the vdc command) with a password set. Then my device shows the green encryption sign and after that the device reboots without having encrypted. I found several solutions regarding this Problem like shrinking the Partition etc. which i tried but nothing changed.
In the logs I found theese Messages (full Logcat is attached):
I/MountService( 2685): encrypting storage...
D/VoldCmdListener( 2170): cryptfs inplace {}
E/CryptfsEE( 2170): Error reading fstab(/fstab.smdk4x12)(0)
E/CryptfsEE( 2170): Encryption type is enable inplace, remove footer
E/CryptfsFK( 2170): Unexpected value for crypto key location
E/CryptfsEE( 2170): Error inplace after framework is shutdown, no data changed, restarting system
So maybe it is the key location, but I dont have a clue how to solve this...
Does someone know this error?
Thanks in advance
Heiko