I used this dev build #241
With device tree gxbb_p200_2G_1Gbit.dtb
Device tree from 14th October. Dev. (device_trees)
If you can see your device on your network just copy to the update folder .
Otherwise fresh install.
Posts by kostaman
-
-
Tried power supply as well. Not the cause.
My wife still uses the MXQ and i have the MiniM8sPro s905 2gb / 8gb which is my favourite box.
I have a Mini MX 2gb/16gb s905 as well in another room. I have no real need for a S905x but can't believe how cheap these chip boxes are now. -
device_trees
You got the tree from above link ?
Your device is ?
Your Chip Is ? S905 OR S905X
- If you have a device with non-standard partition layout and have LE installed to internal memory, you have to perform a clean install.
-
@kostaman imo, likely capacitor as bad ram may not even boot up. Can you change the caps?It only has 1 Capacitor and there is no bulge at the top of it.
It's soldered from top to bottom so i couldn't be bothered. More than likely capacitor as the freezing kicks in when it warms up.
I might post it to PatrickJB , someone mentioned he's the man to pull these things apart and solder them. HA !
Thanks for replying. -
Yes I have 2 of the same, as you know, so I'm obviously interested as to where this all goes. Hope you get it sorted.Thanks for taking the time to read logs kszaq.
I was pretty sure it was Hardware failure but the symptoms may be useful to others who get the same behaviour.The box used to work using LE on Nand. It worked for a while on .006 and it was this version being used when the Hardware failed.
I went back to .004 and same result. Nand and SD card LE.
It only fails under CPU stressing. When cold it works for about 5 minutes browsing the network library and then freezes.
It gets to about 56c operating temp and that is when it occurs.
I don't believe it is overheating as this doesn't happen with my other identical box.
I pulled the board out of the casing and ran it but the same freezing occured.
It happens to an SD Card install of LE so it is not corrupt Nand.
I flashed 2 versions of Android that work on this box and the same freezing occurs during library browsing in Kodi Jarvis 16.1
I believe it may be bad RAM or bad capacitor.
These boxes are not salvageable when this occurs. -
Anyway hope the box isn't dead although it doesn't sound good.I'm not sure why this happened so i just thought the logs might identify the cause if indeed it might not be Hardware.
I will flash Android back after logs are checked and see if this freezing also occurs. I have 2 of these and only one is doing this , however i had a different Android rom on the working one. -
kszaq just need your thoughts on an all Black MXQ S805 which i believe has Hardware Failure due to the following symptoms.
The box is stock with no addons installed. Just network library.
This box was on .006 NAND when it started to freeze at random and now it freezes 10 out of 10 times when browsing library movies on my network. I ran debug and took logs.
The logs are .004 as i went back to .004 to test if it was the update. I also did a fresh SD Card install to test on .004 & .006 with the same freezing issues as running from NAND. There seems to be big spikes in cpu usage just before it freezes and becomes un responsive.
I am putting out here as this is the behaviour when hardware fails.
MXQ, board number: 'AM_MXQ_A 20150825 -
COuld it be the USB stick causing problems?Give it a go with SD Card. I've never used the USB LE.
Wait for kszaq to respond in the meantime. -
I've just had a minor bug come back from way back in the s805 journey.
My Backup folder decided to disappear again from /storage/backup
I rebooted twice. I un plugged box but it was gone. Tried file manager but it was gone.I then smb using file manager in MAC OS, Backup was there. I opened/mounted it and this caused the
folder to suddenly appear in LE file manager and in LE Settings Create System and Kodi Backup & Restore Backup.I had this happen once before so just putting it out there as this is what brought the folder back. :s
S805 - MXQ.arm 7.0.2.6 from Nand on all black MXQ, board number: 'AM_MXQ_A 20150825'
-
Thanks Kostaman got it working.However after shutting down the system and then leaving it a bit and trying to restart the android box I noticed it would nt load up (yes I left the USB stick in!). Instead once it got to the LE logo it had a dozen or so FAILED messages in text down the left hand side and then just got stuck refusing to load properly.
Any suggestions please?
Can you make a signature with the following :
Nexbox A95X B7N S905X 2gb/16gbMembers reading this post including me don't know your box. I had to go back looking for your previous posts to find it.
I don't know what the issue is with USB Booting and your Nexbox.
kszaq for this issue.
Did you try repeating recovery toothpick with the same USB stick to see what happens ?
I can't help further. Sorry i don't have this box nor do i use USB to run LE. I've only used SD Cards. -
Beelink M18 and an MXQ Pro+ (running a Tronsmart version of Android) with the latest dev build Oct 26 of LE.October 24th i hope ?
-
What means "formatted my link" there is something wrong?I only made that into a remote.conf file , i did not change it.
Copy pasted and named to remote.conf.
Sorry for any confusion. :s -
Must work, I have the same box.
Probably you haven't executed /usr/lib/libreelec/remote-config or reboot the system.I formatted your link to remote file to a remote.conf file for BeToven , just to make it clear.
I don't have this box. Just check you guy's are on same version of LE.
If it works for you , it should work.
Leave you guys to it. -
Great! Now mooving keys, return, audio keys are working.
Samall problem though , Power button powers off but there is no way to power on.Go to settings / system / power saving and choose Suspend as a shutdown function.
Try that and see if that allows you to power it back on via remote. -
not being able to power it on using the remote.Nexbox crap U-Boot . They have been advised but cant believe they release an MXQ Pro as well as the A95X s905 with no fix.
You're stuck with it unless Nexbox fix their Android firmware. -
I tried with the fole you sent me, with 777 permitions but still does not work.
Any other idea?V88 PRo.remote.conf.zip
Unzip and copy remote.conf
copy it to /storage/.config
The root of .config
Then reboot. -
It is if something was executed in the background and started using the CPU...
Mini M8S II S905X 2gb/8gb
Is this your box above ?
Please advise whether you used a device tree during fresh install ?
If you did , please disclose.
Are you using wifi when this happens ? If yes , try ethernet and report.
I don't have this box but my MiniM8sPro has a kernel panick if i dont use wifi fix device tree and freezes on wifi.
Are you pressing "o" with remote to bring up codec info? Take a screenshot with Hardware acceleration active. -
It was switching off from the Red button on remote control on Android firmwareSorry about this. In Android
If your box was powering off (I'm talking red button) as it clean powered off , when you turned it back on it powers on with animation etc.
You should leave settings as they are. Choose power off as shutdown function.
If you use the power menu to shut down / power off , you will not be able to power on via remote red button.
Basically power off with remote button and power on via remote button should work.
Use power menu to power off and it wont power back on.
Gee i'm trying to remember the variables with one of my previous All Black MXQ's that had this issue.