[DEV] Mounting issues on KK-AOSP - LG Optimus 4X HD

@Adam77Root , @laufersteppenwolf & @Demetris : I need your help.
I'm building a strictly AOSPKK-based rom, using your sources (tried with android-4.4, cm-11.0 & slim-kk branches). Experienced a very strange issue, related to /cache partition, that doesn't let me work on fixing every other issue on the rom.
In fact, during the boot issue, lot of apps are continously crashing, as /cache doesn't let itself mount.
Pulled a kmsg, who told me this little - important - thing:
Code:
fs_mgr: Cannot mount filesystem on /dev/block/platform/sdhci-tegra.3/by-name/CAC at /cache
Pulled a logcat too, that told me this little thing too (in addition to the numerous error strings to it related):
Code:
F/SystemServer( 530): BOOT FAILURE starting DeviceStorageMonitor service
F/SystemServer( 530): java.lang.IllegalArgumentException: Invalid path: /cache
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:46)
F/SystemServer( 530): at android.os.StatFs.<init>(StatFs.java:39)
F/SystemServer( 530): at com.android.server.DeviceStorageMonitorService.<init>(DeviceStorageMonitorService.java:322)
F/SystemServer( 530): at com.android.server.ServerThread.initAndLoop(SystemServer.java:581)
F/SystemServer( 530): at com.android.server.SystemServer.main(SystemServer.java:1179)
F/SystemServer( 530): at java.lang.reflect.Method.invokeNative(Native Method)
F/SystemServer( 530): at java.lang.reflect.Method.invoke(Method.java:515)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
F/SystemServer( 530): at dalvik.system.NativeStart.main(Native Method)
F/SystemServer( 530): Caused by: libcore.io.ErrnoException: statvfs failed: ENOENT (No such file or directory)
F/SystemServer( 530): at libcore.io.Posix.statvfs(Native Method)
F/SystemServer( 530): at libcore.io.ForwardingOs.statvfs(ForwardingOs.java:132)
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:44)
F/SystemServer( 530): ... 9 more
W/SystemServer( 530): ***********************************************
Have you ever experienced this bug?
Do you nearly know where the cause could be?
PS: this could help to fix any bug in AOSP KitKat, who knows
Let me know.
Thanks in advance,
mackief.

mackief said:
@Adam77Root , @laufersteppenwolf & @Demetris : I need your help.
I'm building a strictly AOSPKK-based rom, using your sources (tried with android-4.4, cm-11.0 & slim-kk branches). Experienced a very strange issue, related to /cache partition, that doesn't let me work on fixing every other issue on the rom.
In fact, during the boot issue, lot of apps are continously crashing, as /cache doesn't let itself mount.
Pulled a kmsg, who told me this little - important - thing:
Code:
fs_mgr: Cannot mount filesystem on /dev/block/platform/sdhci-tegra.3/by-name/CAC at /cache
Pulled a logcat too, that told me this little thing too (in addition to the numerous error strings to it related):
Code:
F/SystemServer( 530): BOOT FAILURE starting DeviceStorageMonitor service
F/SystemServer( 530): java.lang.IllegalArgumentException: Invalid path: /cache
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:46)
F/SystemServer( 530): at android.os.StatFs.<init>(StatFs.java:39)
F/SystemServer( 530): at com.android.server.DeviceStorageMonitorService.<init>(DeviceStorageMonitorService.java:322)
F/SystemServer( 530): at com.android.server.ServerThread.initAndLoop(SystemServer.java:581)
F/SystemServer( 530): at com.android.server.SystemServer.main(SystemServer.java:1179)
F/SystemServer( 530): at java.lang.reflect.Method.invokeNative(Native Method)
F/SystemServer( 530): at java.lang.reflect.Method.invoke(Method.java:515)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
F/SystemServer( 530): at dalvik.system.NativeStart.main(Native Method)
F/SystemServer( 530): Caused by: libcore.io.ErrnoException: statvfs failed: ENOENT (No such file or directory)
F/SystemServer( 530): at libcore.io.Posix.statvfs(Native Method)
F/SystemServer( 530): at libcore.io.ForwardingOs.statvfs(ForwardingOs.java:132)
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:44)
F/SystemServer( 530): ... 9 more
W/SystemServer( 530): ***********************************************
Have you ever experienced this bug?
Do you nearly know where the cause could be?
PS: this could help to fix any bug in AOSP KitKat, who knows
Let me know.
Thanks in advance,
mackief.
Click to expand...
Click to collapse
First, nope, I've never seen this yet
Do you have some more infos from the dmesg, as this line says a lot, but still not much
So, what did you do? did you format the /cache partition manually (not using the wipe-data-way)? If so, which recovery are you using?
What else did you try?
BTW, what do you thing about moving this discussion either into a new thread or into the dev only thread, as it's quite off topic Just let me know and I can move it

