Search results

I still run on LOS 17.1 and can confirm that 5 GHz WiFi (somehow) works. It has week signal sensitivity and transfer rates are low for 5 GHz. If you won't move your tablet too far from router, it will work. But do not expect any great WiFi performace. As far as I know this is the problem of all...

Not sure because it is really long time ago I installed X Neo the last time, but it should be the lineage-17.1-20201215-UNOFFICIAL-treble_arm64_bvS version from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/

I have set up some tiny automation in between X Neo and my phone in Tasker too. I use Join for sharing statuses between these two devices. It works perfect, 100% reliable. Both devices are running on LOS 17.1 and X Neo is connected to 5GHz Wifi. Although this WiFi band works badly on X Neo, it...

Thank you for the info. So I will stay on LOS 17.1 (Android 10) for now. It's pity that 5GHz WiFi on Android 11 seems to be still as bad as on Android 10. Otherwise it would be for me a reason to move.

I tried to change data partition filesystem to f2fs in TWRP 3.3.1. The change command went well without any error. But right afterwards (still in TWRP) errors on data cannot be mounted has appeared. After restarting to recovery again, data is declared to be formatted to ext4. Any idea why...

Thank you for explaining and pointing me at the great information source.

How compares the 5GHz WiFi performance in Havoc to 5GHz performance of other devices in your 5GHz network? I mean how compares the transfer rates and signal sensitivity? I just installed Havoc-OS-v3.8-20200821-Official-arm64-ab.img into one slot and can confirm that 5GHz WiFi works. But performs...

Hmm, I wonder how it knows which system partition to boot up, whether system_a or system_b, if both boot images are identical. It has to contain some logic which decides based on current active boot slot (A or B) then.

My point was that it's (maybe) not good idea to flash the same (single) TWRP patched boot.img into both slots. I mean doing so we are flashing the boot.img coming from slot A to slot B too or the boot.img coming from slot B to slot A too (depends on what boot.img from these two you provide in...

What do you mean by not having 5GHz WiFi? You do not see and/or cannot connect to any 5GHz network? Or you can connect, but the WiFi performance is bad? I have found two problems with 5GHz according to my experience so far: 1. NeoX doesn't work with each 5GHz channel to me. This should depend on...

More on flashing (or should I rather say installing?) the TWRP. I searched for some info and have found the recommended way of doing that on A/B devices, see: https://androidmore.com/install-twrp-on-android/ https://www.droidwin.com/flash-files-a-b-partition-devices/ They both use the same way...

What device have you chosen? Seems not to be easy to find the suitable one.

I guess version 1.3 is too old for our purpose. What about version 2.1? See here: https://sourceforge.net/projects/carliv-image-kitchen/ "Carliv Image Kitchen for Android, version 2.1 with support for boot and recovery images up to Android 10."

I did the same as you and copied the apk into /vendor/overlay. I had to use a different file manager than I'm using to be able to change directory permissions. After restart I'm able to turn auto brightness on and off (was not possible till now), but it does nothing in fact. Here is the log...

I tried to install the enableAutoBrightness-twrp.zip from https://androidfilehost.com/?w=files&flid=312417 as the auto brightness is not working in GSI. It should just put one apk file into /vendor/overlay. Although the installation goes well in TWRP without any errors, the apk is not being...

Thank you a lot! That's promising. But seems not to work well yet. It worked fine until I decided to install LOS 16.0, see below. After flashing the 3.3.1-0 back, the same operation passed well.

There are many complains on WiFi issues here https://github.com/phhusson/treble_experimentations/search?p=1&q=wifi&type=issues. And the Magisk is said to be the cause of the problem in some. But it seems we need Magisk to be able to boot up to GSI ROM. Right? Should we try a different Magisk...

Not me unfortunately.:) But thank you for providing info on the current TWRP situation anyway.

Back to the 5GHz WiFi mystery. I went through the bootloader opening procedure again. Then played with October Chinese ROM (where 5GHz WiFi works alright) for a while. Afterwards I flashed GSI QiDroid. During the very first boot to QiDroid I tried to connect to 5GHz WiFi. But after entering in...

OK, so I checked the TWRP's recovery.log file and can confirm that the thing is exactly as you describe. But still do not have an idea why it doesn't boot after full TWRP restore. It still means that the original and the restored states are not identical. And that's something I wouldn't expect...

Hmm, are you telling me that System and System image are not two backups of two different partitions but two different ways of backing up the single partition? One as simple copy of its content and the other as the dd image? The same for Vendor. Anyway if so, it still doesn't explain the problem...

I still do struggle with the 5GHz WiFi. Cannot make it work well on GSI ROM. Therefore I moved back to October Chinese ROM where 5GHz WiFi works well. I searched through all the files in root filesystem for both the persist.sys.overlay.wifi5g and ro.wlan.mtk.wifi.5g strings and didn't find any...

