Database Develop

Tate power drain is high in sleep mode

Kindle Fire HD7 X43Z60 tate
D025 seems to be 16GB.
I do not know the history of the device.
I got it at a swapmeet.
Stuck in a TWRP boot loop.
I have no idea what I'm doing.
I built a factory cable and followed this tutorial:
1. adb reboot bootloader (then in Fastboot mode) IIRC, I didn't have to do this, factory cable put it in fastboot.
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
_______________________________________________________________
Now it boots and seems to be working.
TWRP seems to be gone.
It claims to be Cyanogen 13.0-20160214-UNOFFICIAL-tate.
Android 6.0.1
kernel [email protected]#1
I had to replace the camera app and the launcher to make it
usable. Seems to do what I want.
Problem now is that battery drain is high in sleep mode.
I don't have any problem with working battery life. I'd just like to
be able to let it sleep for a few days and still have some battery left.
Battery is down ~50% in 24 hours of sleep.
The slope of the graph suggests that it's a constant load.
The "what's using the battery screen"
says it's almost all ANDROID OS.
Awake seems to be ON even in sleep.
On my other devices with stock ROMs, awake is OFF in sleep.
Everything else is very small.
In particular, wifi is about zero. Screen is about zero.
This does not appear to have anything to do with wifi.
Is there a fix for this? Configuration change? Different ROM?
Standby battery life is more important than the latest update.
There are literally thousands of pages on XDA about the battery problem,
but none seem to be specific to tate. Android nomenclature is not very
clear. It's difficult to determine exactly what applies to tate.
I've already turned off everything I can think of.
Problem is that the threads span 5 years. They start out with "this works"
and typically end with "this will permanently brick your tablet if you start
from the wrong state." Since I'm already at Cyanogenmod,
I'm assuming that's not an issue. Is that true?
I have no idea what I'm doing. I'M AFRAID TO BRICK IT.
I'm assuming that all I need to do is fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
with a different .img file and leave the recovery alone. True?
If there's a fix, I want it. If not, I don't want to be trying every version
of ROM and risk breaking it.
Can anybody share a known working sleep power drain fix for tate that's safe for a newbie
to attempt?
Thanks,

spamme0 said:
Kindle Fire HD7 X43Z60 tate
D025 seems to be 16GB.
I do not know the history of the device.
I got it at a swapmeet.
Stuck in a TWRP boot loop.
I have no idea what I'm doing.
I built a factory cable and followed this tutorial:
1. adb reboot bootloader (then in Fastboot mode) IIRC, I didn't have to do this, factory cable put it in fastboot.
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
_______________________________________________________________
Now it boots and seems to be working.
TWRP seems to be gone.
It claims to be Cyanogen 13.0-20160214-UNOFFICIAL-tate.
Android 6.0.1
kernel [email protected]#1
I had to replace the camera app and the launcher to make it
usable. Seems to do what I want.
Problem now is that battery drain is high in sleep mode.
I don't have any problem with working battery life. I'd just like to
be able to let it sleep for a few days and still have some battery left.
Battery is down ~50% in 24 hours of sleep.
The slope of the graph suggests that it's a constant load.
The "what's using the battery screen"
says it's almost all ANDROID OS.
Awake seems to be ON even in sleep.
On my other devices with stock ROMs, awake is OFF in sleep.
Everything else is very small.
In particular, wifi is about zero. Screen is about zero.
This does not appear to have anything to do with wifi.
Is there a fix for this? Configuration change? Different ROM?
Standby battery life is more important than the latest update.
There are literally thousands of pages on XDA about the battery problem,
but none seem to be specific to tate. Android nomenclature is not very
clear. It's difficult to determine exactly what applies to tate.
I've already turned off everything I can think of.
Problem is that the threads span 5 years. They start out with "this works"
and typically end with "this will permanently brick your tablet if you start
from the wrong state." Since I'm already at Cyanogenmod,
I'm assuming that's not an issue. Is that true?
I have no idea what I'm doing. I'M AFRAID TO BRICK IT.
I'm assuming that all I need to do is fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
with a different .img file and leave the recovery alone. True?
If there's a fix, I want it. If not, I don't want to be trying every version
of ROM and risk breaking it.
Can anybody share a known working sleep power drain fix for tate that's safe for a newbie
to attempt?
Thanks,
Click to expand...
Click to collapse
Not sure what the battery drain is here dude, mine's the complete opposite. I can have it in standby for up to 5 days and I'm running the latest resurrection remix rom.
My galaxy tab 2 on the other hand..... That's crap.

squ89r97 said:
Not sure what the battery drain is here dude, mine's the complete opposite. I can have it in standby for up to 5 days and I'm running the latest resurrection remix rom.
My galaxy tab 2 on the other hand..... That's crap.
Click to expand...
Click to collapse
Are you saying that you install it on a Kindle Fire HD tate?
If so, can you point me to the correct version to install?
Thanks, mike