mackief said:
@Adam77Root , @laufersteppenwolf & @Demetris : I need your help.
I'm building a strictly AOSPKK-based rom, using your sources (tried with android-4.4, cm-11.0 & slim-kk branches). Experienced a very strange issue, related to /cache partition, that doesn't let me work on fixing every other issue on the rom.
In fact, during the boot issue, lot of apps are continously crashing, as /cache doesn't let itself mount.
Pulled a kmsg, who told me this little - important - thing:
Code:
fs_mgr: Cannot mount filesystem on /dev/block/platform/sdhci-tegra.3/by-name/CAC at /cache
Pulled a logcat too, that told me this little thing too (in addition to the numerous error strings to it related):
Code:
F/SystemServer( 530): BOOT FAILURE starting DeviceStorageMonitor service
F/SystemServer( 530): java.lang.IllegalArgumentException: Invalid path: /cache
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:46)
F/SystemServer( 530): at android.os.StatFs.<init>(StatFs.java:39)
F/SystemServer( 530): at com.android.server.DeviceStorageMonitorService.<init>(DeviceStorageMonitorService.java:322)
F/SystemServer( 530): at com.android.server.ServerThread.initAndLoop(SystemServer.java:581)
F/SystemServer( 530): at com.android.server.SystemServer.main(SystemServer.java:1179)
F/SystemServer( 530): at java.lang.reflect.Method.invokeNative(Native Method)
F/SystemServer( 530): at java.lang.reflect.Method.invoke(Method.java:515)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
F/SystemServer( 530): at dalvik.system.NativeStart.main(Native Method)
F/SystemServer( 530): Caused by: libcore.io.ErrnoException: statvfs failed: ENOENT (No such file or directory)
F/SystemServer( 530): at libcore.io.Posix.statvfs(Native Method)
F/SystemServer( 530): at libcore.io.ForwardingOs.statvfs(ForwardingOs.java:132)
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:44)
F/SystemServer( 530): ... 9 more
W/SystemServer( 530): ***********************************************
Have you ever experienced this bug?
Do you nearly know where the cause could be?
PS: this could help to fix any bug in AOSP KitKat, who knows
Let me know.
Thanks in advance,
mackief.
Click to expand...
Click to collapse
Looks like a mismatch in fstab or a kernel automount script/fstab mismatch to me.
I'd review init.rc (which is created by the ROM build) if i were you. Chances are it's a simple problem, why not post the ROM and let us look at it?
It should be noted that none of the scripts apart from Omni are AOSP compatible (not that they are compatible, they are most certainly not but it's as close as you'll get), i'd revert to last known good and go from there.
It's what i'm doing, my effort is to drag the entire thing along with kernel and built blobs that are currently used and using the latest cardhu drivers, if you are interested in that and know something about kernel progamming, PM me.
---------- Post added at 01:59 AM ---------- Previous post was at 01:19 AM ----------
Adam77Root said:
New build up with video recording fix! Commits are pushed to P880-dev android-4.4 branches. Enjoy!
(@laufersteppenwolf you're fast! -- already merged modified vendor files which I pushed earlier)
Click to expand...
Click to collapse
Well done, you have PM.

mackief said:
@Adam77Root , @laufersteppenwolf & @Demetris : I need your help.
I'm building a strictly AOSPKK-based rom, using your sources (tried with android-4.4, cm-11.0 & slim-kk branches). Experienced a very strange issue, related to /cache partition, that doesn't let me work on fixing every other issue on the rom.
In fact, during the boot issue, lot of apps are continously crashing, as /cache doesn't let itself mount.
Pulled a kmsg, who told me this little - important - thing:
Code:
fs_mgr: Cannot mount filesystem on /dev/block/platform/sdhci-tegra.3/by-name/CAC at /cache
Pulled a logcat too, that told me this little thing too (in addition to the numerous error strings to it related):
Code:
F/SystemServer( 530): BOOT FAILURE starting DeviceStorageMonitor service
F/SystemServer( 530): java.lang.IllegalArgumentException: Invalid path: /cache
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:46)
F/SystemServer( 530): at android.os.StatFs.<init>(StatFs.java:39)
F/SystemServer( 530): at com.android.server.DeviceStorageMonitorService.<init>(DeviceStorageMonitorService.java:322)
F/SystemServer( 530): at com.android.server.ServerThread.initAndLoop(SystemServer.java:581)
F/SystemServer( 530): at com.android.server.SystemServer.main(SystemServer.java:1179)
F/SystemServer( 530): at java.lang.reflect.Method.invokeNative(Native Method)
F/SystemServer( 530): at java.lang.reflect.Method.invoke(Method.java:515)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:779)
F/SystemServer( 530): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:595)
F/SystemServer( 530): at dalvik.system.NativeStart.main(Native Method)
F/SystemServer( 530): Caused by: libcore.io.ErrnoException: statvfs failed: ENOENT (No such file or directory)
F/SystemServer( 530): at libcore.io.Posix.statvfs(Native Method)
F/SystemServer( 530): at libcore.io.ForwardingOs.statvfs(ForwardingOs.java:132)
F/SystemServer( 530): at android.os.StatFs.doStat(StatFs.java:44)
F/SystemServer( 530): ... 9 more
W/SystemServer( 530): ***********************************************
Have you ever experienced this bug?
Do you nearly know where the cause could be?
PS: this could help to fix any bug in AOSP KitKat, who knows
Let me know.
Thanks in advance,
mackief.
Click to expand...
Click to collapse
I had this once when enabled rootfs security contexts for SELinux. Omni didn't have the needed rules yet. Just revert they commit in the kernel or include common policies from vendor/omni and you're good to go.
Sent from my OmniROM-powered LG Optimus 4X HD

