Related
I'm using aLogcat2.4 free from market. While I'm on DLXA2 stock rom.
I'm getting constant error showing these :
Code:
E/DataRouter( 128): smd_file_fd = 16 and external_file_fd = 27
E/DataRouter( 128): ==KDW(3)== smd_new_status = (356)
E/DataRouter( 128): ==KDW(4)== smd_new_status = (320)
E/DataRouter( 128): DCD pinstatus is ON
E/DataRouter( 128): +
E/DataRouter( 128): -
E/DataRouter( 128): fd is 23 Content read is USB Switch : PDA_AP
E/DataRouter( 128): length is 20
E/DataRouter( 128): Content of Buf
E/DataRouter( 128): DrReadUsbStatus File Open success
E/DataRouter( 128): DrReadUsbStatus 21 characters Buffer from USB file USB_STATE_NOTCONFIGUR
E/DataRouter( 128): DrReadUsbStatus returns false USB is offline
E/DataRouter( 128): DrReadUsbStatus returns false USB is offline
E/DataRouter( 128): Turn OFF the SMD DTR bit
These errors show almost every second. Is this normal?
Apart from reading the Logcat....have you noticed any problems on your device.....
such as Force Close by Apps, or random reboots, stuff like that??
Why are you running Logcat....what problem were you tracking down??
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
It's rather about battery life. I found out when nighttime standby, data disabled, no wifi, no bluetooth, no gps. battery drops 1% less then 1 hour, while I expect it would hold at least 2 hour. While browsing, I see some say they last 3-4 hour every 1%. Maybe there is something wrong with rom or maybe hardware (?)
Can you share if you are getting the same error in logcat?
I'm running DXLA2, even if I do factory reset, then install alogcat, the error is there.
I just now install cwm recovery, and ready to test other rom. if you are not getting the same error, can you share what rom you use?
Thanks.
Really friend....
I am getting constant DataRouter 129 errors
slightly different, but similar....
AFAIK.....
this is Android System checking the Status of USB connection status......
Just try connect your phone to PC/Laptop....
mount USB storage.....
then check do those errors still occur.....
I don't got no PC or Laptop in Vacation
I don't think this will affect Battery Stats!!!
Let us know results of log at with phone connected to PC...OK
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
irishpancake said:
Really friend....
I am getting constant DataRouter 129 errors
slightly different, but similar....
AFAIK.....
this is Android System checking the Status of USB connection status......
Just try connect your phone to PC/Laptop....
mount USB storage.....
then check do those errors still occur.....
I don't got no PC or Laptop in Vacation
I don't think this will affect Battery Stats!!!
Let us know results of log at with phone connected to PC...OK
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
Click to expand...
Click to collapse
Out of curiousity, I tried flash OKVFinal4 by kezra, same DataRouter error..
Tried kernel from cowithgun, same error.
Connecting to PC still show as error in logcat both with MTP or USB storage.
Maybe I just got a bad batch of battery..
I guess this is normal on galaxy W, then this assume solved. Thanks for the information..
Any news on this. I know it's and old thread, but it's the only one on internet.
I lost 10% in sleep mode in 6 hours because of this:
15:23:29.695 DataRouter( 1792)
DrReadUsbStatus returns false USB is offline
I have galaxy w, 2 sg2 and one s3, all have this error.
I've been trying to wrap my head around this.
Running yakju 4.0.4 on a Roger Gnex. Before this I never noticed anything out of the ordinary. But I never came close to using all my data plan. Then I received a warning of my usage. so I crunched the data screen to get some day to day numbers... This is just "android os" mobile data, not what its also pulling on wifi.
19th to the 25th combined 8mb,
Then on May 26 it shot up to 42mb.
27th = 56mb.
28th = 49mb.
29th = 47mb
30th = 55mb
31st = 45mb
1st = 45mb
2nd = 42mb
3rd = 41mb
4th = 59mb
5th = 63mb
6th = 73mb
7th = 76mb
8th = 81mb
9th = 80mb
10th = 80mb
11th = 65mb
12th = 74mb
13th = 80mb
14th = 75mb
15th = 46mb
16th = 53mb
17th = 398mb!! (now I know why I started dying 1/2 way through the day)
18th = 583mb!!!
19th = cutoff for my period... (barely made it under my 6gb plan)
I deleted anything that was updated or installed around May 26th as well as June 17th. It didn't work. I continued to chew through around 500mb of data a day. I did a factory reset, it seems to help but android os was still 80-90% of my data usage and it was around 100mb a day. So I installed a new version of the os, and for a couple days I though I might be in the clear. And then today my phones dead before dinner and there's 400mb sitting under "android os" yet again!!! not to mention what's under wifi. And the days not yet over.
I am at a loss as to why this is happening and what the heck is using android os. I don't want to have to cripple my phone by un-installing everything and turning off features, but I can't survive too many 500mb data days. I'd be out of data in a week, not to mention it's killing my battery...
Any ideas on how to figure out what's using "android os" so I can kill / fix it?
Trying to add pics but its not going well....
Not sure if you need root to run "top -m 15" in the terminal. OS Monitor should work though. Unhide system processes and sort by CPU usage.
Then you'll see what processes are frequently running. Some people think Google Backup Transit can go rogue for data in the Android OS process agglomeration.
You'd imagine a rouge process would show up fairly regularly if you watched it...
Woooooooow. That's insane.
I'll take a pure guess here and say Gallery or fackbook syncing of photo's that you are taking?
Jezz_X said:
I'll take a pure guess here and say Gallery or fackbook syncing of photo's that you are taking?
Click to expand...
Click to collapse
Originally I thought so as well so I turned sync to wifi only and also tried with it off. It didn't appear to help. No matter what I can't account for the amount of data we are talking about. I don't have that many pics on the phone to account for a single day, let alone concurrent days.
I just un-installed every single app (the few that I re-installed on the new os) I have on the phone to see if that makes a difference. Try an empty phone and see what happens...
Does Gmail sync properly (check if there is any exclamation marks on any of the syncs)?
Swiftkey'ed on my CM9 Galaxy Nexus
Herman76 said:
Does Gmail sync properly (check if there is any exclamation marks on any of the syncs)?
Swiftkey'ed on my CM9 Galaxy Nexus
Click to expand...
Click to collapse
Never seen anything like that. It looks normal far as I can tell...
Just for the heck of it I installed 4.1 jb, see if that solves the problem...
Made it 12 hours on mobile and only used 2mb of android os data. Looks like 4.1 could be my solution to this problem.
Monitoring my phone through QXDM I've come to some unfortunate conclusions. I used to have a Touch Pro 2 and it would NOT send gps/agps data back to the tower, this phone on the other hand sends messages like this for data/registration:
EVENT [01162] EVENT_GPS_SEED_GET 18:38:01.955 Option = 2, Latitude = x, Longitude = x, Position Sigma =x, GPS Week = 1719, GPS ms = x
I'm less than thrilled so I went into NV items and set:
gps1_capabilities to 0
gps1_allowed to 0
gps1_privacy to 1
gps1_net_acce to 0
Some of these were inactive but I wrote/set them anyway. Yet the messages persist. How do I make them stop? I've nixed google maps too. The location service runs without use wifi being set in settings and you cannot separate lattitude from maps anymore.
* Set gps1_seedpos_option to 0 and reboot:
get :
EVENT [01162] EVENT_GPS_SEED_GET 19:08:47.422 Option = 4, Latitude = 0, Longitude = 0, Position Sigma = 10000000, GPS Week = 1719, GPS ms = 414527421
Does this mean I've killed it?
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
nxb said:
Monitoring my phone through QXDM I've come to some unfortunate conclusions. I used to have a Touch Pro 2 and it would NOT send gps/agps data back to the tower, this phone on the other hand sends messages like this for data/registration:
EVENT [01162] EVENT_GPS_SEED_GET 18:38:01.955 Option = 2, Latitude = x, Longitude = x, Position Sigma =x, GPS Week = 1719, GPS ms = x
I'm less than thrilled so I went into NV items and set:
gps1_capabilities to 0
gps1_allowed to 0
gps1_privacy to 1
gps1_net_acce to 0
Some of these were inactive but I wrote/set them anyway. Yet the messages persist. How do I make them stop? I've nixed google maps too. The location service runs without use wifi being set in settings and you cannot separate lattitude from maps anymore.
* Set gps1_seedpos_option to 0 and reboot:
get :
EVENT [01162] EVENT_GPS_SEED_GET 19:08:47.422 Option = 4, Latitude = 0, Longitude = 0, Position Sigma = 10000000, GPS Week = 1719, GPS ms = 414527421
Does this mean I've killed it?
Click to expand...
Click to collapse
I confirm. wtf? there must be a way to disable it...
I think the final options disabled it. I also deleted location service and use AFwall. Kernel seems to leak but I think location data is not going to either google or the carrier. GPS with airplane mode and static maps seems all winner.
Wish I could block google services and still use gmail. As a general computing device android is nice but my trust level isn't very high and seems nobody cares they're carying a hostile tracking device on them everywhere they go.
The data it sends is anonymous so its not really hostile, you're just being paranoid. The data allows Google to improve GPS accuracy its basically just a log showing when satellite locks are lost and gained and which carrier and tower it's connected to at the time. It's to help locate deadzones and network conflicts the only identifiable data sent is carrier, tower and latitude/longitude, as well as whether a satellite lock was lost or gained.
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
People are too paranoid now a days.
Sent from my SPH-D710 using XDA
EeyoreSyndrome said:
People are too paranoid now a days.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yes, yes they are. There are many things to be paranoid about, however this isnt one of them. I mean seriously how do people expect location based services like search near me and weather to work? A magic genie living in their battery compartment?
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
Our app reads Type 2 tags (NfcA, Ndef). During the testing we have been able to consistently reproduce a condition where the NFC stack becomes unresponsive to subsequent reads. To restore it, we go to Settings, cycle the NFC box (off->on).
Ways to reproduce: We are moving the tag along the reading area in constant slow motion. Most of the time the tag is not read at all and the familiar "bleh" sound is emitted, as expected. Within a minute or about 10 tries, we hear the "bleh" sound too but no more reading is possible.
We reproduced this problem with the stock 4.2.1 as well as cm nightly based on 4.2.1 with kernel version 3.4.5-g73335a3
Below is logcat snippet from the crash:
D/NativeNfcTag( 620): Connect to a tech with a different handle
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/NfcNciHal( 620): GKI_getbuf() unable to allocate buffer!!!!!
E/NfcNciHal( 620): Failed to allocate GKI buffer
E/USERIAL_LINUX( 620): userial_read_thread(): unable to get buffer from GKI p_buf = 0x0 poolid = 1
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
Any clues much appreciated.
debriter said:
Our app reads Type 2 tags (NfcA, Ndef). During the testing we have been able to consistently reproduce a condition where the NFC stack becomes unresponsive to subsequent reads. To restore it, we go to Settings, cycle the NFC box (off->on).
Ways to reproduce: We are moving the tag along the reading area in constant slow motion. Most of the time the tag is not read at all and the familiar "bleh" sound is emitted, as expected. Within a minute or about 10 tries, we hear the "bleh" sound too but no more reading is possible.
We reproduced this problem with the stock 4.2.1 as well as cm nightly based on 4.2.1 with kernel version 3.4.5-g73335a3
Below is logcat snippet from the crash:
D/NativeNfcTag( 620): Connect to a tech with a different handle
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/NfcNciHal( 620): GKI_getbuf() unable to allocate buffer!!!!!
E/NfcNciHal( 620): Failed to allocate GKI buffer
E/USERIAL_LINUX( 620): userial_read_thread(): unable to get buffer from GKI p_buf = 0x0 poolid = 1
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
E/BrcmNfcJni( 620): nfaConnectionCallback: unknown event ????
Any clues much appreciated.
Click to expand...
Click to collapse
Do you know the specific IC used in the tag? I can't recreate this so far.
Additional info:
We run tests on two different ICs: NTAG203 (NXP) and Vera M1HW (Verayo) -- both crash Nexus 10 NFC fairly easily. Up to 10 attempts max. The key is not to expose the tag for long, but swing it instead "teasing" the reader.
We cannot reproduce this problem on Nexus 7 (4.2.1 OS, kernel 3.1.10-g72e6ca1). Despite hundreds of similar tests, we didn't hang the N7's NFC.
We reproduced this problem on two Nexus 10's (to make sure it wasn't a defective unit perhaps).
debriter said:
Additional info:
We run tests on two different ICs: NTAG203 (NXP) and Vera M1HW (Verayo) -- both crash Nexus 10 NFC fairly easily. Up to 10 attempts max. The key is not to expose the tag for long, but swing it instead "teasing" the reader.
We cannot reproduce this problem on Nexus 7 (4.2.1 OS, kernel 3.1.10-g72e6ca1). Despite hundreds of similar tests, we didn't hang the N7's NFC.
We reproduced this problem on two Nexus 10's (to make sure it wasn't a defective unit perhaps).
Click to expand...
Click to collapse
Yep, I think I could reproduce (sort of) the behavior, I tried it with a (NfcA, Ndef, Mifare classic) tag ... as mifare classic is not recognized by the nexus 10, it should be quite similar ....but i needed round about 20 taps...and it´s reproducible .
One strange thing, I also recognized, is that if no 3rd party App with the right tech filter is installed (or background filters disabled)... the nexus 10 will only give you the standard NFC FAILURE sound.
And finally, I think i found the solution .... at least in my case it crashes the receiving app / launcher ... I tried it with only NFC Retag installed as receiver and a new tag... so every scan showed up a "New Tag detected " dialog .... and after ~20 dialogs the app/ launcher hangs ....
after finding that, tried some other tags (with other tech) ... with the same result .... and i can confirm that the nexus 7 has no problems ... so I think (without a deep analysis), it´s some buffer overflow / memory leak within the nfcdispatcher / launcher....after that, the fix was easy 1 line of code within the app....and now everything works fine, no more crashes ... so if you use an dialog to start your app, it´s probably the same problem.
ascsa said:
1 line of code within the app....and now everything works fine, no more crashes ... so if you use an dialog to start your app, it´s probably the same problem.
Click to expand...
Click to collapse
Our activitity is fine -- the UI remains fully operational. The underlaying NFC stack is hosed and doesn't respond to any further contacts with tags. The only way to bring NFC back is to cycle the (system) NFC Settings. After that, the activity reads tags again, until another NFC crash and so on.
We aren't lunched through a dialog. The activity is started manually (not via AAR or blank tag).
AW: [Nexus 10] NFC stack dies after partial NFC-Tag read
debriter said:
Our activitity is fine -- the UI remains fully operational. The underlaying NFC stack is hosed and doesn't respond to any further contacts with tags. The only way to bring NFC back is to cycle the (system) NFC Settings. After that, the activity reads tags again, until another NFC crash and so on.
We aren't lunched through a dialog. The activity is started manually (not via AAR or blank tag).
Click to expand...
Click to collapse
Hmm then, I can't reproduce your error.... After changing the code, I could tap the tag a hundred times and every thing is fine....
Edit: Though about it, this sounds a little bit like the Nexus 10 NfcV issue (NFC stack relies on an optional command, and if this command is not implemented on the chip, the stack crashes immediately)... However seems that in your case something overflows... But as mentioned I could not reproduce it with my test tags...
Sent from my GT-I9300 using xda premium
same issue faced on samsung galaxy 4 for type b tags
ascsa said:
Yep, I think I could reproduce (sort of) the behavior, I tried it with a (NfcA, Ndef, Mifare classic) tag ... as mifare classic is not recognized by the nexus 10, it should be quite similar ....but i needed round about 20 taps...and it´s reproducible .
One strange thing, I also recognized, is that if no 3rd party App with the right tech filter is installed (or background filters disabled)... the nexus 10 will only give you the standard NFC FAILURE sound.
And finally, I think i found the solution .... at least in my case it crashes the receiving app / launcher ... I tried it with only NFC Retag installed as receiver and a new tag... so every scan showed up a "New Tag detected " dialog .... and after ~20 dialogs the app/ launcher hangs ....
after finding that, tried some other tags (with other tech) ... with the same result .... and i can confirm that the nexus 7 has no problems ... so I think (without a deep analysis), it´s some buffer overflow / memory leak within the nfcdispatcher / launcher....after that, the fix was easy 1 line of code within the app....and now everything works fine, no more crashes ... so if you use an dialog to start your app, it´s probably the same problem.
Click to expand...
Click to collapse
Dear Senior Member,
Can you suggest me that 1 line change.
Hi
From the description this looks like an RF stuck, If possible try to use a Field detector to check
Normally The NFC chip switch between poll phase and Listen phase, In the poll phase the chip is looking for a tag to activate and RF field is ON
in The listen phase the chip waits to be activated by something else(like a reader or another phone) and the RF field is OFF, so if you have a field detector the led should be bliking if everything is Okay. If the led is continuously on or off this mean that something is wrong at RF level.
This could be a firmware level issue, in that case you need to alert the chip maker so they can fix
jhonpaul2020 said:
Dear Senior Member,
Can you suggest me that 1 line change.
Click to expand...
Click to collapse
katongo said:
Hi
From the description this looks like an RF stuck, If possible try to use a Field detector to check
Normally The NFC chip switch between poll phase and Listen phase, In the poll phase the chip is looking for a tag to activate and RF field is ON
in The listen phase the chip waits to be activated by something else(like a reader or another phone) and the RF field is OFF, so if you have a field detector the led should be bliking if everything is Okay. If the led is continuously on or off this mean that something is wrong at RF level.
This could be a firmware level issue, in that case you need to alert the chip maker so they can fix
Click to expand...
Click to collapse
Hi guys, this thread and the issues described are 10+ month old ....the , at this time, new broadcom nfc stack had some issues, but most of the issues were resolved ....so I wouldn´t refer to this anymore.
NFC Issue with Note 3
ascsa said:
Hi guys, this thread and the issues described are 10+ month old ....the , at this time, new broadcom nfc stack had some issues, but most of the issues were resolved ....so I wouldn´t refer to this anymore.
Click to expand...
Click to collapse
Dear Senior Member,
The same issue is still there on Note 3 also with Android version 4.3
I purchased my brand new note 10.1 2014 edition 1.5 weeks back (India) and I have been experiencing random rebooting. There was a minor update but that didn't do the trick either. The frequency of reboot seems random (once every 2 days) to 4-5 times a day. I followed multiple posts of various threads and tweaked my Wifi settings, disable auto updates etc but I still see occasional hanging and automatic rebooting
Would like to know if someone is facing similar problems or is there a way to fix this or atleast debug as to consistently reproduce this error. I don't know how I will convince my Samsung service centre as there is no apparent pattern to this. I also did adb logcat on my PC when it crashed but apparently I have no clue what it is throwing at me..
Thanks for your help
Have you tried removing the ext sdcard and monitor if the restart still occurs?
bruce16878 said:
Have you tried removing the ext sdcard and monitor if the restart still occurs?
Click to expand...
Click to collapse
Thanks for your prompt response. I don't have ext SDCard or SIM inserted currently in my device
arvinds123 said:
Thanks for your prompt response. I don't have ext SDCard or SIM inserted currently in my device
Click to expand...
Click to collapse
I took my devide to Samsung service center who re-flashed the firmware but the problem still persists. I notice that restarts occur mainly when apps are updating by Playstore over Wi-Fi connection. Later, after all the updates it restarts when I am using Youtube/Chrome or Stock browser. If I don't update apps the restarts are infrequent/non-existent. Is this a Wifi problem or google app problem? How can I debug and share a trace file with the communiyt? Can some one help me out
arvinds123 said:
How can I debug and share a trace file with the communiyt? Can some one help me out
Click to expand...
Click to collapse
Yes, there is a debugging function. I will add a description later the day (if nobody else was faster).
But when this also happens after a refresh, I would expect a hardware issue. We will see.
EDIT:
I first checked that logcat is enabled on the device: okay
Now you need to install adb on your pc (if you don't did it already). The adb-tool is a part of the Android SDK (by example here) but you only need the platform-tools which includes adb.
Connect the device via USB to your computer and running the following command:
Code:
adb shell "logcat | grep AndroidRuntime" >logcat.txt
(from where you install dab, from a bash, terminal, command line)
This command will log all critical debug output from your android device in this logcat.txt file.
Now you have to wait for a restart (you can use the Note as normal but didn't connect from the computer)
You can stop the command from above (after the unnormal restart)
Post here the result (as attachment) when you didn't see anything in the file by yourself and I will look into it. And maybe send me a PM so I am aware of your post here
Thanks a lot for your prompt response. I immediately tried out your suggestion..Connected to my PC and did what you instructed. I opened the stock browser and was surfing xda forum and soon enough the freeze and restart occured..Pls find the contents of logcat.txt below
------------
D/AndroidRuntime( 6828): D/AndroidRuntime( 6828): >>>>>>
AndroidRuntime START com.android.internal.os.RuntimeInit
<<<<<<D/AndroidRuntime( 6828): CheckJNI is
OFFD/AndroidRuntime( 6828): setted country_code =
UAED/AndroidRuntime( 6828): setted countryiso_code =
AED/AndroidRuntime( 6828): setted sales_code =
XSGD/AndroidRuntime( 6828): readGMSProperty:
startD/AndroidRuntime( 6828): readGMSProperty: already
setted!!D/AndroidRuntime( 6828): readGMSProperty:
endD/AndroidRuntime( 6828): addProductProperty:
startD/AndroidRuntime( 6828): Calling main entry
com.android.commands.am.AmD/AndroidRuntime( 6828):
Shutting down VMD/AndroidRuntime( 6856):
D/AndroidRuntime( 6856): >>>>>>
AndroidRuntime START com.android.internal.os.RuntimeInit
<<<<<<D/AndroidRuntime( 6856): CheckJNI is
OFFD/AndroidRuntime( 6856): setted country_code =
UAED/AndroidRuntime( 6856): setted countryiso_code =
AED/AndroidRuntime( 6856): setted sales_code =
XSGD/AndroidRuntime( 6856): readGMSProperty:
startD/AndroidRuntime( 6856): readGMSProperty: already
setted!!D/AndroidRuntime( 6856): readGMSProperty:
endD/AndroidRuntime( 6856): addProductProperty:
startD/AndroidRuntime( 6856): Calling main entry com.android.commands.am.AmD/AndroidRuntime( 6856): Shutting down VM
-----------------
See if this helps..Let me know if you require me to do anything else
arvinds123 said:
Thanks a lot for your prompt response.
Click to expand...
Click to collapse
So fat, nothing unusual.
Try now without filtering via grep:
Code:
adb shell "logcat" > logcat.txt
And this time didn't post the results here as text because this will be now megabytes but add it as attachment. Thx.
PS. "com.android.commands.am.Am" is the main activity manager and here something pops up which then terminate the parent process. This can be normal or anything. Therefore we have to see what really happens here.
I was having the issue with my SM-P601. It turns out it was using the travel wallpaper on the lock screen that was causing it. Once I went to another stock wallpaper my device hasn't rebooted since. If you're not using the travel wallpaper you might want to play around with your home and lock screen wallpapers to see if it has any affect.
Hi all,
Thanks for all inputs, I'm also facing the same issue as the OP so I hope we can find solutions for this because this is a great tablet and all. I just tried change Wallpaper & lockscreen as the poster above suggested. Hopefully this cure the random freeze/reboot.
BarryH_GEG said:
It turns out it was using the travel wallpaper on the lock screen that was causing it.
Click to expand...
Click to collapse
I am also you this without and reboots until now. But the day it starts, I will remember your post
Elim said:
So fat, nothing unusual.
Try now without filtering via grep:
Code:
adb shell "logcat" > logcat.txt
And this time didn't post the results here as text because this will be now megabytes but add it as attachment. Thx.
PS. "com.android.commands.am.Am" is the main activity manager and here something pops up which then terminate the parent process. This can be normal or anything. Therefore we have to see what really happens here.
Click to expand...
Click to collapse
I did that for 4 hours.. No reboots and no reboots since.. It has been 15 hours and no reboots. Really surprising. I always have had the stock wallpaper so that could not have been the issue. This is weirdest issue I have seen with an Android device in years.
arvinds123 said:
I did that for 4 hours.. No reboots and no reboots since.. It has been 15 hours and no reboots. Really surprising. I always have had the stock wallpaper so that could not have been the issue. This is weirdest issue I have seen with an Android device in years.
Click to expand...
Click to collapse
After observing the tablet over a week. I found out the random restart occurs mainly due to auto-downloading of apps. I had disabled auto updates in Googe Play/Samsung Apps but it rebooted again when Google Now began downloaded offline voice files automatically after 72 hours of use. Clearly looks like a software issue. Has anybody noticed a similar problem on other samsung devices (looks like not many have a Wifi + 3G SM-P601 model here).
arvinds123 said:
After observing the tablet over a week. I found out the random restart occurs mainly due to auto-downloading of apps. I had disabled auto updates in Googe Play/Samsung Apps but it rebooted again when Google Now began downloaded offline voice files automatically after 72 hours of use. Clearly looks like a software issue. Has anybody noticed a similar problem on other samsung devices (looks like not many have a Wifi + 3G SM-P601 model here).
Click to expand...
Click to collapse
In my case, I found that tablet reboot when installing/update apps from play store will the SanDisk 64gb sd card was in. So I just exchange the sd card with Samsung 64gb and no more reboot during update / installation.
funfun99999 said:
In my case, I found that tablet reboot when installing/update apps from play store will the SanDisk 64gb sd card was in. So I just exchange the sd card with Samsung 64gb and no more reboot during update / installation.
Click to expand...
Click to collapse
However I don't have an extSDCard or a SIM Card inserted. Is it expecting one and that's why it's crashing? I am so disappointed with this tablet..Wants me to run back to the iPad
I have same problem after root and use gsm voice call with callrecorder app and bluetooth but after reconfigure callrecorder app to api, no more random reboot.
After tried to change lockscreen & wallpaper I still facing randomly rebooted. I also tried with Dolphin browser & Chrome and both got rebooted while surfing too. There were time after it got rebooted and loaded to lockscreen where I begin put in lockscreen pattern password and then it hung and rebooted again. However after the 2nd in a row rebooted it managed to not reboot again for couples hours. I disabled auto update in both playstore and Samsung hub but still got rebooted. So hopefully someone who managed to fix this permanently detailing their methods would be helpful for us. Thanks
I have SM-P601, it has sudden reboot after completing setup, and then stuck at samsung logo, I tried recover with Kies but still the same, so tomorrow will have to take it to the Samsung service center. Very dissappointed with this Samsung build
Experiencing reboot issues
Hi I purchased my 2014 edition approx 2 months ago from best buy. I'm now experiencing reboots issues and issues with my screen going to sleep. When powering on the device, it boots up to the login screen or sometimes just the Samsung logo and then reboot several times. After it reboots the device allows me to log in; however if I don't type in my password Fast enough the screen goes to sleep and I can not wake it up by pressing the center button. I have to do a hard reset, and go through the process again. Also after I'm finally able to log In, I have my device set to go to sleep after 30 mind of no use. This is to prevent it from going to sleep too soon if I need to throw it in my bag as the train approaches, or I want to listen to some music; however once it goes to sleep I'm not able to wake it with the center button, and again have to do a hard reset.
I'm a poor artist and I wanted the best tablet to consolidate devices and be my all in one, So far this tablet has been bad ass! I could not afford the insurance and rely on a Tucan case from frys to protect her. I want my baby back to her normal self. How do I get this issued fixed? I'm already salty she has a tiny crack in the corner from me following the YouTube video on how to remove her case. I did that because I wanted to see if there was any debris under the power button that was causing it to reboot.
Thanks All.
Sorry to bump an old thread...but i just bought the p600 model..second hand. It was rooted with supersu and it would reboot randomly but especially when auto updating apps and browsing the web with chrome.
I seem to have fixed the issue. First thing i did was undoing the root. However..i noticed that supersu could not be uninstalled at all even when the rooting had been reversed.
I proceeded to apply another version of the official firmware..(used odin 3.07 and got the firmware from sammymobile) i think i had a xac version (or something like that) from april with kitkat 4.4.2....and i went for a bov version from june with 4.4.2 kit kat. I was now able to uninstall supersu like any other app.
I have not experienced another random reboot since then...and ive been browsing the web with chrome. Ive also had apps autoupdating.
The only difference i can perceive now is that i did not have the peel app used to control the tv and now it was preloaded. Also..the first time i booted the tablet after applying the new firmware i got this 'apps being optimized' message.
Hopefully this helps.
sorry for the double posting
the issue came back, after months of experimentation the only thing that gave me some stability was using the hydronium rom. I never got rid of reboots 100%, but with this rom the device was usable. I don't know if it's because of the rom itself or because it includes thomas' kitkat reboot fix for galaxy s4. "thofmann.blogspot.de/2014/07/fixing-random-reboots-on-samsung-kitkat.html"
I tried his reboot fix with the stock rom but it never worked. so I stuck with hydronium, lesser evil of all.