Vilok Lokhovskih Posted March 8, 2021 Share Posted March 8, 2021 (edited) Hi there, first of all big thanks to this community, what you're doing is awesome :-) Here is my question: I have Scishion v88 4k TV box, it had android 7 I've installed Armbian Buster legacy kernel 4.4.y on nand Configured network, rn it has OctoPrint, Klipper, working webcam etc. No questions, its all working great. But whenever I try to reboot it, it doesn't start up back, I gotta replug the power supply for a few sec, only then it starts up back. While it was on Android, it did the reboot correctly. Maybe it's something about exactly this model of tv box that does not let it to reboot on its own, it doesn't have an on\off buttons, so whenever I use it, I have to manually plug in the power supply and when I shut it down, manually unplug it. I think in the future I would use wifi smart socket for it, but I was wondering, if I could do anything about it using armbian configs or something. Should I upload logs or something? Which ones?) As far as I'm concerned, this is the specification of this board: Model: V88 Type: TV Box GPU: Mali-400 System: Android 5.1 CPU: RK3229 Core: 1.5GHz,Quad Core RAM: 1G ROM: 8G Max. Extended Capacity: 16G Color: Black Decoder Format: H.264,H.265 Video format: 4K,AVI,DAT,MKV,MOV,MPEG,MPG,RM,VC-1,WMV Audio format: AAC,FLAC,MP3,OGG,RM,WMA Photo Format: JPEG,JPG,PNG Support XBMC: Yes Power Supply: Charge Adapter Interface: AV,DC Power Port,HDMI,RJ45,SD Card Slot,SPDIF,USB2.0 Language: Multi-language System Bit: 32Bit Firmware Version: Android 5.1 Power Type: External Power Adapter Mode Power Input Vol: 5V Power Adapter Output: 5V 2A Here are few photos of this board: https://disk.yandex.ru/a/ohSrg-TeCuj_dQ (couldn't insert it by standard "insert image from URL", sorry Thanks a lot. Edited March 8, 2021 by Vilok Lokhovskih Link to comment Share on other sites More sharing options...
jock Posted March 8, 2021 Share Posted March 8, 2021 Hello. Unfortunately NAND-based boards have this issue about rebooting. It is common among most of them and still could not sort it out. Curiously using the mainline 5.10 kernel my NAND board reboots ok, but of course NAND is not accessible because the kernel driver is still missing. 1 Link to comment Share on other sites More sharing options...
Vilok Lokhovskih Posted March 8, 2021 Author Share Posted March 8, 2021 5 hours ago, jock said: Hello. Unfortunately NAND-based boards have this issue about rebooting. It is common among most of them and still could not sort it out. Curiously using the mainline 5.10 kernel my NAND board reboots ok, but of course NAND is not accessible because the kernel driver is still missing. Oh, okay then, thanks for the answer anyway It's not a big deal, I was just thinking, maybe I did something wrong and could fix it software-wise. No more questions then :-) Thanks Link to comment Share on other sites More sharing options...
jock Posted March 8, 2021 Share Posted March 8, 2021 52 minutes ago, Vilok Lokhovskih said: No more questions then :-) Thanks good questions are always welcome 1 Link to comment Share on other sites More sharing options...
Recommended Posts