laufersteppenwolf said:
First, nope, I've never seen this yet
Do you have some more infos from the dmesg, as this line says a lot, but still not much
So, what did you do? did you format the /cache partition manually (not using the wipe-data-way)? If so, which recovery are you using?
What else did you try?
BTW, what do you thing about moving this discussion either into a new thread or into the dev only thread, as it's quite off topic Just let me know and I can move it
Click to expand...
Click to collapse
I formatted /data for a factory reset, after installing the rom, and then manually /cache and dalvik-cache.
I know I'm off-topic, sorry for it, if you think it's better to move my post to a specific thread, then do it, no problem!
IcanhasLG said:
Looks like a mismatch in fstab or a kernel automount script/fstab mismatch to me.
I'd review init.rc (which is created by the ROM build) if i were you. Chances are it's a simple problem, why not post the ROM and let us look at it?
It should be noted that none of the scripts apart from Omni are AOSP compatible (not that they are compatible, they are most certainly not but it's as close as you'll get), i'd revert to last known good and go from there.
It's what i'm doing, my effort is to drag the entire thing along with kernel and built blobs that are currently used and using the latest cardhu drivers, if you are interested in that and know something about kernel progamming, PM me.
---------- Post added at 01:59 AM ---------- Previous post was at 01:19 AM ----------
Well done, you have PM.
Click to expand...
Click to collapse
Thanks, will send a PM with ROM link!
Adam77Root said:
I had this once when enabled rootfs security contexts for SELinux. Omni didn't have the needed rules yet. Just revert they commit in the kernel or include common policies from vendor/omni and you're good to go.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
Could you explain more specificly what do I need from vendor? Could you provide that commit, please?
Or better, could you tell me which is the commit to ne reverted in the kernel?

mackief said:
[...]
Could you explain more specificly what do I need from vendor? Could you provide that commit, please?
Or better, could you tell me which is the commit to ne reverted in the kernel?
Click to expand...
Click to collapse
I think @Adam77Root is referring to THIS commit
About the post moving, I will move it into a new thread when I'm back home later, if you want a special title, just send me a PM

laufersteppenwolf said:
I think @Adam77Root is referring to THIS commit
About the post moving, I will move it into a new thread when I'm back home later, if you want a special title, just send me a PM
Click to expand...
Click to collapse
If he was referring to that one, then I already found it by searching on Google.
Already made a build disabling it, right now gonna test: let you know!
---------- Post added at 02:25 PM ---------- Previous post was at 02:18 PM ----------
#UPDATE: Yep, truly fixed. Thanks, guys!

Just gonna ping some people to let them know I moved these posts.... just ignore this post 
 @mackief @Adam77Root @IcanhasLG @laufersteppenwolf

