(Closed) [DEV] Samsung Crash (Issue Resolved) - Magisk

Issue fixed, thanks for all the feedback and report!!!
Hello, as many of you should be aware, the latest Magisk Manager (v4.2.5) crashes only on Samsung devices.
Here are the logs users submitted through Play Store:
Code:
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(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(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
at com.android.internal.policy.multiwindow.Docking.<init>(Docking.java)
at com.android.internal.policy.MultiPhoneWindow.<init>(MultiPhoneWindow.java)
at android.app.Activity.makeNewWindow(Activity.java)
at android.app.Activity.attach(Activity.java)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(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(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
As you might realize that according to the backtrace, non of them involves my code (which should start with com.topjohnwu.magisk.*), all of them are errors within internal and Zygote, and Samsung's multiwindow internal calls.
I am not able to identify where it crashes, and which part of the Magisk Manager code is breaking it, so of course without knowing why, I have no idea how to fix it. What makes the situation even worse is that I don't own any of the devices, so I cannot properly debug the issue.
This thread is for seeking help from users with a modern Samsung device, as I need more details.
Please describe when do the crash occurs (does splash screen even shows up?), and please upload a full logcat recording the FC.
Also, I'm looking for Samsung experts who are willing to assist me more in Samsung support for Magisk, as I never bought Sammy so I have little experience, but they seem to cause the most problems.
OT, I'm actually willing to buy a Sammy flagship, but I never buy outdated devices (older than 2 months = outdated IMO lol), so I might get the S8. The next Pixel device is already on my list, guess I'll have to spend all my tutor money on smartphones....
For Pixel support, I'll borrow my friend's Pixel XL for a couple of weeks to try things out, but this might not happen soon since school is quite busy.

@topjohnwu
it crash on opening the app, so unable to opeen the app it self
new root programs are unable to use root as it will crash when trying to enable root in the apps
old programs that use root already keep function
my device is
Samsng Galaxy s6 edge+ SM-G928F
Rom: Audax 13 Android MM 6.0.1
Kernel: Arter97
i don't know how to provide anymore info or how to use this logcat
so if you tell me how i can gather more info i do it with pleasure

From what I can tell it only happens in the versions after 4.1 so the problem is in one of the changes after 4.1. A Wild guesses that may or may not could help is that you could set a flag that tells the Samsung framework that it isn't compatible with multi window.
Gesendet von meinem SM-G925F mit Tapatalk

Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.

Didgeridoohan said:
Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.
Click to expand...
Click to collapse
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk

Hello topjohnwu, first of all I would like to thank you for you amazing work, really it made life simplier to many of us, so on behalf of everyone using Magisk I would like to say : THANK YOU.
To answer your question, when launching Magisk Manager, yes there's the splash screen before the crash.
I've attached a logcat to my post which shows "Magisk Manager v4.2.5" behaviour when crashing.
1 - Here are some informations about my device configuration :
- Device: Galaxy S7 Edge G935F (Exynos)
- Rom: Decent Ultralite 5.0 (Android 6.0.1) Based on TouchWiz (Stock Samsung)
- Kernel: SuperStock Kernel by Tkkg1994 (It's the stock Samsung kernel with only one change : SELINUX set to Permissive instead of Enforcing)
- Root: MagiskSU
- Recovery: TWRP v3.0.2.4
2 - Now some infos about my Magisk Config :
- Modules : Emoji One, Unified Hosts Adblock, Xposed Framework (SDK 23).
- Magisk Hide : Only Snapchat (which I don't even use lol)
- Settings Enabled : BusyBox, Magisk Hide, Systemless hosts
3 - Just in case, my modules of Xposed are :
- BootManager
- GalaxyXMod
- Greenify
- Unicon
- XInternalSD
That's it, if you need any more informations, I'm here.
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.

ken2802 said:
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Better to post it or a link here so topjohnwu doesn't have to search too much.

Didgeridoohan said:
Better to post it or a link here so topjohnwu doesn't have to search too much.
Click to expand...
Click to collapse
I made a new one.
https://drive.google.com/file/d/0B94u0_R6vixWbmtuUmFYQzhfWXM/view?usp=drivesdk

here is my logcat s7 edge android 6.0.1
I/Timeline( 5058): Timeline: Activity_launch_request id:com.topjohnwu.magisk time:68806449
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/MultiWindowPolicy( 4137): Gamemode - return 0, when calling identifyForegroundApp(com.topjohnwu.magisk)
V/WindowManager( 4137): addAppToken: AppWindowToken{d07f2779e token=Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594}}} to stack=1 task=594 at 0
D/ISSUE_DEBUG( 4137): InputChannelName : 9fd4a02 Starting com.topjohnwu.magisk
D/ActivityManager( 4137): Launching com.topjohnwu.magisk, updated priority
D/GameManagerService( 4137): NotifyRunnable. pkg: com.topjohnwu.magisk, type: 4, isMinimized: false, isTunableApp: false
E/AndroidRuntime(13507): Process: com.topjohnwu.magisk, PID: 13507
E/AndroidRuntime(13507): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.topjohnwu.magisk/com.topjohnwu.magisk.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
V/MARsPolicyManager( 4137): updatePackagesScore PackageInfo name -- com.topjohnwu.magisk
W/ActivityManager( 4137): Force finishing activity com.topjohnwu.magisk/.SplashActivity
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
V/WindowStateAnimator( 4137): Finishing drawing window Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
I/WindowManager( 4137): Screenshot max retries 4 of Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}} appWin=Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk} drawState=3
D/ISSUE_DEBUG( 4137): InputChannelName : 852d82d Application Error: com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/StatusBarManagerService( 4137): manageDisableList userId=0 what=0x0 pkg=Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=HAS_DRAWN
W/ActivityManager( 4137): Activity pause timeout for ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mServices
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mProviders
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mReceivers
I/ApplicationPackageManager( 4751): load=com.topjohnwu.magisk, bg=192-192, dr=192-192
W/ResourcesManager( 4751): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.android.systemui rsrc of package com.topjohnwu.magisk
I/ActivityManager( 4137): Process com.topjohnwu.magisk (pid 13507)(adj 9) has died(267,1161)
D/ActivityManager( 4137): isAutoRunBlockedApp:: com.topjohnwu.magisk, Auto Run ON
Click to expand...
Click to collapse

I'm gonna try to find out which build breaks it.
Does v4.1 works?

4.1 is the last that works on my s6 edge g925f
Gesendet von meinem SM-G925F mit Tapatalk

topjohnwu said:
I'm gonna try to find out which build breaks it.
Does v4.1 works?
Click to expand...
Click to collapse
Yes it works.

ok i hope ive done it right, i used catlog and saved log after crash magisk
hope its helpfull
see attachment

Samsung Galaxy S6 (SM-G920F) Alexis Rom 8.1, Arter97: Works
Samsung Galaxy S4 (GT-I9505) AICP 12.1: Works
Samsung Galaxy Tab S (SM-T800) IronRom 3.2: Doesn't Work
Samsung Galaxy S4 Mini (GT-I9195) AICP 12.1: Will check when battery is full again
Will try to get log cats from all and the crash occurs during the splash screen of Magisk Manager
edit: Added the log files dunno if they are properly for you.

@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:

aforss said:
here is my logcat s7 edge android 6.0.1
Click to expand...
Click to collapse
I would like to discuss with you about an issue on the S7 Edge, can you check you PMs ?
I don't want to pollute this thread.
Thank You

apc said:
@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:
Click to expand...
Click to collapse
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)

