Tf700 Random Reboots. Anyone else or just me?

elfaure said:

This is the fix guys. Worked wonders for me. No more random reboots. Still get app and Asus taskmanager crashes though. Also fixes some BS player and wifi streaming issues.:good::laugh:

TF700T 32 GB, JB 4.1.1, Stock Locked Unrooted, 64GB Sandisk Ultra Class 10 SDHX, Seagate Wireless Plus 1TB streamer

---------- Post added at 10:44 PM ---------- Previous post was at 10:31 PM ----------



I found it on Transformerforums.com in the 300 section searching for "freeze". Found a short thread on a guy playing cards, gin I think, having random crashes and the same fix cited. If this works for most please get the word out!!:laugh:

Click to expand...

Click to collapse

Didn't work for me.

dmitryu said:

With such non-deterministic issue it must be difficult to pinpoint...
For instance, I haven't had any issues for 3 weeks already, ever since I had a couple of weeks travel

I hypothesized that absence of problems during the travel had something to do with network/local wifi, but now I'm back home and ok for a week already. So much for the scientific approaches...
Would be funny if I wont have issues ever. Nothing was changed in config, no dev options, just the usual work...

Of course it may be some piece of solder finally falling off some pins during handling

Click to expand...

Click to collapse

Interesting...
I've wondered at times if poor wifi performance was in some way causing a browser reboot.
Done a few router resets and re-positioned ours just for grins sometime back and haven't had a crash since.
Yet I would have to attribute my tabs stable performance to customization more than anything.

Meanwhile, I registered reboot (though with black screen this time).

29 days, 44.35 hrs active time, 76 standby/active cycles since the recent one.
One week after returning home (and I guess more active usage, network and otherwise).

So, they wound up repairing it for free! I am beside myself. I am not sure what was done. Will report back. In the meantime, I was so ticked off about the whole thing I went out and got a Nexus 7. That thing is schmoove. I love it.

Would be very interesting to hear if the thing was repaired indeed, especially after some time -- will help others to decide what to do with it...

Apparently my device reboots with approx. same "few days" statistics after returning home from my travel.

dmitryu said:

Would be very interesting to hear if the thing was repaired indeed, especially after some time -- will help others to decide what to do with it...

Apparently my device reboots with approx. same "few days" statistics after returning home from my travel.

Click to expand...

Click to collapse

Got it back! No charge. I think they repaired the creaky screen for starters. Secondly, the only comments regarding the repair was -
"Error after FOTA/firmware update"

The S/N is the same but my Wi-fi MAC is different. I guess they replaced the board. I hope its not a refurb. On to the testing. It is on 4.1.1 and I am reluctant to update it now... I am going to play with it without updating it for 2 weeks or so.

One final note...

I suddenly awoke one night and remembered that my precious 32 G Micro SD card may have been left installed in the tablet. Low and behold it was and they sent it back to me. I am forever grateful. I did have a Titanium Backup folder and 2 TWRP backups on it... ugh. I just got done changing all my passwords. Took about 1 hour. And, no - I don't feel that it was due... LOL

I am happy. Now my gf gets to use the Nexus 7 and she is happy too.

Rebooted, white screen upon ebay app first run.

updating the firmware now to 10.4.4.25...

That's the scenario I've been afraid of -- going through the exchange/repair troubles ending up in the same position...

FYI - I've *never* had a random reboot or sleep-of-death with my TF700 (which I've owned since it was released) until the past few days, which I've now had 2 of them.

After thinking about it, I have a feeling that *my* reboots were caused by the TricksterMod app (and/or the settings that I used in the app), which I just recently installed. I've now un-installed the app and will see if the problem returns or not - I will keep you updated as to whether or not the reboots return or not.

Just an FYI...

Thanks.

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:

FYI - I've *never* had a random reboot or sleep-of-death with my TF700 (which I've owned since it was released) until the past few days, which I've now had 2 of them.

After thinking about it, I have a feeling that *my* reboots were caused by the TricksterMod app (and/or the settings that I used in the app), which I just recently installed. I've now un-installed the app and will see if the problem returns or not - I will keep you updated as to whether or not the reboots return or not.

Just an FYI...

Thanks.

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Click to expand...

Click to collapse

Well, that was quick! Just happened again while I was actively using the system - screen went black and then I eventually get held the power button in for 10 seconds to force it to restart.

