Even Power on might have problems on s905x - just wait a bit longer (12+ hours) and only a "unplug/re-plug power cord" will help.
Posts by GWR
-
-
There was a change in AP6212 firmware that might have broken something. UnfortunatelyDoes the new build (20161201...) incorporate this changed firmware? Tried it and wifi connected but no ssh etc possible.
Is there a simple way to update the file on my own - so I could play with various revisions?
If so: from where to get/build and where to store it?bye
Ron -
Can you please try 7.0.2.008 build?Et voila... reformatted the card with your 008-build, connected to my AP and wireshark came alive fetching dozens of packets. Successfully SSHed into the box and yep.
Works ...
Edit1: ok ... stopped working after a very short period (ssh does no longer respond, addon-updates stay at 0%)Edit2: So I tried a bit more: disconnecting the wifi, disabling/enabling wlan0 etc: for the first time it "repaired" it: was able to ssh in the box, kodi fetched the right sytem time (time zone etc from AP). But I was not able to reproduce it. I then restartet the whole box (real power-off with AC disconnect) and after startup it worked again ... for some seconds until it became more and more sluggish. Within the SSH console I checked "top" whether the sluggishness came from high cpu load... nope, kodi.bin <50%. But using "cursor up" for "last command" sometimes took 2-3 seconds, or even did not react at all. Retrieving a samba share somehow failed - maybe because of the veeeery low connection speed.
Edit3: I measured connection speed via "scp" and sometimes I get
Upload speed: 1440.19 kB/s
Download speed: 1885.92 kB/s
sometimes
Upload speed: 272.37 kB/s
Download speed: 1449.15 kB/s
and sometimes it just times outDownload speed (= from box to my computer) staying > 1400kB/s which far away from the possibilies for a "next room AP" but more than the opposite direction)
This makes a driver bug more and more likely to be the source.
Just for personal interest: this are the SCP speeds via the 100mbit lan connection:
Upload speed (to box): 10607.92 kB/s
Download speed (from box): 2321.63 kB/svia lan the speed-limitations are in the other direction ... odd
I also replaced the dtb.img file with mine as the other one failed to play videos (I only tried a 20mb mkv over smb share - which buffered 3-4 seconds and played for one minute before it "stopped" playing inbetween - playing it again finished the 2 minutes. Dunno if there is another "problem"...)
So I think it "works" but with a really non-constant transfer rate.
My remote has more keys than configured in the android-firmwares "remote.conf" (they ignore the "color buttons" and "numbers"). If there is interest I would use irrecord to fetch the data so the remote.conf would be complete).
It looks like this (ok, the "circular part" is split on mine, but keys and arrangement are the same)
-
Thanks for your fast reply.
I would not worry about "slow wifi" if it was slow - but it just does not do something "data transfer" wise (
no incoming packages from that device seen in wiresharkWireshark of my computer receives "airplay" packages from the device)- it works when booting from android (accessing samba shares, retrieving data from internet)
- it does not allow a communication when booted LE from the sd cardSo I assume there is something borked. Maybe driver is not working as expected? Or a setting is incorrect (no "power").
Edit:
- as mentioned I can see broadcasted "airplay" packages via wireshark, box also announces host to LAN (but not accessible from outside)
- webpage via ip:8080 is not reachable
- ssh'ing into the box is not possible (timeout)
- I extracted my boxes boot.img and via "split_bootimage.pl" I splitted apart the dtb.img file, replaced the one of boot medium and tried that - without changes (if interested it in: its a ~80kb file but I was not able to "dtc" it as the magic numbers failed)plugging in the lan-cable (possible until the device moves to my parents at christmas ;-)) makes everything reachable via the LAN-IP. So it is a direct matter with the wifi-chip/connection/setup and no "samba issue" or other misconfiguration
-
Wired worked as supposed.
A pity I already updated to the last available firmware (it fixed CEC bugs).
Meanwhile I installed mitmproxy on my box and redirect https traffic to my main computer. Now the OTA data traffic is just returning a "nothing new found" instead of a firmware-download link. But maybe the "mid" (the id of the device on that platform) helps to see if someone has the same device.HTTP
Display Moresent: POST /ota/detectdown/detectSchedule.do HTTP/1.1 Content-Type: application/x-www-form-urlencoded Host: fota4.adups.cn User-Agent: Apache-HttpClient/UNAVAILABLE (java 1.4) Content-Length: 1106 key=BA0800000000000 ..... very long serialized key-string --- response HTTP/1.1 200 OK Server: nginx/1.6.0 Date: Wed, 30 Nov 2016 07:27:39 GMT Content-Type: text/html;charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Content-Language: zh-CN {"flag":{"LUrl":"no","isInner":0,"isupgrade":1,"displayApp":0,"rand":"673902368","updateStep":0,"DUrl":"http://hwfotadown.mayitek.com/ota/","mid":"20160825185836hu2205","connfreq":"2940"},"status":1010}
Ignore above - was from my s905x-device (happens if you want to do things for two devices). The S812-box has no root which makes it more difficult to play with.Regarding dtb - I tried to extract the "boot.img" by fetching the newest firmware and extract from there. Now it sounds as if you tell us, this wont help as the u-boot does not support custom dtb.img files on the sdcard? Did I understand that correctly?
-
(There is no reason to "full quote" - it makes it harder than needed to see the answer)
Even if I doubted that this is the solution (I think its a driver issue, not a LE config issue) I tried it.
Did not help.But nonetheless: thanks for the suggestion.
bye
Ron -
If you are talking about the "backup and restore" tool - it is visible if you go to the "full app list" and then use the "down" button to show the next app page - at least it is that way on my box (which has this hm... "colorful" launcher too).
bye
Ron -
I run that "Beta"-Image on a S812 2gb-Ram/8gb-Flash device:
- remote did not work
- wifi has no "data-transfer" (lan, internet) but is able to connect to the router and gets IP / DNS-IP-Assignment / ...
- RAM was recognized as "of 1785 mb" or so (not 2gig)for the remote I extracted it from the android firmware (/etc/remote.conf -> usb-stick, works without root). After putting that file on the "LE-stick /storage/.config/remote.config" the remote worked within Kodi.
For Wifi I am a bit clueless:
- wifi/40183/fw_bcm40183b2.bin seems to be the binary blob for the wifi chip - and this file is very known to some libre/open-elec code repositories, I just do not know if it is contained in your imageJust to have it stored "online" and maybe someone is searching it - the remote.conf for the "skykirin remote" (seems to be the internal name from the devs).
Code
Display More#********************************************************************************************************* #this file is configuration for each factory remote device # work_mode 0 :software mode 1 :hardware mode # repeat_enable 0 :disable repeat 1 :enable repeat # # factory_code each device has it's unique factory code. # pattern:custom_code(16bit)+index_code(16bit) # examble: 0xff000001 = 0xff00(custom cod) 0001 (index) # # release_delay unit:ms.release will report from kernel to user layer after this period of time # from press or repeat triggered. # # debug_enable 0 :debug disable 1 :debug disable # # SW MODE: # bit_count how many bits in each frame # tw_leader_act time window for leader active # tw_bit0 time window for bit0 time. # tw_bit1 time window for bit1 time # tw_repeat_leader time window for repeat leader # REG # reg_base_gen set value for PREG_IR_DEC_BASE_GEN # reg_control set value for PREG_IR_DEC_CONTROL # reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE # reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE # reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE # reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME #************************************************************************************************************* #amlogic NEC remote skykirin02 factory_code = 0xfe010001 work_mode = 0 repeat_enable = 0 repeat_delay = 40 repeat_peroid = 39 release_delay = 121 debug_enable = 1 fn_key_scancode = 0x00 left_key_scancode = 0x51 right_key_scancode = 0x50 up_key_scancode = 0x16 down_key_scancode = 0x1a ok_key_scancode = 0x13 #pageup_key_scancode = 0x04 #pagedown_key_scancode = 0x1b mouse_begin 0 0x51 1 0x50 2 0x16 3 0x1a mouse_end key_begin 0x40 116 0x4d 70 0x41 113 0x4c 114 0x11 115 0x51 105 0x50 106 0x16 103 0x1a 108 0x13 97 0x10 125 0x18 102 0x19 158 0x4e 2 0x0d 3 0x0c 4 0x4a 5 0x09 6 0x08 7 0x46 8 0x05 9 0x04 10 0x42 14 0x01 11 0x00 63 key_end repeat_key_begin 0x4d 70 0x41 113 0x4c 114 0x11 115 0x51 105 0x50 106 0x16 103 0x1a 108 0x13 97 0x10 125 0x18 102 0x19 158 0x4e 2 0x0d 3 0x0c 4 0x4a 5 0x09 6 0x08 7 0x46 8 0x05 9 0x04 10 0x42 14 0x01 11 0x00 63 repeat_key_endTell me if I could help out somehow to make Wifi work.
-
Hi,
I just tried the most current 7.90 build and the 7.0.2 build on my parents christmas box (s905x). I did not need to copy a custom dtb.img (I tried, but problems stayed the same).
No installation was made (nand), just booted from microsd.
RAM (2GB) were recognized, no odd cpu core usages, ...During "Initial Setup"-phase I selected my Wifi and entered my passphrase. Then an error popped up at the bottom, saying it got no response. The wifi list refreshed and correctly displayed an assigned DHCP-IP.
Also the LibreElec "Network"-information-panel displayed this IP, also subnet and DNS IPs were correct.But I was not able to reach my LAN (eg. samba shares) nor WAN (addon updates). My other computers were not able to reach the box' IP (via SSH). Plugging in a lan cable made it get assigned another IP - which is reachable by my computers, also LAN access is possible again.
I tried that autostart.sh-thing (it also executed without errors) but after restarts the Wifi-option in LE went missing - so I assume it wasn't the right thing to do.
dmesg of the box mentions this:
Code
Display More[ 18.555946@2] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI Disable! 240 [ 18.864060@2] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI Enable! 240 [ 19.015877@0] 8021q: 802.1Q VLAN Support v1.8 [ 19.201066@2] sdio: queuing unknown CIS tuple 0x80 (2 bytes) [ 19.204478@2] sdio: queuing unknown CIS tuple 0x80 (3 bytes) [ 19.207687@2] sdio: queuing unknown CIS tuple 0x80 (3 bytes) [ 19.213826@2] sdio: queuing unknown CIS tuple 0x80 (7 bytes) [ 19.378142@2] sdio: new high speed SDIO card at address 0001 [ 19.392696@3] cfg80211: Calling CRDA to update world regulatory domain [ 19.409459@3] dhd_module_init: in [ 19.409473@3] ======== bcm_wlan_set_plat_data ======== [ 19.409477@3] host_oob_irq: 100 [ 19.409480@3] host_oob_irq_flags=0x414 [ 19.409484@3] dhd_wifi_platform_load: Enter [ 19.409500@3] Power-up adapter 'DHD generic adapter' [ 19.409503@3] wifi_platform_set_power = 1 [ 19.409506@3] ======== PULL WL_REG_ON HIGH! ======== [ 19.409527@3] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI Disable! 240 [ 19.609590@3] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI Enable! 240 [ 20.114028@3] wifi_platform_bus_enumerate device present 1 [ 20.114040@3] ======== Card detection to detect SDIO card! ======== [ 20.114044@3] sdio_reset_comm(): [ 20.135126@3] sdio: queuing unknown CIS tuple 0x80 (2 bytes) [ 20.137991@3] sdio: queuing unknown CIS tuple 0x80 (3 bytes) [ 20.140638@3] sdio: queuing unknown CIS tuple 0x80 (3 bytes) [ 20.145358@3] sdio: queuing unknown CIS tuple 0x80 (7 bytes) [ 20.296971@2] [sdio_reinit] finish [ 20.313408@0] bcmsdh_register: register client driver [ 20.313511@2] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter [ 20.313894@2] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter [ 20.313904@2] bus num (host idx)=0, slot num (rca)=1 [ 20.313909@2] found adapter info 'DHD generic adapter' [ 20.314302@2] sdioh_attach: set sd_f2_blocksize 128 [ 20.314523@2] dhdsdio_probe : no mutex held. set lock [ 20.314602@2] F1 signature read @0x18000000=0x1530a9a6 [ 20.316476@2] F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x0 pkg:0x3 [ 20.317226@2] DHD: dongle ram size is set to 524288(orig 524288) at 0x0 [ 20.317351@2] dhd_conf_set_chiprev: chip=0xa9a6, chiprev=0 [ 20.317392@2] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt [ 20.318862@2] dhd_conf_read_nv_by_chip: nv_by_chip_count=9 [ 20.318876@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=0, name=nvram_ap6181.txt [ 20.318880@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt [ 20.318885@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=0, name=nvram_ap6212.txt [ 20.318890@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=1, name=nvram_ap6212a.txt [ 20.318894@2] dhd_conf_read_nv_by_chip: chip=0x4345, chiprev=6, name=nvram_ap6255.txt [ 20.318899@2] dhd_conf_read_nv_by_chip: chip=0x4330, chiprev=4, name=nvram_ap6330.txt [ 20.318903@2] dhd_conf_read_nv_by_chip: chip=0x4339, chiprev=1, name=nvram_ap6335.txt [ 20.318908@2] dhd_conf_read_nv_by_chip: chip=0x4356, chiprev=2, name=nvram_ap6356.txt [ 20.318912@2] dhd_conf_read_nv_by_chip: chip=0x4335, chiprev=1, name=nvram_bcm4335.txt [ 20.318965@2] dhd_conf_read_config: mimo_bw_cap = 1 [ 20.319208@2] dhd_conf_read_config: bcn_timeout = 20 [ 20.319266@2] dhd_conf_read_config: kso_enable = 0 [ 20.319488@2] dhd_conf_read_config: PM = 0 [ 20.320611@0] wl_create_event_handler(): thread:wl_event_handler:b13 started [ 20.320779@0] tsk Enter, tsk = 0xffffff80043e3940 [ 20.321248@0] dhd_attach(): thread:dhd_watchdog_thread:b16 started [ 20.321305@0] dhd_attach(): thread:dhd_dpc:b17 started [ 20.321319@2] dhd_dpc_thread: set dpc_cpucore 0 from config.txt [ 20.321348@0] dhd_attach(): thread:dhd_rxf:b19 started [ 20.321361@0] dhd_deferred_work_init: work queue initialized [ 20.328884@2] Dongle Host Driver, version 1.201.59.6 (r506368) [ 20.328884@2] Compiled in drivers/net/wireless/bcmdhd [ 20.329558@0] Register interface [wlan0] MAC: 44:2c:05:65:07:c2 [ 20.329558@0] [ 20.329572@0] dhd_prot_ioctl : bus is down. we have nothing to do [ 20.329641@2] bcmsdh_oob_intr_unregister: Enter [ 20.329648@2] bcmsdh_oob_intr_unregister: irq is not registered [ 20.329657@2] dhd_txglom_enable: enable 0 [ 20.329662@2] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0 [ 20.329665@2] dhd_conf_set_txglom_params: txglom_bucket_size=0 [ 20.329669@2] dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0, bus_txglom=0 [ 20.329672@2] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0 [ 20.329676@2] dhd_bus_devreset: WLAN OFF DONE [ 20.329720@2] wifi_platform_set_power = 0 [ 20.329724@2] ======== PULL WL_REG_ON LOW! ======== [ 20.329728@2] dhdsdio_probe : the lock is released. [ 20.329874@0] dhd_module_init: Exit err=0So it seems as if the driver which is selected, is not perfectly fitting to the one of the hardware in the box. While others had "BT and Wifi"-problems I just tried BT and it paired without any trouble with my Smartphone.
Any suggestions how to narrow down the bug - and how to bring wifi to function?
Ah... and as I am just posting: CEC was recognized correctly, but remote of my TV still controlled the TV instead of the box. In my test with 7.0.2 this was working as intended. (edit: now it is working again... hmm, will observe that a bit).
Edit:
This is the dmesg-part when enabling wifi again and connecting to one of my routers.Code
Display More[ 2524.565590@3] Dongle Host Driver, version 1.201.59.6 (r506368) [ 2524.565590@3] Compiled in drivers/net/wireless/bcmdhd [ 2524.565600@3] wl_android_wifi_on in 1 [ 2524.565606@3] wl_android_wifi_on in 2: g_wifi_on=0 [ 2524.565611@3] wifi_platform_set_power = 1 [ 2524.565616@3] ======== PULL WL_REG_ON HIGH! ======== [ 2524.565642@3] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI Disable! 240 [ 2524.765679@3] aml_wifi wifi.32: [extern_wifi_set_enable] WIFI Enable! 240 [ 2525.273358@3] sdio_reset_comm(): [ 2525.293246@2] sdio: queuing unknown CIS tuple 0x80 (2 bytes) [ 2525.295843@2] sdio: queuing unknown CIS tuple 0x80 (3 bytes) [ 2525.298426@2] sdio: queuing unknown CIS tuple 0x80 (3 bytes) [ 2525.303069@2] sdio: queuing unknown CIS tuple 0x80 (7 bytes) [ 2525.452881@2] sdioh_start: set sd_f2_blocksize 128 [ 2525.453131@2] [ 2525.453131@2] [ 2525.453131@2] dhd_bus_devreset: == WLAN ON == [ 2525.453217@2] F1 signature read @0x18000000=0x1530a9a6 [ 2525.455048@2] F1 signature OK, socitype:0x1 chip:0xa9a6 rev:0x0 pkg:0x3 [ 2525.455724@2] DHD: dongle ram size is set to 524288(orig 524288) at 0x0 [ 2525.456240@2] dhd_conf_read_nv_by_chip: nv_by_chip_count=9 [ 2525.456246@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=0, name=nvram_ap6181.txt [ 2525.456250@2] dhd_conf_read_nv_by_chip: chip=0xa962, chiprev=1, name=nvram_ap6210.txt [ 2525.456255@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=0, name=nvram_ap6212.txt [ 2525.456259@2] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=1, name=nvram_ap6212a.txt [ 2525.456264@2] dhd_conf_read_nv_by_chip: chip=0x4345, chiprev=6, name=nvram_ap6255.txt [ 2525.456268@2] dhd_conf_read_nv_by_chip: chip=0x4330, chiprev=4, name=nvram_ap6330.txt [ 2525.456273@2] dhd_conf_read_nv_by_chip: chip=0x4339, chiprev=1, name=nvram_ap6335.txt [ 2525.456278@2] dhd_conf_read_nv_by_chip: chip=0x4356, chiprev=2, name=nvram_ap6356.txt [ 2525.456282@2] dhd_conf_read_nv_by_chip: chip=0x4335, chiprev=1, name=nvram_bcm4335.txt [ 2525.456334@2] dhd_conf_read_config: mimo_bw_cap = 1 [ 2525.456576@2] dhd_conf_read_config: bcn_timeout = 20 [ 2525.456634@2] dhd_conf_read_config: kso_enable = 0 [ 2525.456857@2] dhd_conf_read_config: PM = 0 [ 2525.457082@2] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/brcm/fw_bcm43438a0.bin [ 2525.457087@2] dhd_conf_set_nv_name_by_chip: nvram_path=/lib/firmware/brcm/nvram_ap6212.txt [ 2525.457092@2] dhdsdio_download_firmware: set use_rxchain 0 [ 2525.457095@2] dhdsdio_download_firmware: set txglomsize 40 [ 2525.457099@2] sdioh_set_mode: set txglom_mode to multi-desc [ 2525.457102@2] Final fw_path=/lib/firmware/brcm/fw_bcm43438a0.bin [ 2525.457105@2] Final nv_path=/lib/firmware/brcm/nvram_ap6212.txt [ 2525.457108@2] Final conf_path=/lib/firmware/brcm/config.txt [ 2525.510989@2] NVRAM version: AP6212_NVRAM_V1.0.1_20160606 [ 2525.511452@2] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded. [ 2525.572845@2] dhd_bus_init: enable 0x06, ready 0x06 (waited 0us) [ 2525.572950@2] bcmsdh_oob_intr_register: Enter [ 2525.572955@2] bcmsdh_oob_intr_register: HW_OOB enabled [ 2525.572959@2] bcmsdh_oob_intr_register OOB irq=100 flags=414 [ 2525.572987@2] bcmsdh_oob_intr_register: enable_irq_wake [ 2525.572993@2] bcmsdh_oob_intr_register: enable_irq_wake failed with -6 [ 2525.574096@0] dhd_conf_set_fw_int_cmd: set WLC_SET_BAND 142 0 [ 2525.574283@0] dhd_preinit_ioctls: Set tcpack_sup_mode 0 [ 2525.577046@2] Firmware up: op_mode=0x0005, MAC=44:2c:05:65:07:c2 [ 2525.577052@2] dhd_conf_set_country: set country CN, revision 38 [ 2525.577055@2] dhd_conf_set_fw_string_struct_cmd: set country [ 2525.578169@2] CONFIG-ERROR) dhd_conf_set_fw_string_struct_cmd: country setting failed -2 [ 2525.579354@2] Country code: US (US/0) [ 2525.579882@2] dhd_conf_set_fw_string_cmd: set roam_off 1 [ 2525.581897@2] dhd_conf_set_fw_string_cmd: set mimo_bw_cap 1 [ 2525.590957@2] Firmware version = wl0: Sep 21 2016 15:09:45 version 7.46.57.4.ap.r3 (A0 Station/P2P) FWID 01-26e62eff es6.c5.n4.a3 [ 2525.590974@2] Driver: 1.201.59.6 (r506368) [ 2525.590974@2] Firmware: wl0: Sep 21 2016 15:09:45 version 7.46.57.4.ap.r3 (A0 Station/P2P) FWID 01-26e62eff es6.c5.n4.a3 [ 2525.590983@2] dhd_txglom_enable: enable 0 [ 2525.590988@2] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0 [ 2525.590992@2] dhd_conf_set_txglom_params: txglom_bucket_size=0 [ 2525.590996@2] dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0, bus_txglom=0 [ 2525.591001@2] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0 [ 2525.591005@2] dhd_conf_set_disable_proptx: set disable_proptx 0 [ 2525.592019@2] dhd_wlfc_hostreorder_init(): successful bdcv2 tlv signaling, 64 [ 2525.592625@2] wl_android_wifi_on: Success [ 2525.629582@2] dhd_open: Exit ret=0 [ 2536.847859@2] Connectting with c4:e9:84:4a:2b:0f channel (2) ssid "EneGolaBidde", len (12) [ 2536.847859@2] [ 2536.883797@0] wl_iw_event: Link UP with BSSID=C4:E9:84:4A:2B:0F [ 2536.883837@0] wl_bss_connect_done succeeded with c4:e9:84:4a:2b:0f [ 2536.949519@0] wl_bss_connect_done succeeded with c4:e9:84:4a:2b:0fInteresting here: it does some "country" things and fails there. "CN" - I am not from China nor from the "US". I also tried to change "language" to "German" but it just takes a while and stays at "English" (edit 20:13 - tried it again and seems it was a server issue, interface changed to "German" - but this of course did not get rid of the wifi bug).
I know that the "country settings" define the power used for transmitting (in Germany we have different maximum values than other countries) but it should not really stop data flow over wifi.
Edit 2 (22:51):
I extracted some files from the android-firmware - and had a look at the files of the system. For Wifi I am not sure what chip they use:
- wifi/RT2870STA_7601.dat and RT2870STA_7603.dat seem to be for "Ralink RT2870"
- wifi/various-numbers-Directories/fw_bcm4339a0_ag.bin or fw_bcm43455c0_ag / fw_bcm43241b4_ag ... seem to be related to "Broadcom chips"I cannot tell which one is finally used. Is there an "easy to follow" way to add new chip drivers/modules to the LE installation (stored on a micro-sd) to test them out?
Maybe I could "copy" some of the config files from android to LE ?There was no build.prop but a default.pro contained "ro.bootimage.build.fingerprint=Amlogic/p212/p212:6.0.1/MHC19J/20161013:userdebug/test-keys" which isn't really helpful identifying the "product/model" - so I have to trust it to be a "(Plater) Mini M8S II".
Thanks in advance,
bye
Ron