Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

LG L7 freezes and then reboots #694

Closed
smiledexter opened this issue Sep 19, 2013 · 21 comments
Closed

LG L7 freezes and then reboots #694

smiledexter opened this issue Sep 19, 2013 · 21 comments
Labels

Comments

@smiledexter
Copy link
Contributor

My phone LG L7, Android original 4.0.3

Using new versions Xprivacy sometimes reboots the phone.

This Xposed or Xprivacy problem? attach ANR, Xposed and Xprivacy logs:

CATLOG: https://docs.google.com/file/d/0B9sv6okJiG6ZYWFOZGxVTDdmbXc/edit?usp=sharing

Xposed: https://docs.google.com/file/d/0B9sv6okJiG6ZTDhWR0JwdWpTd0k/edit?usp=sharing

ANR: https://docs.google.com/file/d/0B9sv6okJiG6ZbXBza25tb20wa1E/edit?usp=sharing

About ANR: https://docs.google.com/file/d/0B9sv6okJiG6Zdk1yQjYyNkdDMHc/edit?usp=sharing

I am waiting for a decision, is around all

@M66B
Copy link
Owner

M66B commented Sep 19, 2013

Isn't this the same as investigated in detail in #627 ?

My conclusion: #627 (comment)

@M66B
Copy link
Owner

M66B commented Sep 19, 2013

No errors in Xposed log.

@M66B
Copy link
Owner

M66B commented Sep 19, 2013

ANR is also an indication of low resources.

@smiledexter
Copy link
Contributor Author

++Isn't this the same as investigated in detail in #627 ?++
Yes

@smiledexter
Copy link
Contributor Author

This is what give flight to find the mistake? That can not be that there is nothing

so quickly looked INFO?

@M66B
Copy link
Owner

M66B commented Sep 19, 2013

The logcat has no mention of XPrivacy at all.

My conclusion stays the same: this is not an XPrivacy problem.
My best guess your device has not enough resources to run everything including XPrivacy.

@M66B M66B closed this as completed Sep 19, 2013
@M66B
Copy link
Owner

M66B commented Sep 19, 2013

Also, please note @28Black solved this problem by installing another ROM.
So try that.

@rovo89
Copy link

rovo89 commented Sep 19, 2013

Might be a ROM issue as it works fine for so many other phones.

But maybe something to look at in the ANR:

"main" prio=5 tid=1 MONITOR
  at com.android.server.am.ActivityManagerService.unregisterReceiver(ActivityManagerService.java:~12461)
- waiting to lock <0x417a3598> (a com.android.server.am.ActivityManagerService) held by tid=10 (android.server.ServerThread) <-------- several other threads are trying to lock this object as well

