ipdev said:

If you install GApps.

MindTheGApps arm build(s) give me an error and would not install.

I am using "LiteGapps" for Android 13 (Lineage 20) arm (armv7a) devices.

[RECOVERY]LiteGapps_Core_arm_13.0_v2.8_official - [SourceForge] - Link

I am not familiar with the LiteGapps project but, at least it works on deb and flo.

Click to expand...

osm0sis said:

Looks like MTG is expecting an Android 11+ based recovery, where the fstab mounts the ROM to /mnt/system to avoid breaking the recovery's own /system/bin. I'll see how hard it is to work around.

Also still hoping @Nikhil will bless us with some arm Go GApps at some point since an old device like this is pretty much the exact use case for Android Go.

Spielmops said:

Swipe statusbar to change brightness is not working. It was working with LOS 19.

Spielmops

Revert "SystemUI: Port statusbar brightness control" · LineageOS/android_frameworks_base@2919024

Needs to be refactored after QPR2 This reverts commit 54bf717dee23e09971506bd656f292cd650d1b25. Change-Id: I888ba4bc5b2070e60419753c7c5bba9b6b79850c

github.com

followmsi said:

LiteGapps are OK .. but it's good to have more gapps packages available.

Quickly made a custom MindtheGapps package for flo/deb devices !
To be installed using "my" TWRP. (3.7.0)

The "addon" script seems to be working well.
This means .. Gapps will be automatically re-installed when installing new ROM.

Tested on flo device only !

Pls have a test yourself ..

MindTheGapps-13.0.0-arm-20221025_095826_flo.zip

Click to expand...

What's the difference from the standard MTG arm 20221025?

osm0sis said:

What's the difference from the standard MTG arm 20221025?

I was wondering the same.

I assumed it had to do with the mounting so I compared install scripts.

The easiest way to show the changes was just to push it to github.
example - [github] - commit

Not quite a dynamic installer script anymore.


Cheers.

PS.
I haven't had time to try followmsi's MTG-flo build yet.

osm0sis said:

What's the difference from the standard MTG arm 20221025?

ipdev said:

I was wondering the same.

I assumed it had to do with the mounting so I compared install scripts.

The easiest way to show the changes was just to push it to github.
example - [github] - commit

Not quite a dynamic installer script anymore.


Cheers.

PS.
I haven't had time to try followmsi's MTG-flo build yet.

Click to expand...

ui_print "Backup MindTheGapps .."

ui_print "Restore MindTheGapps .."

# update-binary|updater <RECOVERY_API_VERSION> <OUTFD> <ZIPFILE>
OUTFD=$(ps | grep -v 'grep' | grep -oE 'update(.*) 3 [0-9]+' | cut -d" " -f3)

ui_print() {
        echo -e "ui_print $1\nui_print" >> /proc/self/fd/$OUTFD
 }

MindTheGapps / vendor_gapps · GitLab

GitLab.com

gitlab.com

osm0sis said:

@followmsi would you be able to add the GPU OC from EX to your included kernel? It's probably the only thing anyone's interested in from it anymore.

I was tinkering with it and found the OC'd GPU along with the unreleased Adreno beta drivers really helped with the smoothness of animations.

Last thing I noticed helped, and actually helped dramatically, was I switched the I/O scheduler from cfq to noop! Much more fluid System UI, Launcher and app start times/responsiveness.

Edit: Widget resizing/scaling seems a bit wonky on the large screen, but otherwise the ROM seema a fair amount more stable for use than previous builds (though I noted the final 19.1 also seemed quite good before I moved to 20!)

Click to expand...

Great tips. Thank you. Any other tinkering suggestions....

osm0sis said:

@followmsi would you be able to add the GPU OC from EX to your included kernel? It's probably the only thing anyone's interested in from it anymore.

I was tinkering with it and found the OC'd GPU along with the unreleased Adreno beta drivers really helped with the smoothness of animations.

Last thing I noticed helped, and actually helped dramatically, was I switched the I/O scheduler from cfq to noop! Much more fluid System UI, Launcher and app start times/responsiveness.

Edit: Widget resizing/scaling seems a bit wonky on the large screen, but otherwise the ROM seems a fair amount more stable for use than previous builds (though I noted the final 19.1 also seemed quite good before I moved to 20!)

