Hi,
I have an MK808 Stick PC that i'm using as a SmartTV adapter for my TV to play content on local and internet network. I read in the booklet that it is not recommended to leave it plugged in for extended periods, but is kind of inconvenient where it is located to keep plugging in and out all the time. Is it safe to leave it plugged in all the time? Is anyone doing this now? If not, anyone have an alternative idea?
have left mine plugged in for nearly 2 months now, if you touch the stick its cold, so doesn't overheat.
Yup. Mines been plugged in for a while.
I replaced the power supply with a 2A unit and I have no problems playing PS and N64 games. In fact, my old LCD 32" TV is giving me more fits then the MK808.
Sent from my Nexus 7 using XDA Premium HD app
no problem
mine left plugged in for more than 3 months. Do not worry.:good:
Mine too left with plugged in more than a couple of months no issues
Sent from my Micromax A116 using xda premium
If you're really worried about it you could consider a smartstrip type surge protector for you TV setup so the miniPC powers up and down with your TV.
http://www.amazon.com/Smart-Strip-Protector-Autoswitching-Technology/dp/B0006PUDQK#productDetails
Or a remote controlled power strip like this one from Belkin:
http://www.amazon.com/Belkin-Conser...=1365896502&sr=1-8&keywords=smart+power+strip
Just some ideas.
Thanks everyone for the replies, puts the mind to ease. I have left it plugged in since I started this thread (barring power outages) and so far so good. I also got an RC11 air mouse+keyboard and it has a power button on it. I assumed it was for the remote, but when holding it down it brings up the stock android shutdown/reboot screen. Just thought it was worth mentioning, haven't see that said anywhere else yet.
I have been leaving mine powered by my ROKU's USB port.
We will see how it does with my 1st (what appears to be stable ROM: Stock + Goodies http://forum.xda-developers.com/showthread.php?t=2070390), flashed this morning...
colhavoc said:
Thanks everyone for the replies, puts the mind to ease. I have left it plugged in since I started this thread (barring power outages) and so far so good. I also got an RC11 air mouse+keyboard and it has a power button on it. I assumed it was for the remote, but when holding it down it brings up the stock android shutdown/reboot screen. Just thought it was worth mentioning, haven't see that said anywhere else yet.
Click to expand...
Click to collapse
As long as you don't forget to turn it off, you should be fine. I see no reason for that behavior to harm the device.
lesmo_sft said:
As long as you don't forget to turn it off, you should be fine. I see no reason for that behavior to harm the device.
Click to expand...
Click to collapse
I am no expert, but what does it hurt if you pull power while it is in the GUI?
When we pull batteries on locked up phones, I have yet to see ill-effects.
This is just speaking of the following devices: D1 x2, D2 x2, DroidX, Intercept, Optimus Slider, Sidekick 4g x2, and Relay 4g...
I understand Dalvik might get corrupted, and maybe cache, but couldn't you just wipe it? While running WiFiKill, a SK4g sometimes would lock up, and I could either restore a backup, or clear both caches to stop boot lock-up.
How I understand it:
Writes are only done when you select a setting, open an app, etc... unlike Windows that does a bunch of crap in the background, and never stops licking drives/cache/etc.
Enlighten me.
It is not safe. It will start acting up and eventually die. That is why there is a power button in the status bar, so use it!
Sent from my SGH-T989 using Tapatalk 2
It'll probably be fine for a year or more, but eventually the heat will degrade the board and components and cause it to malfunction, by which time it'll be obsolete anyway.
Related
Hello, android developer here.
The other day my xoom drained all the way to 0% (this happened overnight while I was asleep). I noticed right away because I use the xoom as my alarm clock. I ended up sleeping in that day (doh!)
Anyways, now the darn thing simply wont turn on. I try to soft reset (vol up + power) but nothing happens. I tried plugging it in via usb thinking I could reboot it with adb, but my computer fails to see the device. So its turned off and simply will not turn on. I've even let it charge for 2 days straight (green charge light on device).
Nothing.
What the heck man?
Dumb question.... How long have you held the power button? My Xoom (maybe others?) won't turn on unless I hold the button for 2-3 seconds.
Ive gone up to 60 seconds of button pressing...when it doesnt work one tends to go to extremes lol
I can't believe this, first time I've ever had a device die like this :-/
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Try turning on right 3~4 minutes later putting on a yiur charger
Sent from my MZ605 using XDA App
Zhenech said:
Did you charge it before you tried to turn it back on? My Milestone tends not to turn on after it drained below zero for like ten minutes until the battery has at least some basic charge again.
Click to expand...
Click to collapse
Yeah its been charged for 48 hours now, green light on power indicator as well.
It still wont boot. I tell ya its the strangest thing I've seen in a while...
did you try booting in recovery? vol down ±power
zylith said:
did you try booting in recovery? vol down ±power
Click to expand...
Click to collapse
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
techs1200 said:
Of course. I've tried every combo imaginable.
F this, I'm getting an ipad.
Click to expand...
Click to collapse
If you really want the iPad, here's the perfect excuse.
However, if you want to save your Xoom, you might want to check out the Motorola Factory cable from Team Black Hat (Google it). If there was ever a use for this cable, your situation seems to define it. Your Xoom seems to think it's not charged (drained) or can't take a charge, but it sounds more like the former situation. The Factory/Programming cable obviously makes a different electrical connection and makes the Xoom think it's charged...something like that. Check it out.
Also, at least one person made one out of a usb cable and it saved his bacon. You'll have to do a search for his thread...it was a while back.
Good luck, what ever you do.
You need to make or buy the motorola factory cable. That will get you booting.
Sent from my Xoom using xda premium
Well I did buy an iPad2 a few days ago, but I will definitely be making one of those cables.
Wow, thanks so much! XDA never disappoints
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
davidblaine021 said:
Remove your SD card then restart... Happens to me all the time..
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Yes, I have seen this also. Pull out the SD card and the unit comes back to life.
I have been using a new ICS build and wanted to warn everyone about the shutdown problems. It seems that by choosing to shut down by pushing the button and choosing "shut down" leaves the backlight running (you can see it if you look).
This has drained my battery down to nothing preventing my Kindle from booting. The stock charger did nothing, no charge, no light, no boot. Plugging in to the PC made the Kindle come on, but reboot after a couple seconds, not long enough for me to even get into recovery mode.
On a hunch I used my phone charger. Not only did the Kindle kick on and boot, but it seems to be slowly charging. I restored back to the stock ROM and now it seems like the stock charger has no effect at all.
Just be careful and be aware that the back light will stay on for now until the kernel is updated.
Thanks!
Sent from my Kindle Fire using xda premium
It happened to me already, but it woke up with the original charger.
Thanks!
yeah two known bugs for the 3.0 kernal are usb wall charging and the device not shutting all the way off (backlight stays on). if you need to you can always go into recovery to charge up. also turning lockscreen and touch sounds off in settings>sound will help save battery
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
This just happened to me...
My kindle died after shutting down for one day. No battery at all...
Did you even read the first post of the kernel thread?
ryanhuong said:
It's 2 different bugs that can combine in a bad way: quick battery drain and loss of wall charger.
Anyways there is hope, people have been grabbing a USB charger form other devices or for most the USB-PC route still charges.
The ROMs are getting very good, the banding is fixed and it seems the AC charger issues have been patched up, even the small menu buttons are fixed in one of the ROMs. Now all I need is a volume bar and I will have my daily driver for a while.
Click to expand...
Click to collapse
Something for the volume control:
https://play.google.com/store/apps/details?id=rubberbigpepper.VolumeControl
Back to OP, I used to hold power until the backlight would turn off (about 15sec) but one day it just so happened that my kindle did not turn off completely even then. After that I have been holding it down for a straight 20sec.
Sent from my Amazon Kindle Fire using XDA
StaticMatt said:
Did you even read the first post of the kernel thread?
Click to expand...
Click to collapse
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
If the devs were offered a dime every time somebody failed to follow directions...
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Not going to argue with you on that one.
ryanhuong said:
This is a discussion forum right? We are discussing.
If I can help even 1 person avoid that problem then I will. Maybe you guys should stick to the dev threads with all the smart people. This thread is for dummies who can't read.
Click to expand...
Click to collapse
You do see the irony in all that, right?
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
umash4 said:
@ryanhuong - just wanted you to confirm once that the wall charger is not indeed working for you.
I too had the same impression for some time as it _looks_ that way, but then realized it is working when I hit the top-left Refresh button in Settings -> Battery. The % kept going up.
Click to expand...
Click to collapse
With the newest kernel yes it seems to charge fine. The Pure AOKP build seemed to have more issues. Now I am using the newer AOKP and not does the charger work again, but the LED now shows orange or green (but the battery icon s still wrong).
Huge improvements so far.
This happened a few times with my Optimus V. This was because there was no offline charging support for AOSP ROMs at the time. The only way I could get the phone to stay on was to force the battery into a LG Rumor Touch and recharge it with that until the battery could boot the Optimus. Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
I know the AOKP ROMs fully power off the device. So at least I'm okay with that.
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Sent from my Amazon Kindle Fire using Tapatalk 2
It will always work best with the stock charger, but until the bugs are fixed, who knows.
KemikalElite said:
Thinking how the Kindle Fire has no offline charging support and a non-removable battery strikes fear into my soul.
Click to expand...
Click to collapse
It does charge offline, the problem lies in the LED not reporting this properly (it doesn't turn on to reflect the charge status).
KemikalElite said:
Also, is it bad that my Kindle Fire charges extremely slow with any other cable than the stock charger?
Click to expand...
Click to collapse
This is normal, as they usually provide less amps than the stock charger (1.8).
For what it's worth, I am on #33 AOKP KF Edition and the LED works perfectly. It's the icons that don't work right.
EDIT: I take that back. If the KF is asleep and you plug it in the LED stays dark. If the tablet is awake and you connect the charger, the orange comes on, putting the tablet to sleep the LED stays orange till it turns green when full.
Felnarion said:
No, and that's why it's a surprise to them. Hashcode has been saying, repeatedly, he doesn't recommend it as a daily kernel. In big red letters, at the top of two threads, it says wall charging doesn't work. Throughout those threads it has other people posting who say they don't know why their kindle died overnight.
It's just a neverending...I wanna call it a cycle, but there's no cycle to it. It's more like a neverending stream of people who refuse to read.
Guaranteed, if I made a thread offering a kernel and in big red letters at the top it said "THIS KERNEL WILL BRICK YOUR KINDLE" and then proceeded to post a changelog and other information about how to install, etc... There would be no less than 100 posts the following day asking why their kindle doesn't work.
Click to expand...
Click to collapse
Actually as one of the guys that's working on the kernel I would have to say you're incorrect. Wall charging does in fact work. The issue with the led is that the kernel doesn't correctly update it, as well as it doesn't update the from in a manner for the icon to change. If you download a battery widget in the market you will see that it does in fact charge with a wall charger. This is also a better route to go since the OEM charger puts out about 1000mv as opposed to 100mv w/USB 1.0 or 500mv w/USB 2.0. Only other steady charging scenario would be USB 3.0 because its output is 900mv.
Sent from my MB860 using XDA
i have experienced a few time of battery run out, the n7 have like an error runny where like crazy and then the screen went off, and when turn on right after that with the charger in, it will be on for like 2mins, and then the screen running like crazy again
just want to know is it a common thing? cuz i had 2 n7 and it have the same problem
Could you explain in detail what you mean by saying "the screen is running like crazy" or maybe post a photo?
Sent from my Nexus 7 using xda premium
goku16 said:
i have experienced a few time of battery run out, the n7 have like an error runny where like crazy and then the screen went off, and when turn on right after that with the charger in, it will be on for like 2mins, and then the screen running like crazy again
just want to know is it a common thing? cuz i had 2 n7 and it have the same problem
Click to expand...
Click to collapse
When you say the screen went crazy I'm guessing you mean filled with static and wavy lines. Please correct me if I'm wrong.
If that's what you're experiencing, I had the exact same issue, but it occurred when I drained the battery to 0% while it was plugged in to my computer. Apparently, the USB ports on most computers don't provide enough juice to keep the N7 alive while using it. I just long-pressed the power button (for around 30 seconds) after it had charged for a bit and the N7 booted right up.
I solved the problem by charging the N7 from a wall socket (and not from a USB port on a computer) when I want to use it while it's charging.
Sent from my Paranoid Nexus 7
Yes, that what I experience, yeah'wall socket helps but if u run something right after it just boot up, than the lines will dance again^^
Sent from my Nexus 7 using xda premium
goku16 said:
Yes, that what I experience, yeah'wall socket helps but if u run something right after it just boot up, than the lines will dance again^^
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you kill the battery that far dead you need to let it charge 20 or 30 minutes if you're having issues like that.
I understand whats happening now.
OP, if you're going to use the computer and you completely drain it like that, let it charge a bit before you power it back up. Its apparently a habit, and I just don't think its a good thing to kill it dead, connect it to a power source and then immediately kill it again by drawing way more power than we have.
Sent from my Nexus 7 using xda premium
Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
See this thread and good luck.
http://forum.xda-developers.com/showthread.php?t=2013977
Sent from my Nexus 4 using xda app-developers app
chelsierae said:
Hi. I loved this phone till today.
My phone died while working, went home to charge it..and it wont charge, plug it in to several different outlets nothing works. No lights, nothing..
Any suggestions?
Click to expand...
Click to collapse
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
elliot.newnham said:
Where you running Faux's kernel?
Can you hold down the Vol +/- and then plug in your USB cable? If it is a red blinking light then I think it's a battery issue not supplying power to your motherboard.
Click to expand...
Click to collapse
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
chelsierae said:
I believe it is the phone, not the charger. Grabbed my old phone that uses the same charger, and it charges that phone instantly..Not very happy with the Google Nexus 4
Click to expand...
Click to collapse
This happened to me today. The battery indicator is incorrect, and shuts down before notifying you sometimes.
Phone shut down on me randomly and wouldn't turn back on today. Plugging into the wall didn't help. It was only when I plugged it into my PC and let it charge for 5 minutes that it came back. Scary bug.
chelsierae said:
I dont even know what Fauz's Kernel is... I tired that and I still get nothing
Click to expand...
Click to collapse
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
elliot.newnham said:
No need to type in bold...
Faux is a developer who is putting together a new kernel for our device, basically it allows one to modify the 'engine' of our phone.
I think the consensus here is there is a manufacturing defect in your phone and a lot of other phones. It seems like this issue is connected to running a custom kernel but there are reports of 100% stock phone bricking (like yours)
It's time to call up google, nothing we can do from here.
Click to expand...
Click to collapse
I thanked you on accident, you didn't deserve it. There is no evidence that his phone is bricked, a user above reported the same thing happening and how he resolved it.
Also, he can type in bold if he wants to.
I hope the OP issue gets resolved. Wish you all the best buddy!
I'm having the same issue. Except this happened when I pulled the device new out of the box. Can't even get it to stay on long enough to get into bootloader mode. :-/ RMA time
Good luck on fixing the problem.
Sent from my Nexus 4 using Tapatalk 2
Hi All,
I was browsing the web a couple of hours ago and my N10's screen started flashing on/off and after around 10secs the thing crashed/turned itself off. Being an N10 this was not an unusual event! However when I try to turn it back on nothing happens. I can hold the power button / power button with volume buttons pressed and nothing happens. If I plug it in to charge I do not get even get a charging icon.
If it makes any difference I was running the latest Rasaber with Franco's r11 kernel and I know I had at least 40% battery left when it died. I have left it plugged in to the stock charger for around an hour hoping that something might happen but still nothing.
Has anyone ever experienced anything like this?
There was not a sad enough looking Emoticon to convey my sadness over the possibility my lovely Manta is dead......
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Something similar happened to me but I'm totally stock. I Googled and the solution was to recharge the unit via my PC USB instead of plugging it into an outlet. I have no idea what happened but after a few hours of being connected to my PC it was back and working. Hope that helps.
I'm running the same rom and kernel combo. No problems or anything weird happened. It must be hardware related.
Did you try the holding-the-power-button-for-a-minute routine?
I would try to leave it plugged in on the charger for a while and see if it gets fixed. That usually solves all sorts of "wont turn on" problems
samwheat said:
no man ... it s impossible . nexus 10 its the best device ever . acording to some gurus here
your device its dead . now you have to stay on your knees to google replace it . good luck
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
You seem upset
i seem realistic
another nexus 10 with problems
Sent from my Nexus 10 using xda app-developers app
is it possible for the tablet to get overheated?
I have had that happen on stock.
My theory: it is linked to the 'battery status not updating'-bug. Your Nexus thinks the tank is still half full, while in fact you are running on fumes. It does not realize this, so no dimming of screen, no low power warning, it just goes full steam ahead, until the battery is totally and utterly and completely depleted.
Then, obviously, it won't start but it will also have trouble charging. You need to charge it for quite some time, sometimes try a different charger, and sometimes keep the power button depressed for a full minute for it to come back to life.
Now when I use my Nexus, I keep an eye on the battery status. If it does not go down, I know I need to reboot for the battery status to be read properly again. It is a bit of a bother, but not too much. The bug only kicks in after the tab has been lying around for a while sleeping. So if I want to watch a movie, I first reboot. As long as I keep using the tab (i.e.watching the movie), the bug won't 'activate' and the tab will shut off properly when it senses the battery is low, in stead of continuing and deep depleting the battery.
Sent from my Nexus 10 using XDA Premium HD app