Develop Bugs

[Q] Stock Froyo Wi-Max errors = shortened battery life?

I was using aLogcat earlier and noticed an error being scrolled every few seconds. If you turn 4G on it will start and the only way to stop it is to reboot and not use 4G.
Does anyone know how to fix this or what is causing it? Whatever DC is it looks like it is trying to connect to a server and update, but for some reason is it using the loopback address.
A google search showed people on the Aria are seeing this same issue and they don't know what it is either.
From the log:
I/LSState : EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/LSState : EventReceiver:android.intent.action.NOTIFICATION_UPDATE
I/Wimax : <DC> Try to establish a connection to DC server.
E/Wimax : <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refused'

that error looks somewhat similar to one that root users where having with 4g not working...as far as i know the fix they came up with only works with su permission..i could be wrong...wouldnt hurt to poke around dev forum

hmm, I've been using google to search for it and haven't been able to find the thread you are referring to yet. In the mean time I guess I will just leave 4G alone.

[Nexus 10] NFC stack dies after partial NFC-Tag read

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

[Q] Random Reboot and Audio Issue

https://drive.google.com/folderview?id=0ByITINOB1gxMS0RfRUduVjlaOEU&usp=sharing
^^^ Finally figured out log cat ^^^
So ladies and gentlemen after a couple weeks of searching and experimenting, i figured I would bow to the experience and knowledge of others and see what my betters thought of the puzzle i have at hand.
I purchased a T-Mobile Note 2 from a gentleman on CL. The seller mentioned that it randomly rebooted and that was the reason he was selling it. I figured, for the price, it would be worth to take, play around with and get it working again.
I took it home, rooted it with the CF Autoroot, installed CWM, and flashed a number of ROMS, cm10.2, the latest paranoidandroid, jellybeer, beanstalk, Etc. none of them stopped the random reboot issue. the only noticeable change was with the 4.3 cm10.2. It lessened the frequency of the reboots.
Also, as far as i can tell, it shouldn't be having the chipset issues, its MAG4FB, Revision 0xf7, and brickbug has it logged as having the sane chip.
Now here is the kicker, somewhere along the way, the sound stopped working. Whereas originally i had audio, the jingle would play when booting up, now there is no audio/media. No music or sound, youtube will not even play videos, the music players will either force close or look like they are playing a song, but not sound plays. Also, sound recorder shows an internal app error, and google now says it cannot access the mic. Even the phone camcorder will not record video or sound (though the camera will take pictures still). Plugging headphones doesn't yield any result. no music, no notification, nothing (even though i may have the setting for music app to open upon plugging in headphones)
So, with all this, any ideas? suggestions?

It seems the encoder components have faults. You may post some logs to help figure out the problem.
Try the logcat manual from today's XDA portal.
Sent from my HTC One using XDA Premium 4 mobile app

vecio said:
It seems the encoder components have faults. You may post some logs to help figure out the problem.
Try the logcat manual from today's XDA portal.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Finally figured out logcat and added it above.
Tried out Youtube, Apollo Media Player, Google Search, and the Stock Sound Recorder. All failures.
From what i can gather, there seems to be an error with anything media related. Here's a taste of the errors. Any thoughts?
W/AudioPolicyManagerBase( 1945): getOutput() could not find output for stream 1, samplingRate 0,format 0, channels 3, flags 0
E/ActivityThread( 3803): Failed to find provider info for com.android.athome.mediaroute.provider
E/AudioTrack( 2364): Could not get audio output for stream type 1
E/SoundPool( 2364): Error creating AudioTrack
I/AudioService( 2364): AudioFocus abandonAudioFocus() from [email protected]
E/AudioRecord( 4333): Could not get audio input for record source 6
E/AudioRecord-JNI( 4333): Error creating AudioRecord instance: initialization check failed.
E/AudioRecord-Java( 4333): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.
I/decoder ( 4333): ERROR: Exception thrown from GoogleRecognizer.read()
W/System.err( 4333): java.io.IOException: AudioRecord failed to initialize.
W/System.err( 4333): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:134)
W/System.err( 4333): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:213)
W/System.err( 4333): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
W/System.err( 4333): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
W/System.err( 4333): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
W/System.err( 4333): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
W/System.err( 4333): at java.io.InputStream.read(InputStream.java:163)
W/System.err( 4333): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:209)

Also fun fact, phone doesn't reboot when usb connected to the computer, so can't seem to get logcat of the reboot situation

From the logcat, it seems you have connected your device to some external display or speaker?

vecio said:
From the logcat, it seems you have connected your device to some external display or speaker?
Click to expand...
Click to collapse
But I haven't. And wouldn't that connection end after numerous flashes?

MTJ061289 said:
But I haven't. And wouldn't that connection end after numerous flashes?
Click to expand...
Click to collapse
The log just suggests the AudioRecord needs to get output from some external devices.
The "Failed to find provider info for com.android.athome.mediaroute.provider" seems your ROM miss something related to the MediaRouter feature.
Have you tried to swipe cache/data? Or update to the latest version of your ROM.

vecio said:
The log just suggests the AudioRecord needs to get output from some external devices.
The "Failed to find provider info for com.android.athome.mediaroute.provider" seems your ROM miss something related to the MediaRouter feature.
Have you tried to swipe cache/data? Or update to the latest version of your ROM.
Click to expand...
Click to collapse
I have clean flashed multiple different roms, including flashing it back to stock yet the problem persists.

MTJ061289 said:
I have clean flashed multiple different roms, including flashing it back to stock yet the problem persists.
Click to expand...
Click to collapse
Then I have no ideas:what:
Sent from my HTC One using XDA Premium 4 mobile app

[Q] My SM-P601 Random Reboots. Kindly help

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.

Galaxy tab s 10.5 screen freezes

Please help me read these lines from the bug report:
09-04 22:58:04.329 944 4007 D SSRM:n : SIOP:: AP = 430, PST = 422, CUR = -1075
09-04 22:50:51.837 944 4007 D SSRM:n : SIOP:: AP = 450, PST = 448, CUR = -1758
These are 2 separate instances of the tab freezing. Often during Madden Mobile. Plenty of free RAM and storage, tried a couple factory resets. Very few apps installed. The software continues to operate but wont accept any touch input on the screen or touch buttons. A soft reset and it works fine for another minute or hour until it freezes again. I have the entire 18 Mb bug report if there is more information needed. Samsung and Verizon will do nothing because I can't replicate it in safe mode. No other madden mobile and tab s user has complained of this issue.
Thanks for the help.