I'm going to post the so many lines of /proc/last_kmsg, just in case someone can help with figuring out what is causing this - it's driving me crazy now...


[ 10.574212] asuspec: [asuspec_enter_s3_work_function] EC in S3
[ 11.748324] cpu ext_temperature=36
[ 13.437347] EXT4-fs (mmcblk0p8): warning: maximal mount count reached, running e2fsck is recommended
[ 13.441417] EXT4-fs (mmcblk0p8): ext4_orphan_cleanup: deleting unreferenced inode 1631530
[ 13.441692] EXT4-fs (mmcblk0p8): ext4_orphan_cleanup: deleting unreferenced inode 1630928
[ 13.442060] EXT4-fs (mmcblk0p8): ext4_orphan_cleanup: deleting unreferenced inode 1631506
[ 13.442250] EXT4-fs (mmcblk0p8): ext4_orphan_cleanup: deleting unreferenced inode 1630923
[ 13.442427] EXT4-fs (mmcblk0p8): 4 orphan inodes deleted
[ 13.442501] EXT4-fs (mmcblk0p8): recovery complete
[ 14.204098] EXT4-fs (mmcblk0p8): mounted filesystem with writeback data mode. Opts: (null)
[ 14.242179] EXT4-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[ 14.249075] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[ 16.758333] cpu ext_temperature=36
[ 21.692573] asuspec: [asuspec_send_ec_req] send EC_Request
[ 21.754642] asuspec: [asuspec_work_function] 0x2 0x81 0x50 0xff
[ 21.754776] asuspec: [asuspec_smi] ASUSPEC_SMI_HANDSHAKING
[ 21.768332] cpu ext_temperature=37
[ 21.961139] pad_get_capacity val->intval=74 ret=75
[ 21.966096] pad_get_psp val->intval=Charging ret=80
[ 22.964282] asuspec: [asuspec_enter_s3_work_function] EC in S3
[ 24.110051] EXT4-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[ 24.117153] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[ 24.286601] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 24.591280] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 24.804958] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 26.678260] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 26.778371] cpu ext_temperature=37
[ 26.888323] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 27.993864] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 28.194201] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 28.937026] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 29.134807] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 29.376568] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 29.654758] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 29.932109] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 30.215274] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 30.409599] EXT4-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[ 30.416789] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[ 30.521383] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 30.522119] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 30.807420] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 31.100393] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 31.386114] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 31.624952] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 31.788344] cpu ext_temperature=37
[ 31.903083] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 32.187632] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 32.470434] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 32.756551] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 32.959695] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 33.887592] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 34.082406] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 34.855778] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 35.057957] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 35.108451] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 35.185816] EXT4-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[ 35.193211] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[ 35.304847] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 35.594131] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 35.878765] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 36.161865] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 36.398671] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 36.679058] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 36.798377] cpu ext_temperature=37
[ 36.964149] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 37.246404] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 37.530375] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 37.813141] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 38.098252] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 38.384318] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 38.582067] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 41.808335] cpu ext_temperature=37
[ 44.764833] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 44.972039] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 46.818327] cpu ext_temperature=37
[ 47.412806] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 47.620935] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 49.993187] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 50.180222] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 51.723023] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 51.828334] cpu ext_temperature=37
[ 51.905823] EXT4-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[ 51.913070] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[ 51.932053] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 52.188031] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 52.479420] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 52.779071] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 53.066660] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 53.314292] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 53.616175] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 53.915179] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 54.216892] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 54.515943] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 54.817149] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 55.116420] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 55.417600] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 55.716734] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 56.026645] tegradc tegradc.0: Using mode 1920x1200 pclk=154012000 href=0 vref=1
[ 56.838773] cpu ext_temperature=37
[ 61.621986] rt5631_i2c_shutdown+ #####
[ 61.623436] rt5631_i2c_shutdown- #####
[ 61.623575] tegra_dc_shutdown+, ndev->name=tegradc ####
[ 61.623648] tegra_dc_shutdown-, ndev->name=tegradc ####
[ 61.623776] tegra_dc_shutdown+, ndev->name=tegradc ####
[ 61.638397] Check cardhu_panel_disable in TF700T
[ 61.738448] tegra_dc_shutdown-, ndev->name=tegradc ####
[ 61.738634] tegra_ehci_hcd_shutdown instance 2 +
[ 61.738724] tegra_ehci_shutdown instance 2 +
[ 61.738862] tegra_ehci_shutdown instance 2 -
[ 61.738933] tegra_ehci_hcd_shutdown instance 2 -
[ 61.739084] Restarting system.
[ 61.739155]
[ 61.739224] Restarting Linux version 3.1.10-g6e3fd95 (dees_troy@xlii.teamw.in) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Fri Oct 5 16:11:55 EDT 2012
[ 61.739233]

