It bricked btw flashing 912
flashing my stock bootloader back now via sd card
It bricked btw flashing 912
flashing my stock bootloader back now via sd card
Sorry im not explaining it right
PC3-12800 Runs at 800mhz which is 1600 DDR
is the 912mhz the actual mhz e.g. 1824 DDR
No.
Please test the u-boot@912Mhz_DDR3. I doubt that your stock uboot runs over the 1000..Mhz range
ok will make an image now with the amlogic customization tool
is that 912mhz/1824ddr
or
406mhz/912mhz ddr
then i need a log from stock u-boot
is there any way to get that without serial access as i dont have a serial cable
Which uboot should i use
i would like to retain alteast the ram speed that the stock uboot uses
H96 PRO+ 3GB 32GB
PCB CZ-S32-v2.2 20161012(A15)
QL 1730
JOB20170808 3+32/9377
1 x amlogic S912 OCTA-CORE BODGHN01404 J-TNA346.00
1 x 32GB Toshiba 19nm THGBMBG8D4KBAIR 170821AE EMMC HS400 V5.0 Read 270MB Write 90MB
1 x Fn-Link 8223A-SR COB009 1732 (QCA9377 433Mbps 1T1R 802.11a/b/g/n/ac BTLE 4.1)
1 x RTL8211F H6120H4 GH25 Gigabit Ethernet Transceiver
1 x GL850G HH4JB05Y22 713SGF9891 Genesys Logic 4 Port USB 2.0 Hub
2 x 1GB SpecTek 512X16DDR3 HL - FC4F 1708 / DY6L 1704 (SpecTek State 1600MHZ DDR3 1.5v) (rebadged Micron 512x16 DDR3L 1866 CL13)
2 x 512MB Micron 6EN77 D9SDD 3ZRJ (256X16 DDR3L 1866 CL13) D9SDD full PN=MT41K256M16LY-107:N
i have an mxq pro booting libreelec from internal
does libreelec write the dtb to the dtb partition or is it just stored on the system partition?
e.g. how do i update to todays dtb
i think i used gxbb p200 1gb mxq pro 4k.dtb
should i use gxbb p201 1gb.dtb?
ro.product.model=MXQ Pro
ro.product.brand=Android
ro.product.name=p201
ro.product.device=p201
ro.product.board=p201
PCB
MXQ-S905-D16
Ver:1.0 Date:151021
WIFI RTL 8189ETV
NAND 8GiB SK hynix H27UCG8T2ETR BC
RAM SAMSUNG K4B461646B-HCK0
Display MoreBought the Mecool M8S PRO L 4K TV Box Amlogic S912. This doesnt have a hard reset button
So I have installed the terminal. Previous to that flashed LE to memory card and also copied the dtb.img from device tree. Im having issues in rebooting.
$pwd
$/data/data/com.termux/files/home
I do reboot updateIt says "No command reboot found"
From where should I run this?
Note:- I only copied the remote.conf from Index of /MECOOL/ as mine is pro L
i use this to save me picking my fat ass up
What s912 device you own?
H96 PRO+ 3GB 32GB
PCB CZ-S32-v2.2 20161012(A15)
QL 1730
JOB20170808 3+32/9377
1 x amlogic S912 OCTA-CORE BODGHN01404 J-TNA346.00
1 x 32GB Toshiba 19nm THGBMBG8D4KBAIR 170821AE EMMC HS400 V5.0 Read 270MB Write 90MB
1 x Fn-Link 8223A-SR COB009 1732 (QCA9377 433Mbps 1T1R 802.11a/b/g/n/ac BTLE 4.1)
1 x RTL8211F H6120H4 GH25 Gigabit Ethernet Transceiver
1 x GL850G HH4JB05Y22 713SGF9891 Genesys Logic 4 Port USB 2.0 Hub
2 x 1GB SpecTek 512X16DDR3 HL - FC4F 1708 / DY6L 1704 (SpecTek State 1600MHZ DDR3 1.5v) (rebadged Micron 512x16 DDR3L 1866 CL13)
2 x 512MB Micron 6EN77 D9SDD 3ZRJ (256X16 DDR3L 1866 CL13) D9SDD full PN=MT41K256M16LY-107:N
hi thx to elbuit for the power on fix. i add boot logo and elbuit power on fix to this rom
Thanks just installed this on my MXQ Pro 4k same as yours
Install to nand works fine
Power on works fine
Recovery button dont work
had to use this to get to recovery (how i usually get to it)
Couple couple of questions, how much difference are we actually talking about? The current driver seems to work really well.
Second how much money are we talking about? Is this something we could crowdsource if justified?
i wouldnt worry about it i have an s905 and an s912
and tbh the s912 is fine just the same as the 905 in libreelec
kszaq has done a really good job
and on android its night and day better the s905 is a dog compared to the s912
This build seems to idle at lower temps than the last one My H96 Pro+ with an Odroid C1 Heatsink on it
idled at 47 in the last build its 43 in this
Odroid Remote as a secondary remote
remotesecond.conf
factory_code = 0x4db20001
factory_infcode = 1 #set as the second remote
work_mode = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay = 20
debug_enable = 1
key_begin
0xdc 31 #POWER OPTIONS
0x88 113 #MUTE
0x82 102 #HOME
0x99 105 #LEFT
0xc1 106 #RIGHT
0xca 103 #UP
0xd2 108 #DOWN
0xce 28 #ENTER (OK)
0xc5 23 #INFO
0x9a 158 #BACK
0x81 114 #VOL-
0x80 115 #VOL+
key_end
repeat_key_begin
repeat_key_end
Display More
As far as I can tell eMMC clock is determined by Amlogic driver depending on what is supported by eMMC chip. So far it works, I am geting decent R/W rates. I will not touch that code to not break anything.
For example on one of my devices it runs at 200MHz, 8-bit:
thanks
was that 200mhz ddr or sdr
i presume sdr due to the 200 clock and HS200
I noticed that the mmc only runs at 100mhz 8 bit ddr clock instead of 200mhz
due to a corruption bug so max interface bandwidth is 200 before overheads and such instead of 400
I seen some talk about rockchip chipsets bumping that to 150mhz as the corruption doesnt seem to show its self
to maximize performance and not get the corruption bug
is this something that could be done with the s912 as in the long term i would like to move to mmc
EMMC
[ 2.395069@1] mmc driver version: 1.07, 2015-01-21: fix a bug in tuning which caused eMMC data CRC error
[ 2.659473@3] emmc: try set sd/emmc to DDR mode
[ 2.659959@3] emmc: new HS400 MMC card at address 0001
[ 2.660587@3] emmc: clock 100000000, 8-bit-bus-width
SD Card
[ 14.529170@4] sdio: clk 200000000 SDR mode tuning start
[ 14.531451@4] sdio: new ultra high speed SDR104 SDIO card at address 0001
[ 14.531459@6] sdio: clock 200000000, 4-bit-bus-width
My box can turn on and off with LE (and android of course) from remote.
what dbt are you using for libreelec on your h96 pro+ and what base android image?
Ugoos are full of Bullshit. That is false advertising right there, because the 1.5GHz AML CPU hard limit has been known about for about a year.
As kszaq has already said only AML S9xx device we known of that can break the 1.5GHz barrier is the ODROID C2.
i just ran into that video yesterday i presumed they had added kernel support for 2ghz
Fix my C1 wrxtasy j/k im done with that thing
shutdown does works for me. Try with my remote.conf
im not saying i cant shut it down via remote
im saying i cant power the device back up via remote if libreelec shut it down
it powers back up fine via remote if i shut it down via android
I've bought some "karate" H96 Pro Plus 3/16.
When I get my hands on it, and cooling mod it,will see what's up with the dtb and remote.
Here's some setup info for you
Latest android firmware can be got direct from the manufacturer here latest atm 2017/08/26 alfawise is oem branding for gearbest
so banggood etc just have the stock 4k logo as they havnt requested branding on the outside
easiest way to update use burncard maker 2.02 and write it out to an sd card and boot from it with the reset button held down
libreelec device tree im using
my remote.conf
Create remote.conf from scratch
I have some 3m 8815 Thermal tape on order
and will be fitting my Odroid C1 Heatsink to the H96 Pro+ as its about twice the mass as the H96 Heatsink and the C1 can just live with the H96 Heatsink
Heat wise with the current stock heatsink
50° ish in android idle (after fixing rogue processes)
70° ish doing a full fresh library scan over smb in android
50° ish idle in libreelec
65° ish doing a full fresh library scan over smb in libreelec
50° playing a 1080p web-dl in libreelec
Update android temps are inline with libreelec now i noticed a rogue background process via adb
com.droidlogic.SubTitleService using a constant 12% or so cpu time
then another 12% or so on the system log
removing the SubtitleService from /system/SubtitleService and a reboot fixed it the log isnt going mad now either
Im not sure if this is a problem with the H96 Pro+ firmware (most prob not)
Its most prob down to the junk i removed below on first setup of android)
/system/presinstall = all deleted
/system/media/org.xbmc.kodi.zip = deleted (60mb of addons)
/system/app/appinstaller
/system/priv-app/dlna
/system/app/filebrowser
/system/app/gmail2
/system/OTAUPGRADE
/system/app/miracast
/system/app/music
/system/app/pppoe
/system/app/videoplayer
/system/tts/ all deleted apart from gb and us
changes to build.prop
en-GB
dd-MM-yy
#ro.platform.keepbackground.app=com.droidlogic.PPPoE
#ro.platform.has.pppoe=true
Display More
Then reset to factory defaults straight after doing this