Click to expand...

Commits · followmsi/android_kernel_google_msm

Linux kernel for Google MSM devices. Contribute to followmsi/android_kernel_google_msm development by creating an account on GitHub.

github.com

followmsi said:

What about "unreleased Adreno beta drivers" ?

EDIT:

Quick off-topic comment to MTG installer ..

TWRP does rename "twrp.fstab" into "recovery.fstab" while booting .. for this reason MTG installer should find fstab .. but as it looks like it can't read the BLOCK_SYSTEM correctly .. it does work the "hardcoded" way ,,, like said before .. pls feel free to adjust/optimize the MTG scripts.

Click to expand...

# cmdline changes

patch_cmdline androidboot.hardware androidboot.hardware=flox; # change "flo" to "flox"
replace_string $split_img/header bootdevice androidboot.hardware=flox "androidboot.hardware=flox androidboot.bootdevice=msm_sdcc.1"; # add bootdevice support (placement in cmdline matters)

# begin ramdisk changes

# default.prop
patch_prop default.prop ro.build.product flox; # change "flo" to "flox"

# etc/*.fstab
for i in recovery twrp; do
  replace_string etc/$i.fstab bootdevice platform/msm_sdcc.1 bootdevice global; # change "/dev/block/platform/msm_sdcc.1" to "/dev/block/platform/bootdevice"
  insert_line etc/$i.fstab /vendor after by-name/system "/vendor     ext4    /dev/block/bootdevice/by-name/vendor"; # add /vendor support
done;

# fstab.flo
replace_string fstab.flo bootdevice platform/msm_sdcc.1 bootdevice global; # change "/dev/block/platform/msm_sdcc.1" to "/dev/block/platform/bootdevice"
insert_line fstab.flo /vendor after by-name/system "/dev/block/bootdevice/by-name/vendor       /vendor         ext4    ro,barrier=1                                                                 wait"; # add /vendor support

# end ramdisk changes

osm0sis said:

The original thread for the updated Adreno drivers, for more background info on them if you're interested: https://forum.xda-developers.com/t/...drivers-for-nexus-7-updated-10-11-15.3228000/

They are v145 instead of the stock included v127 drivers, and improved benchmark scores and general smoothness noticeably!

I tested them pretty extensively back when this and the Nexus 5 were modern devices, and they unfortunately went in and out of being stable with their later builds, and then Qualcomm never bothered to push any final builds to Google for release, so the Adreno Beta program was the only place they ever saw the light of day.

According to past me the final stable beta build was from February 2016:
https://forum.xda-developers.com/t/...pdated-09-12-15.3228002/page-15#post-73325141

I mirrored all the packages I could find for posterity here: https://androidfilehost.com/?w=files&flid=312875

Would love to see the February ones included in the ROM if you find them stable enough on your device.

The official MTG worked fine on my flo2flox'd official TWRP, so might just be something quick you could add to your TWRP tree to get it working.

The changes my AK3 zip performs are pretty straightforward:

Code:

# cmdline changes

patch_cmdline androidboot.hardware androidboot.hardware=flox; # change "flo" to "flox"
replace_string $split_img/header bootdevice androidboot.hardware=flox "androidboot.hardware=flox androidboot.bootdevice=msm_sdcc.1"; # add bootdevice support (placement in cmdline matters)

# begin ramdisk changes

# default.prop
patch_prop default.prop ro.build.product flox; # change "flo" to "flox"

# etc/*.fstab
for i in recovery twrp; do
  replace_string etc/$i.fstab bootdevice platform/msm_sdcc.1 bootdevice global; # change "/dev/block/platform/msm_sdcc.1" to "/dev/block/platform/bootdevice"
  insert_line etc/$i.fstab /vendor after by-name/system "/vendor     ext4    /dev/block/bootdevice/by-name/vendor"; # add /vendor support
done;

# fstab.flo
replace_string fstab.flo bootdevice platform/msm_sdcc.1 bootdevice global; # change "/dev/block/platform/msm_sdcc.1" to "/dev/block/platform/bootdevice"
insert_line fstab.flo /vendor after by-name/system "/dev/block/bootdevice/by-name/vendor       /vendor         ext4    ro,barrier=1                                                                 wait"; # add /vendor support

