I've seen a couple of mentions about ActiveSynch 3.7 being more finnicky (sp?) about synching, sometimes not being aboe to get a synch going without rebooting either the PC or the XDA.
Here's my observation, in case it helps others diagnose the issue. If I put my laptop on standby or hibernate, when it comes back to life, AS will probably not work. That's the only time I seem to have the AS3.7 problem.
I've been using AS 3.7 since the day it was released, and yesterday had my very first and only failure to connect. I reset the device, and connected. I hibernate and use standby on my laptop regularly and don't have issues with that ever.
I'm going to bet it has something to do with ****ty USB host controllers in some computers. My last laptop, a Sony, had frequent AS issues. It also had occasional issues with other USB devices. My girlfriend's desktop had AS issues until I gave her a new USB card to use instead of the onboard USB, no issues at all any more.
I looked around and searched first for similar threads before posting this one.
On my rooted NT, I have noticed that charging only works when it is powered off. (I rooted immediately so have no point of reference to non-rooted behavior.)
1. When powered on and plugged in to charge(A/C), I look under Settings/Battery and it shows discharging.
2. Also, the light on the micro USB is green, not orange, if the NT is on.
3. I turn off, the light turns orange until fully charged then turns green.
Could someone confirm that this is the correct NT behavior? I was thinking that it should charge if plugged in whether powered on or off.
it charges on or off if you have the nook tablet cable plugged in, the only time you need the nook off is if you are using a micro usb normal cable via computer to charge, so in answer
no not normal behavior
lenardo said:
it charges on or off if you have the nook tablet cable plugged in, the only time you need the nook off is if you are using a micro usb normal cable via computer to charge, so in answer no not normal behavior
Click to expand...
Click to collapse
Thanks. That is what I feared. Unsure what might be causing so hope someone with broader insight might be able to give direction.
Interesting. My NT was charging but after rooting it, it doesn't charge either. I did a search and came across your post. I blocked it from receiving further updates but that shouldn't be the cause.
Berryblue said:
Interesting. My NT was charging but after rooting it, it doesn't charge either. I did a search and came across your post. I blocked it from receiving further updates but that shouldn't be the cause.
Click to expand...
Click to collapse
Mine charges fine when off and have not heard from anyone on a solution or potential cause. As such, I just plug in each night with power off.
I did a nook hardware test and it detects the USB just fine but no charging from what I can tell when power is on.
Nook not charging while turned on
johninsf said:
I looked around and searched first for similar threads before posting this one.
On my rooted NT, I have noticed that charging only works when it is powered off. (I rooted immediately so have no point of reference to non-rooted behavior.)
1. When powered on and plugged in to charge(A/C), I look under Settings/Battery and it shows discharging.
2. Also, the light on the micro USB is green, not orange, if the NT is on.
3. I turn off, the light turns orange until fully charged then turns green.
Could someone confirm that this is the correct NT behavior? I was thinking that it should charge if plugged in whether powered on or off.
Click to expand...
Click to collapse
I have the same issue. It started this morning. I rooted my nook yesterday using this method http://forum.xda-developers.com/showthread.php?t=1354487. Before rooting my nook it charged fine while being plugged in to the wall socket. After rooting last night I could charge the nook (Plugged into the wall) while it was turned on. This morning I can not charge the nook while the device is turned on. Rooting and blocking OTA's using the link above is the only thing i have changed. Thank you guys in advance.
Also, don't have a problem, but I am scared to break the connector since I have heard it is really fragile, so I don't use it plugged up.
lostwhat83 said:
I have the same issue. It started this morning. I rooted my nook yesterday using this method http://forum.xda-developers.com/showthread.php?t=1354487. Before rooting my nook it charged fine while being plugged in to the wall socket. After rooting last night I could charge the nook (Plugged into the wall) while it was turned on. This morning I can not charge the nook while the device is turned on. Rooting and blocking OTA's using the link above is the only thing i have changed. Thank you guys in advance.
Click to expand...
Click to collapse
Interesting,,,, I used Indirect's rooting method and I am charging right now as I write this on my NT. The only differences I can think of is I used one of his earliest root versions (in mid November) so I don't have some of the later script additions. Also to block the OTA update, I just uninstalled the update service instead of the steps to get mine to show as version 9.9.9
To make sure I understand what people have done. You follow Indirect's rooting method, and then use TiBu to restore the DeviceManager app, in order to block OTAs, correct?
Nothing else? You haven't touched the /system directory otherwise?
cfoesch said:
To make sure I understand what people have done. You follow Indirect's rooting method, and then use TiBu to restore the DeviceManager app, in order to block OTAs, correct?
Nothing else? You haven't touched the /system directory otherwise?
Click to expand...
Click to collapse
Well like I said, I used an early version of Indirect's script to root. Then I backed up the DeviceManager app in Titanium backup (just in case I caused problems) and then deleted it completely. That's why I said my software version doesn't show 9.9.9 like others who have used the db version workaround.
cgdash said:
Well like I said, I used an early version of Indirect's script to root. Then I backed up the DeviceManager app in Titanium backup (just in case I caused problems) and then deleted it completely. That's why I said my software version doesn't show 9.9.9 like others who have used the db version workaround.
Click to expand...
Click to collapse
Ok, so you deleted your DeviceManager.apk? I'll see if I can replicate your bug by deleting that apk. That might be what caused the problem.
----
Nope, still charging while powered on...
cfoesch said:
Ok, so you deleted your DeviceManager.apk? I'll see if I can replicate your bug by deleting that apk. That might be what caused the problem.
----
Nope, still charging while powered on...
Click to expand...
Click to collapse
Oh - I don't have the charging bug. I was saying that maybe I can charge because I rooted with an older version of the script and just deleted the DeviceManager APK to avoid firmware upgrade. Whereas others used a newer version of Indirect's script plus the work around to make the version 9.9.9
Not sure why some can't charge while on cause it works fine for me on my rooted NT.
Basically, where I am at as well. I've rooted numerous times, ever since the 24th, and I've never had this no charging problem.
Figuring out what is different about what they did, and what others who don't have the problem is difficult. There is nothing in the rooting process that should make a difference. Except perhaps if they all reverted from 1.4.1 to 1.4.0 ... Indirect, and I both can charge, but never had 1.4.1 on our tablets.
There could be something left over from 1.4.1 that is screwing things up? (Unlikely, but possible?)
cfoesch said:
Indirect, and I both can charge, but never had 1.4.1 on our tablets.
There could be something left over from 1.4.1 that is screwing things up? (Unlikely, but possible?)
Click to expand...
Click to collapse
Yeah I never have had 1.4.1 on mine either and no charging problems.
That is exactly what I did...nothing else.
---------- Post added at 11:49 PM ---------- Previous post was at 11:47 PM ----------
That could be a possibility as I finally rooted after getting the 1.4.1 OTA. Everything else is fine, just the charging issue.
cfoesch said:
Basically, where I am at as well. I've rooted numerous times, ever since the 24th, and I've never had this no charging problem.
Figuring out what is different about what they did, and what others who don't have the problem is difficult. There is nothing in the rooting process that should make a difference. Except perhaps if they all reverted from 1.4.1 to 1.4.0 ... Indirect, and I both can charge, but never had 1.4.1 on our tablets.
There could be something left over from 1.4.1 that is screwing things up? (Unlikely, but possible?)
Click to expand...
Click to collapse
I had to downgrade to 1.4.0 using the zip to SD card method, before rooting, to mod the apk to version 9.9.9.9 to block OTA'S.
Sent from my SGH-T959 using Tapatalk
I used the Factory Reset option since my NT came originally with 1.4.0 so I didn't have to do the SD card. I'm thinking about (banging my head on desk) going back to factory setting and re-installing Indirect's files. Maybe after the New Year.
cgdash said:
Yeah I never have had 1.4.1 on mine either and no charging problems.
Click to expand...
Click to collapse
I started with 1.4.0; never had to downgrade to root. But since I rooted and blocked the OTAs using Indirect's methods, my nook will not charge unless it's off.
I'm not sure I'm all that thrilled with the Nook anyway, but this could be a deal-breaker. I'd hate top be in the middle of something and suddenly have to turn off my Nook for three hours before I could finish with it.
kevalin said:
I started with 1.4.0; never had to downgrade to root. But since I rooted and blocked the OTAs using Indirect's methods, my nook will not charge unless it's off.
I'm not sure I'm all that thrilled with the Nook anyway, but this could be a deal-breaker. I'd hate top be in the middle of something and suddenly have to turn off my Nook for three hours before I could finish with it.
Click to expand...
Click to collapse
Just to be clear, you are plugging it into the wall, and it will only charge with the screen off, or completely powered off? If you are plugged into a computer and it is only charging with the screen off, that is normal.
Sent from my BNTV250 using Tapatalk
ckevinwelch said:
Just to be clear, you are plugging it into the wall, and it will only charge with the screen off, or completely powered off? If you are plugged into a computer and it is only charging with the screen off, that is normal.
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
This is plugging into the wall and using the charger that came with the Nook (when I initially charged it up, I used the cord, etc., from my Samsung Captivate. It charged up completely in about three hours).
The cord indicator shows orange, as if it's charging, but in Settings, it says, "Not charging," as opposed to "Discharging," which is what it says when there's no charger connected--and the battery continues to drain. I have the screen set to go dark after two minutes, so it spent most of the time "Not charging" with the screen dark. Also, it took around five hours for it to charge back to 100% from a low of 15%.
I'd really rather not, but I'm about ready to give a go to sending it back to stock and seeing if one of the other rooting methods will give me back my "on charge." That is, unless someone has some ideas for how to make Indirect's root and OTA block allow for charging regardless of whether it's on or off.
So, I have a Nook Tablet 8gb that's stuck in a boot loop. I was using it last night to read, decided to go to bed and plugged it into the charger. Upon plugging the tablet in, it powered off, tried to boot up again, and then powered off again. It's now stuck in a boot loop (only shows the 'n' screen for 1 second), and it only does this when plugged into the charger or my laptop. When I remove it from the usb cable, it doesn't even power on at all.
I tried calling the Barnes and Noble customer support, but being that my NT is 1.5 years old, it's now out of warranty and they apparently can't do anything for me. The guy tried walking me through some troubleshooting steps and ended up telling me that it's a hardware problem. Before I toss it out, I decided to check here.
I have looked at other posts and seen similar issues that have been posted about, but seeing as how my NT won't even turn on without being plugged into the cable, none of the fixes on here seem to have worked. I did try downloading the repart.img onto a sd card but I was still unable to get my NT to reset to factory settings.
I'm at a loss at what to do with this paperweight, and I can assure anyone reading this, that I will never own a Nook again because of the horrible customer support, and the fact that the one I had only lasted me 1.5 years. Please help if you can, thanks!
Ok, update to my NT situation... (FYI, this appears to be a h/w issue with my battery vice an Android OS issue)
Just to clarify, I'll give a little more information. I've been doing research all day on my problem, and I feel like I need to specify some things in case anyone else has a similar situation going on. After reading some other posts online, this is what the problem initially appeared to be...
My nook tablet's battery drained all the way to 0% before I plugged it in. After plugging it into the cable (via pc or wall outlet), the tablet would power on, show the 'n' screen for approx 1 second, and then power off. After about 5 seconds, it would power on again, show the 'n' screen, and power off again. Basically it was just stuck in a boot loop and did not seem to be charging up at all even though the indication on the cable showed it should have been charging. When I would unplug the nook from the cable, it would not turn on at all.
Possible solution #1... I read somewhere in a couple different posts that it could be just a battery issue caused by me letting it drain all the way down. Some people resolved their issues by removing the back from their tablets, unplugging the battery for 10 seconds, plugging it back in and then letting the tablet charge. (Removing the back and messing with your tablet's hardware will void the warranty!!!) After watching a couple videos about how to access the battery and remove it, I decided to unplug mine and give it a shot.
Results so far.... After plugging my battery back in, my NT has stopped going into the boot loop. I'm now getting the message to let it charge for 15 minutes and then try to power it on again. This is at least a different screen than the boot loop I was seeing, so some success... hoping in about half an hour I'll have even more success. I will update again when I see something different... crossing my fingers!!!
Yep, unplugging my battery did stop the boot loop, and my NT is now charging. I was able to turn it back on and it's now at the stock setup screen.
Even though no-one replied to the post, I'd still like to thank the Android gurus that do post here and help individuals resolve their problems. It seems like I'm always learning something new when I check out the forums. Please keep up the great work!
Now time to root and have some more fun!!!
I have a Kindle Fire HDX 7" that I purchased a couple of months ago for my son. It was rooted and running Thor with Gapps. He plugged it in before going to bed and when we looked at it the next morning it had the Google X showing. We unplugged it and now it will not power up unless it is plugged into a wall charger. It will boot into safestrap, but bootloop before it gets into an OS. I bought a ChargeDR to up the power output on the USB, but as soon as I try to switch to sync it will turn off again. My theory was that if we could get it to fastboot with sync on then we could ADB, but that is out. Not sure if there is any way to salvage this one or not. What is odd is that safestrap still thinks it has 67% battery, but calibration must be off, which is why this happened to begin with.
tuttle36 said:
I have a Kindle Fire HDX 7" that I purchased a couple of months ago for my son. It was rooted and running Thor with Gapps. He plugged it in before going to bed and when we looked at it the next morning it had the Google X showing. We unplugged it and now it will not power up unless it is plugged into a wall charger. It will boot into safestrap, but bootloop before it gets into an OS. I bought a ChargeDR to up the power output on the USB, but as soon as I try to switch to sync it will turn off again. My theory was that if we could get it to fastboot with sync on then we could ADB, but that is out. Not sure if there is any way to salvage this one or not. What is odd is that safestrap still thinks it has 67% battery, but calibration must be off, which is why this happened to begin with.
Click to expand...
Click to collapse
If I read you correctly, you are assuming that you have not developed a hardware problem, but that the software is preventing the battery from charging. That seems highly unlikely.
Sorry for the confusion, I would say there appears to be a hardware issue as well. I am concerned that since it has safestrap installed that if I were to return it to Amazon for repair it would not be covered. Without being able to access it from a computer, I cannot remove safestrap. I have thought about force charging the battery by opening up the case, but it sounds like a complete disassemble would be in order. I cannot find any information about other occurrences of this problem.
tuttle36 said:
Sorry for the confusion, I would say there appears to be a hardware issue as well. I am concerned that since it has safestrap installed that if I were to return it to Amazon for repair it would not be covered. Without being able to access it from a computer, I cannot remove safestrap. I have thought about force charging the battery by opening up the case, but it sounds like a complete disassemble would be in order. I cannot find any information about other occurrences of this problem.
Click to expand...
Click to collapse
Not to worry. If it's still under warranty, tell them it's broken and they'll send you a new one. They don't ask about the software you may or may not have installed.
Thanks. It should be under warranty, it is nice to hear Amazon isn't taking such a hard stance on development for these devices.
So just yesterday I was on here asking how to load/install apps from/to a USB device. I'm unsure if it's something I did to cause this or if it was just my tablet acting up.
I installed 2 new apps, "StickMount" and "FolderMount". StickMount is supposed to be for mounting/unmounting the USB I plug in, and FolderMount is supposed to connect installed apps to the usb in a "pair" so that they can load off of the USB instead of the device.
I had moved a few apps, one being LuckyPatcher, over to usb. However it really didn't seem to do anything. In fact, I'm pretty sure doing that added onto the existing used space (so it took more not less). The other two were just some games I was playing at the time (for testing).
Everything was running normal, I plugged the tablet in as it was close to death (like 14% if I remember correctly). Few hours go by, I decide to use it. Double tap the screen, no response. Click power, no response. HOLD power, nothing. I decide that maybe it was just dead and needed a charge, so I left it in as I went to sleep.
Wake up, and repeat. Nothing happens. I plug it into the computer, computer doesn't show anything is connected. Leave it for like hour to see if it'd charge, nothing. Tried using the steps on the google product forums, and nothing helped.
All the topics on here are people mentioning their tablets are in a similar state and they don't have a solution posted.. Or they say to send it in for repairs. I can't do that as I won this in a contest and there's no warranty or insurance on it.
Is there ANY way I can get this out of this brick state?
P.S: I forgot to mention, When I was taking my case off it, after it was already in the brick state, the nexus tablet itself started to come apart.. That's not normal is it?
P.P.S: I can't link to the page as I have not made enough posts. Googling "Nexus 9 won't boot" should get a product forums link, the user in there posts the link to the troubleshooter. Was just things like holding power and volume down, plugging it in and waiting 15 mins. so on.