[Galaxy S II Original Android Development] Tungstwenty:
It works for me after updating to 4.1.2, but after trying it on my 2nd ROM (CM10) I can replicate the problem.

In both 4.0.3 and CM10, the permissions and ownership on /data/local/tmp is:

I found it strange that there's no "r" on others (for instance, the PackageManager or even "system") but it wouldn't explain why it works on 4.0.3 but not on CM10.

After doing a manual "adb push ..." I saw the difference.

On 4.0.3, the file will be owned by root:root and have permissions -rw-rw-rw, but on CM10 it will only get -rw-------, which makes the PackageManager complain with:

D/AndroidRuntime(12509): Calling main entry com.android.commands.pm.Pm
W/zipro (11886): Unable to open zip '/data/local/tmp/XposedInstaller.apk': Permission denied
D/asset (11886): failed to open Zip archive '/data/local/tmp/XposedInstaller.apk'
W/PackageParser(11886): Unable to read AndroidManifest.xml of /data/local/tmp/XposedInstaller.apk
W/PackageParser(11886): java.io.FileNotFoundException: AndroidManifest.xml
W/PackageParser(11886): at android.content.res.AssetManager.openXmlAssetNative(Native Method)
W/PackageParser(11886): at android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:522)
W/PackageParser(11886): at android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:478)
W/PackageParser(11886): at android.content.pm.PackageParser.parsePackageLite(PackageParser.java:749)
W/PackageParser(11886): at com.android.defcontainer.DefaultContainerService$1.getMinimalPackageInfo(DefaultContainerService.java:169)
W/PackageParser(11886): at com.android.internal.app.IMediaContainerService$Stub.onTransact(IMediaContainerService.java:110)
W/PackageParser(11886): at android.os.Binder.execTransact(Binder.java:367)
W/PackageParser(11886): at dalvik.system.NativeStart.run(Native Method)
W/DefContainer(11886): Failed to parse package

Gokhan, could you check the reason for the CM10's adbd having this behavior difference? In both roms, running umask on a shell always shows 000 and "touch file" creates with access for all. I'm guessing it's the explicit code for the push operation that has its own permissions behavior regardless of umask.

---------- Post added at 02:39 PM ---------- Previous post was at 02:34 PM ----------

I also have faced some situations where I'd like to have a last_kmsg but only have the bootloader info.

Could you try running "make menuconfig" in the build environment, entering the "System Type" menu and in the "*** Debugging feature ***" area playing around with the logging and ramdump (don't know where they end up) entries and rebuilding? Perhaps changing one of those will make last_kmsg or some other storage area retain info from the last session before reboot ...

Also, perhaps googling a bit about last_kmsg and ramdump might yield some tips on how to retain the info, even in generic linux articles not specific to android.

I never found a solution but I do remember noticing those entries.

EDIT: Just saw your previous post about a useful last_ksmg. I guess it's not yet the time that mandates that a more permanent info collector is found :)

---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------

Sorry to hear about the upcoming divorce. Well, I guess there are always personal incompatibilities that might come later along the road and there's no way you can predict all of them beforehand :(