"android.server.ServerThread" prio=5 tid=10 MONITOR
  at com.android.server.am.ActivityManagerService.updateOomAdjLocked(ActivityManagerService.java:~14789)
  - waiting to lock <0x417a8910> (a com.android.internal.os.BatteryStatsImpl) held by tid=75 (Binder Thread #13)

"Binder Thread #13" prio=5 tid=75 MONITOR
  at com.android.server.am.ActivityManagerService.getContentProviderImpl(ActivityManagerService.java:~6057)
  - waiting to lock <0x417a3598> (a com.android.server.am.ActivityManagerService) held by tid=10 (android.server.ServerThread)

Seems like a deadlock between ServerThread and Binder Thread #13.
And in the Binder Thread, the stacktrace is:

  at com.android.server.am.ActivityManagerService.getContentProvider(ActivityManagerService.java:6290)
  at android.app.ActivityThread.acquireProvider(ActivityThread.java:4025)
  at android.app.ContextImpl$ApplicationContentResolver.acquireProvider(ContextImpl.java:1725)
  at android.content.ContentResolver.acquireProvider(ContentResolver.java:939)
  at android.content.ContentResolver.query(ContentResolver.java:315)
  at biz.bokhorst.xprivacy.PrivacyManager.getRestricted(PrivacyManager.java:292)
  at biz.bokhorst.xprivacy.XHook.getRestricted(XHook.java:77)
  at biz.bokhorst.xprivacy.XTelephonyManager.isRestricted(XTelephonyManager.java:215)
  at biz.bokhorst.xprivacy.XTelephonyManager.after(XTelephonyManager.java:164)
  at biz.bokhorst.xprivacy.XPrivacy$1.afterHookedMethod(XPrivacy.java:207)
  at de.robv.android.xposed.XposedBridge.handleHookedMethod(XposedBridge.java:483)
  at android.telephony.TelephonyManager.getNetworkType(Native Method)
  at android.telephony.SignalStrength.getGsmLevel(SignalStrength.java:531)
  at android.telephony.SignalStrength.getLevel(SignalStrength.java:367)
  at com.android.internal.os.BatteryStatsImpl.notePhoneSignalStrengthLocked(BatteryStatsImpl.java:1936)
  at com.android.server.am.BatteryStatsService.notePhoneSignalStrength(BatteryStatsService.java:212)
  at com.android.server.TelephonyRegistry.broadcastSignalStrengthChanged(TelephonyRegistry.java:564)
  at com.android.server.TelephonyRegistry.notifySignalStrength(TelephonyRegistry.java:325)
  at com.android.internal.telephony.ITelephonyRegistry$Stub.onTransact(ITelephonyRegistry.java:95)
  at android.os.Binder.execTransact(Binder.java:341)
  at dalvik.system.NativeStart.run(Native Method)

I don't have the time to analyze this further, so I can't say whose fault this is. Maybe the ROM is doing something wrong here, or maybe it's not allowed to query for content providers with certain locks held.

@M66B
Copy link
Owner

M66B commented Sep 20, 2013

@smiledexter
Copy link
Contributor Author

Was testing versions, and I found!

the 1.8.5 version works fine with the 1.8.7 version of the phone crashes and reboots.

The problem will be the following options:

Version 1.8.7 BETA!
Enable Android usage date 60 seconds after boot
Filter usage date for the last 24 hours
Option to set network / SIM operator name

Version 1.8.6 BETA!
Always lock fallback loading restriction
Limit help icon size

1.8.6 version is not seen where to download. Some of these parameter probably does not work correctly and the phone crashes. Please review, I am ready to test.
If you need to log, write.

@smiledexter
Copy link
Contributor Author

Phone only break when you perform any action.

@M66B M66B reopened this Oct 1, 2013
@smiledexter
Copy link
Contributor Author

Here is fresh 2 crashes and restart in a row with 1.8.7
Attached logcat and ANR trace files

As I said with 1.8.5 everything is ok.

https://drive.google.com/folderview?id=0B9sv6okJiG6ZMnNIMURaeTZpMzg&usp=sharing

@smiledexter
Copy link
Contributor Author

Posted by uncut logcat
1 restart: 16:01
2 restart: 16:03

@M66B
Copy link
Owner

M66B commented Nov 7, 2013

Could you please try if this version fixed the problem: http://d-h.st/Ts8

@smiledexter
Copy link
Contributor Author

ok, to test

@smiledexter
Copy link
Contributor Author

Thank you for caring

@M66B
Copy link
Owner

M66B commented Nov 7, 2013

You're welcome.
Try this version, which also seems to fix the Note 3 uninstall freeze: http://d-h.st/QGy

@smiledexter
Copy link
Contributor Author

ok

@M66B
Copy link
Owner

M66B commented Nov 8, 2013

Did you already test?
The next beta release waits on feedback on this issue.

@smiledexter
Copy link
Contributor Author

Yes. Testing from yesterday evening. So far, works fine, I think the problem repaired. Works fine.

1 similar comment
@smiledexter
Copy link
Contributor Author

Yes. Testing from yesterday evening. So far, works fine, I think the problem repaired. Works fine.

@M66B M66B closed this as completed Nov 9, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants