Xoom randomly shutting off @ ICS? - Xoom General

So I flashed my new Xoom using "[ROM][Nightly][ICS] Team Eos European 3G (GSM) Nightlies", everything seemed ok without any 3G problems and so on.
But, after 2-3 days, the device seems to randomly shut off itself after being in normal sleep for about 10-30min and needed the soft reset using upper volume + power button to start again.
I reflashed and unrooted so Im back to stock firmware 3.2 now, and I havent seen any random shut downs yet (only been 1 day though). Im wondering whether this could be because of the ICS rom or just a faulty device? I didnt install many apps after I flashed ICS, only facebook, cpu spy & quick reboot, so I dont think these where the culprits?
Has anyone else experienced this sort of thing with the Xoom?
Edit: Crap, I thought I where in Q&A-forum. Nice first post... Would someone please care to move this to the right place?

Related

mytouch 3g slide restart itself occasionally after root

I didn't test the device before I rooted it. Now even since I rooted the phone, it reboot itself occasionally when using eugene's legend2slide and SlideM rom. Anyone else have similar problem? I also want to mention that I installed DroidFontsfallback.ttf to the /system/fonts/ after I rooted the phone or using those custom roms. Could the font be the cause of the problem?
.
noticed the same problem i dont know what it is
I have noticed this as well. I went from stock -> ENG -> Legend2Slide -> ENG -> SlideMERoot2. I forget when I think I first started noticing the reboots the second time I had the engineering ROM on - but - I didn't keep the engineering ROM on the first time for more than a few minutes, and I only kept Legend2Slide on for about an hour, so I may just have not had it running long enough to reboot itself those times.
Mine is also rebooting randomly.
Last time it was when i changed it to the camera it lagged for a second and then just restarted.
Move posts to Android Dev thread
Don't remember seeing a "Bug" thread, so maybe start a new Bug thread for things that happen after root. Just a suggestion. Thanks.
Same deal here. Its been doing it for a while I just haven't posted anything about it. I'm rooted but on the stock rom and get the reboots every once in a while. Yesterday it did it twice but not today. If I remember correctly I was listening to music and when I stopped the song and hit home that's when it rebooted. Maybe something to do with low memory I'm not sure though as I didn't see the available memory before it rebooted.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Have you guys thought about going back to stock and checking on this to see if it is the phone? If it is return it to t-mobile and get a new one. I have flashed all the available roms and this has not happened to me at all.
Sup fellas
I doubt it is the phone itself. I have had mine running on the standard OS since I got it. I don't want to root unless the froyo update we receive is crap. I'm bearing the pain of not being able to save apps to SD until froyo comes out as an update for the phone. If no luck, then root.
As for reboots, none here. I have had the memory maxed out with widgets on 7 home screens with GDE running, phone running wireless GPS and bluetooth all at the same time and it did not crash nor reboot.
I think there must be some conflict that is in the adk install somewhere. It seems that this is a standard problem after rooting the 2.1 Slide MT3G.

Any fix for the sleep of death?

