While trying to install LineageOS, I noticed that while trying to fix issues I was having, so I factory reset, which led to me getting stuck on the Wi-Fi setup with "Turning on Wi-Fi...".
After getting LineageOS installed, I also noticed that Bluetooth was also struggling to turn on, which I find odd.
Some things to note, I'm not too experienced when it comes to modifying electronics, and I believe I knocked off a necessary component that allows the tablet to actually handle the connections, since while I was messing with stuff, a little part from the motherboard fell out, but I'm not sure where from. I also pretty much tore off the entire heat shield while doing stuff, although it really doesn't matter if the tablet breaks since it's a spare that I got for free
Related
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
The same problem, HELP US
Elgari said:
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM, I DON´T KNOW WHAT´S HAPPEN. Can you fix it?
i have heard occasionally around on the forums of peoples power buttons and such doing this after a while, if that is the case you might be able to test for it but its kinda complicated. Is it sleeping or shutting off? If it's shutting off it would be interesting to see why but you'd have to have either a logcat running on the pc the entire time, a cat of the kmsg, or something of that nature running and turn off while its doing that, then you can find the root of the problem. If it won't do it while plugged in, cm has a way to wirelessly do adb commands. I think hashcode said in his sources theres a test binary for the buttons to see if they are doing anything, but i'd have to figure out how to cross compile it by itself if thats the case, unless its precompiled.
Yes, cassualy I fix it last week. I open the Kindle, looking the wires and conectors and close again. And voila . . . fixed!
Enviado desde mi Amazon Kindle Fire HD mediante Tapatalk
Recently my N7000 got a weird and pita wifi problem.
So wifi is working fine, connected to the AP etc. I leave the phone be, charging or not doesn't matter, wifi sleep policy doesn't matter.
When i get to it, wifi MIGHT be gone. It's on, but doesn't find networks. Cannot disable. To fix it, i either reboot, or enable Wifi HotSpot and disable.
The moment i do it, the moment wifi start seeing APs again.
logcat bellow, a few of the last lines. It was to big to post it all.
http://logcat.scheffsblend.com/view?id=1849002
Currently i'm running CM11, but i've been able to replicate it in all current AOSP roms, and Stock 4.1 roms.
Anyone care to advise?
Ok, so this doesn't end like this, i'll provide a update.
I tried EVERYTHING. Stock 2.3, stock 4.1, JB bootloader, custom wifi drivers and nothing fixed it. Simptoms remained the same.
Then i went to the hardware side.I opened the device multiple times... lost a screw in the process. I noticed that with the device opened and on, if i pressed the general position of the wifi chips and metal covers, wifi would die instantly. This probably could be fixed with a reflow, but i had no heat gun (and the hairdryer doesn't cut it). So. i cut a few small peaces of paper, folded them a few times into small pads, put them over the wifi chip. and a few other positions, slammed the cover in, screws on it and wifi has been stable ever since. Not sure this will be a permanent solution, but it's working now
Got my Nexus 6 replaced last week due to shattered screen, which meant I had to start fresh with software anyway, so decided to try M Preview 2.
It was working pretty much flawlessly until yesterday, when it suddenly couldn't connect to my Android Wear watches. Eventually I had to forget them, factory reset them, and then they worked again. Until this morning, when they were gone again.
I quickly noticed via Trusted Devices, that ALL of my Bluetooth devices had had their names replaced with MAC addresses, and when I turned my Bluetooth headphones on, sure enough, the phone informed me that they wanted to pair with it, despite the fact that they already had. Over the course of the last hour I've repaired multiple devices only to have them forgotten shortly after.
Now I KNOW this is a beta build (if not alpha), and bugs are to be expected. That's not what I'm asking about. I'm looking to see if anyone else has experienced this either in this build, or in Android in general, and if there are any known fixes, such as data I can reset on a specific app. Otherwise I'll have to return to 5.1.1, which I'm willing to do, but it just requires work to set my phone back up again.
And I'm fully stock with it. No rooting or any other customizations.
Hey Guys,
I've got two Fire (5th Gen) 7in tablets, which are my kids. they're both completely stock, no Root at all running FireOS 5.3.2.1 and are exclusively used in the Fire for Kids app. They're kept in those huge foamy kids cases with handles and we've drummed into them that they should look after them well which they do.
However, both tablets have shown the same issue; When not in use for a couple of minutes they reboot themselves. After each reboot you can start using them fine, but after a few minutes of not being used they reboot again. So if not actively using the tablets, they will reboot continually until the battery dies.
Amazon has replaced both of these tablets. The replacements are doing the exact same thing. I suspected at this point is may be a problem with my account or profile so I factory reset and registered them on my Wife's amazon account, did not restore from backup, just had them fresh.... And the same problem happens.
Is there a known issue with 5.3.2.1?! Amazon have now processed another pair of replacements which I think is unnecessary, it seems like a software issue to me but they don't have any other suggestions. So I'm hoping some of the brains here may have seen it before!
The only idea I have left is that the "Expandable Storage" option suddenly became available around the time this started happening. Might be a coincidence but I've now factory reset one of them and removed the SD card to see if it makes any difference. Any other ideas guys?
Jay_uk1185 said:
Hey Guys,
I've got two Fire (5th Gen) 7in tablets, which are my kids. they're both completely stock, no Root at all running FireOS 5.3.2.1 and are exclusively used in the Fire for Kids app. They're kept in those huge foamy kids cases with handles and we've drummed into them that they should look after them well which they do.
However, both tablets have shown the same issue; When not in use for a couple of minutes they reboot themselves. After each reboot you can start using them fine, but after a few minutes of not being used they reboot again. So if not actively using the tablets, they will reboot continually until the battery dies.
Amazon has replaced both of these tablets. The replacements are doing the exact same thing. I suspected at this point is may be a problem with my account or profile so I factory reset and registered them on my Wife's amazon account, did not restore from backup, just had them fresh.... And the same problem happens.
Is there a known issue with 5.3.2.1?! Amazon have now processed another pair of replacements which I think is unnecessary, it seems like a software issue to me but they don't have any other suggestions. So I'm hoping some of the brains here may have seen it before!
The only idea I have left is that the "Expandable Storage" option suddenly became available around the time this started happening. Might be a coincidence but I've now factory reset one of them and removed the SD card to see if it makes any difference. Any other ideas guys?
Click to expand...
Click to collapse
It sounds like the devices may be trying to auto-update and failing for whatever reason. Pure speculation as I no longer run FireOS.
Hello everyone,
I've come across an interesting issue I haven't seen before and was wondering if anyone else has seen this happen. I just got my X Fold the other day and was trying to remove the bloatware with adb on my computer. When I plug it in and enable USB debugging, my laptop hard crashes, just immediately black screens. It then takes a couple of attempts of it turning on, then shutting off before I can boot, before I finally comes back to life and is acting normally. I've never seen this before or heard of it happening, anyone have any idea what's going on? I wiped the phone when I got it so it's not like there's some malicious code from the last owner, unless it's built into the system? Although I have a feeling it's something more mundane like an incompatible driver.
Update: I've discovered my USB ports no longer transmit data. All of them can input/output power, but anything with data like a USB drive or my Ethernet adapter don't work. This is really odd...
Hello, how can I add the question hashtag in the name like you?