[Q] Newly Rooted TF101 is resetting time and date - Eee Pad Transformer Q&A, Help & Troubleshooting

HI
I got a new (to me - but it looked like new anyway) TF101 for my OH, rooted it using PERI as Easyflasher just would not take, installed KatKiss 4.3 v29 and it is running fine, except, when my OH turns it fully off and restarts it the time resets to 00.00 Jan 01 2000.
This does not happen with my TF101 which is running the same ROM.
I have tried it with both auto time and date and with manual time and date and neither stop this from happening. As soon as she connects to wireless and has auto time/date enabled it corrects itself but I'm curious as to why this is happening. Does the Bios (do tablets have a bios) have a separate battery like PCs have.
Any help will be greatly appreciated and thanks for all help in the past year and have a Great New Year everybody

Nobody? Wow didn't think this issue was that rare/difficult.

Theziggy said:
HI
I got a new (to me - but it looked like new anyway) TF101 for my OH, rooted it using PERI as Easyflasher just would not take, installed KatKiss 4.3 v29 and it is running fine, except, when my OH turns it fully off and restarts it the time resets to 00.00 Jan 01 2000.
This does not happen with my TF101 which is running the same ROM.
I have tried it with both auto time and date and with manual time and date and neither stop this from happening. As soon as she connects to wireless and has auto time/date enabled it corrects itself but I'm curious as to why this is happening. Does the Bios (do tablets have a bios) have a separate battery like PCs have.
Any help will be greatly appreciated and thanks for all help in the past year and have a Great New Year everybody
Click to expand...
Click to collapse
I know this post is a little old, but I had the same issue with my TF101 and I managed to fix it.
I noticed after watching a tear down video there was a very small cmos like battery at the top of the device. I figured that my battery must be dead and decided I'd take a crack at opening it up and replacing it.
Turns out the battery wasn't dead. One of the wires had broken (if it was ever properly connected at all) right at the connector. I used a razor blade to clean the broken wire out of the connector, cut the frayed end of the wire off and pressed it into the connector (the connector is self tapping similar to a RJ-45 cable end).
It's no longer New Years Eve everytime I turn the tablet on!

another solution that doesn't require to open the device is to install NTPsync and auto sync at boot.
Regards

Related

[Q] DIP Switch

