Log files from the 3 different firmwares to try and resolve 5g and bluetooth problem.

[rad]

Here you go folks.

I have labelled them as per the firmware flashed.

I hope they help.

For me I'm going back to version 1 with finless 1.2 on top.

Cheers,

PS. The file was a .rar that I renamed to .zip so I could upload it.

[no_spam_for_me]

Only quick and dirty look at the files:
vega s89 standard_100k4_6330_tronsmart.log
=> 'bluetooth' -> 15 matches
=> 'wifi' -> 32 matches
vega s89_101k4_6330_tronsmart_1.log
=> 'bluetooth' -> 0 matches
=> 'wifi' -> 22 matches

BTW: do you use linux?

[no_spam_for_me]

Which router do you use (but maybe not really important but who knows)?

[rad]

Only quick and dirty look at the files:
vega s89 standard_100k4_6330_tronsmart.log
=> 'bluetooth' -> 15 matches
=> 'wifi' -> 32 matches
vega s89_101k4_6330_tronsmart_1.log
=> 'bluetooth' -> 0 matches
=> 'wifi' -> 22 matches

BTW: do you use linux?

Not that much, I built a headless NAS with ubuntu and plex for storing movies and tv.

If there's a guide I can follow it and I pick things up quickly but I find the whole linux community are not that helpful. lol

[rad]

Which router do you use (but maybe not really important but who knows)?

TP-Link N600, I'm pretty sure it's not the router as I also loose a lot of other SSID's I normally see, I think it's save to assume they are 5Ghz as well.

Plus it would be a clever router that jumped over wifi and broke bluetooth too

[nutzu]

TP-Link N600, I'm pretty sure it's not the router as I also loose a lot of other SSID's I normally see, I think it's save to assume they are 5Ghz as well.

Plus it would be a clever router that jumped over wifi and broke bluetooth too

I use an asus N65u and like u I went back to first version plus Bob Rom 1.2 and it works ok, btw the 2.5g is a joke very slow compared to minix x7,I wouldn't complain that much but I relay on the 5G wi-fi because was the only one fast enough to watch hd movies plus my ethernet is a dud it didn't worked from the beginning

[geekbuying]

Already transferred the log file to factory, thanks OP.

and this must be a firmware problem, because on the other firmware, it can work well.
also it should be the problem of amlogic, because i notice the square m8 box also have this problem after update to the lastest firmware.


and the 5g work with some routers, and don't work with others, we have tested with tp-link and it can work. but asus ones don't work.

so i have collected all of the information and submit to factory.

no worry, guys, Eric is here.

[nutzu]

Already transferred the log file to factory, thanks OP.

and this must be a firmware problem, because on the other firmware, it can work well.
also it should be the problem of amlogic, because i notice the square m8 box also have this problem after update to the lastest firmware.


and the 5g work with some routers, and don't work with others, we have tested with tp-link and it can work. but asus ones don't work.

so i have collected all of the information and submit to factory.

no worry, guys, Eric is here.

Thx Eric I hope the factory is listening to u, because to my email didn't respond,btw can pls do something about the 2.5g

[rad]

Just a stab in the dark and I could be way wrong here but on the ROM where it works it says country = all in the log file, in the one where it doesn't it says country = CN.

I know when you setup routers your country code does have some impact on the bands you get, some go up to 11 and some go up to 13, this is on the 2.4Ghz but maybe there is a similar thing with 5G and because the country on the Vega doesn't match the country on the router there is an issue.

Probably way wrong but I thought it worth a mention.

[oman]

I have two ideas:
1.replace the dhd.ko from 100k4 to 101k4,which is in system/lib;The dhd.ko is the wifi driver.
2.Modify system/etc/firmware/config.txt,change ccode=CN to ccode=ALL.

[gizmomelb]

Just a stab in the dark and I could be way wrong here but on the ROM where it works it says country = all in the log file, in the one where it doesn't it says country = CN.

I know when you setup routers your country code does have some impact on the bands you get, some go up to 11 and some go up to 13, this is on the 2.4Ghz but maybe there is a similar thing with 5G and because the country on the Vega doesn't match the country on the router there is an issue.

Probably way wrong but I thought it worth a mention.

Hi Rad,

that's what I thought initially as well, but I looked up and the bands / frequencies appeared to all be in the same spectrum so I didn't think the different country codes would make a difference, but oman's suggestion seems the easiest way to test if that is the issue or not.

The 5G working for Eric would make sense then as well, as he's in China (presumably - as he said he visited the factory).

[geekbuying]

Factory give some suggestions, i hope the guys who lost 5g can help to test:

change the config_01.txt to config.txt

how to do that:


1、connect the device via ADB

2、push config.txt to system/etc/firmware/

C:\Program Files (x86)\Tencent\AndroidAssistant>adb remount
remount succeeded

C:\Program Files (x86)\Tencent\AndroidAssistant>adb push D:\project\vega s89\config.txt system/etc/firmware
2 KB/s (65 bytes in 0.029s)

I don't know this linux command very well, if someone can try,it will help to fix the problem asap.

Eric

[JustMe]

trying it on square m8 already names config.txt just changing the cn to US or ALL hopefull it will aloww me to upload via file explorer


JustMe

[geekbuying]

trying it on square m8 already names config.txt just changing the cn to US or ALL hopefull it will aloww me to upload via file explorer


JustMe

problem solved?

Eric

[no_spam_for_me]

Maybe this way:
1. get the existing 'system/etc/firmware/config.txt'

adb pull system/etc/firmware/config.txt

2. edit the config.txt with notepad++

3. remount from readonly to read/write
normally the remount needs to know what to do (but I'm not sure and can't compare it at the moment)
To be sure maybe use first

adb shell mount

now you get a list of mounting-points and I think the / is the important one and if it is 'ro' you have to do the following

adb remount -oremount,rw /

4. upload new config.txt

adb push config.txt system/etc/firmware/

5. restart the system
I don't know, if it is needing AND if the changes will lost after a restart

adb reboot

==========================================

To get the old 'dhd.ko' from running old stock rom

adb pull system/lib/dhd.ko

To replace the 'dhd.ko' at running new stock rom, I think you first also have to remount to rw...

Then upload the 'dhd.ko'

adb push dhd.ko system/lib

And I think you have to make it "executable"

adb shell chmod 0755 /system/lib/dhd.ko

And last but not least, normaly you have also to reboot...