Related
Hello,
Last 2-3 weeks a have this strange problem with my phone, when i turn on wifi, the box continiiusly loops ticking and unticking and goes on off without stopping.
I thought initially that this was a problem of the specific rom for Motorola Milestone. But when i installed the initial sbf of the phone, nothing changed :-(
Anyine experienced in the past this issue? Unfortunately this is a reason to change phone and i dont want to buy a new one now...
Thanks in advance
Sent from my NookColor using Tapatalk
It seems that a lot of other users had / have this problem, however i dont know what to do - especially with the wifi-lock help below
http://code.google.com/p/android/issues/detail?id=9677
http://www.htcdesireforum.com/htc-de...g-android-2-2/
http://androidforums.com/captivate-a...i-problem.html
I suppose i am the only user on xda that has this error... :-(
Sent from my NookColor using Tapatalk
A bit dissapointing that there is no help on this :-(
I suppose i should start searching for a new phone.
Sent from my NookColor using Tapatalk
Anyone please? :-(
Sent from my NookColor using Tapatalk
Fekish said:
Anyone please? :-(
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Have you tried installing a new rom?
WiFi - On/Off
I suspect it has something to do with the ROM/HW interface. I would do a complete wipe of your phone back to stock factory settings.
Does it do the same thing on the factory wipe?
Is your problem confined to 1 hotspot or WiFi device or all devices to attempt to attach to?
If the problem continues on the factory ROM and factory settings I would suspect a hardware issue.
ALSO you could try upgrading/downgrading your MODEM to a different one and see if that helps.
Thanks, i really appreicate it guys!
i installed different roms, wiped everything, went back to stock and nothing...
Wifi goes on and off without showing what networks are available.
How to change moden?
Sent from my NookColor using Tapatalk
I had the same Problem with a few ROM's but now I Found CoreDruid for my HTC Desire HD and that problem is history.
When it happens, just reboot!
Fekish said:
Thanks, i really appreicate it guys!
i installed different roms, wiped everything, went back to stock and nothing...
Wifi goes on and off without showing what networks are available.
How to change moden?
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Does that problem occur on a custom rom?
Theonew said:
Does that problem occur on a custom rom?
Click to expand...
Click to collapse
On all custom roms, and atock ones.
Sent from my NookColor using Tapatalk
Have you tried switching ON the OFFLINE mode (Airplane mode) and then switch off OFFLINE mode?? It helps in my Photon...
Further you can try turning WiFi Hotspot On and then Off... Heard that this method also solves WiFi issues in some MoPhos....
Third solution for MoPho, I am not sure it will work for MileStone or not.... goto https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/77706
Please provide some log files, when you turn of wifi: logcat and dmesg. You can get it using app like Quick System Info, or get them using adb.
Try doing this.
Go to Advanced wifi settings and uncheck "Use static IP" .
Hello,
attached is the logcat.
Thanks everyone for spending time in my problem!
From what i see from your log file:
E/wpa_supplicant(19421): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 800508, res = 1, errno = 25)
E/wpa_supplicant(19421): ERROR - Failed to get mac address!
D/WifiStateTracker( 2569): Reset connections and stopping DHCP
I/wpa_supplicant(19421): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 2569): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
E/wpa_supplicant(19421): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8021501, res = 1, errno = 100)
E/wpa_supplicant(19421): ERROR - Failed to do tista scan!
W/wpa_supplicant(19421): Failed to initiate AP scan.
D/WifiStateTracker( 2569): Disabling interface
E/wpa_supplicant(19421): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000001, res = -1, errno = 19)
E/wpa_supplicant(19421): ERROR - Failed to start driver!
I/wpa_supplicant(19421): CTRL-EVENT-DRIVER-STATE HANGED
V/WifiMonitor( 2569): Event [CTRL-EVENT-DRIVER-STATE HANGED]
D/wifi ( 2569): wifi doCommand: ret=-1
Click to expand...
Click to collapse
ioctl system calls fail with different errors. Ioctl is used for controlling the device, WiFi chip in your case. Errors mean that either driver is not ok but if you have original rom it shouldn't be the case, or device itself is not operational.
So probably your have a hardware failure.
You can also try with some unencrypted wifi, maybe the problem occurs in WPA mode only.
ok thanks
first time i heard a broken wifi, but it seems that is time for a new phone!
Hello everyone
I've managed to unlock and root my SGP312 (pollux_windy). Because I always liked AOKP, I tried to install this custom ROM. Here's what I did:
1) Flashed Little Kernel into /boot while in Sony's Fastboot Mode
2) Flashed extracted boot.img of AOKP into "boot" and newest TWRP recovery (v2.6.3) into "recovery" while in LK's Fastboot Mode
3) Rebooted into TWRP recovery, wiped data, cache and dalvik cache
4) Flashed newest AOKP version (jb-mr2 milestone #1 for pollux_windy)
5) Flashed gapps (gapps-jb-20130813-signed.zip)
And tada, the custom ROM booted and everything was fine... No force closes / crashes, no problems, everything worked like a charm.. except the god damn Play Store! Whenever I open the Play Store, it only says "No connection". Pressing retry doesn't help at all. Ofcourse I always search through some forums before posting an issue, so here's what I've already tried:
- Other custom ROM (CM 10.2 stable for pollux_windy)
- Other gapps package (pa_gapps-full-4.3-20131102-signed.zip)
- Force Google Play Store and Google Play Services to stop and delete their data
- Wiped cache and dalvik cache
- Tried a connection without native IPv6 (WLAN hotspot of my HTC One, going over mobile internet which is clearly IPv4 only)
- Checked /etc/hosts (only contains 127.0.0.1 localhost)
- Executed Shark for Root -> There is clearly some data activity going on, my tablet seems to send some data to the google servers but they return an empty response as it seems (see logcat down below)? Unfortunately I am not able to analyze the packets, thanks to SSL/HTTPS...
- Changed some build.prop settings to match an original installation (model=SGP312, device=SGP312 and so on...)
And none of these methods worked. I am totally clueless what else I could try? Here's a logcat snippet:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
My build.prop is now reverted to the original AOKP build.prop, which can be found here: dl.snapserv.net/build.prop.txt (Sorry, I am not allowed to post links yet...) Have you guys any idea? XDA is basically my last hope, otherwise it seems like I am doomed to use the stock ROM :/ Or did I do something wrong?
Thanks for reading and have a nice day!
Regards
NeoXiD
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
[/QUOTE]
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
bondcheg said:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. (How I found that problem? I just went so far that I've intercepted the traffic to the google servers with a fake root certificate and Fiddler...) Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
NeoXiD said:
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD[/QUOTE]
I`m novice user and never conneced my device with adb and dont know how to do it.
bondcheg said:
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
I`m novice user and never conneced my device with adb and dont know how to do it.
Click to expand...
Click to collapse
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
bondcheg said:
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
Click to expand...
Click to collapse
That might be the fault then, because it might get interpreted as serial number '0', which might get rejected by Google. Did you flash any custom bootloader? Normally this should not occur... You can also drop me a PM so we do not spam this thread with a 4-eye-conversation.
Regards
NeoXiD
Hey guys,
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time. (yes I set the permissions to 0644)
Does anyone ... has anyone tried moving / porting this?
Pulled the Dialer from here
http://www.androidpolice.com/2013/1...n-doesnt-show-up-in-my-app-tray-what-can-i-do
Sparatan117 said:
I tried sideloading the 4.4 Dialer into my system/priv-app/ folder and yet it only crashes every single time
Click to expand...
Click to collapse
Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.
I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.
What do I win for being right.. ?
ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3
.
fffft said:
Well I tried it and it works fine. You didn't describe how you tried to install it though, making it rather hard to spot where you went astray.
I'd bet though that you didn't wipe the cache and data in the Application manager plus wipe Dalvik from recovery.
What do I win for being right.. ?
ps: the md5 should be 65:1e:d1:f2:61:07:f9:6e:62:2c:81:08:83:c4:53:a3
.
Click to expand...
Click to collapse
You know, I would have loved if it had worked, but it didn't ...
I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache
... still force close... thoughts?
EDIT:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Edit 2: Nevermind haha
Resorting to flashing via Recovery. See if this works
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
Sparatan117 said:
You know, I would have loved if it had worked, but it didn't ...
I put the APK directly into priv-apps
set the privilages to 0644
cleared the data from the app
cleared the Dalvik Cache
... still force close... thoughts?
EDIT:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Click to expand...
Click to collapse
Are you using a stock unmodified rom?
Like with just towel root or something similar?
Sparatan117 said:
I tried just straight up installing it without it being a system app and it works just fine. Go figure...
Click to expand...
Click to collapse
Okay, I get it.. you don't want to pay off the bet.
=8-0
Sure, whatever. Glad it's working for you though. And it works for the rest of us too.
Good enough.
.
---------- Post added at 07:39 PM ---------- Previous post was at 07:35 PM ----------
Sparatan117 said:
Edit 3:
Flashed via Recovery. Emptied Dalvik Cache/Cache on the way in. Still Force Closes.
Click to expand...
Click to collapse
Seriously? That doesn't make any sense.
I installed it on two systems and it was super easy and has been super stable. And there are 100+ comments on the original article without anyone there having issues either. Write out a detailed description of all the steps you took to install it so we can see where you went wrong.
.
Yeah well I guess pretty close to stock
I have Beans NF6 Factory build (upgrade without wiping data)
I have Chainfire's autoroot
Flashed TWRP recovery
Flashed the file via this ( http://www.androidfilehost.com/?fid=23269279319196848 ) file.
Wiped Dalvik/Cache via TWRP
Rebooted
Wiped data in App Manager
Started.
[insert picture of dog poop]
but in all seriousness I don't get it either... it's weird.
Although I'm glad I'm not the only one.
Sparatan117 said:
but in all seriousness I don't get it either... it's weird.
Although I'm glad I'm not the only one.
Click to expand...
Click to collapse
Okay, two of you ran into problems trying to install it. Still just a minor glitch.
To troubleshoot this though, we need you to be a lot more detailed. You didn't mention a lot of things.. e.g. you didn't say anything about checking permissions in your description.. so did you? And what was the result? Did you check the md5? Did you wipe the cache from the Application manager.. you only mention wiping the data. I know, picky, picky. But troubleshooting is all about the details. And we need to those things if we are to pin down the cause.
I'm also wondering about the order you wiped the data /cache. It's normally done in the reverse and that may be causing you problems. Wiping Dalvik should be the last step.
This procedure works. I've tried it three times now:
Check md5 of download
Move dialer to /system/priv-app
Confirm that permissions are 0644
[you can try running it at this point if you want to. it will force close at this point]
Open the Application manager i.e. Settings > Applications > Application Manager > All > Google Dialer
Force Stop > Clear cache > Clear data > OK
Reboot to recovery mode > wipe cache + Dalvik
Reboot to system
Open app drawer, click on Google Dialer & observe that it works properly
.
bumpkiss
Code:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 1
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): Unable to read user list
E/PersonaManagerService( 746): returning null in getPersonasForUser
E/MotionRecognitionService( 746): mReceiver.onReceive : ACTION_USER_PRESENT :: UNLOCK SCREEN
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_ANIMATING: true
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_EXPANDED: true
E/ActivityThread( 4896): Failed to find provider info for com.dropbox.carousel.CuOwnerCheckProvider
E/SmartFaceService - 3rd party pause( 746): onReceive, ACTION_STATUS_BAR_COLLAPSED: false
E/PersonaManagerService( 746): Unable to read user list
E/ActivityThread( 5740): Failed to find provider info for com.amazon.dcp.settings
E/Watchdog( 746): [email protected] 2
E/ConnectivityService( 746): Attempt to connect to mobile_mms failed (dataEnabled).
E/PersonaManagerService( 746): Unable to read user list
--------- beginning of /dev/log/main
E/MTPJNIInterface( 6390): Status for mount/Unmount :mounted
E/MTPJNIInterface( 6390): SDcard is available
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 93317 of [00bb9c9ce4]
E/SQLiteLog( 6390): (21) API call with NULL database connection pointer
E/SQLiteLog( 6390): (21) misuse at line 96852 of [00bb9c9ce4]
E/ ( 6390): [mtp_init_device] After open the MTP fd = 59 and line = 678...
E/MTPJNIInterface( 6390): Getting gadget reset status0
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false
E/SMD ( 257): DCD ON
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/MTPRx ( 6390): state from USB_STATE event DISCONNECTED
E/MTPRx ( 6390): ignore this event
E/DataRouter( 267): USB Interface is open with 0x9
E/SMD ( 257): ***Received data notification[DR->SMD]***
E/SMD ( 257): Path set is DATA_PATH_DR_SMD_MANAGER
E/SMD ( 257): Message:
E/SMD ( 257): Sending data to SMD: Len = [3]
E/SMD ( 257): buffer = []
E/SMD ( 257): Wrote 3 chars to SMD PORT fd=7 ch = 81
E/LightSensor( 746): RED : 1, GREEN : 1, BLUE : 1, CLEAR : 1, CALCULATED LUX : 0.000000, CCT : 1596.000000, REAL LUX : 0.000000 a_time = 238, gain = 64, ir=1, rp1=1, gp1=0, bp1=0, cp1=0, cpl=3202560
E/MTPRx ( 6390): state from USB_STATE event CONNECTED
E/MTPRx ( 6390): state from USB_STATE event DISCONNECTED
E/MTPRx ( 6390): stop observing and calling usbRemoved
E/MTPRx ( 6390): sendbooster is false!
E/MTPRx ( 6390): In usbRemoved Status bar enabled
E/MTPRx ( 6390): Sending Broadcast
E/SPPClientService( 6195): [[SystemStateMonitorService]] SystemStateMonitorService : noConnect? : false
E/MtpService( 6390): onDestroy.
E/MtpService( 6390): Unregister Mtp disable Receiver
E/MtpService( 6390): Receiver not registered: [email protected]
E/MtpService( 6390): Unregister mtpEmergencyReceiver
E/MtpService( 6390): Receiver not registered: [email protected]
E/MtpService( 6390): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 6390): Receiver not registered: [email protected]
E/MTPJNIInterface( 6390): noti = 3
Sparatan117 said:
--------- beginning of /dev/log/system
E/Watchdog( 746): [email protected] 1
Click to expand...
Click to collapse
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.
Meanwhile, the dialer works here.
.
fffft said:
Thanks for that but that log isn't deep enough to answer most of our questions. But if you could tackle the ones I posed in my last post? And can you try the install procedure that I suggested? It should work or at least give us some insight into what is failing.
Meanwhile, the dialer works here.
.
Click to expand...
Click to collapse
Does it work if you click the call button?
aooga said:
Does it work if you click the call button?
Click to expand...
Click to collapse
Yes it does (just tried it)
Sorry, I did follow your procedure to the letter, and the last post I posted was the result.
I'm thinking it's just not going to happen. Maybe a full system wipe is needed... or something. Who knows. Thanks for trying though.
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,
I have recently purchased a refurb Lenovo K6, it came with an Android 6.0 rom.
Off the bat it had some weird reboots and app crashes, updating and system restore solved nothing; the problem worsened, so I ended up using the official Lenovo tools to perform a system recovery, which flashed a stock Nougat rom (K33_USR_S223_1706101140_Q00440_ROW).
This didn't stop sudden app crashes and system restarts however; even at initial system setup, many apps including Google Play Services would stop responding.
Since then I've lost count of re-flashes, data and cache wipes, permission resets etc. that I've performed.
I've attempted to root the phone with KingRoot in order to wipe the Dalvik Cache but could not complete the process.
I got plenty of logs via logcat, wish you could help me understand what's going on using them; here is a small one (Error level treshold) that I got, includes crashes of Firefox, Lenovo Launcher and I think Google Play Services.
pastebin. com/sZkDYPXi
I got other bigger ones, as well.
Mainly I notice a lot of "no such file or directory" errors, such as:
Code:
07-24 14:46:13.852 1447 1667 E QCOM PowerHAL: Error opening sys/devices/system/cpu/cpu0/cpufreq/scaling_governor: No such file or directory
and a lot of SELinux permission denials:
Code:
07-24 14:31:22.373 474 474 E SELinux : avc: denied { find } for service=android.hardware.fingerprint.IFingerprintDaemon pid=2905 uid=10112 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:fingerprintd_service:s0 tclass=service_manager permissive=0
In another log with Warning treshold I was getting a lot of PackageManager warnings such as these:
Code:
07-22 19:34:36.255 5135 5135 W PackageManager: Not granting permission android.permission.ACCESS_FINE_LOCATION to package com.skype.raider because it was previously installed without
Code:
07-22 19:31:12.912 1422 1595 W PackageManager: Permission com.google.android.googleapps.permission.GOOGLE_AUTH from package com.google.android.gsf in an unknown group android.permission-group.ACCOUNTS
I'd rather try to fix the problem myself if at all possible, rather than returning the phone...
Thanks a lot for your help.
I now suspect there has been a failed root attempt on this device, as many errors have to do with denied permissions.
Also I managed to get a new logcat from many Firefox/Google Play Services and a system reboot, and the following line appears:
Code:
07-24 19:12:21.346 10637 10647 F art : art/runtime/gc/collector/mark_sweep.cc:448] Attempting see if it's a bad root
Also firefox crashes report this:
Code:
07-24 19:10:16.979 6598 6954 E InputDispatcher: channel '28475f0 org.mozilla.firefox/org.mozilla.gecko.BrowserApp (server)' ~ Channel is unrecoverably broken and will be disposed!
and apparently can't read session files:
Code:
07-24 19:10:42.340 10412 10426 E GeckoApp: An error occurred during restore, switching to backup file
07-24 19:10:42.340 10412 10426 E GeckoApp: org.mozilla.gecko.GeckoApp$SessionRestoreException: Could not read from session file
and the backtrace reports failure of some sort with async threads...
I really am banging my head against a wall here :crying:
bumpity bump bump