Related

could not open hw3dc (Permission denied)...

I'm posting this here because the other sections rarely get answers. I tried installing Angry Birds via the download link. It installs but force closes immediately when trying to open. I've tried running it from the phone memory as well with no luck. Here is the logcat from when I try to open the game. Is the problem with hw3dc? I don't have anything relating to hw3dc in /dev. I'm on a mt3g running CM6 stable.
D/dalvikvm( 7438): Trying to load lib /data/data/com.rovio.angrybirds_lite/lib/l
ibangrybirds.so 0x43cc5608
I/ActivityManager( 231): Process com.speedsoftware.rootexplorer (pid 6976) has
died.
D/dalvikvm( 7438): Added shared lib /data/data/com.rovio.angrybirds_lite/lib/lib
angrybirds.so 0x43cc5608
D/dalvikvm( 7438): No JNI_OnLoad found in /data/data/com.rovio.angrybirds_lite/l
ib/libangrybirds.so 0x43cc5608, skipping init
I/KA3D ( 7438): Creating MultiTouchInputDelegator
I/App ( 7438): onResume
I/ActivityManager( 231): Displayed activity com.rovio.angrybirds_lite/com.rovio
.ka3d.App: 919 ms (total 919 ms)
W/IInputConnectionWrapper( 5311): showStatusIcon on inactive InputConnection
D/libEGL ( 7438): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 7438): loaded /system/lib/egl/libGLES_qcom.so
E/EGL.oem ( 7438): could not open hw3dc (Permission denied)
E/libEGL ( 7438): No EGLDisplay for hardware EGL!
W/dalvikvm( 7438): threadid=8: thread exiting with uncaught exception (group=0x4
00207e8)
E/AndroidRuntime( 7438): FATAL EXCEPTION: GLThread 9
E/AndroidRuntime( 7438): java.lang.IllegalArgumentException
E/AndroidRuntime( 7438): at com.google.android.gles_jni.EGLImpl.eglGetCon
figAttrib(Native Method)
E/AndroidRuntime( 7438): at com.rovio.ka3d.MySurfaceView$ConfigChooser.fi
ndConfigAttrib(App.java:236)
E/AndroidRuntime( 7438): at com.rovio.ka3d.MySurfaceView$ConfigChooser.ch
ooseConfig(App.java:209)
E/AndroidRuntime( 7438): at com.rovio.ka3d.MySurfaceView$ConfigChooser.ch
ooseConfig(App.java:202)
E/AndroidRuntime( 7438): at android.opengl.GLSurfaceView$EglHelper.start(
GLSurfaceView.java:916)
E/AndroidRuntime( 7438): at android.opengl.GLSurfaceView$GLThread.guarded
Run(GLSurfaceView.java:1246)
E/AndroidRuntime( 7438): at android.opengl.GLSurfaceView$GLThread.run(GLS
urfaceView.java:1116)
W/ActivityManager( 231): Force finishing activity com.rovio.angrybirds_lite/c
om.rovio.ka3d.App
Try in a terminal:
Code:
su
chmod 666 /dev/hw3dc
This should solve the problem.
If the problem is there again after a reboot
add this line:
Code:
chmod 666 /dev/hw3dc
to your userinit.sh or put a script
with this line in in /system/etc/init.d/
farmatito said:
Try in a terminal:
Code:
su
chmod 666 /dev/hw3dc
This should solve the problem.
If the problem is there again after a reboot
add this line:
Code:
chmod 666 /dev/hw3dc
to your userinit.sh or put a script
with this line in in /system/etc/init.d/
Click to expand...
Click to collapse
Thanks but I don't have /dev/hw3dc. There is no hw3dc anywhere in /dev. In fact, I have /dev but when I go in there with root explorer it says that /dev uses 0k of space. Weird.
To be exact, the correct device name is:
Code:
# ls /dev/msm_hw3d*
/dev/msm_hw3dc /dev/msm_hw3dm
and command to run in terminal:
Code:
chmod 777 /dev/msm_hw3d*
The 777 permission maybe somewhat to lax from a security point of view
so try first if 660 or 666 fix the error.
Thanks, I follow the setting, and it works.
farmatito said:
To be exact, the correct device name is:
Code:
# ls /dev/msm_hw3d*
/dev/msm_hw3dc /dev/msm_hw3dm
and command to run in terminal:
Code:
chmod 777 /dev/msm_hw3d*
The 777 permission maybe somewhat to lax from a security point of view
so try first if 660 or 666 fix the error.
Click to expand...
Click to collapse
Thread moved to Q&A.

