Android keep killing Tasker, please help - Android Q&A, Help & Troubleshooting

My tasker app keeps getting killed after a while. Keeps closing on it's own. Can't figure it out what causing this. Tasker is running in foreground (Prefs / Monitor / Run In Foreground).
System is Cyanogenmod 11, Lenovo k910, Android 4.4. Any help please?
Here's excerpt from the log with the part when tasker get killed. Maybe this will help with identifying the problem.
Code:
com.google.android.location.fused.LOCATION_REQUESTS
I/Fitness ( 1918): WearableSyncHostService elapsedNanos: 8229
W/bt-btif ( 3206): bta_dm_pm_btm_status stopping timer if activesince sniff mode is enabled
I/ActivityManager( 985): Force stopping net.dinglisch.android.taskerm appid=10033 user=0: pkg changed
I/ActivityManager( 985): Killing 9354:net.dinglisch.android.taskerm/u0a33 (adj 2): stop net.dinglisch.android.taskerm
W/ActivityManager( 985): Scheduling restart of crashed service net.dinglisch.android.taskerm/.MonitorService in 1000ms
I/ActivityManager( 985): Force stopping service ServiceRecord{435bb5e8 u0 net.dinglisch.android.taskerm/.MonitorService}
W/Launcher.Model( 8920): Nobody to tell about the new app. Launcher is probably loading.
W/Launcher( 8920): setApplicationContext called twice! [email protected] [email protected]
I/InputReader( 985): Reconfiguring input devices. changes=0x00000010
I/ActivityManager( 985): Force stopping net.dinglisch.android.taskerm appid=10033 user=0: from pid 28752
I/cm.log.servpro( 5146): [AutoStart]/ AutoBgRepair : net.dinglisch.android.taskerm#net.dinglisch.android.taskerm.ReceiverStaticInternal#action:TIME_SET
D/PackageBroadcastService(28288): Received broadcast action=android.intent.action.PACKAGE_CHANGED and uri=net.dinglisch.android.taskerm
I/PackageManager( 985): Action: "android.intent.action.SENDTO"
I/PackageManager( 985): Category: "android.intent.category.DEFAULT"
I/PackageManager( 985): Scheme: "sms"
I/UpdateIcingCorporaServi( 2145): Updating corpora: APPS=net.dinglisch.android.taskerm, CONTACTS=MAYBE

Related

not using google voice?

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.

[Sorta Tutorial] Netflix Stupid Simple Install Explanation-No tutorial needed