spamme0 said:
Are you saying that you install it on a Kindle Fire HD tate?
If so, can you point me to the correct version to install?
Thanks, mike
Click to expand...
Click to collapse
https://forum.xda-developers.com/kindle-fire-hd/7-development/rom-t3297272/page34

squ89r97 said:
https://forum.xda-developers.com/kindle-fire-hd/7-development/rom-t3297272/page34
Click to expand...
Click to collapse
Thanks,
I never got anywhere with resurrection remix . On boot, it offers me two options for launcher, but neither
does anything. I'm dead in the water, stuck in the select launcher loop.
I did finally find BeanStalk-6.25...-tate
Everything seems to be working with OpenCamera
and standby consumption is very low.
I think I'm good to go.
I played with LineageOS. I liked it, but never could make the camera work.
Also had some issues with SAMBA shared files on my windows network
using my favorite File Expert HD,
but TotalCommander made that work.

Working on SailfishOS port: Boot issue

For funsies, I decided to attempt a port of Sailfish OS to the Kindle Fire HD 7 (Tate).
Using the Sailfish hardware adaptation kit, I was able to build an install zip without issues. The problem I am running into, is that on boot the device shows the orange kindle logo. It then fades to blue like it does with Cyanogenmod. And then goes direct to the fastboot screen where it stays.
For those familiar with this device, does this sound like a kernel issue, or another problem with the boot.img?
Fastboot commands do work, and rebooting to TWRP (and using ADB) also work.
My kernel was built from the Cyanogenmod 12.1 sources.

NullSpaceOddity said:
For funsies, I decided to attempt a port of Sailfish OS to the Kindle Fire HD 7 (Tate).
Using the Sailfish hardware adaptation kit, I was able to build an install zip without issues. The problem I am running into, is that on boot the device shows the orange kindle logo. It then fades to blue like it does with Cyanogenmod. And then goes direct to the fastboot screen where it stays.
For those familiar with this device, does this sound like a kernel issue, or another problem with the boot.img?
Fastboot commands do work, and rebooting to TWRP (and using ADB) also work.
My kernel was built from the Cyanogenmod 12.1 sources.
Click to expand...
Click to collapse
So you made your first Sailfish Port? I see you gave up (sadly) but the rom not booting at first is VERY COMMON, in fact, it is going to happen on 99.9% of first builds due to the finnicky nature of Sailfish OS. I reccomend you grab a telnet, dmesg, systemctl, or journalctl log and go to the #sailfishos-porters IRC channel (go on freenode) or debug it yourself. Hope you see this build through, the more devices running Sailfish, the more people will use it, the more popular it'll get, the more people will use it. Cheers! :laugh: :good:

NullSpaceOddity said:
For funsies, I decided to attempt a port of Sailfish OS to the Kindle Fire HD 7 (Tate).
Using the Sailfish hardware adaptation kit, I was able to build an install zip without issues. The problem I am running into, is that on boot the device shows the orange kindle logo. It then fades to blue like it does with Cyanogenmod. And then goes direct to the fastboot screen where it stays.
For those familiar with this device, does this sound like a kernel issue, or another problem with the boot.img?
Fastboot commands do work, and rebooting to TWRP (and using ADB) also work.
My kernel was built from the Cyanogenmod 12.1 sources.
Click to expand...
Click to collapse
due to the nature of the kfhd bootloader, this might be difficult, I think I might try to take a crack at this myself, as I just dusted off my old Kindle Fire HD 7inch (tate), and would love to run sailfish on it. I'll probably use CM11 sources though

Galaxyninja66 said:
due to the nature of the kfhd bootloader, this might be difficult, I think I might try to take a crack at this myself, as I just dusted off my old Kindle Fire HD 7inch (tate), and would love to run sailfish on it. I'll probably use CM11 sources though
Click to expand...
Click to collapse
Let us know how it turns out. I considered trying the CM11 source, but ran out of free time and the whole project got pushed to the back burner.

NullSpaceOddity said:
Let us know how it turns out. I considered trying the CM11 source, but ran out of free time and the whole project got pushed to the back burner.
Click to expand...
Click to collapse
I made a post asking for help, I got it to build, I used the omap4, tate, and bowser common device and kernel trees, and tinkered with them a bit to get it to actually, build. I have the issue you are having, it boots right into fastboot, and I think this is due to the finnicky bootloader of the KFHD. I can't even connect to telnet, which means sailfish never even starts. A possible fix does NOT come to mind (a bit to complicated for me), but I really hope I can figure one out. I pinged hashcode in my post, so maybe he will offer some assistance.

