Timeline for Android tablet kiosk development
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 6, 2015 at 11:51 | comment | added | aivknow tech | Yes Thanks moonbutt74, this gives a very clear idea regarding how I can achieve it. I had looked for it many places. Thank you again. | |
| Aug 6, 2015 at 11:50 | vote | accept | aivknow tech | ||
| Aug 6, 2015 at 11:43 | comment | added | moonbutt74 | You would need to be root to pull your boot.img. You would also need to be root to write it back. The edit may be slightly different for your device but the approach should work exactly the same. You would be reassigning a service directly connect to battery charging from power-off state to run reboot command instead, effectively booting your tab to OS when you plug it in. | |
| Aug 6, 2015 at 11:01 | comment | added | aivknow tech | Hi I was going through the documents related to it. I think you are pointing to the correct point. I would like to know few more points, I will need root permission to do this isn't it ? Also do I need the source of the ROM or just unpacking ram-disk will make the changes permanent ? | |
| Aug 6, 2015 at 4:32 | comment | added | aivknow tech | Great thank you boombutt74. I will try and update the result | |
| Aug 5, 2015 at 21:15 | history | edited | moonbutt74 | CC BY-SA 3.0 |
deleted 184 characters in body
|
| Aug 5, 2015 at 15:30 | history | edited | moonbutt74 | CC BY-SA 3.0 |
added 26 characters in body
|
| Aug 5, 2015 at 14:50 | comment | added | moonbutt74 | @aivknow tech check my edit, if this is what you mean, start tab from powered off state by plugging in charger then try the above. | |
| Aug 5, 2015 at 14:47 | history | edited | moonbutt74 | CC BY-SA 3.0 |
deleted 993 characters in body
|
| Aug 5, 2015 at 5:46 | comment | added | aivknow tech | Thanks for your your answers. I think daydream might not make much difference. please see more thoughts on the Edit. | |
| Aug 4, 2015 at 14:24 | history | edited | moonbutt74 | CC BY-SA 3.0 |
added 1 character in body
|
| Aug 4, 2015 at 14:18 | history | edited | moonbutt74 | CC BY-SA 3.0 |
added 549 characters in body
|
| Aug 4, 2015 at 14:14 | comment | added | moonbutt74 | @aivknow tech, ok neat, so this is where my thought process is going continuing with suspend/resume issue and permissions EDIT - see above, can't wrap thins right in comment... | |
| Aug 4, 2015 at 14:02 | comment | added | aivknow tech | This is for locking the device when power is not connected. Yes my application runs all the time on the device. there is not other foreground application. | |
| Aug 4, 2015 at 13:55 | comment | added | aivknow tech | It is having admin policy permissions also. please see the update given. | |
| Aug 4, 2015 at 13:41 | comment | added | moonbutt74 | @aivknow tech , hmm what permissions does you app have? is it running in foreground when the issue occurs? Is this issue originating from the device or from the device while running the application? | |
| Aug 4, 2015 at 12:46 | comment | added | aivknow tech | Hi , I am not using custom kernel, I have updated the question to depict the scenario well. application is using hardly 10%-15% CPU max and most of the time it is not having any processing in the background. | |
| Aug 4, 2015 at 12:26 | history | answered | moonbutt74 | CC BY-SA 3.0 |