topjohnwu said:
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)
Click to expand...
Click to collapse
It works
No FCs

Works perfectly now
Working great (again) on my Galaxy S5 SM-G900F. Earlier (before MagiskSU) I had removed root to pass SN because Magisk had CTS profile mismatch error. But now SN is passed and I couldn't be happier. Thank you so much topjohnwu . Running RR-N rom 11 Feb 17 build with stock RR kernel, twrp 3.0.2-2

lahceneamine said:
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.
Click to expand...
Click to collapse
@topjohnwu
I've also noticed slow bootup times since Magisk v11.1 on a Samsung Galaxy Note 3 (stock android 5.0). It hangs at the first screen you see when you turn on the phone (before the Samsung logo screen). It eventually boots up and seems to work fine, but I didn't see this delay on earlier versions of Magisk.
Edit:
I'm using MagiskSU with no extra modules.

Related

MIUI - Problem with PreferenceActivity class

Hi, guys. I am having some troubles with the MIUI rom and the application "Cardiotrainer" because of a class that crashes in miui. I sent a message to a couple of admins of the miui main page, and also posted a couple of threads in the miui developers forum, but I had no response of any of the messages. I hope you can help me. I attach the last message I sent:
Hi. I sent you a message a couple of days ago, but I suppose it was deleted when the server failed. I hope you can help me, because I can't read chinese, so I can only read what google can translate hehehehe. First of all I would like to thank all the miui staff because of their great job. I like miui much more than any other rom, but since some versions ago I am having troubles with an application.
When I go running, I use the "Cardiotrainer" application, but since some versions ago, when I select some versions of the settings menu (all of them that display another submenu) the program crashes. It only happens with miui, so it's a rom problem. I read the crash log and I suppose the problem is becaus a NullPointerException in the PreferenceActivity class. Anyway I attach the crash error just in case it's helpful.
Code:
ERROR REPORT
Report type
Crash
Package name
com.wsl.CardioTrainer
Package version
63
Package version name
3.4.1
Installed by
com.google.android.feedback
Process name
com.wsl.CardioTrainer
Time
wednesday 22 december 2010
System app
false
SYSTEM
Device
passion
Build id
MIUI.0.12.11
Build type
userdebug
Model
Nexus One
Product
libra_passion
SDK version
8
Release
2.2.1
Incremental version
0.12.11
Codename
REL
Board
mahimahi
Brand
generic
Running applications
com.google.android.feedback
com.android.inputmethod.latin
com.android.providers.calendar
android.process.acore
com.google.process.gapps
com.android.phone
system
com.google.android.googlequicksearchbox
android.process.media
com.android.vending
com.svox.pico
com.android.voicedialer
com.noshufou.android.su
com.android.defcontainer
com.cooliris.media
com.google.android.apps.mapsocationFriendService
com.android.vending.updater
com.android.launcher
com.android.updater
com.miui.player
com.google.android.apps.uploader
com.twitter.android
(sorry, but it's quite impossible to copy the logs )
CRASH
Exception class name
java.lang.NullPointerException
Source file
PreferenceActivity.java
Source class
android.preference.PreferenceActivity
Source method
bindPreferences
Line number
247
Stack trace
java.lang.NullPointerException
at android.preference.PreferenceActivity.
bindPreferences(PreferenceActivity.java:247)
at android.preference.PreferenceActivity.
access$000(PreferenceActivity.java:86)
at android.preference.
PreferenceActivity$1.handleMessage(PreferenceActivity.java:109)
at android.os.Handler.
dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.
main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(NativeMethod)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.
ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
at com.android.internal.os.ZygoteInit.
main(ZygoteInit.java:626)
at dalvik.system.NativeStart.main(NativeMethod)
I hope with this information the problem can be solved. Thanks for your time.
Click to expand...
Click to collapse
+1
I am also using CardioTrainer on a MIUI ROM and it always crashes in settings :'(
I also have a similar problem with the Youversion Bible app. The tech support guys there reported that this is common problem with different apps in MIUI as MIUI has some "different structure" of handling settings. When pressing settings, the app crashes.
Here's my log:
processName:com.sirma.mobile.bible.android
pid:12915
uid:10072
tag:null
shortMsg:java.lang.NullPointerException
longMsg:java.lang.NullPointerException
stackTrace:java.lang.NullPointerException
at android.preference.PreferenceActivity.bindPreferences(PreferenceActivity.java:247)
at android.preference.PreferenceActivity.access$000(PreferenceActivity.java:86)
at android.preference.PreferenceActivity$1.handleMessage(PreferenceActivity.java:109)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4628)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:870)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:628)
at dalvik.system.NativeStart.main(Native Method)
Click to expand...
Click to collapse
I have MIUI 1.3.5 on the Sprint EVO, but I believe this is a general MIUI problem, so posting here.