Does anyone know what the DIP switch located in the transformer is for? The only thing I found is a post mentioning a different wifi setup.
My experience messing with it is that the transformer won't turn on when it is in the up position unless the tablet is plugged into its charger.
Please see post 7 for the issue I am experiencing and how the Dip switch is involved.
thatton13 said:
Does anyone know what the DIP switch located in the transformer is for? The only thing I found is a post mentioning a different wifi setup.
My experiance messing with it is that the transformer won't turn on when it is in the up position unless the tablet is plugged into its charger.
Click to expand...
Click to collapse
Search Been discussed before
I did search, here and Google many times over the past month. Only found 1 post with the info that I mentioned.
"The only thing I found is a post mentioning a different wifi setup"
If I overlooked something I would appreciate a push in the rite direction. Or is that all the info there is?
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
gee one said:
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
Click to expand...
Click to collapse
While the OP might not...I found your response highly amusing
Post 90-94
http://forum.xda-developers.com/showthread.php?p=16812367#post16812367
Its use is still unknown, but at least the post confirms the behavior that the OP is seeing.
gee one said:
Off the top of my head, I thought it was the switch that disables the battery? Somewhere, in a galaxy far, far away, there is a thread, and buried deep in that that thread, someone speculated that the ASUS techs use that switch to shunt the battery when they service bricked TFs so that the flux capacitor doesn't blow up and send us all back to the 80s. OK, maybe that's a bit of a strech, but I do think it has something to do with the battery.
Click to expand...
Click to collapse
Nice! Especially the Back to the Future reference. Allow me to explain my situation and why I am so interested in that tiny switch.
I purchased my Transformer from Newegg back in July or August. It was an open box and I saved around $150 because of that. Unfortunately that means it only had a 1 month warranty, this brings us to my problem. It runs great but every once in a while a lot of the apps, including the browser, will force close. Also if I go in to settings once this problem starts and shut off the WiFi and then try to turn it back on it just says error. Trying to turn on Bluetooth also does not work.
The solution is to reboot, however, it will only run for a short while before the problem returns. I have tried the stock rom rooted and unrooted, I have tried various roms, revolution, prime, revolver. After flashing a rom or doing a factory reset the transformer will run for around 12 hours without the above mentioned problem but it always comes back and it happens more and more frequently until I do a factory reset.
I have tried countless things. Various roms as mentioned, factory resets, freezing as much as I can using titanium backup, not adding a Google account, turning off gps, different wireless networks, assigning a static ip address, using ExtSd2InternalSd v2.1 to install apps on an sd card. All of this with no success.
Enter that dip switch. I decided since my warranty was over I would open it up and do some poking around. I discovered if I put that switch in the up position and boot the transformer with it plugged into the charger it runs perfectly stable. The issue is gone. only problem is that I can only use it plugged in. This situation lead me to the conclusion that it is a power supply issue, maybe a defective battery (Not getting the full 1.21 gigawatts . So.... I switched out the battery in my dock with the one in the transformer and put the dip switch in its original down position..... No Luck, the problem persisted. Return the switch to up and plug it in, runs great.
Anyone have an idea?
How does it run while the switch is down (in the crappy position) and plugged in?
gee one said:
How does it run while the switch is down (in the crappy position) and plugged in?
Click to expand...
Click to collapse
The problem is still there. I even tried it in the down position with the battery disconnected and the transformer plugged into the charger but the problem continued.
I guess it could be a power/hardware issue or maybe a sleep/software issue. Perhaps it doesn't sleep while it's plugged in?
Regardless, it's quite an interesting problem.
gee one, thanks for your help. Maybe someone will come up with a fresh idea, I have tried most of what I can think of.
I might try the dual boot Ubuntu thing to see if I have the problem in Ubuntu. I figure that mite help narrow down if it is a software or hardware problem. I lean towards hardware because I have not been able to find others with this issue. Then again, maybe others that have had this problem had a warranty and returned it for an exchange.
gee one said:
Perhaps it doesn't sleep while it's plugged in?
Click to expand...
Click to collapse
Forgot to mention, I tried setting the screen to never shut off in hopes that it would prevent the transformer from sleeping. Not sure if there is another way to prevent it from sleeping? Whatever the case leaving the screen on did not prevent the problem from surfacing.
Install ROM Manager and tell it to Fix Permissions?
I've had extensive FCs on some devices I've rooted and fixing the permissions has helped.
Col.Kernel said:
Install ROM Manager and tell it to Fix Permissions?
I've had extensive FCs on some devices I've rooted and fixing the permissions has helped.
Click to expand...
Click to collapse
Thanks for the suggestion. Unfortunately I have cwm installed and have ran fix permissions and while it did help with some of the apps force closing it did not fix my problem.
I was about to ask where this switch was at because I've never seen it, then I read that it's inside the unit. I have no reason to crack this bad boy open yet so that's why I had no idea about it.
It is a battery kill switch, makes it easier to work on without blowing the **** out of the unit by bridging the wrong points on the board for what ever reason. basically with the switch up it is a "service mode"
Need Help with ASUS TF101 back light Out . ! An dip witch . ?
So did u ever find out what the Dip Switch was my friend . ? I'm working on the same unit as this at the min with the back light out so Screen is Dark But it works sound shining a Torch on it, . ? Fing is I'm a Self Tougt Tablet fixer an not bad at it, . But this 1 is full of stuff I've never seen before lol . So im looking to see if any 1 can shed some light on this . lol . ( sorry for the pun there ) . & To help me get this back light for the screen working again on this TF101, . ! An then I find this dip Switch Fing an a Small battery like a Com's battery in a lap top that I've Never seen in a tablet before, . ? So if u can help or any 1 else i would be so Greatfull . Nice 1 . DAY . ! But what is this DIP SWITCH 4 . . ?

[Q] TF101 Screen won't turn on

Hi everyone, this is my first post here. Thanks in advance for any help that you folks can provide.
I've had the TF101 for about six months now, and it's been fine. I was using it yesterday on the train and all was good, but when I got home and took it out of my bag it didn't seem to start up. I thought it might have been a battery issue, so I let it charge overnight. Tried starting it up this morning and I got the same results. So I started looking in to other issues.
The tablet is definitely starting, adb will recognize it in its list of devices, and if I plug it in to my tv or desktop monitor w/ HDMI, I can see and interact w/ the Transformer UI (of course this is kind of painful since I have to do some guessing about where to put my fingers).
I had rooted it using rebound821's scripts and directions here, so tried an unroot to see if that was the problem. I ended up with the same results.
Does anyone here have any insights as to what the problem may be? I'm hoping to avoid sending it back to ASUS, so I'm fine w/ opening it up to look for loose cables.
So I thought that brightness might be the problem. Maybe it was set to 0 and I just wasn't seeing anything on my screen. Sadly, that doesn't seem to be the case.
I tried setting brightness at the path below to to 0, 50, 100.
/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness
Still no luck.
Has anyone encountered anything remotely similar to this (even if similar is just a dead screen)?
There have been others with dead screens reporting what you are, at least I have read a few reports, I think they just had to get them RMA'd, I don't recall anyone 'fixing' a dead screen, especially if you still have adb and touch working then the screen itself and backlight seem to have broken completely- some have reported the backlight dying and thinking the screen was broken, but it was just the backlight (I guess in bright light they could see pixels working, but couldn't make out what was on the screen without the backlight). I still think they had to get it repaired either by Asus or by someone who was capable of doing internal repairs with replacement parts..sorry for your luck
Looks like I'll have to send it back. I took it into the brightest light I could find and couldn't see anything at all. Guess it's the screen and maybe the backlight too. I'm pretty disappointed this happened, the only thing I can think of is that the bag I had it in was hanging from the chair in front of me on the train and it was swaying a little, and that shouldn't be enough to dislodge a connection. Either that or just some freak hardware failure. Still, I guess it's not that common of an occurrence. Thanks for the reply, I'll slink off and try to get in touch w/ Asus now.
I have experience same
My TF101 broke in the same way, screen blank. Conected to tv I`ve got image digital touch work. I shut down my TF101 normaly and screen never go back to live again. Tablet was in a protective bag (when I trave by car), just no reason for not working ( no problem at screen, previously, screen perfect - no dead pixels)
Did you guys get this resolved? I had the EXACT same thing happen yesterday. Was working just fine. Put it in its sleeve, into a protective case, into a briefcase, got home and dead.
HDMI works. I tried to call Asus but they say i'm out of warranty.
Thanks in advance.
Must be something wrong with the connections that it decays over time. I've had mine since October last year and its been fine except for today when I brought it home it wouldn't work.
I was able to fix it though. I held it vertically with the bottom edge down and tapped it firmly on my desk a couple of times. The screen came back on. There is a strong possibility that this will happen again and my tap fix won't work, but it's working at the moment
Asus Transformer screen
elementalfire23 said:
Must be something wrong with the connections that it decays over time. I've had mine since October last year and its been fine except for today when I brought it home it wouldn't work.
I was able to fix it though. I held it vertically with the bottom edge down and tapped it firmly on my desk a couple of times. The screen came back on. There is a strong possibility that this will happen again and my tap fix won't work, but it's working at the moment
Click to expand...
Click to collapse
I had exactly the same problem discussed in this thread. I was also able to bring the screen of my TF101G to life by tapping it firmly on my desk with the bottom edge. It works for now. But it is certainly disconcerting to know that some connection in this rather expensive gadget are loose and all this can happen again. I guess I will not carry my transformer around any more - just leave it at home...
spokey said:
My TF101 broke in the same way, screen blank. Conected to tv I`ve got image digital touch work. I shut down my TF101 normaly and screen never go back to live again. Tablet was in a protective bag (when I trave by car), just no reason for not working ( no problem at screen, previously, screen perfect - no dead pixels)
Click to expand...
Click to collapse
Same problem here had my unlocked bootloader tf101 for awhile now, one of the first ones out... had a great life gave it to my girl when i got the transformer prime and the screen just went out yesterday, still goes in apx mode and still recognized by computer, screen just straight up died, think it's too late for a manufacture warranty, maybe ill look but think it's gonna be no dice... sucks obviously something in the design to make this happen to so many of them...
My TF101 appears to have a dead screen. I am rooted and running Revolver Custom Rom. When connected to my pc, I am able to recognize my device. My screen will not turn on so I cannot use recovery to go back to stock. I am set up to use ADB, however, I am not very knowledgable with ADB. I am convinced I have a bad screen and I am still under warranty. Is there a way to return the TF101 back to stock using ADB? If anyone can point me in the right direction, I can probably figure it out. Otherwise, I may just try and replace my screen and see how that works out. Thanks for the help.
My backlight died on Tuesday. Similar situation of working in the morning, headed into work with it in my bag, no brutal knocks or anything but one jolt just must of finished it off after a year and 2 weeks abuse (yes 2 weeks out of warrenty).
Going to attempt to take it apart this afternoon and play with the ribbon cable as reseating it has solved quite a few peoples problems.
Woo! It worked! Very happy chappy.
Sent from my SK17i using Tapatalk 2
Same thing happened too me, first time i sent it to service, but last time i opened it myself and pushed the connector for the screen thightly in place.. worked nicely
Sent from my Transformer TF101 using xda app-developers app
Screen goes derp
I don't know if I have the same problem or not.
Backstory: I own a Transformer TF101 that I got for my birthday from my girlfriend. It was meant for travel and bs'ing around at home. Took it into work and quickly realized that I could use this for work. That went over so well that the rest of the office became intrigued. Once these came on sale on groupon, the office manager went all in on 10. These are all refurbished transformers with docks.
They have all been handed out and I now have a transformer for home and work. Kind of nice...but I do a lot of site observation so using my personal transformer was a risk that I had to take all on my own (survived a 5' fall off of a parapet wall already).
The problem: From the first 5 minutes that I had the thing, the transformer screen went blank. I opened up google play to download a few apps that I could use for work. Scrolling down I saw some choppyness which I considered the processor/memory having issues loading everything on the screen. Before I knew it - boom blank screen. Rebooted and the loading screen stays on for 2 seconds before the screen goes blank. I can tell it's working because it plays a sound at start up. I can also tell the screen is lit up (it's like it's showing a grey screen because it can't show true black colors). If I hit the power button again it goes completely black. I hit the power button again and the screen flashes to the lock screen and immediately goes blank again. I could do this over and over and over again.
Anybody having the same problem? It's refurbished....I'm guessing apparently I got the dud.
I ran into pretty much the same problem. One morning, the tablet screen would just not turn on. Sometimes, it came on and immediately shutdown, but it is still on the "On" mode. Hit the power button again will bring it to the off mode. Toggle it one more time, sometimes, will turn on the screen a off again. I was able to get it back to work with a factory restore. However, it has the following problems.
1) As soon as I adjust the brightness, the screen will go off again. And there is nothing I can do to bring it back except another factory restore.
2) The screen will flicker (and sometimes produces some clicking sound) when charging with the screen on.
Looks like my TF101 is having same issue, screen gone off suddenly (hdmi shows up in TV fine)...I am going give a try on reseating the cable hoping it resolves the issue.
leonpr, is there some tips/things I have to make sure before attempting this. I found a guide here and another youtube video on this issue as a reference...
Thanks..
Screen won't turn on unless factory reset "fix"
My girlfriend has an ASUS TF101. If the brightness goes up to 60%, the screen is blanked (no backlight either) and the only way to get it to turn back on again is to hard reset. This coincidentally happened at the same time as an update from ASUS. After lots of Googling it does not appear to be related. I was hoping it was and installed several custom ROMS which all experienced the same issue.
As a temporary work around, until I get the guts & the money to be able to replace her tablet if I break it, I found and installed AutomateIt. I set a trigger so that when the screen is turned off, the brightness is set to 50%.
Why trigger when the screen is off instead of when the screen hits above 59%? If you have this same problem, hold the brightness and go all the way until the screen blanks and then still holding your finger on the screen, move it all the way to the left and you will notice that the screen did not come back on. Press the power button once to turn it off and then again to turn it on and you will see the screen at the lowest brightness setting.
So, with the trigger in place, if you accidentally (or one of your rotten kids intentionally:angel raises the brightness above the threshold, simply press the power once to turn off the screen and then press it again to turn the screen on.
Just a note, I ended up installing AutomateIt Pro, Available for $1.60 from the Play Market. The free version works fine, but my girlfriend has been struggling with this issue for a couple of months and after so many hard resets, the little app is more than worth the money.
Have you tried Power + Volume Down for 15 seconds, and then leaving it alone for one minute? It will cold boot. Try that and it may work. Just saying; Hope it will help
Sorry for the necro-bump but here's the actual solution.
Problem: The video cable inside the Transformer comes loose and just needs to be pushed back in.
I can't post a link since I don't have 10 posts yet so just search youtube for the following key words:
blank or no display issue on the asus transformer - fix
The user who posted the video is DoCWaSaBe
Tokyudo said:
Sorry for the necro-bump but here's the actual solution.
Problem: The video cable inside the Transformer comes loose and just needs to be pushed back in.
I can't post a link since I don't have 10 posts yet so just search youtube for the following key words:
blank or no display issue on the asus transformer - fix
The user who posted the video is DoCWaSaBe
Click to expand...
Click to collapse
Just fixed my blank display problem on a TF101 which is well out of warranty. Here is the link. I found the connector loose after dropping my TF101.
Thanks!
Fix lasted for a few days, now backlight dead, tried all cables again. No joy . I hate intermittent faults so ordered a Samsung Galaxy TabPRO 10.1.

Random turn-offs/reboots FRUSTRATION!

This tablet is a great piece of tech, however I've had two major problems with it. AMOLED screen burn-in and random reboots/shut-downs.
In the past week it's at least turned itself off or rebooted itself 9 times. Is anyone receiving this problem? Also in the past 3 hours or so, it's been rebooting to the Samsung Galaxy Tab 7.7 screen just before the tab turns on and gets stuck there. I managed to get out of that situation but I'm not sure how.
If you have problems list which version of the tablet you have, your firmware or kernel version and your specific problem.
Hopefully we can get Samsung's attention if theres enough people and have this patched with an update. Or maybe it'll all go away with ICS... just being optimistic lol.
If anyone knows any sort of customer service or someone from Samsung I can email about this problem that'd be appreciated.
Details:
GT-P6810
32GB WIFI Only
2.6.36 P6810DTKL5 Rooted.
I don't have the problem but if I can maybe suggest, have you reset the device back into factory setting?
Your not the first one to ask this nor your alone, this also happens with the Galaxy Note with some users, I've never been able to pinpoint the cause for this on the note.. I'll see if it happens on my Tab7.7 when I get it tomorrow.
Do you by any chance have a sim card inserted? I noticed yesterday as I was working with AT&T to get my device set up that each time I had to take my sim card out (to give them the serial number) the Tab would reboot on its own.
I have had 2 reboots since getting my tab, very weird.
Sent from my GT-P6800 using xda premium
We need more people to chime in and see how wide spread this issue is, it could be cause by a very aggressive deep sleep state that is used by samsung?
torakun said:
I don't have the problem but if I can maybe suggest, have you reset the device back into factory setting?
Click to expand...
Click to collapse
I thought that factory resetting it would help but as far as I can tell it hasn't. I tried that about a week ago but am willing to give it another shot if someone proves me wrong. Thanks for the input though.
lulugirl896 said:
Do you by any chance have a sim card inserted? I noticed yesterday as I was working with AT&T to get my device set up that each time I had to take my sim card out (to give them the serial number) the Tab would reboot on its own.
Click to expand...
Click to collapse
I have the wifi version so I don't have a sim slot. Sorry for not being more specific in the opening. Although I remember someone else mentioning that their sim may have been the problem. Thanks anyway.
EarlZ said:
Your not the first one to ask this nor your alone, this also happens with the Galaxy Note with some users, I've never been able to pinpoint the cause for this on the note.. I'll see if it happens on my Tab7.7 when I get it tomorrow.
Click to expand...
Click to collapse
Maybe something with the processor, they're relatively similar aren't they? Anyway hopefully I didn't discourage you from your tab, it's still one of the best pieces of tech. Lets hope this problem isn't that widespread and if it is lets hope for a patch or something, maybe with the ICS update hehe.
Have had my GT-P6800 for about a month and I have had several random reboots -- since the reboot is complete and I end up where I was I cannot determine what's behind it.
Haven't had reboots, but I've ran into issues with it turning itself off at least once a week. Currently on LA2 firmware.
I had about 4-5 reboots in a week . don't remember details .
Is everyone using 3G card that are having reboots? I did NOT have any reboots until getting a 3G card this weekend. It JUST did it. Also, I notice if it's on charger (not USB) that when it's full it will more likely reboot. That's my $.02.
My 7.7 p6800 has not exhibited any reboot. I am on KL1..but it has prompted me to update...
Please post
7.7 model wifi or 3g
Baseband Version
reboot yes or no
Sent from my SAMSUNG-SGH-I717
I just got my Tab7.7 but I do not have a spare simcard yet to test if its causing the issue but I will update this post for any findings
P6800
16GB 3G+WIFI
DXLA2 - Kernel Build Date Jan 2012
1 Sleep of death so far, watched a movie but locked the device to take a phone call from another phone. Had it in flight mode but wifi enabled.. so thats about 24hrs from initial power up.. I also performed a factory reset before using the Tab.
copualt3 said:
My 7.7 p6800 has not exhibited any reboot. I am on KL1..but it has prompted me to update...
Please post
7.7 model wifi or 3g
Baseband Version
reboot yes or no
Sent from my SAMSUNG-SGH-I717
Click to expand...
Click to collapse
yep, my tab prompted me to update as well, I it yes, it downloaded something over wifi, then it rebooted, then it goes to recovery and installed the new stuffs, then said "failed" lol
I only have one crash that is when I used the cam then hurriedly hit back several times, then it froze and rebooted, that's the only time it did it
I've structured the OP a bit better hopefully. I've provided my details and asked people for theirs.
Going to go look for who to complain to now lol.
No reboots yet but I did see it wake up to the lock screen while it was sitting on my desk, I have it in flight mode if it matters. It was actually spooky..
Ok I just had the sleep of death on my Tab7.7
Airplane mode but wifi is enabled, the last thing that I was doing was watching a movie and locked the tablet to take a phone call on my other phone. No SIMcard inserted only a 32GB microSD card.
Hi all.
Got my tab 7.7 3G about 3 weeks ago. Rooted on day 2 (this is my 4th droid so pretty confident doing so.... but...) using the simple root method posted somewhere here in XDA.
Not sure if this is related to the rooting, but I've had about 6-8 reboots, several shutdowns and one really strange rebooting which led to the tab unresponsive to anything (only showed the samsung name logo). I was about to factory reset again (I did about a week ago but only because I forgot to reboot after I rooted) when the tab suddenly woke up and started booting normally.
Normally until apps started loading and for almost all the apps, errors of some kind started popping up.
Since I had control again, I factory-resetted the tab.
Since then, I've had no reboots or shutdowns. I do not know why.
Other strange quirks - sometimes, when waking the device with a quick push of the power switch, the screen does this strange graphic swirly thing (almost seems like a graphic image gone mad while loading) and then loads the proper graphic/lock screen.
Sometimes too, when changing orientation, the graphic seems to lag behind the action. Not all the time though. I use Go Launcher as my default but I've noticed the TW screen do the same thing when I change orientation.
As far as Go launcher is concerned (I use it as well on my GS2), only the dock seems to have a problem - when flicking from one dock to another, the next dock does not 'center'.
So far I am a bit disappointed and hoping (hugely) that ICS releases this tab to its dual core, SAmoled glory.
Edit - if I were to say which was the biggest disappointment, that would be the media rescan. When I have a new photo or image, the image does not appear right away in Gallery. When I try to use the music player, the player will not load (rescanning) but the image appears in gallery after.
wujae said:
Hi all.
Got my tab 7.7 3G about 3 weeks ago. Rooted on day 2 (this is my 4th droid so pretty confident doing so.... but...) using the simple root method posted somewhere here in XDA.
Not sure if this is related to the rooting, but I've had about 6-8 reboots, several shutdowns and one really strange rebooting which led to the tab unresponsive to anything (only showed the samsung name logo). I was about to factory reset again (I did about a week ago but only because I forgot to reboot after I rooted) when the tab suddenly woke up and started booting normally.
Normally until apps started loading and for almost all the apps, errors of some kind started popping up.
Since I had control again, I factory-resetted the tab.
Since then, I've had no reboots or shutdowns. I do not know why.
Other strange quirks - sometimes, when waking the device with a quick push of the power switch, the screen does this strange graphic swirly thing (almost seems like a graphic image gone mad while loading) and then loads the proper graphic/lock screen.
Sometimes too, when changing orientation, the graphic seems to lag behind the action. Not all the time though. I use Go Launcher as my default but I've noticed the TW screen do the same thing when I change orientation.
As far as Go launcher is concerned (I use it as well on my GS2), only the dock seems to have a problem - when flicking from one dock to another, the next dock does not 'center'.
So far I am a bit disappointed and hoping (hugely) that ICS releases this tab to its dual core, SAmoled glory.
Edit - if I were to say which was the biggest disappointment, that would be the media rescan. When I have a new photo or image, the image does not appear right away in Gallery. When I try to use the music player, the player will not load (rescanning) but the image appears in gallery after.
Click to expand...
Click to collapse
Hm, mines rooted too. I wonder if that affects how often you get a reboot/shut-down? Still, it better get fixed with an update.
Btw, don't use this tablet as an alarm. I woke up half an hour late to find that the tab was off. I turned it on and the battery was at 60% so it definitely wasn't the battery running out. Maaan was I late for school lol.
tab 7.7
I have the same problem especially when watching the movie or downing torrents after the screen shutdown especially when the battery over 50%. when I want to switch on the screen, the tab will not response until long press on power button switch on with galaxy tab 7.7 screen. that means it was shut off !

Touchscreen unresponsive when dock is connected

After updating OTA the other day (I've always been on stock firmware), my tablet seemed to be working fine. However, once I connect the dock sections of my touchscreen become unresponsive. I can still scroll and click with the touchpad on my dock and parts of the touchscreen still work. This only started happening after the update - without the dock my touchscreen works perfectly (unless I connect the dock first, in which case I need to restart my tablet before the screen works again).
I'm not sure if this is an issue with the update or if anyone else has experienced the same problems. Hopefully someone will know what's up.
Any help is appreciated!
Edit: Was playing around a bit and realized I could "fix" it by locking/unlocking the tablet with the dock connected...so I suppose it's not a hardware issue but rather a problem with the new update.
bamtori said:
After updating OTA the other day (I've always been on stock firmware), my tablet seemed to be working fine. However, once I connect the dock sections of my touchscreen become unresponsive. I can still scroll and click with the touchpad on my dock and parts of the touchscreen still work. This only started happening after the update - without the dock my touchscreen works perfectly (unless I connect the dock first, in which case I need to restart my tablet before the screen works again).
I'm not sure if this is an issue with the update or if anyone else has experienced the same problems. Hopefully someone will know what's up.
Any help is appreciated!
Edit: Was playing around a bit and realized I could "fix" it by locking/unlocking the tablet with the dock connected...so I suppose it's not a hardware issue but rather a problem with the new update.
Click to expand...
Click to collapse
After the 4.2 update, my tablet has also become totally incapable of working with the dock connected.
Everything stops working as soon as I connect it; Seems even worse than what you're experiencing.
I hope Asus knows this, because I am sure it has to do with their update, not my tablet
Mmmmhh... So far for quality control? I really do feel f r you guys, asn many of you will not have been able to unlock, and therefore cannot go the custom route. (Especially sad for you, adelancker, since your tablet was unlocked originally!)
You tried a complete system reformat. Restore to Factory?
KinetiClutch said:
You tried a complete system reformat. Restore to Factory?
Click to expand...
Click to collapse
with the dock connected? You can't
Without the dock connected, yes, and got no results
Hahaha, Asus really messed up good.
@MartyHulskemper I have been able to unlock after a lot of whining!
But still, the problem originated from before the unlocking itself...
But you might have given me an idea!!!!
I can try and:
1) make a nandroid
2) go back to 4.1 Cromi
3) connect the dock: see if that works
and then try to
4) flash 4.2 Cromi-X on it with the dock connected.
Maybe that'd help?
adelancker said:
After the 4.2 update, my tablet has also become totally incapable of working with the dock connected.
Everything stops working as soon as I connect it; Seems even worse than what you're experiencing.
I hope Asus knows this, because I am sure it has to do with their update, not my tablet
Click to expand...
Click to collapse
bamtori said:
After updating OTA the other day (I've always been on stock firmware), my tablet seemed to be working fine. However, once I connect the dock sections of my touchscreen become unresponsive. I can still scroll and click with the touchpad on my dock and parts of the touchscreen still work. This only started happening after the update - without the dock my touchscreen works perfectly (unless I connect the dock first, in which case I need to restart my tablet before the screen works again).
I'm not sure if this is an issue with the update or if anyone else has experienced the same problems. Hopefully someone will know what's up.
Any help is appreciated!
Edit: Was playing around a bit and realized I could "fix" it by locking/unlocking the tablet with the dock connected...so I suppose it's not a hardware issue but rather a problem with the new update.
Click to expand...
Click to collapse
Did you apply the update with the dock detached?
Have you tried rebooting with the dock attached? If that does not solve it, I would reflash the last update with the tablet docked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
berndblb said:
Did you apply the update with the dock detached?
Have you tried rebooting with the dock attached? If that does not solve it, I would reflash the last update with the tablet docked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
The update was applied without the dock. I tried a factory reset to no avail - although, cold-booting a few times seemed to make the problem less frequent. Restarting with the dock connected had no effect.
Strangely enough, I noticed the system bar lock was enabled by default (it was disabled before the update), once I disabled it again I noticed an immediate difference in the performance of my tablet. Much less frequent lag/unresponsiveness with the dock connected - No idea why this would make a difference though
berndblb said:
Did you apply the update with the dock detached?
Have you tried rebooting with the dock attached? If that does not solve it, I would reflash the last update with the tablet docked.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Click to expand...
Click to collapse
I can say that I did that update to 4.2 without dock, I am afraid.
I have tried rebooting, but it just won't boot as long as the dock's connected...
I have the same thing* . Tried many things hard reset, cold boot, downgrade..but unfortunately nothing helps :/
Now I want to drain completely battery-especially in mobile dock
*The same thing means tablet is unresponsive when dock connected(I can't: boot with it, lock scren, neither make factory reset)
Fortunetly I still have warranty, but can't give it now, because I need it for holidays. So did you find something that could help me?
Temporary solution is downgrade to 4.1(10.4.2.20), then it doesn't lag and I can use USB port so I can have keyboard and mouse, but this isn't mobile solution.. (sometimes it also charges from dock-I think when tablet battery is below 90% , but when dock is connected to charger, then it charges whole time)
I don't remember if I made update with or without dock connected.

[Q] ASUS TF300T stuck on boot. Can anyone help?

Hello,
I have searched the threads but cannot find a situation similar to mine so am posting, but apologise in advance if this has been solved before. It's a bit of a long story. About a year ago I was foolish enough to have stood on my TF300T, cracking the screen. The tablet was still working, but it would not register touch. I put it to one side and left the battery to drain. For various reasons I have just got around to replacing the screen.
I found a screen and digitiser of the correct version for my UK TF300T (version G01) and I'd thought the replacement went without any problems, although I was slightly unsure of one digitiser connection. On pressing the power button (I had pre-charged the battery) the screen came to life just as I'd left it as if coming out of sleep rather than being off for a year. It was short lived though and soon the tablet went to black and would not turn on. I thought maybe it was the digitiser connection so went back in to re-fit it. It was only then that I noticed the power switch on the logic board itself under the plastic shell. I hadn't switched it to off before (duh) so did so then, refitted the digitiser cable much more securely,switched the power back on and tried to boot, but nothing happened at all, apart from the power LED flashing orange. After some experimenting (trying to charge the tablet again etc) I found I could only boot by charging the dock and plugging the tab in the dock, but the tablet would only get as far the ASUS screen (not the 3D one, just the flat lettering), with the 'device is unlocked' message in the top left corner and stops there. I can turn it off, but can't boot into recovery at all. And that's where I am now.
Things I have tried - a different logic board from a TF300T's scrounged from eBay which also had a cracked screen (this, weirdly, seemed to have the same problem as mine), swapping various parts out from some other TF300T's (without logic boards) from eBay and contacting the device through Sandix's ADB GUI (after downloading and extracting the SDK), which registered no device.
My best guess at what's happened is that the battery on the tab itself is totally gone (as are the three other batteries I have accumulated) after a last valiant effort and either that going or me messing with the on off switch has some how corrupted the boot process. Is that possible? What do people think? I could buy a brand new logic board, but the only ones I seem to be able to find have some different brand chips on them and appear to be different versions - versions probably not compatible with my digitiser. :S
I am quite a novice here (and maybe poking around the inside of my tab wasn't a great idea, but then neither is wearing boots in the house) so any help would be greatly appreciated! Sorry for the long post, but I wanted to give a detailed report. Let me know if you have any questions. Although unlocked, it is running the stock ROM.
I would make sure drivers are reinstalled properly, by removing the drivers, reboot the computer, reinstall the drivers and then reboot again.
See if that works.
I had something similar happen on a different tablet. That was one from Box.co.uk, but after trying to get it fixed under warranty (and missing the end date by 1 day), I opened it myself. When the charger was plugged in, it showed the charging LED, but it didn't actually charge it.
I don't suppose you've checked the terminals for the battery to the mainboard? On this other tablet, one had broken off. I re-soldered it on, charged it fully and it worked fine.

Categories

Resources