Problem changing resolution to 240dpi on VengeaneNote2 - RC Build 1.0 - MIUI 2.9.14

Hi
I'm posting this question here because I'm not allowed to post to the development thread (yet)
I installed the last version of VengeaneNote2 (RC Build 1.0 - MIUI 2.9.14) but after I changed the screen resolution to 240dpi, I started getting this exception when opening the dialer:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.TwelveKeyDialer}: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2070)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2095)
at android.app.ActivityThread.access$600(ActivityThread.java:133)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1198)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4758)
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)
Caused by: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:258)
at android.app.Activity.setContentView(Activity.java:1873)
at com.android.contacts.activities.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:528)
at android.app.Activity.performCreate(Activity.java:5014)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2034)
... 11 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 26 more
Caused by: android.content.res.Resources$NotFoundException: File res/drawable-hdpi/dialer_buttons.9.png from drawable resource ID #0x7f020046
at android.content.res.Resources.loadDrawable(Resources.java:1944)
at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
at android.view.View.<init>(View.java:3339)
at android.view.View.<init>(View.java:3275)
... 29 more
Caused by: java.io.FileNotFoundException: res/drawable-hdpi/dialer_buttons.9.png
at android.content.res.AssetManager.openNonAssetNative(Native Method)
at android.content.res.AssetManager.openNonAsset(AssetManager.java:413)
at android.content.res.Resources.loadDrawable(Resources.java:1936)
... 32 more
I did it many times (full wipe and format /system between each), but still having the same problem.
This only new in this version. I was able to switch to 240dpi in all previous versions without problem.
Any help on this?
Thanks
update
yelkarama said:
Hi
I'm posting this question here because I'm not allowed to post to the development thread (yet)
I installed the last version of VengeaneNote2 (RC Build 1.0 - MIUI 2.9.14) but after I changed the screen resolution to 240dpi, I started getting this exception when opening the dialer:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.TwelveKeyDialer}: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2070)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2095)
at android.app.ActivityThread.access$600(ActivityThread.java:133)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1198)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4758)
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)
Caused by: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:258)
at android.app.Activity.setContentView(Activity.java:1873)
at com.android.contacts.activities.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:528)
at android.app.Activity.performCreate(Activity.java:5014)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2034)
... 11 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 26 more
Caused by: android.content.res.Resources$NotFoundException: File res/drawable-hdpi/dialer_buttons.9.png from drawable resource ID #0x7f020046
at android.content.res.Resources.loadDrawable(Resources.java:1944)
at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
at android.view.View.<init>(View.java:3339)
at android.view.View.<init>(View.java:3275)
... 29 more
Caused by: java.io.FileNotFoundException: res/drawable-hdpi/dialer_buttons.9.png
at android.content.res.AssetManager.openNonAssetNative(Native Method)
at android.content.res.AssetManager.openNonAsset(AssetManager.java:413)
at android.content.res.Resources.loadDrawable(Resources.java:1936)
... 32 more
I did it many times (full wipe and format /system between each), but still having the same problem.
This only new in this version. I was able to switch to 240dpi in all previous versions without problem.
Any help on this?
Thanks
Click to expand...
Click to collapse
I changed the dpi to 280 and it's working!
update 2
yelkarama said:
Hi
I'm posting this question here because I'm not allowed to post to the development thread (yet)
I installed the last version of VengeaneNote2 (RC Build 1.0 - MIUI 2.9.14) but after I changed the screen resolution to 240dpi, I started getting this exception when opening the dialer:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.contacts/com.android.contacts.activities.TwelveKeyDialer}: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2070)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2095)
at android.app.ActivityThread.access$600(ActivityThread.java:133)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1198)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4758)
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)
Caused by: android.view.InflateException: Binary XML file line #174: Error inflating class <unknown>
at android.view.LayoutInflater.createView(LayoutInflater.java:613)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:746)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:749)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
at android.view.LayoutInflater.inflate(LayoutInflater.java:352)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:258)
at android.app.Activity.setContentView(Activity.java:1873)
at com.android.contacts.activities.TwelveKeyDialer.onCreate(TwelveKeyDialer.java:528)
at android.app.Activity.performCreate(Activity.java:5014)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2034)
... 11 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
at android.view.LayoutInflater.createView(LayoutInflater.java:587)
... 26 more
Caused by: android.content.res.Resources$NotFoundException: File res/drawable-hdpi/dialer_buttons.9.png from drawable resource ID #0x7f020046
at android.content.res.Resources.loadDrawable(Resources.java:1944)
at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
at android.view.View.<init>(View.java:3339)
at android.view.View.<init>(View.java:3275)
... 29 more
Caused by: java.io.FileNotFoundException: res/drawable-hdpi/dialer_buttons.9.png
at android.content.res.AssetManager.openNonAssetNative(Native Method)
at android.content.res.AssetManager.openNonAsset(AssetManager.java:413)
at android.content.res.Resources.loadDrawable(Resources.java:1936)
... 32 more
I did it many times (full wipe and format /system between each), but still having the same problem.
This only new in this version. I was able to switch to 240dpi in all previous versions without problem.
Any help on this?
Thanks
Click to expand...
Click to collapse
So I tried many resolutions. Each time I modify the line ro.sf.lcd_density= in /system/build.prop and I reboot.
Conclusion: The phone dialer works correctly for resolution more than 270. if I go beyondm it start FCing with the excption above.