[Q:] PowerAmp Instability (on JB)

I have been experiencing this issue on my Galaxy Note N7000 for the past couple weeks running everything from Liquid Smooth v2.0 to Utaka Paranoid Android v2.10-v2.15.
Each time I attempt to open PowerAmp (v2.0.6-build-508) it says that it has encountered an error; (Even though I can continue to use PowerAmp, I must close the crash report each time)
This is the log:
New Trace collected :
=====================
Poweramp Error Report, collected on: Tue Sep 25 23:40:53 PDT 2012
==============
Version: 2.0.6-build-508 full version verified
Unlocker: 1.1-build-12
Version Sign: a007ecbb65d49f9fe01839b804ef51a4cc37cf4d
Skin: 800a0000 /data/app/com.ikorolkov.poweramp.skins.ics-1.apk
Phone Model: GT-N7000
Locale:en_CA
Android Version: 4.1.1
Board: smdk4210
Cpu: armeabi-v7a armeabi Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
Brand: Samsung
Device: GT-N7000
Finger Print: samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys
ID: JRO03R
Product: GT-N7000
Tags: test-keys
Thread: 1 main
Stack :
=======
android.content.res.Resources$NotFoundException: Resource ID #0x8002009a
at android.content.res.Resources.getValue(Resources.java:1033)
at android.content.res.Resources.getDrawable(Resources.java:678)
at com.maxmpz.audioplayer.widget.f.��(":34)
at com.maxmpz.audioplayer.widget.listwrappers.��.0XF.onPostExecute(":106)
at android.os.AsyncTask.finish(AsyncTask.java:631)
at android.os.AsyncTask.access$600(AsyncTask.java:177)
at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:644)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4940)
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:791)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
at dalvik.system.NativeStart.main(Native Method)
**** End of current Report ***
New Trace collected :
=====================
Poweramp Error Report, collected on: Tue Sep 25 23:41:07 PDT 2012
==============
Version: 2.0.6-build-508 full version verified
Unlocker: 1.1-build-12
Version Sign: a007ecbb65d49f9fe01839b804ef51a4cc37cf4d
Skin: 800a0000 /data/app/com.ikorolkov.poweramp.skins.ics-1.apk
Phone Model: GT-N7000
Locale:en_CA
Android Version: 4.1.1
Board: smdk4210
Cpu: armeabi-v7a armeabi Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
Brand: Samsung
Device: GT-N7000
Finger Print: samsung/GT-N7000/GT-N7000:4.0.3/IML74K/ZCLP6:user/release-keys
ID: JRO03R
Product: GT-N7000
Tags: test-keys
Thread: 1 main
Stack :
=======
android.content.res.Resources$NotFoundException: Resource ID #0x8002009a
at android.content.res.Resources.getValue(Resources.java:1033)
at android.content.res.Resources.getDrawable(Resources.java:678)
at com.maxmpz.audioplayer.widget.f.��(":34)
at com.maxmpz.audioplayer.widget.listwrappers.��.0XF.onPostExecute(":106)
at android.os.AsyncTask.finish(AsyncTask.java:631)
at android.os.AsyncTask.access$600(AsyncTask.java:177)
at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:644)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4940)
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:791)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
at dalvik.system.NativeStart.main(Native Method)
**** End of current Report ***
Click to expand...
Click to collapse
This is quite frustrating as I adore PowerAmp, but this has become unusable.
I'm aware that this is most likely caused by Jelly Bean, but I am wondering if anyone else out there has expereienced this, and knows of any fix.
Thanks in advance
-Ranafram
P.S. I have already attempted un-installing, and re-installing PowerAmp, but sadly with no avail
Poweramp v2.0.7-build-512 for JB
Ranafram said:
I have been experiencing this issue on my Galaxy Note N7000 for the past couple weeks running everything from Liquid Smooth v2.0 to Utaka Paranoid Android v2.10-v2.15.
Each time I attempt to open PowerAmp (v2.0.6-build-508) it says that it has encountered an error; (Even though I can continue to use PowerAmp, I must close the crash report each time)
This is the log:
This is quite frustrating as I adore PowerAmp, but this has become unusable.
I'm aware that this is most likely caused by Jelly Bean, but I am wondering if anyone else out there has expereienced this, and knows of any fix.
Thanks in advance
-Ranafram
P.S. I have already attempted un-installing, and re-installing PowerAmp, but sadly with no avail
Click to expand...
Click to collapse
Hello,
You can check out the developer's site, dev uploaded Poweramp v2.0.7-build-512 for those having issues with Jelly Bean. Can't comment about the improvements though, I'm still on ICS.
right. There is a new jb version of power amp on devs Site.. may be that will work better. did u try it out?
Sent from my GT-N7000 using xda premium
I have attempted to install the .apk, but when I try to tap install there is no reaction (button is not greyed out, but upon key press, no change is apparent to the button and no install begins).
I've noticed this since I moved to any ROM using Jelly Bean (tested on Paranoid Android and Liquid Smooth)
Anyone else experience this, or are aware of a fix?
-Ranafram
Sent from my GT-N7000 using xda premium

