I'm on my way on modifying some custom ROM (DUI)'s System UI custom features that currently are yielding some minor errors on my devices.
So, I build the ROM from source in eng variant, I can attach to the systemui process and start debugging. It works pretty well, but only for a little while. After this, the device's screen turns black and SystemUI restarts; the debugging session is lost.
On logcat there's this message of interest:
Code:
02-14 11:53:10.005: W/BroadcastQueue(5796): Timeout of broadcast BroadcastRecord{9b4c2d1 u-1 android.intent.action.TIME_TICK} - [email protected], started 10001ms ago
02-14 11:53:10.006: W/BroadcastQueue(5796): Receiver during timeout: BroadcastFilter{bf8a6f7 u0 ReceiverList{15542f6 6006 com.android.systemui/10035/u0 remote:f58e391}}
02-14 11:53:10.005: W/ActivityManager(5817): type=1400 audit(0.0:17499): avc: denied { ptrace } for scontext=u:r:system_server:s0 tcontext=u:r:init:s0 tclass=process permissive=0
(...)
02-14 11:53:10.090: I/Process(5796): Sending signal. PID: 6006 SIG: 3
02-14 11:53:10.090: I/art(6006): Thread[3,tid=6024,WaitingInMainSignalCatcherLoop,Thread*=0x40484e00,peer=0x12c00670,"Signal Catcher"]: reacting to signal 3
02-14 11:53:10.543: I/art(6006): Wrote stack traces to '/data/anr/traces.txt'
02-14 11:53:10.558: E/ActivityManager(5796): ANR in com.android.systemui
I'm sorry because I'm quite new in Android Framework programming, so maybe this is quite obvious. But the problem is that there's a 10 secs timeout from android.os.BinderProxy and when it expires the ANR is raised. Am I right? Is it possible to avoid/extend this timeout to debug SystemUI?
I tried in Developers Options to set SystemUI as the debugged application, with no success.
Related
When I dial a call all that happens is it places the call through verizon and not google voice any one else have this issue?, The guy at the store ran the ota before I was even handed the phone...
*Update 1 (4:13 pm): google voice seems to crash when rebooting =\
*Update 2 (4:23 pm): ADB Logcat output with grep on voice
Code:
[email protected]:~/Desktop/****/SDK/android-sdk-linux_86/tools$ cat adb.log | grep voice
W/PackageManager( 74): Unknown permission com.google.android.permission.SEND_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.permission.RECEIVE_DATA_MESSAGE in package com.google.android.apps.googlevoice
W/PackageManager( 74): Unknown permission com.google.android.apps.googlevoice.REMOTE_INTENT in package com.google.android.apps.googlevoice
D/HtcCdmaPhoneApp( 111): voice privacy setting=1
D/HtcCdmaPhoneApp( 111): voice privacy status=-1
I/ActivityManager( 74): Start proc com.android.voicedialer for broadcast com.android.voicedialer/.VoiceDialerReceiver: pid=336 uid=10042 gids={3002}
D/VoiceDialerReceiver( 336): onReceive Intent { action=android.intent.action.BOOT_COMPLETED comp={com.android.voicedialer/com.android.voicedialer.VoiceDialerReceiver} }
D/RecognizerEngine( 336): deleteCachedGrammarFiles /data/data/com.android.voicedialer/files/openentries.txt
D/GooglePartnerSetup( 341): voicesearch client id: ms-android-verizon
I/ActivityManager( 74): Start proc com.google.android.apps.googlevoice for broadcast com.google.android.apps.googlevoice/.BootUpReceiver: pid=348 uid=10049 gids={3003}
E/dalvikvm( 348): Could not find method android.content.Context.getApplicationInfo, referenced from method com.google.android.apps.googlevoice.BootUpReceiver.onReceive
W/dalvikvm( 348): VFY: rejected Lcom/google/android/apps/googlevoice/BootUpReceiver;.onReceive (Landroid/content/Context;Landroid/content/Intent;)V
W/dalvikvm( 348): Verifier rejected class Lcom/google/android/apps/googlevoice/BootUpReceiver;
W/dalvikvm( 348): Class init failed in newInstance call (Lcom/google/android/apps/googlevoice/BootUpReceiver;)
E/AndroidRuntime( 348): java.lang.VerifyError: com.google.android.apps.googlevoice.BootUpReceiver
I/ActivityManager( 74): Process com.google.android.apps.googlevoice (pid 348) has died.
-Chr1831
Yes it started crashing here after the MR2
Snakehn said:
Yes it started crashing here after the MR2
Click to expand...
Click to collapse
I can confirm this on my end as well. After the first OTA update there was no issue, but MR2 screwed with it. I found I can launch the application after the initial boot crash, but haven't confirmed that it is working as it should on my phone.
I get GV FC's on startup but then again I only use it for voicemail and its working pretty good.
I got version 2.5 to work just not 3.0 hopefully the (htc) update on the 22end will address this bug
Still some issues for me. It FCs on boot. All though most functionality is there..
When I call out things are strange, contact pics don't work and the outgoing number is not the dialed number its the GV "bridge" number.
Both of the above issues do not exist on my moto droid.
I wish it was fixed.
Can someone put this on the thread for the CM11 nightly build for Galaxy S4 i9505, unofficial I believe. I don't have the post count required. ROM is very good and works fine apart from the following issue, at least so far.
HDR won't save pictures from stock 4.4 camera app. It shows as a blank square on the gallery. Turning off HDR works fine. Logcat (first time so let me know if it's wrong and I'll do another):
--------- beginning of /dev/log/main
I/dalvikvm(16916): Enabling JNI app bug workarounds for target SDK version 11...
E/Term (16916): onCreate
D/Term (16916): TermService started
I/TermService(16916): Activity called onBind()
I/Term (16916): Bound to TermService
I/TermService(16916): Activity binding to service
D/dalvikvm(16916): Trying to load lib /data/app-lib/jackpal.androidterm-1/libjackpal-androidterm4.so 0x418e9ae8
D/dalvikvm(16916): Added shared lib /data/app-lib/jackpal.androidterm-1/libjackpal-androidterm4.so 0x418e9ae8
I/libjackpal-androidterm(16916): JNI_OnLoad
I/Term (16916): waiting for: 16941
I/Term (16916): Subprocess exited: 129
W/IInputConnectionWrapper(16916): showStatusIcon on inactive InputConnection
E/Term (16916): onCreate
D/Term (16916): TermService started
I/TermService(16916): Activity called onBind()
I/Term (16916): Bound to TermService
I/TermService(16916): Activity binding to service
I/Term (16916): waiting for: 17246
I/Term (16916): waiting for: 17402
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
MasterAwesome said:
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
Click to expand...
Click to collapse
Hello again,
I've made logcat, here is an interesting part, I think:
I/SecurityManagerService( 671): SMS received security event: App[START/com.android.keyguard]
I/WindowState( 556): WIN DEATH: Window{26a85ad0 u0 Keyguard}
I/ActivityManager( 556): Process com.android.systemui (pid 622) has died.
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
W/ActivityManager( 556): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
D/InputMethodManagerService( 556): --- calledFromForegroundUserOrSystemProcess ? calling uid = 1000 system uid = 1000 calling userId = 0, foreground user id = 0, calling pid = 556dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
I/StatusBarManagerService( 556): binder died for pkg=com.android.keyguard
I/WindowState( 556): WIN DEATH: Window{269b48a8 u0 NavigationBar}
W/InputDispatcher( 556): Attempted to unregister already unregistered input channel '268ba8e8 StatusBar (server)'
D/dalvikvm( 3948): Try to disable coredump for pid 3948
D/dalvikvm( 3948): Process 3948 nice name: com.android.systemui
D/dalvikvm( 3948): Extra Options: not specified
Click to expand...
Click to collapse
I discovered also that when the battery level drops to 99% process starts to work properly.
I include also whole log file compressed to .zip.
Still need help!
I have the same problem, even after a factory reset.
me too having the same issue. Is it hardware failure or just android?
I found a solution in an other tread :
http://forum.xda-developers.com/android/general/review-teclast-x89-baytrail-tablet-dual-t3039961
Hi guys,
my problem is that my Nexus 5 is rebooting all the time since yesterday. My roommate had the same problem yesterday, but now its suddenly gone. My Android version is 6.0.1 and I can tell you the last few logs before the restart occures:
Code:
03-12 15:17:51.221 203-924/? D/NuPlayerDriver: reset(0xb60585e0)
03-12 15:17:51.221 203-924/? D/NuPlayerDriver: notifyListener_l(0xb60585e0), (8, 0, 0)
03-12 15:17:51.221 203-7815/? D/NuPlayerDriver: notifyResetComplete(0xb60585e0)
03-12 15:17:51.222 812-826/? I/ActivityManager: Killing 4914:android.process.acore/u0a2 (adj 15): empty #17
03-12 15:17:52.052 1908-4068/? W/ctxmgr: [AclManager]checkPermissionTypeStatus: no inject permission for { uid=10010, packageName=com.google.android.gms }. Returned permission was: PACKAGE_NOT_WHITELISTED for context name=POWER_CONNECTION, account=account#-517948760#
03-12 15:17:52.054 1908-4068/? W/ctxmgr: [AclManager]checkPermissionTypeStatus: no inject permission for { uid=10010, packageName=com.google.android.gms }. Returned permission was: PACKAGE_NOT_WHITELISTED for context name=POWER_CONNECTION, account=account#-517948760#
03-12 15:17:52.055 1908-1908/? E/ctxmgr: [PowerConnectionProducer]Could not write powerInfo=Plug state: 2 BatteryLevel: 0.77, status=Status{statusCode=unknown status code: 7503, resolution=null}
01-01 00:00:00.000 0-0/? E/Internal: device 'XXXXXXXXX' not found
I really have no idea where to start looking for the problem. I mean, the log does not tell me much about a fault or something like that and as far as I know Android does not provide crash logs on reboot.
Do you have any hints?
Ah and by the way: The only app I installed recently before the problem occured was runtastic, but removing it did not change anything.
Best regards,
Arma
Ok, it was the power button...
I would get a case that protects the power button .
Hello everyone. I've got a problem with Google Maps Navigation. I think it's an app bug because its' very strange.
GPS Data, Here Maps and Google Maps can fix position.
But when I switch to Navigation mode in Google Map, the app loose satellites and can not fix.
As soon as I exit Navigation mode to come back to Maps mode, the fixed satellites increase.
Please does someone have the same bug?
I've cleaned every caches, restored ROM backup and now I'm on a clean installation of CM 12.1 (2016-02-03) and the position bug is still there.
I think I will go crazy. I've installed Waze and it works! Reception is not very good but he can guide me. Only Google Navigation does not work anymore. :crying:
So, that seems to be a hardware problem. And Google Navigation is the app that has most trouble with it ...
hey, i also got the same problem on cm13, but can't believe its a hardware-bug.
did you already find a solution/workaround?
for me i got good signals in AutoMate (there is a map integrated) and GPS-Test, but i always get a on-off signal in GoogleMaps and(!) Waze.
Did you already tried stock-rom? i wonder if it is the same there, but im afraid of the difficult flash process to go back to stock.
Which radio/baseband do you have?
Typhoon_Master said:
hey, i also got the same problem on cm13, but can't believe its a hardware-bug.
did you already find a solution/workaround?
for me i got good signals in AutoMate (there is a map integrated) and GPS-Test, but i always get a on-off signal in GoogleMaps and(!) Waze.
Did you already tried stock-rom? i wonder if it is the same there, but im afraid of the difficult flash process to go back to stock.
Which radio/baseband do you have?
Click to expand...
Click to collapse
My baseband : XXLS8
Yes I flashed Stock 4.1 Rom yesterday and I have seen the same behavior: poor GPS fix.
Now I come back to CM12.1 but it's getting worse! My phone can not find his position, even with applications that worked before.
For me it's a Google Services or a hardware problem.
Note: I've got a Samsung Tab A with Android 6.0 and Google Services (9.2.56) and GPS works good ...
So I made the ultimate test. I restored a backup I've made early May 2016. At android start I activate Plane mode in order to prevent Google play services to auto update. I checked the version, it's 8.7.03, excellent.
I start GPS Data to test position and the bug is still there. My phone can't fix 0 on 4~5 satellites.
So my GPS is dying
For the last test I made a dangerous action. I rewrite nv_data files from a EFS backup i've made two year ago. (It was Epic, I lost my IMEI, then I get it back, Phew!)
Unfortunately it didn't fix my poor GPS reception.
Here's what I have:
- GPS Data : 5-6 satellites fixed and no drop
- Waze : 3-4 satellites fixed and many drops
- Google Maps : 3-4 satellites fixed and many drops
- Google Navigation : 0 satellite fixed
Whereas few months ago I could get up to 11 satellites!
I tried everything, I have no idea ...
Some news. I've seen that sometimes phone thinks that Position is disabled !?!
In GPS Data app sometimes it display "OFF" instead of "Wait" in the top bar. But the compass screen display 0/8 satellites fixed!
So he sees satellites but thinks GPS is disabled.
I have to disable and enable Position in order to hook satellites.
Maybe this is why I get 0 satellites in Google Navigation. Is it a RIL bug ???
I looked at log files in order to find error. There are many denials but there are these related to GPS:
modem.log
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): requestOEMHookRaw
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): Logging Oem Func ID : 14
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): Logging Oem Sub Func ID : 55
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): requestOemGps: gps_status 0 sub_id 0x37 len 1
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): requestFrequencyAiding: state 1
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): GR err: 0x8000
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): GPS_onRequestComplete: sub_id 55 error 13 param 0xb657ccf4 plen 1
07-26 13:42:35.227 E/use-Rlog/RLOG-RIL(20022): RIL_onRequestComplete: tok(0xb8790120)
logcal.log
07-26 12:08:21.046 D/WifiService( 4559): acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
07-26 12:08:21.163 I/GoogleLocationS(16130): type=1400 audit(0.0:1886): avc: denied { setattr } for name="nlp_devices" dev="mmcblk0p10" ino=124272 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:unlabeled:s0 tclass=file permissive=1
07-26 12:08:21.183 D/WifiService( 4559): releaseWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
07-26 13:35:30.707 I/WAZE [ ConnEventReceiver ](28264): Received event: android.net.conn.CONNECTIVITY_CHANGE. Connectivity: true. Type: WIFI ( 1 ). State: CONNECTED. Connected: true
07-26 13:35:30.707 I/WAZE (28264): getConfig - callback
07-26 13:35:30.707 D/WAZE (28264): Got ShareConfig values: FB: true
07-26 13:35:30.720 D/WAZE (28264): onStatusChanged
07-26 13:35:30.734 D/WAZE (28264): getFacebookSettings - event
07-26 13:35:30.770 E/NowAuthenticator(28264): Token recevied
07-26 13:35:30.788 E/GpsLocationProvider( 4559): native_start failed in startNavigating()
07-26 13:35:30.878 D/WAZE (28264): SpeedometerView: Not shown. (speed == -1 && !mSpeedometerShownOnce=false ) || !mSpeedometerEnabled=true
event.log
07-26 11:01:37.074 I/auditd (16130): type=1400 audit(0.0:1761): avc: denied { getattr } for comm="GoogleLocationS" path="/data/data/com.google.android.gms/files/nlp_clts" dev="mmcblk0p10" ino=124822 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:unlabeled:s0 tclass=file permissive=1
07-26 11:01:37.078 I/auditd (16130): type=1400 audit(0.0:1762): avc: denied { setattr } for comm="GoogleLocationS" name="nlp_clts" dev="mmcblk0p10" ino=124822 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:unlabeled:s0 tclass=file permissive=1
07-26 11:01:37.081 I/auditd (16130): type=1400 audit(0.0:1763): avc: denied { write } for comm="GoogleLocationS" name="nlp_clts" dev="mmcblk0p10" ino=124822 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:unlabeled:s0 tclass=file permissive=1
07-26 11:01:37.081 I/auditd (16130): type=1400 audit(0.0:1764): avc: denied { open } for comm="GoogleLocationS" path="/data/data/com.google.android.gms/files/nlp_clts" dev="mmcblk0p10" ino=124822 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:unlabeled:s0 tclass=file permissive=1
07-26 12:08:21.163 I/auditd (16130): type=1400 audit(0.0:1886): avc: denied { setattr } for comm="GoogleLocationS" name="nlp_devices" dev="mmcblk0p10" ino=124272 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:unlabeled:s0 tclass=file permissive=1
07-26 13:36:23.505 I/auditd (32613): type=1400 audit(0.0:1993): avc: denied { execute } for comm="rtcross.gpstest" path="/data/data/com.google.android.gms/app_chimera/m/00000006/arm/DynamiteModulesA_GmsCore_prodlmp_hdpi_release.odex" dev="mmcblk0p10" ino=123381 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:unlabeled:s0 tclass=file permissive=1
Click to expand...
Click to collapse
Some news:
- First I found why sometimes all apps can't fix any satellites. The problem is the app I use to test gps! I've installed GPS Data on another phone (Wiko Cink Five) in order to compare gps signal strength. And then position has been broken! So do not use GPS Data app. I think it's a A-GPS database update bug. I've installed GPS Test which works much better.
- As I noted that I have better reception in GPS test app and not in Navigation apps, I tried an app that force GPS activation. I found GPS Connected. I launch it at the same time I start navigation. It's better. Now Google Navigation can see satellites. but signal strength is still poor and can not guide me because of GPS drop and bad accuracy.
I can't believe it! I've resolved my GPS problem. It was a hardware problem. My antenna started poorly receive the satellite signal, for an unknown reason.
I found by chance a discussion in a French forum about enhance antenna signal helped by an aluminum sheet. I've have done the trick and it worked!
Now my S2 can fix satellites during navigation. It works nearly good as before. I have no more signal drop and Google Navigation and Waze can guide me.
I change this discussion to Resolved.
Hello there! Wow, 6 months passed.
I come back to tell you that my GPS still working good. This aluminum trick saved my phone.