[Q] Native App Crashes Because of Xposed?

I'm the developer of an app that loads a native library (.so). I'm getting a large number of error reports where loading a native library seems to be failing and the stack trace contains references to Xposed. Any ideas what might be going on here and how to fix it?
Stack trace:
java.lang.RuntimeException: exception during library load
at co.kr36.krypton.activity.Main.onCreate(Unknown Source)
at android.app.Activity.performCreate(Activity.java:5451)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1093)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2292)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2386)
at android.app.ActivityThread.access$900(ActivityThread.java:169)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1277)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5476)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
at dalvik.system.NativeStart.main(Native Method)
Caused by: org.chromium.base.library_loader.ProcessInitException
at org.chromium.base.library_loader.LibraryLoader.loadAlreadyLocked(Unknown Source)
at org.chromium.base.library_loader.LibraryLoader.ensureInitialized(Unknown Source)
at org.chromium.base.library_loader.LibraryLoader.ensureInitialized(Unknown Source)
... 16 more
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load seaturtle from loader dalvik.system.PathClassLoader[dexPath=/data/app/co.kr36.krypton.x-1.apk,libraryPath=/data/app-lib/co.kr36.krypton.x-1]: findLibrary returned null
at java.lang.Runtime.loadLibrary(Runtime.java:358)
at java.lang.System.loadLibrary(System.java:526)
... 19 more
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load seaturtle from loader dalvik.system.PathClassLoader[dexPath=/data/app/co.kr36.krypton.x-1.apk,libraryPath=/data/app-lib/co.kr36.krypton.x-1]: findLibrary returned null
Click to expand...
Click to collapse
Looks like you need to double check the path for the .so file. According to android, it is returning null when it tries to load the library path. Not exactly sure where is .so binary is, assets? So I can't really specify where the file is exactly. Also, double check read/write permissions.
As for xposed causing it, I highly doubt it.
The lines referencing xposed in the logcat is because xposed is able to hook into the method that you are calling. It doesn't do anything unless there is a module installed that uses a hook to that method. printStackTrace will show everywhere the method is referenced/called. So that is why you see the xposed line in the logcat.

Failed to add attachment in e-mail --> Mi3(MIUI 7 6.2.25)