I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
Optimus-Prime said:
I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
Click to expand...
Click to collapse
I know that when I installed Prime 1.5, I get "Sleep of Death" every hour... I went back to stock and "Sleep of Death" went away... I'm not sure if this issue was fixed yet. I was told last week that it might be kernel related issue. But in the meantime, you can also try a different kernel and see if that fixes the problem... If not, try a different rom or even use Prime 1.4. Worst case is to go back to stock 3.1.
I'm still using stock rom right now and plan on using it for a while...
ill have to give stock a test drive. i did see that when i changed roms i did get sleep of death.
we can just flash a CWM stock rom right?
I had this problem for the first time today. I'm on Prime 1.5.
I also had no sound when I got it back on. Had to reboot to get the sound back.
Any similar sound/sleep of death issues?
Any new information on a permanent fix for this?
Thanks.
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
I had it nearly every time I left the tablet on for more than an hour without touching it. Upgraded to stock 3.1 and it hasn't happened since... (I manually flashed it; didn't wait for the OTA if that matters..)
My first TF suffered a SOD but I think it was a screen of death not sleep of death. I could never get it back so I replaced it at TigerDirect. My current solution? I pushed the TF off to the side of my desk and bought a Xoom...
zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I read Asus saying they were fixing hte dock draining issue, nothing about the sleep of death. I have never had this happen, though I'm on stock, and form the looks of it the peeps that are on custom roms have this issue so doubt they'd fix a non-stock problem.
zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I also only saw reference to the dock issue being fixed in an OTA. If you have a link to any information about the fix they are working on, it would be most appreciated.
Thanks.
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
Optimus-Prime said:
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
Click to expand...
Click to collapse
Thanks... let me know if it works for you.
Bought my TF a week ago, with 3.01, NEVER has seen SOD; today -finally- OTA upgrade to 3.1 in the Netherlands; since upgrade SOD every time TF goes in sleep mode..
Great upgrade, thanks ASUS! Any solution (except downgrading) around, plz?
Last nights OTA update fixed my deep sleep problems. This update apparently included a power management fix.
I've had my transformer for 2 months now. I had it stock, always updated OTA, until the NVflash/APX mode rooting method appeared and then I flashed PRIME! v1.4 and never had any SOD until recently when I upgraded to PRIME! v1.5. However, I did two other things around the time of the v1.5 upgrade that could equally have started the problem, namely; I started using a 16GB SDHC card in the keyboard dock and I also connected HDMI to my TV for the first time using a C-to-A adapter (this also does not work properly - uinstable image - intermittent digital interference flickers along the bottom of the screen).
I have since re-flashed PRIME! v1.5 using the APX/NVflash method and have stopped using the 16GB SDHC card in the dock and now the SOD has stopped happening..... HDMI is still an issue but that could be the cable and/or adapter.
Deep sleep , could it be tegra 2 issue?
the Folio 100, the toshiba thrive and Asus TF has this problem. all of them have Tegra 2. if i set the folio 100 to 30 minutes before sleep i can use it as long as i don't let it go over 30 min before i wake up the screen. if i close the screen (via the button) i don't get deep sleep problem before 30 min has gone. so there is some problem related to the CPU and memory going to deep sleep and can not get interupts from the button anymore
My SOD seems to only happen when it's attached to the keyboard dock. If I leave it undocked, it never get's the SOD. I'm on a replacement dock, and the original dock I had never gave me the SOD either.
I have the latest firmware installed and that didn't make a difference.
No dock. But had my first SOD with Prime 1.6 + Netformer and IO fix OC'd to 1.5
My first post so I'm locked out of development forum with the relevant thread
http://forum.xda-developers.com/showthread.php?t=1070343&highlight=waking+sleepsleep+of+death
Anyway, had my TF for only a couple of days, goes to SOD two-three times a day already. I didn't play around with 3.0 much before doing OTA to 3.1 but 3.1 and now 3.2 still put it to this unnatural sleep.
Actually, it didn't wake up after updating to 3.2 itself.
From reading that thread the best probable cause appears to be the voltage issue when CPU clock speed changes - when waking form sleep clock speed goes up but voltage doesn't or something like that, and if some processes are left running, like logging to a file, the system never really goes to sleep so no problem with waking but a problem with catching the culprit.
Someone also said that in 3.2, by design, there should be even more sudden clock speed increases so SOD problem might become even more frequent.
One more possible argument for the voltage theory - SOD doesn't happen when TF is charging, meaning that CPU management is not that strict. Someone reported that Juice Defender, the app to minimize power consumption/CPU load, actually caused SOD on his TF.
The actual cause of SOD is a failure to get the correct value for blacklight on waking so looking at the display closely with a flashlight one still can see it running, allegedly, and can even unlock it. If that happens and the system is otherwise responsive maybe there's a way to force the backlight on, maybe some widget that toggles autobrightness on something. I'm waiting for my next SOD to test this theory, sometimes the screen doesn't look black, simply not light enough.
Maybe all I've said is nonsense but I'm an unrooted noob, I'm allowed.

