Question [Solved] Android 12 upgrade to Android 13 latest version developer options crash

Search This thread
By:
Advanced…
B

Bob Pan

Member
Apr 10, 2017
13
1
Has anyone have Galaxy A52s(Upgraded to Android 13) encountered the same problem?

When open the "Developer Options", the setting APP will turn into a blank screen, and then crash immediately.

Try to dial *#9900# to bypass the ADB and export system Log, can see a lot of "getNrMode" prints, and then cause Stack Overflow Error, finally Settings APP seems to crash because of this exception.

The guide about the log dump refers to this article:

(The complete log file is attached below.)

The Exception like this
Code: 
...

02-01 15:09:50.590  1000  8860  8860 I BluetoothHfpRvpCodecPreferenceController: isAvailable :: supportRvp : false, debug : false
02-01 15:09:50.590  1000  8860  8860 I BluetoothHfpRvpCodecPreferenceController: onDeveloperOptionsEnabled :: supportRvp : false, debug : false
02-01 15:09:50.590  1000  8860  8860 I BluetoothHfpDisablePreferenceController: isAvailable :: debug false
02-01 15:09:50.590  1000  8860  8860 I BluetoothHfpDisablePreferenceController: onDeveloperOptionsEnabled :: debug false
02-01 15:09:50.590  1000  8860  8860 I BluetoothDualModeDisablePreferenceController: isAvailable :: debug false, support dual mode false
02-01 15:09:50.590  1000  8860  8860 I BluetoothDualModeDisablePreferenceController: onDeveloperOptionsEnabled :: debug false, support dual mode false
02-01 15:09:50.590  1000  8860  8860 I BluetoothMapNetworkTypePreferenceController: isAvailable :: debug false
02-01 15:09:50.590  1000  8860  8860 I BluetoothMapNetworkTypePreferenceController: onDeveloperOptionsEnabled :: debug false
02-01 15:09:50.590  1000  8860  8860 I BluetoothSapActivationController: onDeveloperOptionsEnabled :: debug false
02-01 15:09:50.591  1000  8860  8860 D SecSimFeatureProvider: getTelephonyProperty : 0 : 2
02-01 15:09:50.591  1000  8860  8860 D SecSimFeatureProvider: getTelephonyProperty : 1 : 0
02-01 15:09:50.591  1000  8860  8860 D SecSimFeatureProvider: getEnabledSimCnt : 1
02-01 15:09:50.591  1000  8860  8860 D ConnectionsUtils: isNoSIM : 1
02-01 15:09:50.591  1000  8860  8860 I ConnectionsUtils: default network mode : 26
02-01 15:09:50.591  1000  8860  8860 D ConnectionsUtils: isSupport5GConcept : true
02-01 15:09:50.591  1000  8860  8860 D SecSimFeatureProvider: getTelephonyProperty : 0 : 2
02-01 15:09:50.591  1000  8860  8860 D SecSimFeatureProvider: getTelephonyProperty : 1 : 0
02-01 15:09:50.591  1000  8860  8860 D SecSimFeatureProvider: getEnabledSimCnt : 1
02-01 15:09:50.591  1000  8860  8860 D ConnectionsUtils: isNoSIM : 1
02-01 15:09:50.591  1000  8860  8860 I ConnectionsUtils: default network mode : 26
02-01 15:09:50.591  1000  8860  8860 D ConnectionsUtils: isSupport5GConcept : true
02-01 15:09:50.591  1000  8860  8860 I NetworkModeOf5gTypeController: onDeveloperOptionsEnabled : state = TRUE
02-01 15:09:50.591  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
02-01 15:09:50.594  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
02-01 15:09:50.595  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
02-01 15:09:50.596  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
02-01 15:09:50.596 10216  9335  9335 E roid.apps.turbo: Not starting debugger since process cannot load the jdwp agent.
02-01 15:09:50.596  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
02-01 15:09:50.597  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
02-01 15:09:50.598  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
02-01 15:09:50.599  1000  8860  8860 D NetworkModeOf5gTypeController: [getNrMode]
(A lot of getNrMode prints)