Dears,
I have installed the latest stock ROM(MIUI 7 6.2.25, Android 6.0.1) on my Mi3 handset. When I tried to write a new e-mail and attach a file, I always got FC with the following error log message and failed to add an attachment. Does anyone have any idea why this happens?
Thanks for the prompt help.
java.lang.RuntimeException: Unable to instantiate application com.android.documentsui.DocumentsApplication: java.lang.ClassNotFoundException: Didn't find class "com.android.documentsui.DocumentsApplication" on path: DexPathList[[zip file "/system/app/DocumentsUI/DocumentsUI.apk"],nativeLibraryDirectories=[/system/app/DocumentsUI/lib/arm, /vendor/lib, /system/lib]]
at android.app.LoadedApk.makeApplication(LoadedApk.java:580)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4693)
at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:675)
at android.app.ActivityThread.handleBindApplication()
at android.app.ActivityThread.access$1600(ActivityThread.java:153)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1410)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5432)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:735)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:625)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:114)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.android.documentsui.DocumentsApplication" on path: DexPathList[[zip file "/system/app/DocumentsUI/DocumentsUI.apk"],nativeLibraryDirectories=[/system/app/DocumentsUI/lib/arm, /vendor/lib, /system/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
at android.app.Instrumentation.newApplication(Instrumentation.java:982)
at android.app.LoadedApk.makeApplication(LoadedApk.java:575)
... 13 more
Suppressed: java.io.IOException: Failed to open dex files from /system/app/DocumentsUI/DocumentsUI.apk
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:295)
at dalvik.system.DexFile.(DexFile.java:80)
at dalvik.system.DexFile.(DexFile.java:59)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:279)
at dalvik.system.DexPathList.makePathElements(DexPathList.java:248)
at dalvik.system.DexPathList.(DexPathList.java:120)
at dalvik.system.BaseDexClassLoader.(BaseDexClassLoader.java:48)
at dalvik.system.PathClassLoader.(PathClassLoader.java:65)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:57)
at android.app.LoadedApk.getClassLoader(LoadedApk.java:376)
at de.robv.android.xposed.XposedBridge$1.beforeHookedMethod(XposedBridge.java:170)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:655)
... 10 more
Suppressed: java.lang.ClassNotFoundException: com.android.documentsui.DocumentsApplication
at java.lang.Class.classForName(Native Method)
at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
... 16 more
Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack trace available

[Help] Xposed causes apps crashes.

Hello I have Xposed installed on Redmi Note 3 hennessy (MTK) and xposed causes app crashes. Can anyone help? I already tried to wipe cache and dalvik but didn't help. Crashes also includes system apps.
Code:
java.lang.RuntimeException: Unable to instantiate application com.google.android.gm.MailMigrationApplication: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gm.MailMigrationApplication" on path: DexPathList[[zip file "/data/app/com.google.android.gm-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]
at android.app.LoadedApk.makeApplication(LoadedApk.java)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java)
at de.robv.android.xposed.XposedBridge.invokeOriginalMethodNative(Native Method)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:334)
at android.app.ActivityThread.handleBindApplication(<Xposed>)
at android.app.ActivityThread.access$1500(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:102)
Caused by: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gm.MailMigrationApplication" on path: DexPathList[[zip file "/data/app/com.google.android.gm-1/base.apk"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
at java.lang.ClassLoader.loadClass(ClassLoader.java:469)
at android.app.Instrumentation.newApplication(Instrumentation.java)
... 15 more
Suppressed: java.io.IOException: Failed to open oat file from dex location '/data/app/com.google.android.gm-1/base.apk'
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:295)
at dalvik.system.DexFile.<init>(DexFile.java:80)
at dalvik.system.DexFile.<init>(DexFile.java:59)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:262)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:231)
at dalvik.system.DexPathList.<init>(DexPathList.java:109)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:48)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:65)
at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java)
at android.app.LoadedApk.getClassLoader(LoadedApk.java)
at de.robv.android.xposed.XposedInit$2.beforeHookedMethod(XposedInit.java:139)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:314)
... 11 more
Caused by: java.io.IOException: Failed to open oat file from /data/app/com.google.android.gm-1/arm64/base.odex (error Failed to open oat filename for reading: No such file or directory) (no dalvik_cache availible) and relocation failed.
... 24 more
Caused by: java.io.IOException:
... 24 more
Caused by: java.io.IOException: Failed to remove obsolete file from /data/dalvik-cache/arm64/[email protected]@[email protected]@classes.dex when searching for dex file /data/app/com.google.android.gm-1/base.apk: Permission denied
... 24 more
Suppressed: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gm.MailMigrationApplication" on path: DexPathList[[dex file "/data/dalvik-cache/xposed_XResourcesSuperClass.dex"],nativeLibraryDirectories=[/vendor/lib64, /system/lib64]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:511)
at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
... 17 more
Suppressed: java.lang.ClassNotFoundException: com.google.android.gm.MailMigrationApplication
at java.lang.Class.classForName(Native Method)
at java.lang.BootClassLoader.findClass(ClassLoader.java:781)
at java.lang.BootClassLoader.loadClass(ClassLoader.java:841)
at java.lang.ClassLoader.loadClass(ClassLoader.java:504)
... 18 more
Caused by: java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack available
Xposed is unstable, rather wait for official to drop.
Theres not much you can do with the app crashes other than uninstall xposed

Categories

Resources