The latest version of the Netflix android app (1.2.1) seems to work fine on any 2.3 vibrant roms out of the box, no mods needed!
The previous tutorial is now obsolete, all you need to do is install any 2.3 rom and Netflix should work directly from the market, or you can download it here: http://bit.ly/mA0ar0. Enjoy. Btw, from my personal experience, I have yet to find a 2.2 rom where Netflix actually works, but this shouldn't be a problem if you install a ginger-rom or wait for the official sammy 2.3 update (if it ever happens lmao).
Reserved for OP
And another update uninstalled flash all together and it still works fine.. also i don't think it was a data toggle that helped but more locking the device and really unlocking but i think that's just because I'm running miui! And thanks for the props!!! much appreciated...
Sent from my HTC Vision using XDA Premium App
n1gh7mar3 said:
And another update uninstalled flash all together and it still works fine.. also i don't think it was a data toggle that helped but more locking the device and really unlocking but i think that's just because I'm running miui! And thanks for the props!!! much appreciated...
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
By unlocking the device you mean, actually pressing the lock button on the side of the phone and unlocking it? I know, stupid questions, but I wasn't sure lol. And no problem on the credit or the tutorial, it was the least I could for the guy who discovered how to get netflix running on the Vib!
works!
I did what the tutorial said on my vibrant running simply honey 3.3 update 1. at first i got all the weird color lines on my phone then i toggled data and air plane mode off and on and it worked...i subscribed to netflix, only 7.99$ not too bad. super clear video, im loving it..
gramlights4 said:
I did what the tutorial said on my vibrant running simply honey 3.3 update 1. at first i got all the weird color lines on my phone then i toggled data and air plane mode off and on and it worked...i subscribed to netflix, only 7.99$ not too bad. super clear video, im loving it..
Click to expand...
Click to collapse
awesome good to know.
Build.prop: This isn't the galaxy s your looking for
Netflix: oh okay.
Edit: got it installed, and it isn't telling me wrong device. But when I log in it flashes white the exits out.. updating flash to see if that helps.
Tynen said:
Build.prop: This isn't the galaxy s your looking for
Netflix: oh okay.
Click to expand...
Click to collapse
very nice reference my friend, very nice indeed lmao.
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Tynen said:
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Click to expand...
Click to collapse
Getting the same thing, right when I hit login, it sits and spins for a bit, then dumps me out to home.
LOGCAT from when I hit login, til it dumped me to home
Code:
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Dn(0=>1)
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Up(1=>0)
D/navcache( 6988): cursorInputFieldAction : Focused node is not an inputfield
E/MAXKTK ( 6988): socket443
D/dalvikvm( 6988): GC_FOR_MALLOC freed 9402 objects / 610496 bytes in 44ms
E/MAXKTK ( 6988): socket443
W/PowerManagerService( 3469): Timer 0x3->0x3|0x3
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /data/data/com.netflix.mediaclient/lib/libnetflix_devicex.so: Cannot load library: link_image[1995]: failed to link libnetflix_device1.so
E/NRDdevice2( 6988):
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /system/lib/libnetflix_devicex.so: Cannot load library: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createBufferManager: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createPlaybackDevice: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
D/Zygote ( 2719): Process 6988 terminated by signal (11)
I/ActivityManager( 3469): Process com.netflix.mediaclient (pid 6988) has died.
I/WindowManager( 3469): WIN DEATH: Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
I/UsageStats( 3469): Unexpected resume of com.ebproductions.android.launcher while already resumed in com.netflix.mediaclient
V/RenderScript_jni( 4193): surfaceCreated
V/RenderScript_jni( 4193): surfaceChanged
W/InputManagerService( 3469): Got RemoteException sending setActive(false) notification to pid 6988 uid 10207
W/Resources( 3469): Converting to boolean: TypedValue{t=0x3/d=0x1574 "res/anim/accelerate_decelerate_interpolator.xml" a=2 r=0x10a0004}
W/PowerManagerService( 3469): Timer 0x3->0x3|0x0
Tynen said:
It's not complaining about the device type but once I log in it dumps out of the program. Any ideas?
Click to expand...
Click to collapse
I get the same thing with the Bionix-v 1.3.2.
I sure that there will be some work around soon. I am so happy that this app was finally released.
d_bot said:
Getting the same thing, right when I hit login, it sits and spins for a bit, then dumps me out to home.
LOGCAT from when I hit login, til it dumped me to home
Code:
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Dn(0=>1)
V/WindowManager( 3469): Dsptch > Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
V/InputDevice( 3469): ID[0]=0(0) Up(1=>0)
D/navcache( 6988): cursorInputFieldAction : Focused node is not an inputfield
E/MAXKTK ( 6988): socket443
D/dalvikvm( 6988): GC_FOR_MALLOC freed 9402 objects / 610496 bytes in 44ms
E/MAXKTK ( 6988): socket443
W/PowerManagerService( 3469): Timer 0x3->0x3|0x3
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /data/data/com.netflix.mediaclient/lib/libnetflix_devicex.so: Cannot load library: link_image[1995]: failed to link libnetflix_device1.so
E/NRDdevice2( 6988):
E/NRDdevice2( 6988): DeviceLib::init Cannot load library /system/lib/libnetflix_devicex.so: Cannot load library: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createBufferManager: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
E/NRDdevice2( 6988): DeviceLib::init Cannot Cannot load symbol createPlaybackDevice: Invalid library handle: find_library[1188]: 2719 'libnetflix_device1.so' failed to load previously
D/Zygote ( 2719): Process 6988 terminated by signal (11)
I/ActivityManager( 3469): Process com.netflix.mediaclient (pid 6988) has died.
I/WindowManager( 3469): WIN DEATH: Window{487610f0 com.netflix.mediaclient/com.netflix.mediaclient.UIWebViewActivity paused=false}
I/UsageStats( 3469): Unexpected resume of com.ebproductions.android.launcher while already resumed in com.netflix.mediaclient
V/RenderScript_jni( 4193): surfaceCreated
V/RenderScript_jni( 4193): surfaceChanged
W/InputManagerService( 3469): Got RemoteException sending setActive(false) notification to pid 6988 uid 10207
W/Resources( 3469): Converting to boolean: TypedValue{t=0x3/d=0x1574 "res/anim/accelerate_decelerate_interpolator.xml" a=2 r=0x10a0004}
W/PowerManagerService( 3469): Timer 0x3->0x3|0x0
Click to expand...
Click to collapse
forgot to mention you need to flash a gingerbread rom for this to actually work, sorry my bad.
I'm flashing CyanogenMod now to see if it'll work there. I just finished editing the build.prop I'm rebooting after Dalvik cache wipe.. takes a while
Edit:
bobofosho123 said:
forgot to mention you need to flash a gingerbread rom for this to actually work, sorry my bad.
Click to expand...
Click to collapse
Figured as much.
I wonder what the Nexus One (running 2.2) has that Vibrant 2.2 doesn't.... hmmmmm
Didn't Google add a DRM framework into GB?? Makes sense that it wouldn't work without that framework.
Tynen said:
I'm flashing CyanogenMod now to see if it'll work there. I just finished editing the build.prop I'm rebooting after Dalvik cache wipe.. takes a while
Edit:
Figured as much.
I wonder what the Nexus One (running 2.2) has that Vibrant 2.2 doesn't.... hmmmmm
Click to expand...
Click to collapse
it's made by htc. the hardware and software on the nexus s 2.3 is the only similar one.
Yeah i definately think a 2.3 rom needs to be the base!
Sent from my HTC Vision using XDA Premium App
i flashed Simply Galaxy RC3.3 and all i did was install netflix and it worked!!!!
works gorgeously on miui 1.5.6b edited reboot cleared, rebooted play. no data toggling, locking etc.
Got it working on CM7.
Sent from my SGH-T959 using XDA Premium App
Hmmm so I either get GPS or Netflix...... I think I use my GPS much more than I will Netflix
Sent from my HTC Vision using XDA App
I amgetting a boot loop with bonixV 1.2.1, I let it sit for awhile then restore my nandroid backup.
Ahhh it booted up.

