While i'm extracting a new system.sin from Nordic ICS ftf for Xperia Neo i have this problem:
Code:
1 [main] unyaffs 1088 exception::handle: Exception: STATUS_ACCESS_VIOLATION
835 [main] unyaffs 1088 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump
in stackdump is:
Code:
Exception: STATUS_ACCESS_VIOLATION at eip=004010B0
eax=9207DAAB ebx=00000084 ecx=00004800 edx=00C5147A esi=0028CD34 edi=61179FC3
ebp=0028CCD8 esp=0028CCA0 program=C:\Users\Lukasz\Desktop\Xperia Neo\ftf_extractor\unyaffs.exe, pid 7988, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CCD8 004010B0 (00C51420, 00000000, 612058E8, 00401333)
0028CD08 004013AF (00000002, 00C383C0, 00C38290, 00000001)
0028CD68 61006CD3 (00000000, 0028CDA4, 61006570, 7EFDE000)
End of stack trace
What's going on? system.sin from old Gingerbread is extracting fine
EmannsXperia said that experts from here are the best experts so i'm posting it here
Try posting in this thread
http://forum.xda-developers.com/showthread.php?p=17557317
Your friends are right the xda devs are awesome
From XDA on my XPERIA X10-S, powered by DooMKerneL
Related
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
I/ActivityManager( 93): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.cooliris.media/.Gallery }
V/RenderScript_jni( 6329): surfaceDestroyed
V/RenderScript( 6329): setSurface 0 0 0x0
D/ViewFlipper( 6329): updateRunning() mVisible=false, mStarted=true, mUserPresent=true, mRunning=false
D/LocationManager( 6198): removeUpdates: listener = [email protected]
D/NetworkLocationProvider( 93): removeListener(): wallpaper
D/NetworkLocationProvider( 93): enableLocationTracking(): false
E/NetworkLocationProvider( 93): releaseCheckLocationLock: wake lock has already been released
D/SensorManager(18699): found sensor: BMA150 3-axis Accelerometer, handle=0
D/SensorManager(18699): found sensor: AK8973 3-axis Magnetic field sensor, handle=1
D/SensorManager(18699): found sensor: AK8973 Orientation sensor, handle=2
D/SensorManager(18699): found sensor: CM3602 Proximity sensor, handle=4
D/SensorManager(18699): found sensor: CM3602 Light sensor, handle=5
W/ResourceType(18699): Failure getting entry for 0x7f02003a (t=1 e=58) in package 0: 0xffffffb5
D/AndroidRuntime(18699): Shutting down VM
W/dalvikvm(18699): threadid=3: thread exiting with uncaught exception (group=0x4001b178)
E/AndroidRuntime(18699): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(18699): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.cooliris.media/com.cooliris.media.Gallery}: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
E/AndroidRuntime(18699): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
E/AndroidRuntime(18699): at android.app.ActivityThread.access$2200(ActivityThread.java:119)
E/AndroidRuntime(18699): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
E/AndroidRuntime(18699): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(18699): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(18699): at android.app.ActivityThread.main(ActivityThread.java:4363)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(18699): at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(18699): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime(18699): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(18699): Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f02003a
E/AndroidRuntime(18699): at android.content.res.Resources.getValue(Resources.java:891)
E/AndroidRuntime(18699): at android.content.res.Resources.getDrawable(Resources.java:579)
E/AndroidRuntime(18699): at com.cooliris.media.HudLayer.<init>(HudLayer.java:121)
E/AndroidRuntime(18699): at com.cooliris.media.GridLayer.<init>(GridLayer.java:134)
E/AndroidRuntime(18699): at com.cooliris.media.Gallery.onCreate(Gallery.java:78)
E/AndroidRuntime(18699): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
E/AndroidRuntime(18699): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
E/AndroidRuntime(18699): ... 11 more
I/Process ( 93): Sending signal. PID: 18699 SIG: 3
I/dalvikvm(18699): threadid=7: reacting to signal 3
I/dalvikvm(18699): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 93): Added state dump to 1 crashes
Click to expand...
Click to collapse
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
arctu said:
I've been trying to compile AOSP apps individually and that doesn't seem to work. These are the steps I took:
1. Install GCC and Java
2. The repo commands (sync from android git etc)
3. make Gallery3D
4. push Gallery3D.apk /system/app/
So as you can see, compilation went on fine. And pushing to my phone also went fine (CM 5.0.4.1). However, when I try to run Gallery3D, I got FC. Here's my logcat:
Besides this, I noticed that my Gallery3D.apk is smaller size(~500kb) than the one which comes with CM (~700kb).
Any help guys? Been trying to figure this out and googling. What did I miss?
Click to expand...
Click to collapse
Q&A section ma man
I believe this is the right section, it's a question on compiling/development. I believe Gallery3D might be lacking mdpi images, and you're compiling for mdpi devices (may be wrong, not able to check now).
What you can do is to do a search for "PRODUCT_LOCALES", within all your files, I think it's in build.mk or product.mk. You will see that the default is mdpi, follow by <something> (can't remember now) += nodpi. Add a <something> += hdpi after the nodpi line, and compile and push again. I had a similar issue and was able to fix it this way, with advice from cyanogen.
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
nano build/core/product_config.mk
Click to expand...
Click to collapse
2. Find:
PRODUCT_LOCALES += nodpi
Click to expand...
Click to collapse
3. Add in after that line:
PRODUCT_LOCALES += hdpi
Click to expand...
Click to collapse
4. Save and Exit: Ctrl+X
5. Run make again:
make Gallery3D
Click to expand...
Click to collapse
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
*** Build configuration changed: "generic-eng-{mdpi,nodpi}" -> "generic-eng-{mdpi,nodpi,hdpi}"
*** Forcing "make installclean"...
*** Done with the cleaning, now starting the real build.
Click to expand...
Click to collapse
It works now. Hope this helps the others.
arctu said:
Thanks Wysie. That helps!
To those facing the same problem here are the exact steps I took (using terminal and nano):
1. Open/Edit build/core/product_config.mk:
2. Find:
3. Add in after that line:
4. Save and Exit: Ctrl+X
5. Run make again:
If you did everything correctly, and have compiled before, the compiler should write this at the beginning:
It works now. Hope this helps the others.
Click to expand...
Click to collapse
cheers, helped me out
after quick grep to confirm I used sed
Code:
sed s/PRODUCT_LOCALES\ \+\=\ nodpi/PRODUCT_LOCALES\ \+\=\ hdpi/ build/core/product_config.mk -i
Hey guys, I'm trying to extract system.img from a system.img on Windows 7 x64 but when I try using unyaffs, it just says
Code:
Exception: STATUS_ACCESS_VIOLATION at eip=004010A0
eax=E1A04000 ebx=00000003 ecx=00E1A000 edx=00F51DA2 esi=0028CD3C edi=00000000
ebp=0028CCD8 esp=0028CCA0 program=C:\Users\Konstantin\unyaffs\unyaffs.exe, pid 17288, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CCD8 004010A0 (0028CD3D, 00000000, 611F0108, 00401323)
0028CD08 0040139F (00000002, 00F383F0, 00F38278, 00000001)
0028CD68 61006E73 (00000000, 0028CDA4, 61006720, 7EFDE000)
End of stack trace
Anyone got an idea?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hello,
so I extracted a .DZ ROM file. The system.img(.ext4) has 6 parts:
system.img.ext4_0
...
system.img.ext4_5
How can I merge them into a functional system.img(.ext4) file in Windows?
I've used this cmd command:
copy /b "system.img.ext4_*" "system.img"
Then I used unyaffs to extract it, but it returned this errors:
7 [main] unyaffs 1564 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1529 [main] unyaffs 1564 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump
1114863 [main] unyaffs 1564 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1131084 [main] unyaffs 1564 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
The content of unyaffs.exe.stackdump is:
Exception: STATUS_ACCESS_VIOLATION at eip=610DEFA1
eax=00000000 ebx=00000009 ecx=FFFFFFFF edx=00000000 esi=611021A0 edi=00000000
ebp=0028CC08 esp=0028CC04 program=C:\***\unyaffs.exe, pid 1564, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CC08 610DEFA1 (00000000, 0040DC70, 00000200, 610E5635)
0028CC48 004010BF (0028CCA9, 00000000, 0040130E, 00401333)
0028CC78 004013AF (00000002, 00F401B0, 00F40090, 610BEE77)
0028CD58 610060D8 (00000000, 0028CD90, 61005450, 0028CD90)
61005450 61004416 (0000009C, A02404C7, E8611021, FFFFFF48)
1114863 [main] unyaffs 1564 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1131084 [main] unyaffs 1564 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack)
What am I doing wrong?
_/=-)+(-=\_ said:
Hello,
so I extracted a .DZ ROM file. The system.img(.ext4) has 6 parts:
system.img.ext4_0
...
system.img.ext4_5
How can I merge them into a functional system.img(.ext4) file in Windows?
I've used this cmd command:
copy /b "system.img.ext4_*" "system.img"
Then I used unyaffs to extract it
Click to expand...
Click to collapse
Simple.
You're using an unyaffs extractor on a non-yaffs2 file.
Look for tools that let you open ext4 images instead, such as this one.
Hello all
I am having some trouble with SDK installing apps to my Android. I've tried to find many forums about my issue, but I've hit a brick wall every time. My rooted device is an LG Optimus C running Android 2.2 (ancient lol). My issue is that I'm getting the error: Failure [INSTALL_FAILED_DEXOPT] for every app I try to install. I've wiped the device twice and then found out that this error happens every time after I've installed a good amount of apps...which I read somewhere that this will happen because of not having enough space in Dalvik..or in the data area and won't allow the install to write anything else..correct me if I'm wrong on this I've also cleared all caches multiple times, including Dalvik.
I've also tried the work around where you try and skip that all together and put the app straight into /system /app. That came up with no resolution, even with the correct properties selected (read/write/execute etc). So now, I really have no other avenues left but to come here and ask.
Here is the Logcat results I get using adb install -r app.apk no matter what app it is. I will use tumblog.apk (compatible with device) for this example:
D/AndroidRuntime( 4201):
D/AndroidRuntime( 4201): >>>>>> AndroidRuntime START com.android.internal.os.Run
timeInit <<<<<<
I/AndroidRuntime( 4201): Heap size: -Xmx32m
D/AndroidRuntime( 4201): CheckJNI is OFF
D/AndroidRuntime( 4201): Calling main entry com.android.commands.pm.Pm
W/ActivityManager( 1356): No content provider found for:
W/ActivityManager( 1356): No content provider found for:
D/PackageParser( 1356): Scanning package: /data/app/vmdl-166230949.tmp
D/PackageManager( 1356): Scanning package com.luckydroid.tumblelog
E/PackageManager( 1356): Package com.luckydroid.tumblelog has mismatched uid: 10
060 on disk, 10061 in settings
I/PackageManager( 1356): Linking native library dir for /data/app/com.luckydroid
.tumblelog-1.apk
D/installd( 1256): DexInv: --- BEGIN '/data/app/com.luckydroid.tumblelog-1.apk'
---
D/dalvikvm( 4211): Zip inflate: partial write (will retry): (24536 of 32768)
E/dalvikvm( 4211): Zip inflate: write failed: No space left on device
W/dalvikvm( 4211): DexOptZ: extraction of classes.dex from /data/app/com.luckydr
oid.tumblelog-1.apk failed
W/installd( 1256): DexInv: --- END '/data/app/com.luckydroid.tumblelog-1.apk' --
- status=0xff00, process failed
E/installd( 1256): dexopt failed on '/data/dalvik-cache/[email protected]@com.luckydroid.
[email protected]' res = 65280
W/PackageManager( 1356): Package couldn't be installed in /data/app/com.luckydro
id.tumblelog-1.apk
D/AndroidRuntime( 4201): Shutting down VM
I/AndroidRuntime( 4201): NOTE: attach of thread 'Binder Thread #3' failed
D/jdwp ( 4201): adbd disconnected
I really have no clue what any of this means lol...pretty new to logcat. I am aware of the file name not matching the original name of the apk..shouldn't matter considering I've installed many apps with shortened names. Any help would be greatly appreciated! Thanks
EDIT: Looks like "E/dalvikvm( 4211): Zip inflate: write failed: No space left on device" is the problem. Not enough space in Dalvik. Still have no idea how to work around.
Bump
Is this not posted in the correct forum? I'm just guessing no one knows of a solution?
Çözüme Yakın
Sizin sorununuz apk~classes.dex~.smali dosyalarının içinde gereksiz kodları siliniz. "Ayrıca Facebook klasörünü bulup siliniz (her clasess.dex'te bulunmaz)" ayrıca kimi classes.dex boyutu 9MB iken yükleniyor bazı clasess.dex dosyaları ise 7,8*MB olunca yüklenmiyor. Tabikide kodlar içinde dexOpt= dex options ayarı vardır ama ben bulamadım sadece bunları biliyorum. Umarım çözüm bulan çıkar. TR
Hello people. I would like some advice on my problem.
Currently using JB 4.2.1 Ultralight 3.6 ROM along with Experimental V12 Kernel.
Although the keyboard works perfectly otherwise, once I choose Greek language along with the English one,
I get constant FCs. The keyboard won't even open.
I provide the logcat of the error for troubleshooting purposes.
Thanks in advance for all the replies! :good:
Code:
[ 03-11 06:59:19.297 5392: 5392 D/TextInput::Requirement ]
xt9-engine-database-id = 2130968817
[ 03-11 06:59:19.297 5392: 5392 E/AndroidRuntime ]
FATAL EXCEPTION: main
java.lang.RuntimeException: result:10
at com.sonyericsson.textinput.uxp.model.xt9.XT9Engine.XT9Engine_setActiveLanguage(Native Method)
at com.sonyericsson.textinput.uxp.model.xt9.XT9Engine.setLanguage(XT9Engine.java:482)
at com.sonyericsson.textinput.uxp.model.xt9.XT9Engine.initOptional(XT9Engine.java:644)
at com.sonyericsson.collaboration.ObjectBinder.init(ObjectBinder.java:448)
at com.sonyericsson.textinput.uxp.glue.InputMethodServiceGlue.bind(InputMethodServiceGlue.java:445)
at com.sonyericsson.textinput.uxp.glue.InputMethodServiceGlue.onStartInputView(InputMethodServiceGlue.java:393)
at android.inputmethodservice.InputMethodService.showWindowInner(InputMethodService.java:1420)
at android.inputmethodservice.InputMethodService.showWindow(InputMethodService.java:1378)
at android.inputmethodservice.InputMethodService$InputMethodImpl.showSoftInput(InputMethodService.java:422)
at android.inputmethodservice.IInputMethodWrapper.executeMessage(IInputMethodWrapper.java:184)
at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:61)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4744)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
I can provide a more extensive logcat if needed but I think that's the main problem described above.
anyone? :3
Turns out the dictionary lib for the greek language was missing. so I just placed it under /usr/xt9. I hope this helps someone in case they have the same problem.