...
Code: 
--------- beginning of crash
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime: FATAL EXCEPTION: main
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime: Process: com.android.settings, PID: 8860
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime: java.lang.StackOverflowError: stack size 8188KB
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.NetworkModeOf5gTypeController.getNrMode(NetworkModeOf5gTypeController.java:182)
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.NetworkModeOf5gTypeController.updateState(NetworkModeOf5gTypeController.java:141)
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.NetworkModeOf5gTypeController.getNrMode(NetworkModeOf5gTypeController.java:191)
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.NetworkModeOf5gTypeController.updateState(NetworkModeOf5gTypeController.java:141)
02-01 15:09:56.259  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.NetworkModeOf5gTypeController.getNrMode(NetworkModeOf5gTypeController.java:191)

.... (Cause by 141 line and 191 line repeats a lot)

02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.NetworkModeOf5gTypeController.onDeveloperOptionsEnabled(NetworkModeOf5gTypeController.java:164)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.DevelopmentSettingsDashboardFragment.enableDeveloperOptions(DevelopmentSettingsDashboardFragment.java:524)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at com.android.settings.development.DevelopmentSettingsDashboardFragment.onActivityCreated(DevelopmentSettingsDashboardFragment.java:262)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.Fragment.performActivityCreated(Fragment.java:3076)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentStateManager.activityCreated(FragmentStateManager.java:578)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentStateManager.moveToExpectedState(FragmentStateManager.java:264)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentStore.moveToExpectedState(FragmentStore.java:115)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentManager.moveToState(FragmentManager.java:1374)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentManager.dispatchStateChange(FragmentManager.java:2841)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentManager.dispatchActivityCreated(FragmentManager.java:2784)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentController.dispatchActivityCreated(FragmentController.java:262)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.fragment.app.FragmentActivity.onStart(FragmentActivity.java:477)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at androidx.appcompat.app.AppCompatActivity.onStart(AppCompatActivity.java:246)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1510)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.Activity.performStart(Activity.java:8603)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.ActivityThread.handleStartActivity(ActivityThread.java:4191)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2571)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:106)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.os.Looper.loopOnce(Looper.java:226)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:313)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:8741)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
02-01 15:09:56.364  1000  8860  8860 E AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
02-01 15:09:56.403 10131  9687  9687 V GraphicsEnvironment: ANGLE Developer option for 'com.microsoft.appmanager' set to: 'default'
02-01 15:09:56.404 10131  9687  9687 V GraphicsEnvironment: ANGLE GameManagerService for com.microsoft.appmanager: false
02-01 15:09:56.428 10131  9687  9687 D NetworkSecurityConfig: No Network Security Config specified, using platform default
02-01 15:09:56.433 10131  9687  9687 D NetworkSecurityConfig: No Network Security Config specified, using platform default
02-01 15:09:56.434  1000  1345  9704 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x6
02-01 15:09:56.447  1000  1345  2381 W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.sendBroadcast:1252 com.android.server.am.AppErrors.crashApplicationInner:722 com.android.server.am.AppErrors.crashApplication:598 com.android.server.am.ActivityManagerService.handleApplicationCrashInner:10389 com.android.server.am.ActivityManagerService.handleApplicationCrash:10258
02-01 15:09:56.448  1000  1345  2381 W ActivityTaskManager:   Force finishing activity com.android.settings/.SubSettings
02-01 15:09:56.448  1000  1345  2381 W WindowManager: Prepare app transition: mNextAppTransitionRequests=[TRANSIT_CLOSE], mNextAppTransitionFlags=TRANSIT_FLAG_KEYGUARD_GOING_AWAY_TO_LAUNCHER_WITH_IN_WINDOW_ANIMATIONS | TRANSIT_FLAG_APP_CRASHED, displayId: 0 Callers=com.android.server.wm.DisplayContent.prepareAppTransition:6380 com.android.server.wm.DisplayContent.requestTransitionAndLegacyPrepare:6396 com.android.server.wm.Task.finishTopCrashedActivityLocked:6613 com.android.server.wm.RootWindowContainer.lambda$finishTopCrashedActivities$19:2641 com.android.server.wm.RootWindowContainer.$r8$lambda$4nB35TzseTo6qyVD9NxDieoJN1Y:0
02-01 15:09:56.449  1000  1345  2381 W WindowManager: Prepare app transition: mNextAppTransitionRequests=[TRANSIT_CLOSE, TRANSIT_CLOSE], mNextAppTransitionFlags=TRANSIT_FLAG_KEYGUARD_GOING_AWAY_TO_LAUNCHER_WITH_IN_WINDOW_ANIMATIONS | TRANSIT_FLAG_APP_CRASHED, displayId: 0 Callers=com.android.server.wm.DisplayContent.prepareAppTransition:6380 com.android.server.wm.DisplayContent.prepareAppTransition:6371 com.android.server.wm.ActivityRecord.finishIfPossible:4103 com.android.server.wm.ActivityRecord.finishIfPossible:3923 com.android.server.wm.Task.finishTopCrashedActivityLocked:6614
02-01 15:09:56.452  1000  1345  2381 W ActivityTaskManager:   Force finishing activity com.android.settings/.homepage.SettingsHomepageActivity
02-01 15:09:56.453  1000  1345  2381 D InputDispatcher: Focused application(0): ActivityRecord{171c3eb u0 com.sec.android.app.launcher/.activities.LauncherActivity} t21}
02-01 15:09:56.454  1000  1345  2381 D SGM:FgCheckThread: TaskStackListener.onTaskFocusChanged(), taskId=22, focused=false
02-01 15:09:56.454  1000  1345  2381 D SGM:FgCheckThread: TaskStackListener.onTaskFocusChanged(), taskId=21, focused=true
02-01 15:09:56.454  1000  1345  2381 D SGM:FgCheckThread:   sendRunningComponentFocus(), pkgName: com.sec.android.app.launcher, userId: 0
02-01 15:09:56.454  1000  1345  2128 D SGM:FgCheckThread: onLooperPrepared(), msg: MSG_TASK_FOCUSED, pkgName: com.sec.android.app.launcher, userId: 0
02-01 15:09:56.454  1000  1345  2128 D SGM:FgCheckThread: handleTaskFocused().
02-01 15:09:56.454  1000  1345  2128 D SGM:FgCheckThread: sendFocusOutConditionally() - mPrevNotiPkg: (unknown), userId: 0
02-01 15:09:56.454  1000  1345  2128 D SGM:FgCheckThread:   handleTaskFocused(), pkgName: com.sec.android.app.launcher, userID:0 mResumedPkgMap does not containsKey.
02-01 15:09:56.455  1000  1345  2381 V WindowManager: Setting visibility of Window{1bb67b2 u0 com.sec.android.app.launcher/com.sec.android.app.launcher.activities.LauncherActivity}: true, caller=com.android.server.wm.WindowContainer.sendAppVisibilityToClients:1236 com.android.server.wm.WindowToken.setClientVisible:431 com.android.server.wm.ActivityRecord.setClientVisible:7565 com.android.server.wm.ActivityRecord.setVisibility:5985 com.android.server.wm.ActivityRecord.setVisibility:5889
02-01 15:09:56.455 10126  2802  2802 I [email protected][LauncherActivity]: handleAppVisibility mAppVisible = false visible = true
02-01 15:09:56.456 10037  2338  2338 D TileLifecycleManager: Unbinding service Intent { cmp=com.samsung.android.lool/com.samsung.android.sm.battery.ui.mode.BatteryModeTile (has extras) } UserHandle{0}
02-01 15:09:56.458  1000  8860  8860 I Process : Sending signal. PID: 8860 SIG: 9
02-01 15:09:56.458  1000  1345  1703 D PersonaActivityHelper: Activity not in resumed state, do not run immediate lock
02-01 15:09:56.459  1000  1345  5494 I ActivityManager: Changes in 10126 5 to 2, 8 to 15
02-01 15:09:56.459  1000  1345  5494 I AppOps  : updateUidProcState uid: 10126 procState: 2 capability:15
02-01 15:09:56.459  1000  1345  5494 I AppOps  : commitUidPendingStateLocked() :: UID - 10126, 500 > 200, 8 > 15
02-01 15:09:56.460  1000  1001  4604 I sensors-hal: handle_sns_std_sensor_event:231, [SSC_LIGHT] P: 201(184),als:255,green:94,ir:1,delta_avg:0,delta_max:6,stdev:1,stdev_per_4sample:1,magig_code or itime:384
02-01 15:09:56.460  1000  1345  1701 D SSRM:LoadDetectMonitor: PID = 2802, UID = 10126
02-01 15:09:56.460  1000  4950  4950 I PowerMode.Tile: onUnbind
02-01 15:09:56.461 10126  2802  2802 I TopTaskTracker: onTaskMovedToFront : taskId = 21
02-01 15:09:56.461  1000  1345  1701 D Native_CFMS: CFMS Delete Task Tid(9216)
02-01 15:09:56.461  1000  4950  4950 I PowerMode.Tile: onDestroy