No errors detected



Does any of this mean anything to anyone? I can't tell *why* it shutdown....

Thanks!


Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jtrosky said:

I'm going to post the so many lines of /proc/last_kmsg, just in case someone can help with figuring out what is causing this - it's driving me crazy now...

...
[ 61.739224] Restarting Linux version 3.1.10-g6e3fd95 (dees_troy@xlii.teamw.in) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Fri Oct 5 16:11:55 EDT 2012

Does any of this mean anything to anyone? I can't tell *why* it shutdown....

Click to expand...

Click to collapse

This log is from the recovery, with a total uptime of 61 seconds ... apparently you booted into the recovery after crashing, and this is the last log - your original log from the crash is lost.

jtrosky said:

Well, that was quick! Just happened again while I was actively using the system - screen went black and then I eventually get held the power button in for 10 seconds to force it to restart.

I'm going to post the so many lines of /proc/last_kmsg, just in case someone can help with figuring out what is causing this - it's driving me crazy now...


Does any of this mean anything to anyone? I can't tell *why* it shutdown....

Thanks!

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Click to expand...

Click to collapse

In order for a quick process of elimination, I recommend you should perform the following:
** Take a full nandroid backup using TWRP.
1. Not to use fsync or data2sd.
2. Reformat your SDcard (use TWRP and wipe everything, specially "Format SDcard", this should fix any internal corruption.
3. Install CROMI from scratch with no fsync, seeder or lagfix, and use stock kernel
See if reboot stills there or not.

_that said:

This log is from the recovery, with a total uptime of 61 seconds ... apparently you booted into the recovery after crashing, and this is the last log - your original log from the crash is lost.

Click to expand...

Click to collapse

Ahh, that makes sense since I did go into recovery in order to try wiping cache, dalvik cache and fixing permissions (some I generally do to start my troubleshooting process) - didn't realize that overwrote the last_kmsg log though! Thanks for clearing that up - I will remember that for future use).

Before I go to more drastic measures, I just removed some of the last few apps that I've installed (I installed about 5 or 6 wifi-detection-related apps) - so far, no more issues, but it's only been 8 hours of mostly non-use, so we'll see.... If that seems to clear up the problem, I'll post which apps I removed. I did not remove them one-by-one though so I couldn't pinpoint the exact culprit (I was in the middle of trying to work remotely using my TF700 with Jump Desktop, which was going great before the reboots). Jump Desktop is a great RDP/VNC app - I must say - worth every penny.

Anyway, I will be sure to report back - thanks for the replies guys - I appreciate it!


Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

FYI - my reboots have not come back, so I have to assume that they were directly related to one of the wifi apps that I recently installed (and then un-installed).

If anyone is interested, I can figure out what apps they were that I removed and post a list here...

Thanks.

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

I think it indeed might be the case that wifi has something to do with the problems. This aligns well with my experience of longest problem-free run of 2 weeks while I was travelling with limited wifi access. It might be just raw frequency/intensity of wifi usage, or some specific patterns which can be provoked by some application.
I tend to believe in the former, since I havent seen any correlations with actual applications.

While I'm home, days-to-failure distribution looks like exponential law more or less. Which suggests random & independent distribution of the triggering events. Poisson process

Btw, current statistics, now with histograms

https://docs.google.com/spreadsheet/pub?key=0AtWC8vr3mCUJdDFiUnByT3Z0NlpCT0JrcVpLRHl2QVE&output=html

Hello. I also want to get to the bottom of this rebooting issue. I'll contribute something:
It is definitely not related to overloaded ram; I experienced a reboot 2 hours ago after spending about two days of consistently closing applications to avoid RAM overload. The machine rebooted with only Chrome open (2 tabs).

Immediately after the reboot, I had a notification from the XDA Developers app, so of course, I removed the app and I'll post here if I get another reboot.

Are you guys using "browser2ram" ?
I had a lot of reboots while browsing regardless of which browser.
After I installed "browser2ram" no more reboots so far for 2 weeks, and I really haven't cold booted to my recollection.

Yes this device is very very sensitive to wifi, bluetooth, glitchy network issues in general. I would have to say poor error trapping in the code is the issue. For example I was watching a movie the other night and decided to turn in. I tether this pad to my phone for internet access. As soon as I turned off my wifi (3g) hotspot on my phone (HTC DINC2), the movie stopped playing and the pad went to the home screen.

Another example is with bluetooth. Unfortunately I can't remember exactly what it was, but something to do with having my BT keyboard connected was causing some app some indigestion. I finally figured out that the problem only was occurring when my BT keyboard disconnected automatically after 10 minutes of non-use and it crashed the app. Oh! Now I remember, it was with My Backup Pro. I would start a backup, but it would never finish. Because I started it with the keyboard connected, and when it disconnected the backup just stopped. No error, no log, just quit. And it left and incomplete backup on my drive with no indication that it was incomplete. This was a hard one to diagnose.

I just discovered a glitch with brower2ram. Has to do with editing and selecting text in a text box, like an online form or a forum post. When I try to select text with the double-blue grab handles and drag the handles to back and forward select more/less of the text, it doesn't work. Sometimes it leaves a floating zoom window just stuck there. After some strategic troubleshooting i was able to disable browser2ram at startup and the problem went away.

Another glitch was BS and MX player both lost the left brightness control? I disabled a few startups related to screen (Backlight Switch, Screen Brightness Control) and the problem went away. I re-enabled the same apps and the problem did not come back until the next boot. I believe it has something to do not only with what startups, but also in WHAT ORDER are they loaded. Lots of little glitches to work thru with this device on the stock ROM, that is a fact. I believe that is the main reason so many non-proficient people go Apple over Android. Its more polished, more tested, and they work these things out at the factory not the street. I see Android like I see Windows. They both use the general population as beta testers for the most part.

Sent from my ASUS Transformer Pad TF700T using xda app-developers app

I'm sorry, but most of the "glitches" mentioned in the last post are app-specific issues that Asus and Google have no control of. You can't expect Asus or Google to be able to test every single app and combination of apps, especially once your root your device.

Besides, if you do a Google search for "ipad random reboot", you will see that Apple products experience some of the same issues...

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

No device is perfect including iPAD. But aren't most glitches app-specific? You don't just boot your OS and look at your homescreen do you? No, you get the apps that suit you and you run them. And only a fraction are made by Google and Asus only makes utilities for their devices, not apps for the open market. So what are you left with? 97 percent of the other apps on the market. So PLEASE don't go defending Android just because you are on a dev site for their OS when what you are saying has no merit. These are main stream top paid apps I listed that I've had issues with: My backup Pro, BS Player (Paid), MX Player Pro, and the infamous Browser2RAM which was developed specifically for the Transformer Prime mind you, which has an identical hardware platform as the Infinity less the CPU, and it still glitches.

I've had so many other glitches unlisted with this device I could scream, ES products as well. If you think Apple products are glitch-equivilent then you are fooling yourself in my opinion. I've had the same iPOD for 6 years and its reset itself once. Their devices are better made, better tested, have better market apps, and if you can give up expansion and customization which I can't, they are much less hassle to use on a daily basis. I don't necessarily believe they have better hardware as this device is quality hardware, fit, and form, but not function. Don't get me wrong, I dislike Apple and prefer Android, but at an added user frustration level I accept because I don't mind troubleshooting the problems and learning about the OS and the device. Its been kinda my new hobby lately but it ain't for most I would think. Android has come a long way since Froyo but its got a long way to go to match Apple reliability. I highly doubt they have users with so many varied cited problems.

Sent from my ASUS Transformer Pad TF700T using xda app-developers app

---------- Post added at 11:22 PM ---------- Previous post was at 11:16 PM ----------

Rooting my device has dramatically reduced the number of glitches I have, in no way increased them. Rooting has given me the rights by which I can remedy the problems native to the stock OS, mainly free RAM so apps can run clean.

Sent from my ASUS Transformer Pad TF700T using xda app-developers app