[Q] Debugging userland reboots - General Questions and Answers

I've been running Cyanogenmod 10.2 on my 2012 Nexus 7, and I've been having trouble with random reboots every few days. I have no idea if this is hardware, ROM, or app related, and debugging it has been tough because it seems to only happen when I'm not actively using the tablet.
I installed RebootLogger along with catlog, and luckily it captured something during a reboot. What's interesting is that it's not a full reboot to the bootloader, but just seems to reload the UI / app layers. So far, these are the only logs I've been able to capture. I've got more, but I think this is the relevant subset:
Code:
02-27 15:18:44.060 I/ActivityManager(20034): Process com.levelup.touiteur (pid 2793) has died.
02-27 15:18:44.150 I/ActivityManager(20034): Process com.google.android.partnersetup (pid 1768) has died.
02-27 15:18:59.514 I/ActivityManager(20034): Process com.google.android.googlequicksearchbox:search (pid 1750) has died.
02-27 15:19:45.146 I/ActivityManager(20034): Start proc com.google.android.googlequicksearchbox:search for broadcast com.google.android.googlequicksearchbox/com.google.android.sidekick.main.calendar.CalendarIntentService$CalendarReceiver: pid=3429 uid=10037 gids={50037, 3003, 1028, 3002, 1015}
02-27 15:19:46.146 I/ActivityManager(20034): Start proc com.google.android.partnersetup for content provider com.google.android.partnersetup/.RlzAppProvider: pid=3446 uid=10058 gids={50058, 3003, 1028}
02-27 15:22:28.584 W/Watchdog(20034): *** WATCHDOG KILLING SYSTEM PROCESS: null
02-27 15:22:28.984 E/AndroidRuntime(3489): FATAL EXCEPTION: main
02-27 15:22:28.984 E/AndroidRuntime(3489): java.lang.NullPointerException
02-27 15:22:28.984 E/AndroidRuntime(3489): at android.app.ActivityThread.attach(ActivityThread.java:5156)
02-27 15:22:28.984 E/AndroidRuntime(3489): at android.app.ActivityThread.main(ActivityThread.java:5276)
02-27 15:22:28.984 E/AndroidRuntime(3489): at java.lang.reflect.Method.invokeNative(Native Method)
02-27 15:22:28.984 E/AndroidRuntime(3489): at java.lang.reflect.Method.invoke(Method.java:525)
02-27 15:22:28.984 E/AndroidRuntime(3489): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
02-27 15:22:28.984 E/AndroidRuntime(3489): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:555)
02-27 15:22:28.984 E/AndroidRuntime(3489): at dalvik.system.NativeStart.main(Native Method)
02-27 15:22:29.024 E/AndroidRuntime(3489): Error reporting crash
02-27 15:22:29.024 E/AndroidRuntime(3489): java.lang.NullPointerException
02-27 15:22:29.024 E/AndroidRuntime(3489): at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
02-27 15:22:29.024 E/AndroidRuntime(3489): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:693)
02-27 15:22:29.024 E/AndroidRuntime(3489): at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:690)
02-27 15:22:29.024 E/AndroidRuntime(3489): at dalvik.system.NativeStart.main(Native Method)
02-27 15:22:29.054 E/ActivityThread(3429): Failed to find provider info for com.android.calendar
02-27 15:22:29.054 E/ActivityThread(3429): Failed to find provider info for com.android.calendar
02-27 15:22:31.834 W/dalvikvm(3526): PR_SET_NO_NEW_PRIVS failed. Is your kernel compiled correctly?: Invalid argument
02-27 15:22:34.384 I/SystemServer(3740): Entered the Android system server!
02-27 15:22:34.384 I/SystemServer(3740): Waiting for installd to be ready.
02-27 15:22:34.384 I/SystemServer(3740): Enabled StrictMode logging for UI Looper
02-27 15:22:34.384 I/SystemServer(3740): Enabled StrictMode logging for WM Looper
02-27 15:22:34.384 I/Installer(3740): connecting...
02-27 15:22:34.384 I/SystemServer(3740): Power Manager
So far, my best guess is that it might be an app or service causing the crash, but that the actual bug might be in the ROM since I would assume that logging "null" as the failed process is not correct. To end this with some actual questions:
Are there any other, better methods for debugging this? Since it only happens every few days leaving it wired up isn't really an option.
Anything I'm missing in the above that points to where I should start looking next?
Is there a way I can get it to wait for a debugger on the exception, even if I'm unplugged at the moment? Just some way so I can inspect the system at the moment of the exception without constantly being on USB.