...
 

Attachments

  • dumpState_A528BZTU1DWA4_202302011510Z.zip
    15.8 MB · Views: 11
BlackMesa123

BlackMesa123

Recognized Contributor
Aug 29, 2015
1,921
3,635
20
Adrano
Samsung Galaxy S5
Samsung Galaxy J5
Under the hood it looks like there's an issue with the TelephonyManager service in your phone, a preference item in the Developer Option bounces back and forth between these two functions since the "mStateMode" variable isn't set correctly, causing that stack overflow crash.

Screenshot 2023-02-02 alle 17.52.24.png

Screenshot 2023-02-02 alle 17.52.56.png
 
  • Like
Reactions: Bob Pan
B

Bob Pan

Member
Apr 10, 2017
13
1
BlackMesa123 said:
Under the hood it looks like there's an issue with the TelephonyManager service in your phone, a preference item in the Developer Option bounces back and forth between these two functions since the "mStateMode" variable isn't set correctly, causing that stack overflow crash.

View attachment 5826253
View attachment 5826255
Click to expand...
Click to collapse
Yes, I bought this phone in Taiwan, and use Taiwan's telecommunications provider.

So what can I do to solve this problem? Can it be solved without wiping the data?
 
B

Bob Pan

Member
Apr 10, 2017
13
1
I'm trying to write a small program that executes decompiled instructions from the Settings App when the button is pressed (want to see what can I get when call the same thing)
But it seems that will cause "InvocationTargetException", maybe something I writes is wrong.