Working solution for random boot issues

So this morning I got a call from a friend who told me that his TF is running like crap after doing OTA upgrade to ICS.
We met up at school and I got to take a look at it. Yes, it was indeed running like crap and it even randomly rebooted while we were eating breakfast. He told me the random reboots were happening every 3-5 hours(that he could notice).
Here's what I did to fix it.
Removed his MicroSD card(not sure if necessary)
Shut down TF.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen. Left icon is Wipe Data. Right icon is Cold boot. Right icon is selected by default.
Press [volume down] to highlight the LEFT ICON, which is Wipe Data.
Press [volume up] to confirm your selection
Go through the process.
Let your TF reboot.
Shut down TF again.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen.
You need to do cold boot. It's already selected by default so just wait like 10 seconds and it will happen automatically. Press [volume up] if you don't want to wait.
Go through the process. Your TF will reboot afterwards.
Done.
It has been over 24 hours and his TF has been running smooth without any glitches or any random reboot. I told him to let me know immediately if a random reboot happens again.
This is simple to do. Worth trying unless you can't read English.
Edit: I didn't include this at first because I thought it would be common sense for everyone but it apparently isn't....
DO NOT JUST RESTORE ALL YOUR PREVIOUS APPS AND WIDGETS YOU HAD FROM HONEYCOMB. THAT DEFEATS THE ENTIRE PURPOSE OF DOING A RESET AND PREVENTING APP INCOMPATIBILITY.
thnx man for sharing . I actually tried every thing to solve this issue but no luck , I'll try your as sson as i go home .
This did indeed work for me as well. I tried this a couple days ago and I have yet to have any freezes or random reboots. I think that not restoring any backed up data, apps or settings is key to fixing the problem. I'm now very happy with ICS- burn in hell Honeycomb.
Shameful bump
When you switch from a version like HC. This is what you exactly should do!
I did this and never experienced random reboots.
My Transformer is running since three days and everything works fine!
Edit:
Another quick hint:
If you want to work with Google Docs, you have to disable Forced Hardware Rendering!
I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk
billouetaudrey said:
I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
.....lol, why post in this thread that you are not going to follow the advice of the Op?.......
Sorry to say but this is not working, already done this since the minute it was out and still have so now and then a hang boot
(random reboots that hangs on the boot)
Giving it a try
I am experiencing random reboots after ICS
Wiped transformer, cold booted, and installed the following.
Adobe Reader
Dog Catcher
updated G+ and GMail but have not run it.
Charging now, I will let you know.
Previously I had wiped it and reinstalled all, disabled syncing, disabled location info, adjusted wi-fi settings, and added CPU throttle control obviously none worked.
It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.
JesterOC said:
It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.
Click to expand...
Click to collapse
why are you installing dogcatcher? And this does work.. do it again. Don't install your apps.enusre it dos not lock up before you install anything.... If it locks up before you install any apps then call Asus. If not start installing one app at a time. Wait after each install. Ensure that its not doing it, once you are sure install Another ....rinse/repeat....
I installed dogcatcher because I needed something to listen to on the way in to work. I have uninstalled it. But I doubt that is the issue.
I have had these sorts of reboots on my Transformer until the third or fourth Honeycomb update. But eventually they fixed it. I suspected this would happen again.
Considering that dogcatcher one of the most popular podcast apps on the market I suspect that there are many people with no problems using it just fine.
But since I need a podcast listener to be able to use the device as I want to, does anyone without issues have a podcast listener that they use?
2 hours into the last experiment and it died again while sleeping.
So that about sums it up. This procedure might help with some issues Transformer's are having but not all.
Recap. Wiped, cold booted, gmail setup, G+ updated still equals failure.
I love how horndroid 'solved' this issue and then goes on the belittle people who are still having it as 'stupid', and probably their own fault. Horndroid, I appreciate your attempt to contribute, but your attitude and stabbing-in-the-dark protocol is not becoming nor helpful to anyone. Definitive statements pertaining to ONE TF101 device that you own are quite naive, there are several different models, and until you have personal access to each model version you should advertise your 'solutions' as "worked for ME", and understand if it doesn't work with others it isn't THEIR fault..this is not a blanket solution for every device's reboot problems. In fact, I am willing to bet the reboots being resolved by this method are of an entirely different genesis than the reboots that I and others are experiencing (hang-boots).
I hear what you are saying I have the reboot issue as well.
I did a reset before and after and only installed xda HD and ran it for 2 days and got 3 reboots so I did the cold boot and then it did it 2 more times that day. Earlier today I almost couldn't get out of the boot loop, so I wouldn't say its a app problem its something wrong with the firmware somewhere
Sent from my SGH-I897 using xda premium
Some aren't too lazy we just don't want to wipe data after every update. I think i have gotten 4? OTA updates and 2 of them screwed up deep sleep while docked. Guess what the first trouble shooting step was...wipe data. Guess what worked...the next OTA. I don't have time to read through all the different threads on the same subject but are people that flashed through cmw instead of ota having the same issue? My buddy went this route and has no issues.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.
knoxploration said:
Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.
Click to expand...
Click to collapse
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..
luna_c666 said:
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..
Click to expand...
Click to collapse
It's hilarious how you think YOUR problem is the only problem that everyone is experiencing.
For a lot of people, it was the app incompatibility that was causing them issues.
Obviously you think your problems are caused by something different, but that doesn't mean there are different problems caused by other reasons.
While all of you are speculating, at least I've posted a solution(even though it's merely doing a data wipe and cold boot, pretty much common sense) that has been proven to work for a lot of people. I've never claimed it will work for everyone; just those having problems due to app incompatibility.
I'm pretty sure this is an issue with the update itself and all these "fixes" are going to be pointless in a little while when an actual fix is released by Asus.