I did end up revisiting this multiple times with no success, I tried modifying how boot images are built, adding the freedom boot patch to the hybris-boot script, all that stuff. No luck. I think this is a case of the hybris-boot creator not being made to talk to the kfhd boot loader. if I knew more about how the second bootloader worked, I'd be able to play with it a bit.

Repeated shutdowns.

Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan

jonathanmoneill said:
Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
Click to expand...
Click to collapse
Symptoms are similar to a recently reported issue in the Lineage 12.1 thread if you applied the latest Nexus update. If that's the case simply roll back to the prior build.

Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?

jonathanmoneill said:
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
Click to expand...
Click to collapse
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.

Davey126 said:
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Click to expand...
Click to collapse
Thanks for the ROM advice. I love the Nexus ROm but I've been tempted by lineage for a while so I might take this opportunity to give it a go
In relation to sorting my current issues, the device doesn't shut down while the grey logo is being displayed, the OS loads and I usually get about 30-90 seconds of functioning before it dies again. Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).

jonathanmoneill said:
Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
Click to expand...
Click to collapse
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!

Davey126 said:
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Click to expand...
Click to collapse
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....

jonathanmoneill said:
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
Click to expand...
Click to collapse
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.

Davey126 said:
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Click to expand...
Click to collapse
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this

jonathanmoneill said:
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
Click to expand...
Click to collapse
I was the one having the update issues, but it was on the Lineage ROM! Looks like whatever ggow did, it's affecting both Nexus and Lineage. I think I'll just roll back to the previous build then restore apps.

Kindle Fire HD 7" - Reinstall Stock OS - No Root, 2nd Bootloader, Custom Recovery

Kindle Fire HD 7" - Reinstall Stock OS - No Root, 2nd Bootloader, Custom Recovery
OK this is my moms Kindle Fire HD 7" with complete stock Amazon OS installed currently with no root, no custom recovery, no 2nd bootloader or any such customization. Shes been having issues with it for a while now with it randomly shutting off regardless of battery %. It wont happen of course when its plugged in to the charger though. A while back we thought it was the battery dying or faulty somehow so she got a new battery and I installed that. Then she thought it was some game or app installed so she tossed everything to the cloud and tried pulling down one app or game at a time to see if it happened with one particular app. That didnt work either so she tried a return to factory defaults but she said the weirdest thing happened, she tried it multiple times and each time it asked her different parts of the setup. Never did the complete setup from when you first buy it and turn it on. I did at one point try the wipe from recovery mode and then it seemed to ask the complete setup questions. I want to just completely wipe /system and reinstall the OS from scratch, thinking something has been corrupted somehow. Ive tried grabbing the latest update from Amazon and putting in the root and going to Update OS from the settings but it doesnt do anything cause its already at the current version, 7.5.1.
Ive looked around the forums and various other sites found through google and its just been a sea of broken downloads, incomplete directions or just things that involve rooting or adding a 2nd bootloader or custom recovery and I dont want to mess with any of that. I just want to flash on the original OS and have it work right again the way it did when she first got it.
I understand I may have to create a fastboot cable and I am prepared to do so, I have the parts and just gotta do it. I have the Kindle Fire drivers and adb and fastboot set up and working as well on my Windows computer.

Bringing an old Nook HD+ back to life

Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben

benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Bumping my original post - can someone help please? Cheers, Ben

benobi37 said:
Hi there
First post so apologies in advance for any noob questions.
So I bought a Nook HD+ back in 2013 since my techie mates both had one and I bought one for the ride. From memory we used Cyanogenmod and CM11 or CM 12 I think, and installed an Ovation image. Since then I might have attempted an install of an ovation image from 2016, but have not used it at all. I've recently found the Nook HD+ in my storage boxes and wanted to either flash to the latest version or reset to stock to sell the unit off. However it no longer seems to want to boot up. Can anyone advise why it's not working when it was happily working back in the day, given nothing's been touched of late?
I charged it up and switched it on but it doesn't make it past the loader screen. Any ideas on what I should do to get this working again? Kinda don't want to spend time reloading an image or stuffing around with it as I only plan on offloading it assuming it's working.
I've tried to clear all cache and dalvik and various attempts to reboot. No difference to the outcome - always ends back at the loader screen.
I get a "Root Access possibly lost" message from time to time when trying to reboot. Doesn’t make a difference whether I choose yes or no, it ultimately ends up on that loader screen.
I’ve also tried booting into TWRP but don’t see any options to revert back to stock.
Any thoughts?
Cheers
Ben
Click to expand...
Click to collapse
Hey, one question, are you able to boot into TWRP? If so, you can flash any rom. Also, here is the link for installing stock rom again if you want. https://forum.xda-developers.com/nook-hd/development/stock-nook-hd-nook-hd-2-2-1-2018-update-t3840163 I personally haven't tested it though.