hi deviantintegral, did you ever get an answer to this? I'm having similar problems with my GS4. I had official rom on it and had random restarts which only seemed to occur when I wasn't looking at the phone (about 1 a day). I'm now using the latest CM and it still reboots. I too am wondering if there is some method to debug to a log which would indicate if it was an app or hardware that cause a reboot.

Sniipe said:
hi deviantintegral, did you ever get an answer to this? I'm having similar problems with my GS4.
Click to expand...
Click to collapse
Not really. I did manage to get logs during a crash, but the exception was very generic and didn't indicate anything specific. I've since upgraded to CM11 and haven't noticed any more reboots.

Related

[Q] android development

Site did't let me post in the development section..
I am trying to create a small app that uses the camera but when I try to setContentView() to another layout than the one with the SurfaceView used by th camera, an unhandled exception occurs which terminates the program. Here is the stack trace:
Code:
04-08 14:24:55.104: WARN/dalvikvm(328): threadid=1: thread exiting with uncaught exception (group=0x40015560)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): FATAL EXCEPTION: main
04-08 14:24:55.194: ERROR/AndroidRuntime(328): java.lang.RuntimeException: Method called after release()
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at android.hardware.Camera.setHasPreviewCallback(Native Method)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at android.hardware.Camera.access$600(Camera.java:114)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at android.hardware.Camera$EventHandler.handleMessage(Camera.java:545)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at android.os.Handler.dispatchMessage(Handler.java:99)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at android.os.Looper.loop(Looper.java:123)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at android.app.ActivityThread.main(ActivityThread.java:3683)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at java.lang.reflect.Method.invokeNative(Native Method)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at java.lang.reflect.Method.invoke(Method.java:507)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
04-08 14:24:55.194: ERROR/AndroidRuntime(328): at dalvik.system.NativeStart.main(Native Method)
04-08 14:24:55.274: WARN/ActivityManager(61): Force finishing activity net.stamoulis.frames/.main
I guess some callback is generated after I call Camera.stopPreview() and Camera.release() but I can't see where it is actually generated. So, is there a way to find out which of my methods generates the callback and in which thread is this taking place? I've tried android.os.Debug.startMethodTracing(); but I can't really understand the output I'm getting.
Could anyone help me out with this?
I thank you in advance,
George.

"Unfortunately, Terminal Emulator has stopped." -- Missing library?

It's been a while since I've used Terminal Emulator on the phone, but this is a new failure for me. As far as I know, I'm still running the same CM9 build from months ago and shouldn't have changed much. As best as I can tell it is an unsatisfied library linkage.
Code:
Caused by: java.lang.UnsatisfiedLinkError: Couldn't load jackpal-androidterm4: findLibrary returned null
but no indications as to what might be missing. I've re-installed a fresh APK from both Market/Play, as well as deleting and side-loading from the source distribution site, without much change in behavior. APK is installed in /system/app/ and is ODEX-ed when installed by Market/Play over the original. Installing from Market/Play or side-loading as a user app
Has anyone else run into this?
More logcat:
Code:
I/ActivityManager( 224): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=jackpal.androidterm/.Term bnds=[240,170][360,302]} from pid 14011
I/ActivityManager( 224): Start proc jackpal.androidterm for activity jackpal.androidterm/.Term: pid=20860 uid=10081 gids={3003, 1015}
I/dalvikvm(20860): Turning on JNI app bug workarounds for target SDK version 11...
E/Term (20860): onCreate
D/OpenGLRenderer(14011): Flushing caches (mode 1)
D/Term (20860): TermService started
I/TermService(20860): Activity called onBind()
I/Term (20860): Bound to TermService
I/TermService(20860): Activity binding to service
W/dalvikvm(20860): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Ljackpal/androidterm/Exec;
D/AndroidRuntime(20860): Shutting down VM
W/dalvikvm(20860): threadid=1: thread exiting with uncaught exception (group=0x40a2b1f8)
E/AndroidRuntime(20860): FATAL EXCEPTION: main
E/AndroidRuntime(20860): java.lang.ExceptionInInitializerError
E/AndroidRuntime(20860): at jackpal.androidterm.ShellTermSession.createSubprocess(ShellTermSession.java:198)
E/AndroidRuntime(20860): at jackpal.androidterm.ShellTermSession.initializeSession(ShellTermSession.java:135)
E/AndroidRuntime(20860): at jackpal.androidterm.ShellTermSession.<init>(ShellTermSession.java:88)
E/AndroidRuntime(20860): at jackpal.androidterm.Term.createTermSession(Term.java:430)
E/AndroidRuntime(20860): at jackpal.androidterm.Term.createTermSession(Term.java:439)
E/AndroidRuntime(20860): at jackpal.androidterm.Term.populateViewFlipper(Term.java:352)
E/AndroidRuntime(20860): at jackpal.androidterm.Term.access$400(Term.java:78)
E/AndroidRuntime(20860): at jackpal.androidterm.Term$2.onServiceConnected(Term.java:148)
E/AndroidRuntime(20860): at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1068)
E/AndroidRuntime(20860): at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1085)
E/AndroidRuntime(20860): at android.os.Handler.handleCallback(Handler.java:605)
E/AndroidRuntime(20860): at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime(20860): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(20860): at android.app.ActivityThread.main(ActivityThread.java:4575)
E/AndroidRuntime(20860): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(20860): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(20860): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
E/AndroidRuntime(20860): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
E/AndroidRuntime(20860): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(20860): Caused by: java.lang.UnsatisfiedLinkError: Couldn't load jackpal-androidterm4: findLibrary returned null
E/AndroidRuntime(20860): at java.lang.Runtime.loadLibrary(Runtime.java:365)
E/AndroidRuntime(20860): at java.lang.System.loadLibrary(System.java:535)
E/AndroidRuntime(20860): at jackpal.androidterm.Exec.<clinit>(Exec.java:33)
E/AndroidRuntime(20860): ... 19 more
W/ActivityManager( 224): Force finishing activity jackpal.androidterm/.Term