Xposed initialization error (v2.5 on CM11 Nightly 2012-04-12 / Nexus 5)

As the title suggests, Xposed fails to initialize, resulting in the installer giving an error about Xposed not being active, despite the framework installation screen displaying active version numbers in green. I'm currently running the 2012-04-12 CM1 nightly on a Nexus 5 (32GB).
Here's what looks like the relevant part of the log:
Code:
Apr 12, 2014 6:18:38 PM UTC
Loading Xposed v46 (for Zygote)...
Running ROM 'cm_hammerhead-userdebug 4.4.2 KVT49L 670861c82b test-keys' with fingerprint 'google/hammerhead/hammerhead:4.4.2/KOT49H/937116:user/release-keys'
Errors during resources initialization
- android.content.res.Resources android.app.ActivityThread.getTopLevelResources(java.lang.String,java.lang.String[],int,android.content.res.Configuration,android.app.LoadedApk,android.content.Context)
- public android.content.res.Resources android.app.ResourcesManager.getTopLevelResources(java.lang.String,java.lang.String[],int,java.lang.String,android.content.res.Configuration,android.content.res.CompatibilityInfo,android.os.IBinder,android.content.Context)
Errors during Xposed initialization
java.lang.NoSuchMethodError: android.app.ResourcesManager#getTopLevelResources(java.lang.String,int,android.content.res.Configuration,android.content.res.CompatibilityInfo,android.os.IBinder)#exact
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:208)
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:155)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:167)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:179)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:342)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:268)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)
And for good measure, here's the complete log: h**p://cl.ly/text/2T2S1e3c1w2f/xposed_debug_20140412_193135.log.txt
Please let me know if there's anything else I can provide.
Yes, I know: http://forum.xda-developers.com/app...d-rom-modding-modifying-t1574401/post51839299
Fixed with 2.5.1.
rovo89 said:
Yes, I know: http://forum.xda-developers.com/app...d-rom-modding-modifying-t1574401/post51839299
Fixed with 2.5.1.
Click to expand...
Click to collapse
Thanks, 2.5.1 works perfectly