The code after pressed the button like below:
Java: 
    public void btnActivate(View view) {
        TelephonyManager tel = (TelephonyManager) this.getSystemService(Context.TELEPHONY_SERVICE);
        try {
            Method method = TelephonyManager.class.getDeclaredMethod("semGetNrMode", new Class[0]);
            method.setAccessible(true);
            editText.setText(((Integer) method.invoke(tel, new Object[0])).intValue());
        } catch (Exception e) {
            StringWriter sw = new StringWriter();
            PrintWriter pw = new PrintWriter(sw);
            e.printStackTrace(pw);
            editText.setText(sw.toString());
        }
    }

And the program outputs(I can't open ADB because the developer options is broken):
Screenshot_20230203_143826_BugTest230203.jpg
 
BlackMesa123

BlackMesa123

Recognized Contributor
Aug 29, 2015
1,921
3,635
20
Adrano
Samsung Galaxy S5
Samsung Galaxy J5
Bob Pan said:
I'm trying to write a small program that executes decompiled instructions from the Settings App when the button is pressed (want to see what can I get when call the same thing)
But it seems that will cause "InvocationTargetException", maybe something I writes is wrong.

The code after pressed the button like below:
Java: 
    public void btnActivate(View view) {
        TelephonyManager tel = (TelephonyManager) this.getSystemService(Context.TELEPHONY_SERVICE);
        try {
            Method method = TelephonyManager.class.getDeclaredMethod("semGetNrMode", new Class[0]);
            method.setAccessible(true);
            editText.setText(((Integer) method.invoke(tel, new Object[0])).intValue());
        } catch (Exception e) {
            StringWriter sw = new StringWriter();
            PrintWriter pw = new PrintWriter(sw);
            e.printStackTrace(pw);
            editText.setText(sw.toString());
        }
    }

And the program outputs(I can't open ADB because the developer options is broken):
View attachment 5826625
Click to expand...
Click to collapse

I don’t think you can call those API’s if your app doesn’t have the required permissions granted, by looking at the snippets of code I sent you it’s clear the returned value is “-1”, which is causing the loop.
 
BlackMesa123

BlackMesa123

Recognized Contributor
Aug 29, 2015
1,921
3,635
20
Adrano
Samsung Galaxy S5
Samsung Galaxy J5
Bob Pan said:
Yes, I bought this phone in Taiwan, and use Taiwan's telecommunications provider.

So what can I do to solve this problem? Can it be solved without wiping the data?
Click to expand...
Click to collapse

I’ll check later if there’s a way that specific preference can be disabled, but I’d try disabling 5G in network settings and see if the Developer Options page still crashes
 
B

Bob Pan

Member
Apr 10, 2017
13
1
BlackMesa123 said:
I’ll check later if there’s a way that specific preference can be disabled, but I’d try disabling 5G in network settings and see if the Developer Options page still crashes
Click to expand...
Click to collapse
I try to change some settings and... It solved?

The settings under the Mobile Network Options(maybe) (I need to switch language to the English to see what that things exactly in the English's firmware)

Switch the mode from "4G/3G/2G" to "5G/4G/3G/2G"
Weird...
 
BlackMesa123

BlackMesa123

Recognized Contributor
Aug 29, 2015
1,921
3,635
20
Adrano
Samsung Galaxy S5
Samsung Galaxy J5
Bob Pan said:
I try to change some settings and... It solved?

The settings under the Mobile Network Options(maybe) (I need to switch language to the English to see what that things exactly in the English's firmware)

Switch the mode from "4G/3G/2G" to "5G/4G/3G/2G"
Weird...
Click to expand...
Click to collapse

Well the preference causing that crash is related to 5G so it doesn’t surprises me, doesn’t changes the fact something’s wrong with the TelephonyManager service
 
B

Bob Pan

Member
Apr 10, 2017
13
1
The exactly options under the Connection > Mobile Network > Network Mode
(In Chinese: 連接 > 行動網路 > 網路模式)

Switch it to default(5G/4G/3G/2G) fixes the problem.

When I switch back to original options(4G/3G/2G), it broken again
Maybe some firmware bug cause it...?
 

Attachments

  • Screenshot_20230203_145953_Call settings.jpg
    Screenshot_20230203_145953_Call settings.jpg
    189.3 KB · Views: 22
  • Screenshot_20230203_145940_Call settings.jpg
    Screenshot_20230203_145940_Call settings.jpg
    214.6 KB · Views: 21
  • Screenshot_20230203_145741_Call settings.jpg
    Screenshot_20230203_145741_Call settings.jpg
    164.3 KB · Views: 17
  • Screenshot_20230203_145404_Call settings.jpg
    Screenshot_20230203_145404_Call settings.jpg
    191.5 KB · Views: 21
Last edited:
B

Bob Pan

Member
Apr 10, 2017
13
1
Bob Pan said:
The exactly options under the Connection > Mobile Network > Network Mode
(In Chinese: 連接 > 行動網路 > 網路模式)

When I switch back to original options(4G/3G/2G), it broken again
Maybe some firmware bug cause it...?
Click to expand...
Click to collapse

I try to use Samsung Members to reports this problem, hope the official developers can fix this problem at later updates.
 
Last edited:
  • Like
Reactions: BlackMesa123
B

Bob Pan

Member
Apr 10, 2017
13
1
wong36987 said:
May I know any update for this issue?? I am facing the same problem...
Click to expand...
Click to collapse

Just sets your Network Mode, like the comment I writed before

Bob Pan said:
The exactly options under the Connection > Mobile Network > Network Mode
(In Chinese: 連接 > 行動網路 > 網路模式)

When I switch back to original options(4G/3G/2G), it broken again
Maybe some firmware bug cause it...?
Click to expand...
Click to collapse

It will temporary fixed the problem. But it seems like the firmware bug, so we need to wait the Samsung's team released the new firmware to fix it.

I tried the firmware released last month, seems the bug still exists.
 
Last edited:
You must log in or register to reply here.

Similar threads

BlackMesa123
Development [KERNEL][12/13][A528B/N] Mesa's Custom Kernel R4
Replies
87
Views
9K
dornz
dornz
ShaDisNX255
Development [ROM][Port][OneUI5] NcX S21FE ROM [SM-A528B]
Replies
155
Views
14K
P
pp202ku
B
Question Android 12 and One UI4 Update for A52s
Replies
38
Views
6K
P
pejicgoran
muppetz
Question Android 13 (+ One UI 5) for Samsung Galaxy A52s 5G
Replies
1
Views
5K
BlueChris
BlueChris
robogo1982
General Android 13 with OneUI 5.0 out in the EU
Replies
32
Views
4K
L
Lebatman

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 1
    BlackMesa123
    BlackMesa123
    Under the hood it looks like there's an issue with the TelephonyManager service in your phone, a preference item in the Developer Option bounces back and forth between these two functions since the "mStateMode" variable isn't set correctly, causing that stack overflow crash.

    Screenshot 2023-02-02 alle 17.52.24.png

    Screenshot 2023-02-02 alle 17.52.56.png
    View
    1
    B
    Bob Pan
    Bob Pan said:
    The exactly options under the Connection > Mobile Network > Network Mode
    (In Chinese: 連接 > 行動網路 > 網路模式)

    When I switch back to original options(4G/3G/2G), it broken again
    Maybe some firmware bug cause it...?
    Click to expand...
    Click to collapse

    I try to use Samsung Members to reports this problem, hope the official developers can fix this problem at later updates.
    View

New posts