emu-ex-plus-alpha emulators cause KatKernel-based TF101 to reboot

I am having a very irritating issue with my TF101. I can't run any of the emu.ex.plus.alpha suite of emulators on any OS based on the KatKernel—attempting to open the emulators simply causes the device to reboot.
The emulators worked on stock, they worked on the last official version of CyanogenMod for the TF101, but they will not work on KatKiss, Omni, or any other OS based on KatKernel.
Sorry to double-post
Found a potential lead in an lc dump:
Code:
09-08 10:18:07.025 I/ActivityManager( 416): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.explusalpha.Snes9xPlus/com.imagine.BaseActivity bnds=[798,85][956,193]} from pid 634
09-08 10:18:07.034 D/PermissionCache( 107): checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (149 us)
09-08 10:18:07.065 W/BroadcastQueue( 416): Permission Denial: receiving Intent { act=com.android.launcher3.action.LAUNCH flg=0x10 (has extras) } to com.google.android.googlequicksearchbox/com.google.android.search.core.summons.icing.InternalIcingCorporaProvider$ApplicationLaunchReceiver requires com.android.launcher3.permission.RECEIVE_LAUNCH_BROADCASTS due to sender com.android.launcher3 (uid 10008)
09-08 10:18:07.135 I/ActivityManager( 416): Start proc com.explusalpha.Snes9xPlus for activity com.explusalpha.Snes9xPlus/com.imagine.BaseActivity: pid=1420 uid=10063 gids={50063, 1028, 1015, 1023, 3002, 3001}
09-08 10:18:07.185 I/qtaguid ( 1101): Failed write_ctrl(u 59) res=-1 errno=22
09-08 10:18:07.185 I/qtaguid ( 1101): Untagging socket 59 failed errno=-22
09-08 10:18:07.185 W/NetworkManagementSocketTagger( 1101): untagSocket(59) failed with errno -22
09-08 10:18:07.225 E/cutils ( 104): Failed to mkdirat(/storage/sdcard2/Android): Read-only file system
09-08 10:18:07.225 W/ContextI
It is at this point that the device reboots.

Phone rebooting when mobile network is unreachable