LAG since updating to 4.0.4

I just got my update to ICS 4.04 and it's made my xoom worse! Things have got really laggy, it sometimes freezes when selecting things and typing has become a nightmare again! Has anyone else experienced any problems :-(
Iam a bit annoyed now, might just go and root.
Sent from my Xoom using Tapatalk
Well its just gone from bad to worse...my xoom went to sleep and when I tried to wake it up it would not come back on. I had to do a soft boot but now its stuck on the Motorola screen. I have tried to go into android recovery and do a factory restore but it comes up with an error
I am really stuck on what to do next, can somebody help please?
Thanks
Hmmm mine went to 4.0.4 and I was thinking the opposite! it seem alot smoother and faster
Mines seems to run slow too after the OTA, but i'm not sure if that's the tTorrent app, when it's running it makes the xoom lag out like crazy, when its off everything runs fine.
burt_ie said:
Well its just gone from bad to worse...my xoom went to sleep and when I tried to wake it up it would not come back on. I had to do a soft boot but now its stuck on the Motorola screen. I have tried to go into android recovery and do a factory restore but it comes up with an error
I am really stuck on what to do next, can somebody help please?
Thanks
Click to expand...
Click to collapse
You could go into Developer settings and switch off animation or set to .5. That should help with lag. I never use live wallpaper either. A big download may also make it lag .
Well the lag didn't last long because I actually had a complete failure after installing 4.0.4. My Xoom went to sleep and would not wake up, had to do a soft reboot and then could not get passed the motorola boot screen, was stuck on it for hours! Tried to go into recovery to wipe and reset but that would not work either. Tried to push a rom image from my pc but then my xoom decided that it didn't want to be detected by my pc anymore so it looked like my xoom was bricked :-(
Luckily I had some help from some great people over at xoom forums who helped me to get it back up and working by using RSD Lite and a stock Rom SBF file.
I now have a working xoom updated to 4.0.4 with no problems at all
Not sure but I think it may have been a freak accident that just happened to me.... I just hope it doesn't happen to anyone else
Sent from my Xoom using Tapatalk
My Xoom went to sleep today also, couldn't get it to power up for anything, I then held power and Vol up and down all at same time and she booted right up.
Bone stock wifi Xoom by the way, incase happens to anyone else
Sent from my SCH-I500 using Tapatalk
Mine has gotten really bad with scrolling lately...
Seems that I can only scroll either up or down (or both) for no more than a couple seconds. Ive been able to move my finger up and down on a scroll area and it only lasts a couple seconds and seems to "lose" my finger press even though my finger never left the screen or the area. I have to wait a couple seconds before I can scroll again or else it doesnt recognize the finger press.
Sometimes I think the lags just android its never constantly smooth. You'd think dual core would be as smooth as butter but it really makes no difference. Still waiting for Google to fix it. I've had months of smoothness then the odd time something slows it down
I agree, 4.03 was great with no lag issues then nightly 90 had some lag again with scroll issues, so far on #91 I'm not having any issues. I had the biggest problem when I was trying the OC @1600, I slowed it back to 1408 interactive and all is smooth as glass:thumbup:
Sent from my DROIDX using Tapatalk

[Q] So i got TF101 Refurb from Newegg..

(Item: N82E16834230172)
.. & I'm just not sure if i should return it or if these issues are pretty much whats expected.
I have not upgraded to ICS from HC
Problems so far:
1. Re-booted twice on first day i had it. I'd been using it all day (installing/using apps etc) - I used it all day 2 days after that w/out issue.
2. Re-booted last night? Not sure exactly but there were no apps suspended in the bg from the night before (~8 hours before) - i had quite a few in the bg
3. 2 out of 3 times so far if i "shut down" *the power button will not power it back on* - i have to plug it into the wall/power for it to turn back on
They aren't the worst issues..yet? I don't know.. I'm pretty happy with HC at the moment & will probly avoid ICS upgrade for a bit.
Stick with it?
#3 is not supposed to happen.
#1 and #2, it depends on exactly which version of the Honeycomb firmwares you are running. Honeycomb 3.2.1 didn't do those for me, but the versions pre-3.2.1 had occasional incidents.
It's 3.2.1
We can assume that you know that you have to hold the button down for three seconds to power it on when it's completely off. Therefore, I would see about swapping it because #3 sounds like a major problem.
ssl123 said:
We can assume that you know that you have to hold the button down for three seconds to power it on when it's completely off. Therefore, I would see about swapping it because #3 sounds like a major problem.
Click to expand...
Click to collapse
Yeah i just shut it down again and it would not come on until plugging into the wall. Problem seems pretty consistent. Ugh i really don't want to have to go through this.
QUESTION: how can i pretty much wipe this device of the apps/personal info i've entered into it before sending it back?
QUESTION: Try ICS then if i'm gonna ship it back anyways?
To wipe the device, you run "Factory Reset Data" in the Settings.
Sure, might as well try out ICS if you're curious.
Sometimes when mine gets a random reboot/shutdown I have to hold the power button down for about 10 seconds to turn it on. Try this if you haven't already.
yeah the power button issue may be it not being totally shut off, so when you hold power you are shutting it down instead of starting it. happened to me a few times so figured it was worth a mention.
Thanks for the suggestions guys. Although it's a bit inconsistent on whether or not i have to hold it down for 3 seconds or 10+ one way or another (after a struggle) it does appear to consistently come up. Emphasis on struggle though.
Have you tried any custom roms yet? I personally seem to have a more stable tablet when using a custom rom due to the various tweaks and fixes.
Just install ICS - such a relief from Honeycomb!
No_u said:
Just install ICS - such a relief from Honeycomb!
Click to expand...
Click to collapse
This thing decided to re-boot randomly again. So i decided to upgrade to ICS (4.0.3) - nearing last ditch efforts.
Problems came up right away:
1. Browser having strange connectivity issues? I have Wifi Analyzer and watching the scrolling graph i don't see any dropping or problems with the connection itself. So i'm not sure what the situation is but sometimes it just doesn't want to load pages - I can't fully say if Dolphin has the same problems or not.
2. Screen tearing. Fairly frequently there's a diagonal tear occurring across the screen, when switching around in/out of apps.
3. The shutdown issue. This problem is at best the same, if not worse. So in hopes of shrugging off the other issues i did a "shut down" and i seriously battled with the power button and never got it to come back up w/out plugging into into the wall.
- What's interesting is how it always comes up RIGHT AWAY once it's plugged into the wall. I tried and tried and tried again with holding the power button 3-10-20-30+ seconds random intervals nothing worked. Hard to express the amount of times & different timings i tried.
So i'm gonna give it a whirl like this for a while and see.. i might end up doing a factory reset .. if problems persist after that it's going back to newegg
Edit: i just tried to play a youtube video and it stopped trying to cache 1/4th through it.. then i pulled up Aljazeea live and it's echoing/choking/stalling .. these problems didn't exist prior. Also, i noticed another streaming (scanner radio) app not doing so well earlier too... heh
bgl said:
This thing decided to re-boot randomly again. So i decided to upgrade to ICS (4.0.3) - nearing last ditch efforts.
Problems came up right away:
1. Browser having strange connectivity issues? I have Wifi Analyzer and watching the scrolling graph i don't see any dropping or problems with the connection itself. So i'm not sure what the situation is but sometimes it just doesn't want to load pages - I can't fully say if Dolphin has the same problems or not.
2. Screen tearing. Fairly frequently there's a diagonal tear occurring across the screen, when switching around in/out of apps.
3. The shutdown issue. This problem is at best the same, if not worse. So in hopes of shrugging off the other issues i did a "shut down" and i seriously battled with the power button and never got it to come back up w/out plugging into into the wall.
- What's interesting is how it always comes up RIGHT AWAY once it's plugged into the wall. I tried and tried and tried again with holding the power button 3-10-20-30+ seconds random intervals nothing worked. Hard to express the amount of times & different timings i tried.
So i'm gonna give it a whirl like this for a while and see.. i might end up doing a factory reset .. if problems persist after that it's going back to newegg
Edit: i just tried to play a youtube video and it stopped trying to cache 1/4th through it.. then i pulled up Aljazeea live and it's echoing/choking/stalling .. these problems didn't exist prior. Also, i noticed another streaming (scanner radio) app not doing so well earlier too... heh
Click to expand...
Click to collapse
Do a factory reset already and test it without installing any apps. You need to find out whether the problem is with hardware or software.
There's a good chance that it's a hardware problem since you got it refurbished. Maybe it was broken already and Asus didn't completely fix it.
Do yourself a favor. Root it and install the latest CM9 build. I was having all kinds of reboot and sleep issues with the stock ROM, mainly the ICS one but a few issues with HC as well. CM9 has been rock solid for me so far.
Headcase_Fargone said:
Do yourself a favor. Root it and install a custom rom. I was having all kinds of reboot and sleep issues with the stock ROM, mainly the ICS one but a few issues with HC as well. CM9 has been rock solid for me so far.
Click to expand...
Click to collapse
Fixed it for you
CM9 might not suit him, so instead he should try out several roms until he finds one hes satisfied with
Telling him to install a specific rom is fine, but it doesnt really help him out.
That said, since you brought up "rock solid", Team EOS build 19 has been really rock solid for me. Currently 202h uptime and counting.
Wow i didn't think things could get much worse but they did.
I decided to do a factory reset because generally things hadn't improved. Initially after the reset things were "OK" ("better" @ 1st but short lived)
Then a while later..
It appears the connectivity of the wireless has completely died. It will connect to wireless fine but is incapable of anything beyond that. No web pages, no connectivity/data transfer in any apps.
I did another factory reset, installed nothing, imported nothing, signed into nothing.. same issue.
Even though i have 2 other netbooks right here w/no issues at all, i tried resetting the AP multiple times. No diff.
Just before the wifi dying it was acting like it was before the reset, where things would randomly fail to stay connected, videos wouldn't fully cache, web pages wouldn't fully load etc. (general connectivity problems that didn't exist in HC, but have in ICS since update)
I think ICS was really the nail in the coffin for this thing.

Categories

Resources