Hello there, Fire 7 ,9th Gen (2019) complete Hickjack running Lawnchair V2 launcher, Use Fire Toolbox V13.1
Everything Was and is Runnig Fine, except When In sleep Mode It take like 40 to 60 sec to "wake up"
This only happen when is more that 1 min on sleep mode.
If you Push Power button to go sleep it turn off the screen, and immediately push again it wake up Normally .
I have Try Everything, Uninstall all Apps, Only Google play related, launcher, youtube vance.
I really cant find a answer To what can be happening.
Be grateful to have a Hand here.
English is no My 1st language.
Sorry If is no the place for This post.
Related
Hi all,
I am experiencing the dreaded sleep of death on my Lenovo K1, I cant post in the android development section as I dont have 10 posts yet. I flashed the V2 CM10 via NVflasher and then updated to V6 via Clockword Recovery. I have checked that my Wifi is set to "Always on", I have not done a system restore so this is a clean device. This is now my 3rd flash of this image with the same problem(My previous JB AOSP worked fine). Does anyone have any idea what I can try next?
Thanks!!!
I'm having the same problem with my WiFi version of the K1. I have flashed krook1's build a couple of times and have tried setting the WiFi to Always on. I also have tried Better WiFi On Off and Soft Locker apps to manage the wifi and keep it out of deep sleep (both recommendations in the dev forum) but neither have helped. Every time my screen goes off, the device appears to continue functioning; I can hear notifications going off for emails or text messages. If I try to turn on the screen again using the power button, the two lights on either side of the home button will flash but the screen does not turn on. I then have to hold the power button down and boot up the device again. It doesn't matter if the screen times out or if I turn it off manually, it will always die immediately after.
Ne3M said:
Hi all,
I am experiencing the dreaded sleep of death on my Lenovo K1, I cant post in the android development section as I dont have 10 posts yet. I flashed the V2 CM10 via NVflasher and then updated to V6 via Clockword Recovery. I have checked that my Wifi is set to "Always on", I have not done a system restore so this is a clean device. This is now my 3rd flash of this image with the same problem(My previous JB AOSP worked fine). Does anyone have any idea what I can try next?
Thanks!!!
Click to expand...
Click to collapse
Hi,
I was experiencing the same issue, the Sleep of death, and would not wake up after turning the screen off or locking the device.
After a lot of testing without positive results, I found this app from the market:
https://play.google.com/store/apps/details?id=com.omd.autoscreenon
It allows to have a "Wake Lock" sensor on all the time, it drains battery a little faster (I haven't noticed much of a difference) which seems to have solve the wake up problem.
I've tried this app the whole day and I haven't had any SoD so far.
Hope this helps.
Hi
I've purchased a Amazon Fire HD10 (2017) tablet for my daughter and have a couple of questions.
1. I purchased a case for it, which arrived from China after 15 days! It's meant to have an Auto/ Wake sleep function, but it doesn't work. Does the Amazon Fire tablet have this functionality, or does it have to be enabled somewhere?
2. I've set a profile up for my child with a lot of stuff locked down and a max of an hours use a day, however whenever the tablet is booted up it defaults to the parent profile. That's passworded but it means she has to bring the tablet to me and ask for it to be unlocked. Is there any way I can default it to her profile (which she knows the password too) so she can use it straight away?
Thanks!
Hi,
so title basically says it already - since 5.6.2.0 I have real problems with my 2017 Fire HD 8. The battery runs dry very quickly - charged last evening, only read a few pages of a book and otherwise standby, 37% at the morning. That can't be right. Nothing else installed since.
Also, there's an Alexa Accesoires notification that I can not get rid of. It's there all the time, regardless whether I deactivate Alexa.
Is there any known problem with 5.6.2.0 and battery draining? Is there a battery monitor I could use to find out who the culprit is?
And what about that Alexa notification? Thanks!
fBx said:
Hi,
so title basically says it already - since 5.6.2.0 I have real problems with my 2017 Fire HD 8. The battery runs dry very quickly - charged last evening, only read a few pages of a book and otherwise standby, 37% at the morning. That can't be right. Nothing else installed since.
Also, there's an Alexa Accesoires notification that I can not get rid of. It's there all the time, regardless whether I deactivate Alexa.
Is there any known problem with 5.6.2.0 and battery draining? Is there a battery monitor I could use to find out who the culprit is?
And what about that Alexa notification? Thanks!
Click to expand...
Click to collapse
Try a factory reset
Sent from my PH-1 using Tapatalk
The Alexa notification is known by Amazon, they're supposedly working on it. You can long press on the notification and when the "I" comes up you can turn that off.. until you reboot...
JoshHefnerX said:
The Alexa notification is known by Amazon, they're supposedly working on it. You can long press on the notification and when the "I" comes up you can turn that off.. until you reboot...
Click to expand...
Click to collapse
I did the long press and turned it off.
Just to check, I went ahead and rebooted - it hadn't been done in a couple months anyway so I figured it would need it - and that notification has not come back... so far.
Hi
Is there an way to make an app start on wake up?
I use Launch on boot, for Kodi and that works when it boots.
But the choise of start app on wake up does not work.
Is there some other way to do this?
I would have Kodi to stop/turn off when I put the Shield to sleep, and start Kodi again when it wakes up. This because then Kodi is started fresh
every time and works way better.
Petter
Hey,
I have a ticwatch pro 3 and one of the reasons i bought it were the long battery life and for alarms so i wouldnt wake my partner with an alarm in the morning.
After setting up the watch and configuring essential mode to start and end automatically when i am asleep i have noticed that when essential mode ends in the morning wear OS does not actually start unless i unlock the watch screen which is not ideal as the alarm will not go off unless i unlock screen first.
Is there some way around this? I basically still want essential mode to start and stop but also have my alarm go off without having to unlock the watch to start wear OS.
Appreciate any help
GrimEire said:
Hey,
I have a ticwatch pro 3 and one of the reasons i bought it were the long battery life and for alarms so i wouldnt wake my partner with an alarm in the morning.
After setting up the watch and configuring essential mode to start and end automatically when i am asleep i have noticed that when essential mode ends in the morning wear OS does not actually start unless i unlock the watch screen which is not ideal as the alarm will not go off unless i unlock screen first.
Is there some way around this? I basically still want essential mode to start and stop but also have my alarm go off without having to unlock the watch to start wear OS.
Appreciate any help
Click to expand...
Click to collapse
I read this on another forum, so please consider bringing watch up from essential mode after your alarm wakes you:
"I've tested this and already work on TicWatch Pro 3
Seriously, I've recorded it
All set alarms ring normally on ESSENTIAL MODE, waking me up as usual"
toncheee said:
I read this on another forum, so please consider bringing watch up from essential mode after your alarm wakes you:
"I've tested this and already work on TicWatch Pro 3
Seriously, I've recorded it
All set alarms ring normally on ESSENTIAL MODE, waking me up as usual"
Click to expand...
Click to collapse
Ok weird looks like i have some testing to do why it doesnt work for me.
thanks for the help and video.
I have the same issue...
i tested and no luck. I tried the exact same thing @toncheee video does and the alarm does not go off when in essential mode and instead goes off about a minute after i take the watch out of essential mode.
@toncheee @quack3d may i ask what version your watch is on mine is on
Code:
wear: OS 2.31
Home app: 2.51.0.398500942
Google Play store services: 21.36.14
system version: H MR2
Android Security Patch Level: March 5, 2021
@toncheee if you set an alarm and you go into essentials mode and then out of essential mode what happens if you have screen lock enabled. As that my main issue. watch comes out of essentials mode about 30 mins before alarm goes off but i need to unlock watch for wearOS to start and alarm to go off.
here is a video of me. sorry about the moving of the camera.
ticwatch-alarm
Watch "ticwatch-alarm" on Streamable.
streamable.com
Same versions as you except for: Google Play services: 21.36.55. Thread on the issue here too: https://forum.mobvoi.com/viewtopic.php?f=76&t=57963
quack3d said:
Same versions as you except for: Google Play services: 21.36.55. Thread on the issue here too: https://forum.mobvoi.com/viewtopic.php?f=76&t=57963
Click to expand...
Click to collapse
thanks it looks like its not just us with the issue, hopefully they will fix it soon as this is essential for me and other.