Recently, an Xperia M2 of ours started to reboot from time to time. It seems to be related to disconnects from mobile network:
When no SIM card was inserted, reboots occured every few minutes
Also when signal is weak, the phone reboots every few minutes
Turning mobile data on/off also causes crashes sometimes
Yesterday, the phone rebooted exactly every 30 minutes while mobile data was turned on
The phone is running the latest stock firmware. Here's the relevant part of the log:
--------- beginning of crash
08-29 15:25:50.163 E/AndroidRuntime( 770): *** FATAL EXCEPTION IN SYSTEM PROCESS: NetworkStats
08-29 15:25:50.163 E/AndroidRuntime( 770): java.lang.RuntimeException: Error receiving broadcast Intent { act=com.android.server.action.NETWORK_STATS_POLL flg=0x14 (has extras) } in [email protected]
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:882)
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.os.Handler.handleCallback(Handler.java:739)
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.os.Handler.dispatchMessage(Handler.java:95)
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.os.Looper.loop(Looper.java:211)
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.os.HandlerThread.run(HandlerThread.java:61)
08-29 15:25:50.163 E/AndroidRuntime( 770): Caused by: java.lang.IllegalArgumentException: tried recording negative data
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.net.NetworkStatsHistory.recordData(NetworkStatsHistory.java:304)
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.net.NetworkStatsHistory.recordHistory(NetworkStatsHistory.java:377)
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.net.NetworkStatsHistory.recordEntireHistory(NetworkStatsHistory.java:353)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsCollection.recordHistory(NetworkStatsCollection.java:224)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsCollection.read(NetworkStatsCollection.java:288)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsCollection.read(NetworkStatsCollection.java:262)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsRecorder$CombiningRewriter.read(NetworkStatsRecorder.java:303)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.internal.util.FileRotator.readFile(FileRotator.java:372)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.internal.util.FileRotator.rewriteSingle(FileRotator.java:242)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.internal.util.FileRotator.rewriteActive(FileRotator.java:184)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsRecorder.forcePersistLocked(NetworkStatsRecorder.java:240)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsRecorder.maybePersistLocked(NetworkStatsRecorder.java:227)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsService.performPollLocked(NetworkStatsService.java:971)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsService.performPoll(NetworkStatsService.java:914)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsService.access$600(NetworkStatsService.java:136)
08-29 15:25:50.163 E/AndroidRuntime( 770): at com.android.server.net.NetworkStatsService$3.onReceive(NetworkStatsService.java:703)
08-29 15:25:50.163 E/AndroidRuntime( 770): at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:872)
08-29 15:25:50.163 E/AndroidRuntime( 770): ... 4 more
08-29 15:25:50.175 D/ActivityManager( 770): New dropbox entry: system_server, system_server_crash, 94e67198-5dd2-4a3d-af5e-5f7b9ef92cae
08-29 15:25:50.175 I/ActivityManager( 770): A system dump is comming => Stay in memory
08-29 15:25:50.372 D/ActivityManager( 770): System dump requested by: system_server (crash)
08-29 15:25:50.381 D/ActivityManager( 770): Sync fs
08-29 15:25:50.526 D/ActivityManager( 770): Sync done
08-29 15:25:50.533 I/ActivityManager( 770): Continue force dump
08-29 15:25:50.536 I/ActivityManager( 770): Do sysrq
Also, starting from yesterday, accessing Data usage crashes the Settings app. I guess that's only corrupt data remaining from one of the system crashes. Relevant logs:
08-30 09:37:10.229 D/SubSettings(23848): Launching fragment com.android.settings.DataUsageSummary
08-30 09:37:10.417 D/TelephonyManager(23848): getDataEnabled: retVal=false
08-30 09:37:10.421 D/DataUsage(23848): generating cs=1596232800000 to ce=1598911200000 waiting for hs=1594483200000
08-30 09:37:10.429 D/DataUsage(23848): generating cs=1593554400000 to ce=1596232800000 waiting for hs=1594483200000
08-30 09:37:10.454 E/AndroidRuntime(23848): FATAL EXCEPTION: AsyncTask #3
08-30 09:37:10.454 E/AndroidRuntime(23848): Process: com.android.settings, PID: 23848
08-30 09:37:10.454 E/AndroidRuntime(23848): java.lang.RuntimeException: An error occured while executing doInBackground()
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.os.AsyncTask$3.done(AsyncTask.java:304)
08-30 09:37:10.454 E/AndroidRuntime(23848): at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
08-30 09:37:10.454 E/AndroidRuntime(23848): at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
08-30 09:37:10.454 E/AndroidRuntime(23848): at java.util.concurrent.FutureTask.run(FutureTask.java:242)
08-30 09:37:10.454 E/AndroidRuntime(23848): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
08-30 09:37:10.454 E/AndroidRuntime(23848): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
08-30 09:37:10.454 E/AndroidRuntime(23848): at java.lang.Thread.run(Thread.java:818)
08-30 09:37:10.454 E/AndroidRuntime(23848): Caused by: java.lang.IllegalArgumentException: tried recording negative data
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.os.Parcel.readException(Parcel.java:1559)
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.os.Parcel.readException(Parcel.java:1505)
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.net.INetworkStatsSession$Stub$Proxy.getSummaryForAllUid(INetworkStatsSession.java:257)
08-30 09:37:10.454 E/AndroidRuntime(23848): at com.android.settings.net.SummaryForAllUidLoader.loadInBackground(SummaryForAllUidLoader.java:62)
08-30 09:37:10.454 E/AndroidRuntime(23848): at com.android.settings.net.SummaryForAllUidLoader.loadInBackground(SummaryForAllUidLoader.java:27)
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.content.AsyncTaskLoader.onLoadInBackground(AsyncTaskLoader.java:312)
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:69)
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:57)
08-30 09:37:10.454 E/AndroidRuntime(23848): at android.os.AsyncTask$2.call(AsyncTask.java:292)
08-30 09:37:10.454 E/AndroidRuntime(23848): at java.util.concurrent.FutureTask.run(FutureTask.java:237)
08-30 09:37:10.454 E/AndroidRuntime(23848): ... 3 more
08-30 09:37:10.688 I/Process (23848): Sending signal. PID: 23848 SIG: 9
08-30 09:37:10.757 I/ActivityManager( 732): Process com.android.settings (pid 23848) has died
Has someone experienced this kind of problem before? I can only think of factory resetting the phone as a possible solution, so any ideas are appreciated.

