We are using Kindle Fire 7 tablets as our new tablet for customer with an app we built. The issue we are having is the screen will go blank if it has not been used for a little while. These are being used as a loyalty program with signup information so the screen need to stay on. We went into settings and the max is 30 minutes, is there a programming method we can include in our app or some type of java script that will stop this from happening ?
Generally the tablets will be in a stand on the counter so the last thing we want is customers to see a blank screen..
Thank You
Related
I rooted my kindle fire 7 2 and ever since it won't go into sleep mode screen just stays on. have been search but did not see anyone with that problem. any fix for this.
Application Hanging - Android will not Sleep
MisterSir69 said:
I rooted my kindle fire 7 2 and ever since it won't go into sleep mode screen just stays on. have been search but did not see anyone with that problem. any fix for this.
Click to expand...
Click to collapse
MisterSir69,
This is an odd problem. What method did you use to Root the Kindle? Once you give us this information
maybe I can back out what happened. Let's give you a little information that may help solve the problem.
What keeps the Kindle awake is either touching the screen or an application that has a "keep alive"
feature. A good example of Keep alive, it when we install remote access software on a customer computer
we always tell the software to not allow Windows to go to sleep so we can access it and perform
maintenance at night. Did you install some software after you Rooted the kindle? What software
did you install?
prokennexusa said:
MisterSir69,
This is an odd problem. What method did you use to Root the Kindle? Once you give us this information
maybe I can back out what happened. Let's give you a little information that may help solve the problem.
What keeps the Kindle awake is either touching the screen or an application that has a "keep alive"
feature. A good example of Keep alive, it when we install remote access software on a customer computer
we always tell the software to not allow Windows to go to sleep so we can access it and perform
maintenance at night. Did you install some software after you Rooted the kindle? What software
did you install?
Click to expand...
Click to collapse
I used your method to root it not really installed anything other then go luancher and google play store, also installed a task killer
I'm sure you checked this but...
Settings > Sounds & Display > Screen timeout.
Sent from my KFHD7 using xda premium
How to isolate Services Running
MisterSir69 said:
I used your method to root it not really installed anything other then go luancher and google play store, also installed a task killer
Click to expand...
Click to collapse
MisterSir69,
What I would do is install a solid Process Manager like Android Process Manager, then reboot the Kindle, wait
about 5 minutes, do not do anything on the Kindle for 5 minutes. Then open the Process Manager and see
what is running. Then kill one by one until the Kindle falls asleep. I would set the Display Sleep Timer at
the lowest setting so you do not have to wait long between each process.
prokennexusa said:
MisterSir69,
What I would do is install a solid Process Manager like Android Process Manager, then reboot the Kindle, wait
about 5 minutes, do not do anything on the Kindle for 5 minutes. The open the Process Manager and see
what is running. Then kill one by one until the Kindle falls asleep. I would set the Display Sleep Timer at
the lowest setting so you do not have to wait long between each process.
Click to expand...
Click to collapse
thanks worked looked like a wallpaper app was causing the issue
Follow Up - Feedback
MisterSir69 said:
thanks worked looked like a wallpaper app was causing the issue
Click to expand...
Click to collapse
MisterSir69,
Great work MisterSir69! I knew you would be able to figure out which service was causing you trouble.:good:
Yes, we have seen wallpaper, specifically live wallpaper, disable the sleep mode on Android devices.
This is a real bug, when you have time send the results to the developer, if you know the source.
You can usually find the developers contact information in Google Play.
Just got mine yesterday and finally started playing with it tonight. Only issue so far is Amazon Kindle app will not work. Launches, shows the splash screen and the loading circle, then just disappears. No notice about FC or anything.
Any ideas? Found another thread about gpu force rendering, tried to run it with it checked and unchecked, still no go. I like to read quite often on my lunch break, so this is a major issue for me.
I had a very odd experience with my tablet last night. After a few hours of non-use, I picked it up to begin reading. Went to adjust the brightness level and pulled down the settings bar. I noticed the bar was behaving strange, like as soon as I pulled down, it would snap right back up. There was also a flicker at the bottom of the shade. Unable to access anything there, I went into my app drawer to do something else. As soon as I went in, things got even stranger. Apps began opening themselves. Two games in particular, Gunman Clive and Lep's World 2. I would watch as the game opened by itself, then once inside the game, I would hit quit. The app, would immediately re-open.. This happened several times over. After the first app stopped doing that, it began opening the second app. Tried closing that one several times the same way and watched it re-open the same way. I decided to go further in Lep's World once it opened again. I watched as the character began jumping(but, not walking) on his own. Exited this app. Next my Kindle opened up the settings for LMT launcher on it's own. It did this same thing with these 3 apps, almost as if something(or someone) has compromised by tablet. I could physically see the buttons being pushed for these apps and it was not being pushed by my finger.
Fed up, I attempted to restart via Quickboot. Just as soon as I opened Quickboot, instead of me having a chance to pick one of the boot options, it would pick Hot Boot for me. This happened a couple of times, but finally I was able to do a full reboot. After the full reboot, My Kindle started up normally and there seems to be no sign of anything like this happening since.
Has anyone ever heard of anything like this before? Please tell me I'm not hacked. I'm running hashcode's CM 10 with Nova Launcher if that makes any difference.
Sounds like your digitizer went nuts
Sent from my GT-P3110 using xda app-developers app
Try installing this app and enabling screen touches. At least then you can see where the Kindle is touching itself (as weird as that sounds:what: ). Just a thought.
http://forum.xda-developers.com/showthread.php?t=2124384
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
I have a problem that's almost identical to something similar. My settings bar behaves strangely and I get the flicker at the bottom of the shade. My apps start behaving strangely. It seems to happen about once a week. I believe it happens after my apps have been automatically updated. To solve my problem I run Clean Master app and select the memory boost and junk folders tiles. After the cleaning the problem goes away until it happens again.
Was your device connected to a wall charger when misbehaving? With some power adaptors it detects more than a touch for every real touch, which could explain the weird behaviour you described.
Sent from my Amazon Kindle Fire HD using Tapatalk 4
I have had similar problems in the past and, odd as it may seem, my issue was a dirty screen. You see, I noticed that several "touches" were occurring on a particular area of the screen, the area taken up by the d pad in minecraft pe. I believe that the accumulation of fingerprints and skin oils was enough for the screen to recognize a touch. It still happens from time to time and always stops when I clean my screen. I've found that a little bit of purel and a soft napkin work great. Good luck!
First things first, grab some PopCorn. Now, here's is my story between me and Samsung
Day 28/04/2018 - The beginning
Well, on 28/04/2018, my tablet went to warranty because it could not charge. It when't with the version T810XXU2DRB1 (latest official version of Android to this model on my region) .
The days have passed....
Day 19/05/2018 - Tablet arrived
On 19/05/2018, I received my tablet back. Samsung said that they replaced the main board the updated the software.
After I receive, immediately made the setup. I updated every single app and installed Instagram, Facebook, and PubG (because, why not). Then, I checked the software version and it was T810XXU2DRB1. So, after it was setup completely, I went to sleep...
Day 20/05/2018 - The heartbreak day
In the next day, I played PubG to test if the tablet performance was still the same before going to warranty. Well, it was a total disaster. The tablet (with the same firmware version before going to warranty), was slower after going to Warranty. Every single app was freezing. The settings app of android was also freezing. Well, I thought "this is the setup, in the beginning is slower because is setting up the android and its apps".
Well, things got worst. Facebook was lagging, Instagram app was getting everything black on the screen (the screen was completely black, with the exception of the android top bar that was on the screen) and the screen was not responding sometimes. Also, when I was installing the apps from Play Store (the Facebook, Instagram and PubG app), the Play Store was freezing sometimes, and the screen sometimes was not responding (not even the android top bar). Ohh I forgot, and yes, it had more than 80% of battery and I never put it in power save mode.
Again, before going warranty the device only had the charging issue, the play store and the other apps didn't freeze.
Then I saw device information on settings app. After some time, the battery reached 10%.
While on Instagram and after the battery reached 8%., it started to show on the screen some vertical lines and each line with a single color, and the lines had different colors. Then, the screen stopped responding until I pressed the power button to lock the device and then unlock it (and it made the lock sound). After that, passed some seconds/minutes, the device made the same thing again and again.... :crying:
Then, passed some minutes, the screen was getting black and not responding. Again, I tried the same trick and the screen worked for some seconds before getting black. While locking the device with the screen black, again, I could hear the locking sound effect. Then, on the day 20/05/2018, I sent back to warranty because the device was worst after going to warranty.
Day 24/05/2018 - The Call
Today, they called me to go to the Samsung Store tomorrow to "demo" what’s happening on my tablet. What can I do about this situation? The tablet warranty is finishing this year on the summer (July or June maybe).
Stay tuned to this story between me and Samsung
What is your opinion? Don't forget to comment below ZenJB
as far as i know, in Indonesia, Samsung is quite famous for its service center.
btw, good luck, hope they will replace yours with a new one
@ZenJB just turn on logcat and you will see what is problem here.
Please excuse me if this has been covered elsewhere BUT!
I have just bought a fire 10 hd to use as a photoframe to display my Google photo albums. I'm using Fotoo which is able to schedule start & stop times, the stop works fine and afterwards the tablet goes to sleep but it will not switch on again. This worked in Jan 2022 but stopped sometime later in the year so I assume amazon have removed something within the OS that enables this.
I've looked for anything that could help in settings but there is nothing and I've tried various task managers but they seem to suffer the same problem so I just wondered if anyone here might have a solution or work around?
For anyone searching for a solution to this the issue is with the Fire OS removing some std os features around Nov 2022, however, you can get round this using the Fire Toolbox found on this forum