[ROM][5.1.1][T710][UNOFFICIAL] CyanogenMod 12.1 for Tab S2 8.0 [BETA]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM is BETA at the moment​
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@moonbutt74
@yeshwanthvshenoy
@gladiac
@RaymanFX
@sub77
@T_I
@hennymcc
@Sarum4n - for Donating XDA add free
Each of them helped me with this project so a big thanks goes to them!
Before you start
THIS ROM IS ONLY FOR THE SM-T710
A T810 port of this rom by @T_I is available here
Code:
*
* Your warranty will be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
About the ROM
Current state of ROM : BETA
What is Fixed
Camera
Sound
Wifi
Storage
Headphones
External sdcard
Screen Rotation
Bluetooth shows note 4 instead of tab s2
Resolution
What is not working
Important
MTP
Minor
Microphone
Minor graphical glitches
Lag after trying to send a text via sms app (Just don't do it and disable the app. It will try to reach RIL even tough its wifi only)
Instructions
How to install CM12.1
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 12.1, enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
18/4/2016 - Fixed Camera (Yes I'm still alive)
**********
27/1/2016 - Fixed Headphones not working
**********
30/12/2015 - Fixed External sdcard
**********
28/12/2015 - Fixed Sound
- Removed Calling option from lockscreen
- Added missing OMX formats
- ROM is now BETA
**********
21/12/2015 - Fixed Storage problems
**********
19/12/2015 - ROM is now ALPHA
- Fixed Wifi
**********
15/12/2015 - Fixed Rotation/Orientation
- Lowered to 320 DPI
- Updated Screenshots
**********
12/12/2015 - Fixed Bluetooth showing note 4
- Fixed bad resolution
- Updated Screenshots
**********
11/12/2015 - CM12.1 Booted for the first time
**********
Downloads
Latest CM 12.1 build : Android File Host
All CM 12.1 releases can be found here : Android File Host
Recommended GAPPS Open Gapps
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/Galaxy-Tab-S2
Screenshots
XDA:DevDB Information
CyanogenMod 12.1 for Samsung Galaxy Tab S2 8.0 T710, ROM for the Samsung Galaxy Tab S2
Contributors
CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 5.1.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2015-12-11
Last Updated 2016-04-18
Q&A
Q : Why does it say Galaxy Tab S2 9.7 on Android File Host if this is for the 8.0 version ?
A : Android File Host doesn't feature the 8.0 version in their devices. Because of that, all is located under a folder called 8.0
Q : Why is everything so small?
A : The DPI rate is 320 which is the same as on the Stock rom. However, Samsung has made everything bigger. Since this is personal preference, you may always higher your DPI to make things bigger or lower your DPI to make things smaller under Settings > Display > DPI
Q : Will you ever work on CM13?
A : Yes, once we feel like CM12 is good enough, we will move to CM13
Reserved 2
New build 12/12/2015
- Fixed Bluetooth bug showing Galaxy note 4 instead of tab s2
- Fixed bad resolution
- Updated Screenshots
Great work!
Can't wait to use this once it reaches a point where it's functional for everyday use! Excellent work so far!
Good job man!!! Will test this as soon as the WiFi works
Sent from my SM-T710 using Tapatalk
good news for all T810 users! @T_I is working on a port of my ROM. It came to the CM setup wizzard however had some problems with the touchscreen. Should hopefully be a easy fix.
So the sensor module just isn't loading.
Code:
I/ ( 3857): System server: starting sensor init.
D/SensorService( 3857): nuSensorService starting...
E/HAL ( 3857): load: module=/system/lib/hw/sensors.exynos5.so
E/SensorService( 3857): couldn't load sensors module (Invalid argument)
I/ ( 3857): System server: sensor init done.
Tried to use the note 4 ones. They did load up successfully but use different drivers.
Ex the gyroscope uses ICM20610 where mine uses LSM6DS3. I really only came this far. My nightmare would be to make my own sensor libs. That would mean that I would have to learn lot's of lot's of coding!
CTXz said:
So the sensor module just isn't loading.
Code:
I/ ( 3857): System server: starting sensor init.
D/SensorService( 3857): nuSensorService starting...
E/HAL ( 3857): load: module=/system/lib/hw/sensors.exynos5.so
E/SensorService( 3857): couldn't load sensors module (Invalid argument)
I/ ( 3857): System server: sensor init done.
Tried to use the note 4 ones. They did load up successfully but use different drivers.
Ex the gyroscope uses ICM20610 where mine uses LSM6DS3. I really only came this far. My nightmare would be to make my own sensor libs. That would mean that I would have to learn lot's of lot's of coding!
Click to expand...
Click to collapse
I really dont know but doea this help:
https://github.com/STMemsLinuxDrivers/lsm6ds3-input
Sent from my SM-G928I using Tapatalk
Beukhof1 said:
I really dont know but doea this help:
https://github.com/STMemsLinuxDrivers/lsm6ds3-input
Sent from my SM-G928I using Tapatalk
Click to expand...
Click to collapse
Sadly those are for the kernel.
However,
I found this open source sensor for the s3 I9300 that uses a , what I believe, older version of the gyro found in our device. I will see what I can decompile/reverse out of the current module for the tab and will compare it with the open source ones for the I9300. This will be hard and I would be very thankfull if you could redict any expierienced dev you know, here
Suprise!
Turns out I was just missing a shared libary. That caused the module not to load. Sooo.... all that s3 sensor work for nothing
Hey.... atleast I learned something.
Also, build will be released in about 1-2h
CTXz said:
Suprise!
Turns out I was just missing a shared libary. That caused the module not to load. Sooo.... all that s3 sensor work for nothing
Hey.... atleast I learned something.
Also, build will be released in about 1-2h
Click to expand...
Click to collapse
Nice! Good job mate!
Did you have time to look at wifi yet? I would love to try it if that works!
Sent from my SM-T710 using Tapatalk
Beukhof1 said:
Nice! Good job mate!
Did you have time to look at wifi yet? I would love to try it if that works!
Sent from my SM-T710 using Tapatalk
Click to expand...
Click to collapse
Not yet, but I will take a look at it soon!
New build is out !
**********
15/12/2015 - Fixed Rotation/Orientation
- Lowered to 320 DPI
- Updated Screenshots
**********
Links have been updated!
Ok so to wifi :
I know most of you want as number 1. priority a working WIFI connection, but this doesn't seem to be that easy to fix, at least not for my empty brain. As you've probably already noticed, my debugging skills are still quite bad (Yes I'm still learning... Yes I'm not perfect.... well maybe yes... ok no just kidding). The current issue i'm facing has probably to do something with the api drivers and wpa_supplicant. I've noticed that the KMSG doesn't even show a tiny trace of the cfg80211 driver and the nl80211 driver. If any developer out there knows what to do with the following log output when trying to access the wifi HAL / Enabling WIFI please tell me.
Code:
D/SoftapController( 3507): Softap fwReload - Ok
W/CommandListener( 3507): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 3507): Setting iface cfg
E/WifiStateMachine( 3901): Unable to change interface settings: java.lang.IllegalStateException: command '90 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 90 Failed to set address (No such device)'
E/WifiMonitor( 3901): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
I/wpa_supplicant( 7883): Successfully initialized wpa_supplicant
I/wpa_supplicant( 7883): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 7883): Could not read interface wlan0 flags: No such device
I/wpa_supplicant( 7883): nl80211: Driver does not support authentication/association or connect commands
E/wpa_supplicant( 7883): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 7883): wlan0: Failed to initialize driver interface
E/WifiStateMachine( 3901): Failed to start supplicant!
D/WifiService( 3901): setWifiEnabled: false pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/SoftapController( 3507): Softap fwReload - Ok
W/CommandListener( 3507): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 3507): Setting iface cfg
E/WifiStateMachine( 3901): Unable to change interface settings: java.lang.IllegalStateException: command '93 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 93 Failed to set address (No such device)'
E/WifiMonitor( 3901): killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
I/wpa_supplicant( 7915): Successfully initialized wpa_supplicant
I/wpa_supplicant( 7915): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 7915): Could not read interface wlan0 flags: No such device
I/wpa_supplicant( 7915): nl80211: Driver does not support authentication/association or connect commands
E/wpa_supplicant( 7915): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 7915): wlan0: Failed to initialize driver interface
E/WifiStateMachine( 3901): Failed to start supplicant!
D/WifiService( 3901): setWifiEnabled: true pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/WifiController( 3901): WifiController msg { when=0 what=155656 target=com.android.internal.util.StateMachine$SmHandler } deferred for 313ms
D/WifiService( 3901): setWifiEnabled: false pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/WifiController( 3901): DEFERRED_TOGGLE handled
D/WifiService( 3901): setWifiEnabled: true pid=5956, uid=1000
E/WifiService( 3901): Invoking mWifiStateMachine.setWifiEnabled
D/SoftapController( 3507): Softap fwReload - Ok
And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!
CTXz said:
And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!
Click to expand...
Click to collapse
Thanks a lot for the effort you're putting into this.
New build 19/12/2015
This build is no longer PRE-ALPHA but ALPHA
**********
19/12/2015 - ROM is now ALPHA
- Fixed Wifi
**********
CTXz said:
And then.... all of a sudden a wild google appeared!
Big thanks to @gladiac
Build coming soon!
Click to expand...
Click to collapse
Ok, this convinced me, sdcard 4th, wifi 3rd. Build on the T810 stack is running.