General Lenovo P11 Pro "User Experience Program"

Hi everyone,
with the latest OTA update, Lenovo forces the user (via pop-up message and specific notification OTAUserExpr_noti_channel, at every startup) to join the user experience program.
I have solved the problem removing the app involved (com.lenovo.ue.device), using ADB.exe.
From Adb command prompt:
ADB shell
pm uninstall -k --user 0 com.lenovo.ue.device
Restart tablet at end.
Now the notification is gone e the system works well without this useless (confirmed by other users) bloatware .
You got an update from Lenovo?!? What a rare treat!
mardon85 said:
You got an update from Lenovo?!? What a rare treat!
Click to expand...
Click to collapse
it was incredible for me too
OP, thanks for this bit of info. However, after running your command line and seeing the word "success" and rebooting my P11, the stupid thing still shows up. lol
I tried rebooting the tablet and running your commands again and it tells me:
J606F:/ $ pm uninstall -k --user 0 com.lenovo.ue.device​Failure [not installed for 0]​
I've gotten updates quite a few times for my P11. I'm not sure why everyone thinks that is shocking?
@usafle You are right I tried too and I have the same result, when I have time I'll check if I can find out another way.
@NolanBart is this method still working for you?
If it's working there must be something different, did you use that exact command or did you uninstall without -k parameter?
I've searched and haven't found anything yet concerning this either - just on this forum.
@MrCrayon and @NolanBart - either of you find anything out yet?
@MrCrayon , @usafle I have got the european version TB-J706L.
I ran the command pm uninstall -k --user 0 com.lenovo.ue.device with the TB-J706L_S620144_211227 firmware.
The app com.lenovo.ue.device was permanently removed and the popup message no longer appeared (after reboot).
I recently got the version TB-J706L-S630223-220313 but all works fine as before.
Without root privileges you have to use --user 0, because it is the default and main user of the phone.
-k parameter means that the cache/data of the system application will be preserved, you can't run this command without -k if you haven't root access.
Failure [not installed for 0]​It's TRUE, because you have just removed the app for default user.
Try to disable, on system settings -> info, the "Lenovo user experience Program" menu item: maybe it's still enabled.
usafle said:
@MrCrayon and @NolanBart - either of you find anything out yet?
Click to expand...
Click to collapse
No nothing, I also searched in the ROM for OTAUserExpr and I can't find it anywhere.
NolanBart said:
@MrCrayon , @usafle I have got the european version TB-J706L.
I ran the command pm uninstall -k --user 0 com.lenovo.ue.device with the TB-J706L_S620144_211227 firmware.
The app com.lenovo.ue.device was permanently removed and the popup message no longer appeared (after reboot).
I recently got the version TB-J706L-S630223-220313 but all works fine as before.
Click to expand...
Click to collapse
Thank you for your feedback, I think the difference is TB-J706F vs TB-J706L, yours has LTE module right?
NolanBart said:
Without root privileges you have to use --user 0, because it is the default and main user of the phone.
-k parameter means that the cache/data of the system application will be preserved, you can't run this command without -k if you haven't root access.
Click to expand...
Click to collapse
I tried, in different tablets, both with -k and without and the app was uninstalled in both cases but it still did not solve.
I also tried to enable User experience and then disable it, click on the notification and then NO, removed all bloatware and disabled these ones:
Code:
pm disable-user --user 0 com.tblenovo.center
pm disable-user --user 0 com.tblenovo.userguide
pm disable-user --user 0 com.google.android.apps.mediahome.launcher
pm disable-user --user 0 com.lenovo.lcui.translator
MrCrayon said:
Thank you for your feedback, I think the difference is TB-J706F vs TB-J706L, yours has LTE module right?
Click to expand...
Click to collapse
Yes, is the LTE version, region Europe.
The process running in memory and associated to that popup it's just com.lenovo.ue.device (ue=User Experience).
Indeed, if I try to enable the "User Experience program" from settings, it's crash, nothing happens.
Lenovo really wants that User Exp program to stick around, don't they? lol
NolanBart said:
It's TRUE, because you have just removed the app for default user.
Try to disable, on system settings -> info, the "Lenovo user experience Program" menu item: maybe it's still enabled.
Click to expand...
Click to collapse
So if I long press on the notification it informs me that "Notifications for this can not be modified"
If I navigate to Settings and then System, I see nothing related to the "Lenovo user Experience Program" in there. The only APP I have is something called Lenovo_PAI but again, nothing related to the "User Experience Program"
usafle said:
If I navigate to Settings and then System, I see nothing related to the "Lenovo user Experience Program" in there. The only APP I have is something called Lenovo_PAI but again, nothing related to the "User Experience Program"
Click to expand...
Click to collapse
It's under Settings -> System -> About Tablet
NolanBart said:
The process running in memory and associated to that popup it's just com.lenovo.ue.device (ue=User Experience).
Indeed, if I try to enable the "User Experience program" from settings, it's crash, nothing happens.
Click to expand...
Click to collapse
If I try to enable it from settings a white popup shows up, I think it should show the agreement text but I have connection blocked by netGuard, if I press "GOT IT" I suppose it should enable the service, and it does not crash even if it's uninstalled for that user.
You said it crashes, what process crashes and what do you see?
That's the only way the message is gone at restart for me.
I'll have to check if something tries to access internet when that's enabled, also check with adb if I can see something in the logs.
MrCrayon said:
It's under Settings -> System -> About Tablet
If I try to enable it from settings a white popup shows up, I think it should show the agreement text but I have connection blocked by netGuard, if I press "GOT IT" I suppose it should enable the service, and it does not crash even if it's uninstalled for that user.
You said it crashes, what process crashes and what do you see?
That's the only way the message is gone at restart for me.
I'll have to check if something tries to access internet when that's enabled, also check with adb if I can see something in the logs.
Click to expand...
Click to collapse
It may be that the pop-up message is independent of the presence of the app com.lenovo.ue.device in yours firmware version.
If I try to enable the "User Experience Program" i get a black screen for a while and then the checkbox is disabled again.
MrCrayon said:
It's under Settings -> System -> About Tablet
Click to expand...
Click to collapse
Thanks for the clarification. It's definitely disabled. I can enable/disable it from there without any crashes or, error messages.
Hey, creating an account to say thanks for this. I really have no idea what im doing programming wise but this helped me remove the user experience on my lenovo p11 plus.
If anybody else comes across this thread via google I used this link to learn how to install and use ADB. https://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Hi,
NolanBart said:
ADB shell
pm uninstall -k --user 0 com.lenovo.ue.device
Restart tablet at end.
Now the notification is gone e the system works well without this useless (confirmed by other users) bloatware .
Click to expand...
Click to collapse
It causes a reboot after unlocking welcome screen. Then it goes to the recovery with the message "can't load Android system. You data may be corrupt. Factory data reset is proposed but I hesitate to do that as I have still access to ADB to resinstall that module. Unfortunatelly I don't have that module. Can somebody upload it?
I have LenovoTB-J606F
My firmware version was S320243_221118_ROW
[EDIT] com.lenovo.ue.device can be downloaded from there https://4pda.to/forum/index.php?showtopic=1014576&st=7060, but I can't restore it. So I selected Reset Factory (it wipes data) and reconfigured the tablet.
I had a similar issue on my Lenovo Yoga Tab 13. Disabling com.lenovo.ue.device caused a shutdown just after system start.
I've investigated this issue a little and noticed this happens only after connecting to WiFi. When I quickly disabled WLAN system was working correctly but just after enabling WiFi again it shutdowns.
I've also checked logcat and it turns out this issue is caused by com.lenovo.tbengine package because it's crashing without com.lenovo.ue.device so much entire OS reboots. After disabling it as well and rebooting OS it doesn't shutdown by itself.
So the solution is to disable both com.lenovo.ue.device and com.lenovo.tbengine or neither of them.
This is the interesting logcat part:
Code:
02-27 21:35:36.802 5440 5440 D UDSEngine14: [UNKNOWN][SystemBroadcastReceiver.onReceive:48][2]Network wifi connected : true , Mobile Connected : false
02-27 21:35:36.803 1849 3496 D CompatibilityInfo: mCompatibilityFlags - 4
02-27 21:35:36.804 1849 3496 D CompatibilityInfo: applicationDensity - 240
02-27 21:35:36.804 1849 3496 D CompatibilityInfo: applicationScale - 1.0
02-27 21:35:36.804 5440 5480 E ActivityThread: Failed to find provider info for com.lenovo.ue.device.provider
02-27 21:35:36.805 5440 5480 E AndroidRuntime: FATAL EXCEPTION: Thread-2
02-27 21:35:36.805 5440 5480 E AndroidRuntime: Process: com.lenovo.tbengine, PID: 5440
02-27 21:35:36.805 5440 5480 E AndroidRuntime: java.lang.IllegalArgumentException: Unknown URL content://com.lenovo.ue.device.provider/app
02-27 21:35:36.805 5440 5480 E AndroidRuntime: at android.content.ContentResolver.insert(ContentResolver.java:2192)
02-27 21:35:36.805 5440 5480 E AndroidRuntime: at android.content.ContentResolver.insert(ContentResolver.java:2157)
02-27 21:35:36.805 5440 5480 E AndroidRuntime: at com.lenovo.tbengine.core.util.PromptUtils.lambda$sendData$0$PromptUtils(PromptUtils.java:93)
02-27 21:35:36.805 5440 5480 E AndroidRuntime: at com.lenovo.tbengine.core.util.-$$Lambda$PromptUtils$Ciq_uYvVjyh8lbPyrVBSnqRFTKM.run(Unknown Source:6)
02-27 21:35:36.805 5440 5480 E AndroidRuntime: at java.lang.Thread.run(Thread.java:920)
02-27 21:35:36.805 3713 3713 D GmsGcmRegister: onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }
02-27 21:35:36.805 5440 5440 D UDSEngine14: [V1.1.20.230201/999000002][OtaPolicy.isABUpdate:206][2]is ab update true
02-27 21:35:36.805 5440 5440 D UDSEngine14: [V1.1.20.230201/999000002][MainService.initWorkFlowTable:182][2]initWorkFlowTable isABUpdate true
02-27 21:35:36.805 1094 1094 D SurfaceFlinger: isVirtual : 0
02-27 21:35:36.805 1094 1094 D CompositionEngine: Output::prepare isVirtual : 0
02-27 21:35:36.805 1094 1094 D CompositionEngine: setColorTransform, return
02-27 21:35:36.808 1849 2147 W RescueParty: get module info error:
02-27 21:35:36.808 1849 2147 W RescueParty: android.content.pm.PackageManager$NameNotFoundException: No module info for package: com.lenovo.tbengine
02-27 21:35:36.808 1849 2147 W RescueParty: at android.app.ApplicationPackageManager.getModuleInfo(ApplicationPackageManager.java:1080)
02-27 21:35:36.808 1849 2147 W RescueParty: at com.android.server.RescueParty.needNoteCrash(RescueParty.java:783)
02-27 21:35:36.808 1849 2147 W RescueParty: at com.android.server.am.AppErrors.crashApplicationInner(AppErrors.java:582)
02-27 21:35:36.808 1849 2147 W RescueParty: at com.android.server.am.AppErrors.crashApplication(AppErrors.java:562)
02-27 21:35:36.808 1849 2147 W RescueParty: at com.android.server.am.ActivityManagerService.handleApplicationCrashInner(ActivityManagerService.java:8025)
02-27 21:35:36.808 1849 2147 W RescueParty: at com.android.server.am.ActivityManagerService.handleApplicationCrash(ActivityManagerService.java:7914)
02-27 21:35:36.808 1849 2147 W RescueParty: at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:2030)
02-27 21:35:36.808 1849 2147 W RescueParty: at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2521)
02-27 21:35:36.808 1849 2147 W RescueParty: at android.os.Binder.execTransactInternal(Binder.java:1179)
02-27 21:35:36.808 1849 2147 W RescueParty: at android.os.Binder.execTransact(Binder.java:1143)
02-27 21:35:36.808 1849 2147 D RescuePartyRecorder: notePersistentAppCrash(com.lenovo.tbengine)
02-27 21:35:36.808 5440 5440 D UDSEngine14: [V1.1.20.230201/999000002][SwfABInstalling.<init>:345][2]mPowerSaveMode false
02-27 21:35:36.809 1849 2147 W ActivityManager: Process com.lenovo.tbengine has crashed too many times, killing! Reason: crashed quickly
02-27 21:35:36.810 3642 3681 D GmsServicesProvider: query caller=com.google.android.ims name=gms:phenotype:phenotype_flag:debug_bypass_phenotype value=null
02-27 21:35:36.812 5440 5440 D UDSEngine14: [V1.1.20.230201/999000002][AvatarPlugin.<init>:50][2]versionCode 8060162
02-27 21:35:36.812 5440 5440 D UDSEngine14: [V1.1.20.230201/999000002][PromptUtils.canCollectData:160][2]Lenovo YT-K606F
02-27 21:35:36.812 5440 5440 D UDSEngine14: [V1.1.20.230201/999000002][AvatarPlugin.<init>:70][2]persist.sys.backgrounddata=false
02-27 21:35:36.813 5440 5440 D UDSEngine14: [V1.1.20.230201/999000002][AvatarPlugin.<init>:77][2]persist.backgrounddata.enable=false
02-27 21:35:36.813 5440 5440 W UDSEngine14: [V1.1.20.230201/999000002][MainService.registerPlugins:235][2]AvatarPlugin report enabled!
02-27 21:35:36.813 5323 5323 I CarrierServices: [2] CarrierServicesReleaseApp.initialize:163 Initializing CarrierServices application without voice library.
02-27 21:35:36.814 1849 2147 D jxs0707 : ActivityManagerService handleApplicationCrash ProcessRecord r: ProcessRecord{7425b7a 5440:com.lenovo.tbengine/u0a85}
02-27 21:35:36.814 1849 2147 D jxs0707 : ActivityManagerService handleApplicationCrash ProcessRecord : com.lenovo.tbengine
02-27 21:35:36.814 5440 5480 I Process : Sending signal. PID: 5440 SIG: 9
02-27 21:35:36.817 3642 3681 D GmsServicesProvider: query caller=com.google.android.ims name=gms:phenotype:phenotype_flag:debug_bypass_phenotype value=null
02-27 21:35:36.820 3642 3690 D GmsServicesProvider: query caller=com.google.android.ims name=gms:phenotype:phenotype_flag:debug_bypass_phenotype value=null
02-27 21:35:36.822 1849 2147 I ActivityManager: Process com.lenovo.tbengine (pid 5440) has died: pers PER
02-27 21:35:36.822 1094 1094 D SurfaceFlinger: isVirtual : 0
02-27 21:35:36.822 1094 1094 D CompositionEngine: Output::prepare isVirtual : 0
02-27 21:35:36.822 891 891 I Zygote : Process 5440 exited due to signal 9 (Killed)
02-27 21:35:36.822 1094 1094 D CompositionEngine: setColorTransform, return
02-27 21:35:36.823 3642 3681 D GmsServicesProvider: query caller=com.google.android.ims name=carrier_services_rcs_flags_enable_rcs value=null
02-27 21:35:36.823 1849 2147 E ActivityManager: Service ServiceRecord{e8e1d80 u0 com.lenovo.tbengine/.core.services.MainService} in process ProcessRecord{7425b7a 5440:com.lenovo.tbengine/u0a85} not same as in map: ServiceRecord{cc947ef u0 com.lenovo.tbengine/.core.services.MainService}
02-27 21:35:36.823 1849 2147 E ActivityManager: Service ServiceRecord{dd6de28 u0 com.lenovo.tbengine/.core.services.MainService} in process ProcessRecord{7425b7a 5440:com.lenovo.tbengine/u0a85} not same as in map: ServiceRecord{cc947ef u0 com.lenovo.tbengine/.core.services.MainService}
02-27 21:35:36.824 1849 2147 W ActivityManager: Not scheduling restart of crashed service com.lenovo.tbengine/.core.services.MainService - system is shutting down

Categories

Resources