The TWRP backup/restore doesn't work as it should unfortunately. At least for me. Having the October Chinese ROM installed I flashed TWRP into both slots and did the backup of all the partitions in each slot that TWRP provides for backing up. Then flashed both slots with QiDroid. After some time...

Sure, I know that. That's why I always restore the correct/other data partition from backup before booting to the other slot. Or at least wipe data when want to start from the beginning for testing purposes. I believe that it should work this way and can have different ROMs in each slot. Just...

I wonder how did you managed to get your hack with ro.wlan.mtk.wifi.5g working at least. Even I added ro.wlan.mtk.wifi.5g=1 and (later) persist.sys.overlay.wifi5g=true as well to /system/build.prop and restarted I cannot get neither one in getprop output listed. And still do have those error...

I do confirm that. It is according to my experience too. I tried to find any confirmation of that on Internet, but didn't find any though. The same do apply for installing Magisk or GApps in TWRP, or resizing the partition. I would say that besides flashing the ROM everything else applies to the...

After restart only persist.sys.overlay.wifi5g remains to be set (according to getprop). ro.wlan.mtk.wifi.5g doesn't. Although both still in /system/build.prop. Even manual setting ro.wlan.mtk.wifi.5g in shell and cycling WiFi off and on doesn't help. Still the "bad" WiFi.

Hmm, strange. Earlier today I tried to add directly the persist.sys.overlay.wifi5g=true to /system/build.prop, but had no effect. After your promising message I added the ro.wlan.mtk.wifi.5g=1 too there. But again without any effect. So unlike you I didn't recognized any effect of these...

Maybe found the cause of the 5GHz issue. See the logcat outputs the from booted custom LOS 16.0 and GSI LOS 17.1 below. Just to remind you, in custom LOS 16.0 the WiFi 5GHz works nice, but in LOS 17.1 GIS (and other GSI ROMs) has issues (slow transfer rates, weak signal, has to be enabled by...

It's a pity. But thank you for the info anyway. I thought to keep LOS 16.0. But had issues with bluetooth. Was not able to connect speaker nor headphone. Showstopper for me. So decided to flash LOS 17.1 GSI system image over LOS 16.0. It boots, it works, but 5GHz WiFi is again back where it was...

Wow, cannot believe that! The LOS 16.0 (lineage-16.0-20200516-UNOFFICIAL-t1009) works really great in terms of WiFi 5GHz performance! I get approx. 300Mbit/s download as well as upload speeds in Ubiquti WiFiman speed test and some 220Mbit/s download speed in real life download test from FTP...

So I flashed the LOS 17.1 to my slot B (I keep QiDroid in slot A for now) and briefly checked the 5GHz WiFi. It behaves the same as on QiDroid, so no good news here. Then I tried to flash the LeOS, but was successful only with the LeOS-Q variant, which is basically the LOS 17.1 on Android 10. I...

I did some more testing and have to say that the tablet have either a very bad 5GHz antenna or maybe it misses it at all. The signal reception sensitivity is really very bad. I believe it cannot be problem of the SD660 chipset, but the signal reception stuff.

Maybe do not need to climb, but still can. ;) I have an idea to flash LOS 17.1 into the other slot and check if the airplane mode trick would work there too. When doing that I could try the LeOS too. I already think of that earlier. And I already did so many flashing tries (and errors) that I...

I'm still struggling with the "WiFi cannot be turned on" issue I have. The current example follows. I flashed the Chinese October ROM and unlocked the bootloader. Everything seemed OK, WiFi worked, even the 5GHz one. Then I flashed the TWRP to both A/B slots, did the backup in TWRP and started...

Hurrah, I get connected to 5GHz WiFi too! On October Chinese ROM. I turned on the airplane mode on and rebooted into bootloader in order to unlock it. When it booted back the AM was off. It surprised me as I set it on before rebooting. But maybe that was caused because the bootloader was just...

Great news! You are the candidate for the next award! I already tried that in LOS 16.1 (including reboot in airplane mode), but was not working. Currently I'm passing through the bootloader unlock procedure again because of what I wrote in #187. So already tried the trick (including reboot in...

Thank you for this info. I'll try QiDroid then. During all my tries and errors I already manged to achieve the real transfer (download) speed around 11MB/s from home FTP server with the bonding module installed and connected to 40MHz Wifi. But was not able to make this state persistent. Most of...

Is there any recommended way how to test various ROMs? Just reflashing the system with the ROM's img from fastboot leads me often to unbootable state. It would be solved by doing all the two original ROMs flashing and unlocking the bootloader procedure. But this is extremely time consuming...

Sounds really nice. What ROM are you running? Do you have installed the WiFi bonding Magisk module?