Xposed related error in logcat

Hi everyone,
I hope I am posting in the right thread. I am getting errors related to xposed repeatedly in my logcat. This could be because of a module that wasn't updated yet for the latest version of xposed but I can't seem to find out which one or this could be because of other reasons. I am posting here hoping to find a resolution.
[ 06-04 13:00:07.202 16150:16150 E/Xposed ]
java.lang.NoSuchMethodError: com.android.internal.telephony.PhoneSubInfo#getDeviceId()#exact
at de.robv.android.xposed.XposedHelpers.findMethodExact(XposedHelpers.java:339)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:176)
at de.robv.android.xposed.XposedHelpers.findAndHookMethod(XposedHelpers.java:251)
at com.phoneinfo.changerpro.hooks.f.a(Unknown Source)
at com.phoneinfo.changerpro.hooks.MainHook.handleLoadPackage(Unknown Source)
at de.robv.android.xposed.IXposedHookLoadPackage$Wrapper.handleLoadPackage(IXposedHookLoadPackage.java:34)
at de.robv.android.xposed.callbacks.XC_LoadPackage.call(XC_LoadPackage.java:61)
at de.robv.android.xposed.callbacks.XCallback.callAll(XCallback.java:106)
at de.robv.android.xposed.XposedBridge$1.beforeHookedMethod(XposedBridge.java:193)
at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:720)
at android.app.ActivityThread.handleBindApplication(<Xposed>)
at android.app.ActivityThread.-wrap1(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1424)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5471)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
I appreciate any kind of suggestions. Thanks.
why not disabling all modules and then checking one by one?
it seems one of your modules is designed for a different variant of Android (one that has the method com.android.internal.telephony.PhoneSubInfo#getDev iceId()), or the module works but isn't implemented well to avoid the exception in logcat
gitfib said:
why not disabling all modules and then checking one by one?
it seems one of your modules is designed for a different variant of Android (one that has the method com.android.internal.telephony.PhoneSubInfo#getDev iceId()), or the module works but isn't implemented well to avoid the exception in logcat
Click to expand...
Click to collapse
Thanks, I'll try doing that.
Sent from my "i9300/1+2" powered by Carbon/RR
Fueled by 7000mAh ZeroLemon Battery

Categories

Resources