# end ramdisk changes

I'd say just ignore the flox-specific ones, e.g. where flo only gets changed to flox, and add the remaining fixes for profit?


Edit:

Just tried 0401 and the only other thing that looks like it's missing from the kernel are the updated TCP congestion algorithms. I believe westwood and bbr are considered the best currently from kdrag0n's research: https://docs.google.com/spreadsheet...xMNz9pgS9OLKcFHssIBlj9xXI/edit#gid=1926845420

Would be great to have those, and then no more need for EX bring-ups on this device.


Edit 2:

Oh, and any way to hook up this old kernel's Double Tap 2 Wake function to the usual Lineage Settings option?

Click to expand...

osm0sis said:

The original thread for the updated Adreno drivers, for more background info on them if you're interested: https://forum.xda-developers.com/t/...drivers-for-nexus-7-updated-10-11-15.3228000/

They are v145 instead of the stock included v127 drivers, and improved benchmark scores and general smoothness noticeably!

I tested them pretty extensively back when this and the Nexus 5 were modern devices, and they unfortunately went in and out of being stable with their later builds, and then Qualcomm never bothered to push any final builds to Google for release, so the Adreno Beta program was the only place they ever saw the light of day.

According to past me the final stable beta build was from February 2016:
https://forum.xda-developers.com/t/...pdated-09-12-15.3228002/page-15#post-73325141

I mirrored all the packages I could find for posterity here: https://androidfilehost.com/?w=files&flid=312875

Would love to see the February ones included in the ROM if you find them stable enough on your device.

The official MTG worked fine on my flo2flox'd official TWRP, so might just be something quick you could add to your TWRP tree to get it working.

The changes my AK3 zip performs are pretty straightforward:

Code:

# cmdline changes

patch_cmdline androidboot.hardware androidboot.hardware=flox; # change "flo" to "flox"
replace_string $split_img/header bootdevice androidboot.hardware=flox "androidboot.hardware=flox androidboot.bootdevice=msm_sdcc.1"; # add bootdevice support (placement in cmdline matters)

# begin ramdisk changes

# default.prop
patch_prop default.prop ro.build.product flox; # change "flo" to "flox"

# etc/*.fstab
for i in recovery twrp; do
  replace_string etc/$i.fstab bootdevice platform/msm_sdcc.1 bootdevice global; # change "/dev/block/platform/msm_sdcc.1" to "/dev/block/platform/bootdevice"
  insert_line etc/$i.fstab /vendor after by-name/system "/vendor     ext4    /dev/block/bootdevice/by-name/vendor"; # add /vendor support
done;

# fstab.flo
replace_string fstab.flo bootdevice platform/msm_sdcc.1 bootdevice global; # change "/dev/block/platform/msm_sdcc.1" to "/dev/block/platform/bootdevice"
insert_line fstab.flo /vendor after by-name/system "/dev/block/bootdevice/by-name/vendor       /vendor         ext4    ro,barrier=1                                                                 wait"; # add /vendor support

# end ramdisk changes

I'd say just ignore the flox-specific ones, e.g. where flo only gets changed to flox, and add the remaining fixes for profit?


Edit:

Just tried 0401 and the only other thing that looks like it's missing from the kernel are the updated TCP congestion algorithms. I believe westwood and bbr are considered the best currently from kdrag0n's research: https://docs.google.com/spreadsheet...xMNz9pgS9OLKcFHssIBlj9xXI/edit#gid=1926845420

Would be great to have those, and then no more need for EX bring-ups on this device.


Edit 2:

Oh, and any way to hook up this old kernel's Double Tap 2 Wake function to the usual Lineage Settings option?

Click to expand...

followmsi said:

Pls post links to network related commits in original EX kernel ... Thanks

Not sure about DT2W .. personally don't like it .. too much energy for nothing

TCP Congestion Control is just some switches in the defconfig. Here is basically what we want, but from an OP9Pro kernel: https://github.com/engstk/op9/commit/cc75e300d8e2522ae16950691578aba8fba8bd3a

I'd also suggest making the default westwood or bbr.

DT2W is already in the kernel, just asking to have it more easily exposed to the end user by having it be a toggle in Settings like it is on modern devices with Lineage.