[Q] Cannot subscribe to Google Play Music All Access using carrier billing

This is mostly a post about a specific problem with Google Play carrier billing.
Here is the problem:
I want to subscribe to a trial of Google Play Music All Access
I want to use carrier billing (with my Verizon Wireless phone)
When I select "Bill my Verizon Wireless account", I get a red message stating "Error processing your purchase"
Notes:
Carrier billing usually works for me with Verizon Wireless
I am NOT using WiFI while trying to make the purchase
I do not have blocks on messaging or web purchases with Verizon Wireless
Verizon Wireless support cannot find any reason why the purchase would fail
I am well below the $25/mo. cap for Verizon Wireless carrier billing (I've only spent $.99 this month so far)
Step by step:
I turned off WiFi on my android phone (mostly stock rooted Samsung Galaxy Nexus running JB 4.2.2 on VzW).
I plugged my phone into my PC with the USB cable.
USB debugging is on.
I fired up adb shell on my PC.
I used su to start a superuser shell in adb
I typed:
Code:
logcat | grep --color=auto -i -E 'play|market|store|carrier|billing|finsky|phonesky|vending'
I launched Play Music (version v5.0.1041J.689753)
I opened the menu (...)
I selected "Settings" from the menu
I selected "Try All Access for free" in settings
I was sent to a "Google play" screen titled "Try Google Play Music All Access"
I selected "Try it FREE"
A modal dialog box opened titled "Google Play Music All Access"
From logcat:
Code:
I/ActivityManager( 378): START u0 {act=com.android.vending.billing.PURCHASE cat=[android.intent.category.DEFAULT] pkg=com.android.vending cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity (has extras)} from pid 8403
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity: +121ms
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity (has extras)} from pid 1708
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity: +153ms
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I clicked "Free"
I clicked "Payment options"
I clicked "Bill my Verizon Wireless account"
From logcat:
Code:
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity (has extras)} from pid 1708
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity: +140ms
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
D/Volley ( 1708): [155] BasicNetwork.logSlowRequests: HTTP response for request=<[ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133> [lifetime=14351], [size=7526], [rc=200], [retryCount=0]
D/Volley ( 1708): [1] Request.finish: 14363 ms: [ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133
I get "Error processing your purchase." in red print
This line really got my attention:
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
I'm assuming "DCB" is "Direct Carrier Billing", and "DCB 2" might be something like a monthly subscription billed with carrier billing. I make purchases with carrier billling so I'm not sure why it would say "Carrier billing config is null."
To make sure carrier billing is working (still), I launched "Angry Bird Seasons", and went "shopping" for 80 power-up bundles for $4.99. I select the same options for "Payment Options" and "Bill my Verizon Wireless account" and "Buy" (bringing me to the "Confirm password" screen, where I canceled the purchase).
This line stood out from logcat:
Code:
D/Finsky ( 1708): [1] PurchaseFragment.runCompleteFlowAndContinue: Start complete flow for DCB3 instrument.
"DCB3" ???. Maybe another "Direct Carrier Billing" purchase type (for a one-time consumable purchase)?
Since Google Play is not open source, I have no way of looking at the code to see what these debug lines actually mean.
Can anybody give me any guidance on this?
Having the same problem with a rooted Droid RAZR. Does it on both the stock rom and CM10.1.
Edit: Called customer service. They are looking into it. Told me they should contact me back in 24/48 hours.

CM11 bug (can't post in dev thread, can someone else?) + logcat

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

com.android.systemui keeps crashing when charging level at 100%

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

Categories

Resources