Hi all,
I am using modpunks CM 12.1 on my G850F.
Working very nice. Now I get the following problem(s):
Random freezes, if I get freezings, very regular I cannot switch on the phone instantly. It's draining battery but I cannot boot it (no samsung logo...) nor I cannot boot into recovery. Only download mode works sometimes.
The SAME happens with stock ROM. Tried the "old" frenche XEF version, the "new" one from late november and the one the phone was initially delivered with.
To me it seems kind of if there is either a memory problem OR a CPU problem especially as I only get this problems when using the phone. so I can keep it in my pocket and it works.
Do you have other ideas howto narrow the problem down? Up to now there is no clear variant how to reproduce this behavior. but it happens now very often and EVEN when restoring CM from recovery once.
Best and thanks for your ideas and help,
Blubberor
I would suggest testing with some benchmark app. If it crashes take notice when it did. If not make a clean flash with odin with repertition ticked ON and see if it repeats the error.
Sent from my P6-U06
Same issue
Hi. I have the same issue with my Alpha. Official room, tried to reset several times with no result. It gets hot and then freezes. A friend of mine has same phone and OS version, no freezes encountered. Waiting for an update from Samsung.
Blubberor said:
Hi all,
I am using modpunks CM 12.1 on my G850F.
Working very nice. Now I get the following problem(s):
Random freezes, if I get freezings, very regular I cannot switch on the phone instantly. It's draining battery but I cannot boot it (no samsung logo...) nor I cannot boot into recovery. Only download mode works sometimes.
The SAME happens with stock ROM. Tried the "old" frenche XEF version, the "new" one from late november and the one the phone was initially delivered with.
To me it seems kind of if there is either a memory problem OR a CPU problem especially as I only get this problems when using the phone. so I can keep it in my pocket and it works.
Do you have other ideas howto narrow the problem down? Up to now there is no clear variant how to reproduce this behavior. but it happens now very often and EVEN when restoring CM from recovery once.
Best and thanks for your ideas and help,
Blubberor
Click to expand...
Click to collapse
flc555 said:
Hi. I have the same issue with my Alpha. Official room, tried to reset several times with no result. It gets hot and then freezes. A friend of mine has same phone and OS version, no freezes encountered. Waiting for an update from Samsung.
Click to expand...
Click to collapse
my wife as well.
although I have to admit, mine had to go 3 times to Samsung CSC, while hers is just working fine.
This is just a strange happening.
will do two things. soon.
Complete erase of all files.
Will open the phone to check if I see something strange...
In case I can get it back to work I will report back.
Best,
Blubberor
Why is it no matter what i post on XDA people just ignore it wut
now its official.
Odin was not able to repartition only regular flashing..., while completely opening in the end the display broke.
so I loved this phone, but as it made problems all over the time (even before testing and using CM (thx @modpunk ones again!!!)) won't stick to samsung.
now first use the good old nexus 4....
best and thanks to all from the samsung alpha area here on xda!!
was lucky...had the phone connected to adb and logcat was running when it crashed.
maybe someone can have a look. to me there is nothing strange on the system going on...
I have checked with E2FSCK memory and integrity of SYSTEM, DATA, EFS....partition without any strange error reports..
I was wondering if one can fully check the whole memory to exclude just bad blocks.
right now the phone was just charging when I unlocked screen and was starting logcat---
Code:
01-03 16:25:04.882 10126 10126 W GAv4 : AnalyticsReceiver is not registered or is disabled. Register the receiver for reliable dispatching on non-Google Play devices. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.886 10126 10126 W GAv4 : CampaignTrackingReceiver is not registered, not exported or is disabled. Installation campaign tracking is not possible. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.891 10126 10163 W GAv4 : AnalyticsService not registered in the app manifest. Hits might not be delivered reliably. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.990 2865 5470 I ActivityManager: Start proc 10164:com.estrongs.android.pop/u0a160 for broadcast com.estrongs.android.pop/.app.StartServiceReceiver
01-03 16:25:05.003 2865 3167 I ActivityManager: Killing 9510:com.android.deskclock/u0a39 (adj 15): empty #17
01-03 16:25:05.264 2457 2457 D gpsd : WakeLock(Acquire,GPSD)
01-03 16:25:05.264 2457 2457 D gpsd : WakeLock(Release,GPSD)
01-03 16:25:05.277 2865 3106 D WifiService: releaseWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
01-03 16:25:05.361 3066 10110 I SecHAL : device_sleep: NFC can be going to sleep
01-03 16:25:05.405 4517 4630 I GCoreUlr: Successfully inserted 3 locations
01-03 16:25:05.409 4517 4630 I GCoreUlr: Starting service, intent=Intent { act=com.google.android.location.reporting.UPLOAD cmp=com.google.android.gms/com.google.android.location.reporting.service.DispatchingService }, extras=null
01-03 16:25:05.416 10164 10184 W ResourceType: No package identifier when getting value for resource number 0x00000000
01-03 16:25:05.421 2865 2979 D WifiService: New client listening to asynchronous messages
01-03 16:25:05.495 2865 3622 I ActivityManager: Killing 8291:com.cyanogenmod.lockclock/u0a53 (adj 15): empty #17
01-03 16:25:05.893 4517 10195 W BaseAppContext: Using Auth Proxy for data requests.
01-03 16:25:05.917 4517 4517 V GLSActivity: AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
01-03 16:25:05.925 4517 4517 V GLSActivity: AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
01-03 16:25:06.218 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.220 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.222 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.224 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.226 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.255 2865 5101 D NetlinkSocketObserver: NeighborEvent{elapsedMs=382899, fd00::9ec7:a6ff:fe12:55e6, [9CC7A61255E6], RTM_NEWNEIGH, NUD_REACHABLE}
01-03 16:25:06.705 2865 2980 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 100]
01-03 16:25:06.730 4517 10195 I GCoreUlr: Batch Location Update succeeded for account account#-16#
01-03 16:25:06.767 4517 10195 I GCoreUlr: Upload task finished
01-03 16:25:06.770 2865 2876 W AppOps : Finishing op nesting under-run: uid 10012 pkg com.google.android.gms code 40 time=1451834705429 duration=97 nesting=0
01-03 16:25:06.819 2451 2899 V audio_hw_primary: do_out_standby: output standby: 0
01-03 16:25:06.877 3012 3012 D PhoneStatusBar: disable: < expand ICONS* alerts SYSTEM_INFO* back home recent clock search quick_settings >
01-03 16:25:08.695 2451 2899 V audio_hw_primary: out_set_parameters: key value pairs: routing=2
01-03 16:25:08.698 9786 9786 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-03 16:25:08.706 2451 2899 V audio_hw_primary: start_output_stream: starting stream
01-03 16:25:08.709 2451 2899 V audio_hw_primary: *** select_devices: Routing hasn't changed, leaving function.
01-03 16:25:08.709 2451 2899 V audio_hw_primary: start_output_stream: stream out device: 2, actual: 2
Blubberor said:
was lucky...had the phone connected to adb and logcat was running when it crashed.
maybe someone can have a look. to me there is nothing strange on the system going on...
I have checked with E2FSCK memory and integrity of SYSTEM, DATA, EFS....partition without any strange error reports..
I was wondering if one can fully check the whole memory to exclude just bad blocks.
right now the phone was just charging when I unlocked screen and was starting logcat---
Code:
01-03 16:25:04.882 10126 10126 W GAv4 : AnalyticsReceiver is not registerэ...
Click to expand...
Click to collapse
I'll help you. Turn the unlocking fingerprint.
What does this mean exactly?
Still have freezings. Kind of desperate how to brick the device..
Sent from my Nexus 4 using XDA Free mobile app
Turn off unlocking fingerprint.
Volks.com.ua said:
Turn off unlocking fingerprint.
Click to expand...
Click to collapse
would even be not supported in CM13 so there is no option I guess.
Thanks already - fingerprint was already exchanged and broken again bei CSP some months ago....
Best,
Blubberor
Hi! My cellphone has the same problem. Please, let me know if you could solve it.
Thanks,
Pablo
pablitolandia said:
Hi! My cellphone has the same problem. Please, let me know if you could solve it.
Thanks,
Pablo
Click to expand...
Click to collapse
Unfortunately could not solve it.
No errors in file checks, efs restored....Samsung refused warranaty due to Knox. Today a used alpha that I bought is going to arrive.
Good luck.
Blubberor
Sent from my Nexus 4 using XDA Free mobile app
Hi all, a quick fix that worked for me was to use another launcher.
nickps17 said:
Hi all, a quick fix that worked for me was to use another launcher.
Click to expand...
Click to collapse
To me happened with Stock as well as with cm.
Crossing the fingers for you.
Sent from my SM-G850F using XDA Free mobile app
Related
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.
Hi all,
I've got a little problem here and i was wondering if anyone can help please.
when i install CM10 or any other custom roms i get such an issue that power button works great, it can even lock my screen but when i press it for unlocking screen it doesn't unlock the screen is still black but pressing volume buttons makes sounds, i think screen is unlocked but it's stays black till i don't reboot with longpressing power button.
when i go back to ICS this problem is solved, but it's terrible OS so please someonehelp me
here is the logcat if someone can find out what the problem is
05-31 20:51:40.180 I/PowerManagerService( 406): Going to sleep by user request...
05-31 20:51:40.250 I/Choreographer( 406): Skipped 39 frames! The application may be doing too much work on its main thread.
05-31 20:51:40.250 D/MPLSensor( 406): handle : 4 en: 1
05-31 20:51:40.250 D/MPLSensor( 406): enabled_sensors: 16 dmp_started: 0
05-31 20:51:40.250 D/MPLSensor( 406): MLSetMPUSensors: 70
05-31 20:51:40.250 I/MPL-ml ( 406): Actual ODR: 25 Hz
05-31 20:51:40.250 D/MPLSensor( 406): set_power_states > MLDmpStart()
05-31 20:51:40.250 I/ ( 406): mpu3050_resume: Resuming to 0070
05-31 20:51:40.250 I/ ( 406): mpu3050_suspend: suspending sensors to 0000
05-31 20:51:40.250 I/ ( 406): mpu3050_suspend: Will resume next to 0070
Click to expand...
Click to collapse
At first sight it looks okay, are you sure you have the US bootloader installed?
DefQoN_BE said:
At first sight it looks okay, are you sure you have the US bootloader installed?
Click to expand...
Click to collapse
no i'm not. can u give me a link that i should flash?
I found out that the problem appears after rooting the device
FLaMpeR said:
no i'm not. can u give me a link that i should flash?
I found out that the problem appears after rooting the device
Click to expand...
Click to collapse
If you live in europe you probably have a UK bootloader installed, if you want to install cm 10.1 you need a US ICS bootloader, you can find the files for your device on www.droidbasement.com, click on your device name, download the US_LPL_4.0.4_bootloader.zip and flash it under PDA slot in ODIN
thanks a lot this worked for me
Sent from my Nexus 4 using Tapatalk 4 Beta
FLaMpeR said:
thanks a lot this worked for me
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
No problem
Hi,
I am experiencing an issue with mobile data being repeatedly enabled.
I have found that
1) given mobile data in OFF state
2)
i.) plugging in usb cable to computer (plugging in usb cable to charger has no effect) automatically switches on mobile data
ii.) unplugging usb cable from computer also switch on mobile data (if mobile data is switched off manually after i.) happened)
I am using aokp rom android 4.1.2 from th3bill
(link: http://forum.xda-developers.com/showthread.php?t=1755836)
How can I change such behavior?
Thanks.
added:
I used aSpotCat to look at apps that request permission to change network connectivity, here is the list:
youtube, google play services, line, tango, and viber
These apps are all in frozen state, but the behavior as described persist.
Update 7/4/2014, with catlog:
07-04 15:41:24.159 I/BATTD (1459): Battd USB INSERT = Success
07-04 15:41:24.199 D/MotUsbService(1856): handleUsbCableAttachment()
07-04 15:41:24.199 D/MotUsbService(1856): handleUsbEvent(), Received event: 0, current state: 0
07-04 15:41:24.219 D/MotUsbService(1856): handleUsbEvent(), Received event: 2, current state: 1
07-04 15:41:24.399 D/MotUsbService(1856): handleGetDescriptor()
07-04 15:41:24.399 D/MotUsbService(1856): setUsbConnectionNotificationVisibility()
07-04 15:41:24.409 D/MotUsbService(1856): enableInternalDataConnectivity(): true
07-04 15:41:24.409 D/ConnectivityService(1632): setMobileDataEnabled(true)
I take that MotUsbService is probably from com.motorola.usb
Now the question remains how I can stop this behavior.
I would suggest to check if the bug is present on a clean install, with gapps and on a clean install without gapps. Might as well be a rom issue
Enviado desde mi MB860 usando Tapatalk 2
I looked at the catlog, the following service seems to be guilty:
07-04 15:41:24.159 I/BATTD (1459): Battd USB INSERT = Success
07-04 15:41:24.199 D/MotUsbService(1856): handleUsbCableAttachment()
07-04 15:41:24.199 D/MotUsbService(1856): handleUsbEvent(), Received event: 0, current state: 0
07-04 15:41:24.219 D/MotUsbService(1856): handleUsbEvent(), Received event: 2, current state: 1
07-04 15:41:24.399 D/MotUsbService(1856): handleGetDescriptor()
07-04 15:41:24.399 D/MotUsbService(1856): setUsbConnectionNotificationVisibility()
07-04 15:41:24.409 D/MotUsbService(1856): enableInternalDataConnectivity(): true
07-04 15:41:24.409 D/ConnectivityService(1632): setMobileDataEnabled(true)
I take that MotUsbService is probably from com.motorola.usb
Now the question remains how I can stop this behavior.
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
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Sigosuuu said:
Sr My English is very bad
I've been running Nexus v4.0.5 on my Apollo device. The issue is my kindle start to rebooting or turning off after entering sleep mode I wanted to try another rom, but I'm not sure it could help
What is the problem ?Please help.
Click to expand...
Click to collapse
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Davey126 said:
Nexus v4.0.5 is very old and is no longer supported. Suggest installing the immediate successor (Fire Nexus) which you can do without loss of data.
Is the device running Safestrap?
Click to expand...
Click to collapse
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Sigosuuu said:
I installed (Fire Nexus) but the issue not fix :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Likely an app. You will need to use a tool like GSAM or BBS to identify the culprit.
My Apollo HDX behaves similarly, and has since I got it (refurbished) six months ago: very shortly after going into screen-off mode, a reboot occurs.
This happened under the stock 4.5.5.2 OS, but seemed to be mitigated if I set it to keep wifi on during sleep.
Under LineageOS 14.1, however, it reboots whether that option is enabled or disabled.
I've tried several times to see if anything interesting appears via wireless logcat, but nothing is terribly obvious. Here's the last attempt:
Code:
07-03 01:59:19.246 1157 1234 E WifiHAL : wifi_error acquire_supported_features(wifi_interface_handle, feature_set *): requestResponse Error:-95
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.247 1157 1540 E BatteryStatsService: no controller energy info supplied
07-03 01:59:19.248 1567 1567 E PhoneInterfaceManager: [PhoneIntfMgr] queryModemActivityInfo: Empty response
07-03 01:59:19.257 1157 1540 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}
07-03 01:59:20.383 544 884 D audio_hw_primary: out_standby: enter: stream (0xb624ab00) usecase(1: low-latency-playback)
07-03 01:59:20.489 544 884 D hardware_info: hw_info_append_hw_type : device_name = speaker
After that, the device no longer pings as it has begun restarting.
Using Wake Lock (https://play.google.com/store/apps/details?id=eu.thedarken.wl), I found certain combinations that would prevent reboots when the screen goes off:
wifi on, wakelock WIFI_MODE_FULL_HIGH_PERF => ok
wifi on, wakelock WIFI_MODE_FULL (or less) => *restart on sleep*
wifi off, wakelock PARTIAL_WAKELOCK => ok
wifi off, wakelock WIFI_MODE_FULL_HIGH_PERF (or less) => *restart on sleep*
airplane mode, no wakelock => ok
Seems almost like some sort of hardware/driver issue.