[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]

[osm0sis]

Ok .. let's test the adreno stuff in next build.

Tested the "bootdevice" in TWRP .. does not work for me.
TWRP does not find/mount partitions anymore.
Need to check what I made wrong .. or whats missing.

Ok .. just enabling westwood .. but no special patches for it.
bbr is not in flo EX kernel .. disabled all this stuff years ago .. on other devices too.
I will enable for next build .. and switch default from cubic to westwood.

I know about DT2W .. disabled in my kernel.
Do you have an idea on how to make it work for flo ?
Actually don't want to spent much time on this topic.

Anyway .. for today I spent enough time for flo ..

The main thing I noted for bootdevice was that it had to come after hardware in the final cmdline, i.e.:

androidboot.hardware=flo androidboot.bootdevice=msm_sdcc.1

Then the fstab changes in recovery.fstab, twrp.fstab and fstab.flo from "platform/msm_sdcc.1" to "bootdevice" should work if the TWRP base is up-to-date with the latest official.

DT2W is currently present in your kernel but disabled by default, please leave it at least present... As for how to hook it up to the Lineage Settings > Display > Tap to wake toggle, I'm not sure, but I assume it would be just swapping out whatever command Settings sends under the hood to instead use the old flo implementation.

e.g., to enable it I have this in my boot script:

echo 1 > /sys/android_touch/doubletap2wake;

Edit:

My current boot script if anyone's interested.

/data/adb/post-fs-data.d/000bootsettings:

#!/system/bin/sh

for i in /sys/block/*/queue; do
  echo 512 > $i/nr_requests;
  echo 256 > $i/read_ahead_kb;
  echo 2 > $i/rq_affinity;
  echo 0 > $i/rotational;
done;

echo 585000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk;

echo 1 > /sys/android_touch/doubletap2wake;
echo 1 > /sys/kernel/fast_charge/force_fast_charge;

echo 128 > /proc/sys/kernel/random/read_wakeup_threshold;
echo 256 > /proc/sys/kernel/random/write_wakeup_threshold;

echo westwood > /proc/sys/net/ipv4/tcp_congestion_control;
echo 1 > /proc/sys/net/ipv4/tcp_low_latency;

for i in /sys/class/net/*; do
  echo 100 > $i/tx_queue_len;
done;

 

[followmsi]

The main thing I noted for bootdevice was that it had to come after hardware in the final cmdline, i.e.:

androidboot.hardware=flo androidboot.bootdevice=msm_sdcc.1

Then the fstab changes in recovery.fstab, twrp.fstab and fstab.flo from "platform/msm_sdcc.1" to "bootdevice" should work if the TWRP base is up-to-date with the latest official.

DT2W is currently present in your kernel but disabled by default, please leave it at least present... As for how to hook it up to the Lineage Settings > Display > Tap to wake toggle, I'm not sure, but I assume it would be just swapping out whatever command Settings sends under the hood to the old flo implementation.

e.g., to enable it I have this in my boot script:

echo 1 > /sys/android_touch/doubletap2wake;

Edit:

My current boot script if anyone's interested.

/data/adb/post-fs-data.d/000bootsettings:

#!/system/bin/sh

for i in /sys/block/*/queue; do
  echo 512 > $i/nr_requests;
  echo 256 > $i/read_ahead_kb;
  echo 2 > $i/rq_affinity;
  echo 0 > $i/rotational;
done;

echo 585000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk;

echo 1 > /sys/android_touch/doubletap2wake;
echo 1 > /sys/kernel/fast_charge/force_fast_charge;

echo 128 > /proc/sys/kernel/random/read_wakeup_threshold;
echo 256 > /proc/sys/kernel/random/write_wakeup_threshold;

echo westwood > /proc/sys/net/ipv4/tcp_congestion_control;
echo 1 > /proc/sys/net/ipv4/tcp_low_latency;

for i in /sys/class/net/*; do
  echo 100 > $i/tx_queue_len;
done;

Today it's a (hardcore) flo day

Thanks .. found the issue in TWRP .. typo .. added too much "platform".
But .. as to change all fstab and cmdline .. I simply used a good old symlink.

on fs
    wait /dev/block/platform/msm_sdcc.1
    symlink /dev/block/platform/msm_sdcc.1 /dev/block/bootdevice

And - Yes .. Unmodified MTG installer will work now !

Already uploaded the new TWRP versions to gdrive ...

twrp-3.7.0_9-1-flo_followmsi.img
twrp-3.7.0_9-1-deb_followmsi.img

Removed all the "_flo" MTG versions from gdrvie too,
Pls use and test ..
MindTheGapps-13.0.0-arm-20230401_160426.zip

Last but not least I have added all the "westwood" stuff into kernel too ..
flo-deb-followmsi-kernel-thirteen-20230401-AK3.zip

Yes .. DT2W will be kept in kernel .. but disabled.
Need to check how to trigger from settings .. we will see.

Cheers

 

[retiredtab]

Yes .. DT2W will be kept in kernel .. but disabled.
Need to check how to trigger from settings .. we will see.

@followmsi , this overlay?

https://review.lineageos.org/c/LineageOS/android_device_xiaomi_Mi8937/+/351111

<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
    <!-- Whether device supports double tap to wake -->
    <bool name="config_supportDoubleTapWake">true</bool>
</resources>

 

[ipdev]

The main thing I noted for bootdevice was that it had to come after hardware in the final cmdline, i.e.:

androidboot.hardware=flo androidboot.bootdevice=msm_sdcc.1

Then the fstab changes in recovery.fstab, twrp.fstab and fstab.flo from "platform/msm_sdcc.1" to "bootdevice" should work if the TWRP base is up-to-date with the latest official.

DT2W is currently present in your kernel but disabled by default, please leave it at least present... As for how to hook it up to the Lineage Settings > Display > Tap to wake toggle, I'm not sure, but I assume it would be just swapping out whatever command Settings sends under the hood to instead use the old flo implementation.

e.g., to enable it I have this in my boot script:

echo 1 > /sys/android_touch/doubletap2wake;

Edit:

My current boot script if anyone's interested.

/data/adb/post-fs-data.d/000bootsettings:

#!/system/bin/sh

for i in /sys/block/*/queue; do
  echo 512 > $i/nr_requests;
  echo 256 > $i/read_ahead_kb;
  echo 2 > $i/rq_affinity;
  echo 0 > $i/rotational;
done;

echo 585000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk;

echo 1 > /sys/android_touch/doubletap2wake;
echo 1 > /sys/kernel/fast_charge/force_fast_charge;

echo 128 > /proc/sys/kernel/random/read_wakeup_threshold;
echo 256 > /proc/sys/kernel/random/write_wakeup_threshold;

echo westwood > /proc/sys/net/ipv4/tcp_congestion_control;
echo 1 > /proc/sys/net/ipv4/tcp_low_latency;

for i in /sys/class/net/*; do
  echo 100 > $i/tx_queue_len;
done;

Today it's a (hardcore) flo day

Thanks .. found the issue in TWRP .. typo .. added too much "platform".
But .. as to change all fstab and cmdline .. I simply used a good old symlink.

on fs
    wait /dev/block/platform/msm_sdcc.1
    symlink /dev/block/platform/msm_sdcc.1 /dev/block/bootdevice

And - Yes .. Unmodified MTG installer will work now !

Already uploaded the new TWRP versions to gdrive ...

twrp-3.7.0_9-1-flo_followmsi.img
twrp-3.7.0_9-1-deb_followmsi.img

Removed all the "_flo" MTG versions from gdrvie too,
Pls use and test ..
MindTheGapps-13.0.0-arm-20230401_160426.zip

Last but not least I have added all the "westwood" stuff into kernel too ..
flo-deb-followmsi-kernel-thirteen-20230401-AK3.zip

Yes .. DT2W will be kept in kernel .. but disabled.
Need to check how to trigger from settings .. we will see.

Cheers

This thread got serious all of a sudden.
Do you two think this is a developers forum?

---

Here I was thinking about trying to fix/update MTG's mounting function to work with older devices.

I like the symlink idea in TWRP.
That should allow both paths to be found so better compatibility.

----

As for DT2W, I know it is suported by the kernel but, I am not sure if you can enable it under the setting option in Lineage.
I remember making a flo/deb build a few years ago with the DT2W flag enabled.
The option was available under settings to toggle it on/off but it did not work.

From what I understand, it will only work if DT2W is supported by the touch drivers.

I am not sure but, I think DT2W kernel implementation was removed from all official Lineage builds.​

flox and the never released debx for example.​

In turn, I went looking for how to enable DT2W by command line.
I found there are a few different settings depending on device/build.

I am too lazy to manually place boot script(s) on a device so, I turned it into a Magisk module.
[github] - mModule_dt2w

DT2W service script.

#!/system/bin/sh

## DT2W
## Simple script that will enable double tap to wake during late boot.
## For Nexus 7 [2013] (Flo/Deb) and Nexus 10 (Manta)
## Nexus 9 (Flounder)

if [ $(find /sys/ -name 'doubletap*' | sed '$!d') ]; then
    echo "1" >$(find /sys/ -name 'doubletap*' | sed '$!d');
elif [ $(find /sys/ -name 'dt2w*' | sed '$!d') ]; then
    echo "1" >$(find /sys/ -name 'dt2w*' | sed '$!d');
elif [ $(find /sys/ -name 'wake_gesture' | sed '$!d') ]; then
    echo "1" >$(find /sys/ -name 'wake_gesture' | sed '$!d');
fi;

Why do I always forget I have a Flounder? ​

---

Got a bit of time this evening to do some testing and will let you know what happens.

Cheers.

Edit:
PS.
I did not find what I was looking for about Lineage DT2W but, I found something relevant.
LineageOS (device-support-requirements) - [github] - Kernel

• All devices MUST NOT implement software based touchscreen wake features such as double tap to wake, swipe to wake or gestures if there is no hardware-backed support for them in the touchscreen firmware.

 

[BadFly2]

Good afternoon. Sorry for my English, I use google translator. The tablet does not see the hidden wifi network. Installed version 20230323. Installed kernel 20250325 - did not help. Do I need to install kernel 20200117? (found by searching on the topic)

 

[followmsi]

@followmsi , this overlay?

https://review.lineageos.org/c/LineageOS/android_device_xiaomi_Mi8937/+/351111

<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
    <!-- Whether device supports double tap to wake -->
    <bool name="config_supportDoubleTapWake">true</bool>
</resources>

This thread got serious all of a sudden.
Do you two think this is a developers forum?

---

Here I was thinking about trying to fix/update MTG's mounting function to work with older devices.

I like the symlink idea in TWRP.
That should allow both paths to be found so better compatibility.

----

As for DT2W, I know it is suported by the kernel but, I am not sure if you can enable it under the setting option in Lineage.
I remember making a flo/deb build a few years ago with the DT2W flag enabled.
The option was available under settings to toggle it on/off but it did not work.

From what I understand, it will only work if DT2W is supported by the touch drivers.

I am not sure but, I think DT2W kernel implementation was removed from all official Lineage builds.​

flox and the never released debx for example.​

In turn, I went looking for how to enable DT2W by command line.
I found there are a few different settings depending on device/build.

I am too lazy to manually place boot script(s) on a device so, I turned it into a Magisk module.
[github] - mModule_dt2w

DT2W service script.

#!/system/bin/sh

## DT2W
## Simple script that will enable double tap to wake during late boot.
## For Nexus 7 [2013] (Flo/Deb) and Nexus 10 (Manta)
## Nexus 9 (Flounder)

if [ $(find /sys/ -name 'doubletap*' | sed '$!d') ]; then
    echo "1" >$(find /sys/ -name 'doubletap*' | sed '$!d');
elif [ $(find /sys/ -name 'dt2w*' | sed '$!d') ]; then
    echo "1" >$(find /sys/ -name 'dt2w*' | sed '$!d');
elif [ $(find /sys/ -name 'wake_gesture' | sed '$!d') ]; then
    echo "1" >$(find /sys/ -name 'wake_gesture' | sed '$!d');
fi;

Why do I always forget I have a Flounder? ​

---

Got a bit of time this evening to do some testing and will let you know what happens.

Cheers.

Edit:
PS.
I did not find what I was looking for about Lineage DT2W but, I found something relevant.
LineageOS (device-support-requirements) - [github] - Kernel

• All devices MUST NOT implement software based touchscreen wake features such as double tap to wake, swipe to wake or gestures if there is no hardware-backed support for them in the touchscreen firmware.

Thanks for your help !

Yes ,, the overlay just enables the toogle in settings / display menu.

DT2W seems to require software changes for sensor and/or power hal.

As we use qti power service i have tested the DT2W flag ..

"TARGET_TAP_TO_WAKE_NODE := /sys/android_touch/doubletap2wake"

Still not working .. it requires more changes to make it work on flo .. if possible at all.


Just an idea .. we make simple "flo/deb dt2w app" .. like DragonParts for Pixel C.
This app could send "echo 1" or "echo 0" .. ideally.
Or just set sysprop 1 or 0 .. the sysprop will trigger init service to echo 1 or 0,

As I am not the coder we need some experts to make this working ..

Cheers

 

[followmsi]

Today is "adreno" day

lineage-20.0-20230402-UNOFFICIAL-flo.zip

lineage-20.0-20230402-UNOFFICIAL-deb.zip

Changes:
- Used the recommended adreno drivers from feb 2016
- Added DT2W overlay and power HAL flag.

The DT2W stuff has been added for testing .. it's not working.
Pls use kernel manager or scripts to enable DT2W in kernel.

Enjoy

 

[osm0sis]

Today is "adreno" day

lineage-20.0-20230402-UNOFFICIAL-flo.zip

lineage-20.0-20230402-UNOFFICIAL-deb.zip

Changes:
- Used the recommended adreno drivers from feb 20l6

Quick flash and I'm not seeing the the updated GPU string in 0402

 

[followmsi]

Quick flash and I'm not seeing the the updated GPU string in 0402

Thanks for checking !

This are the disadvantages of unclean builds .. Very quick - but "problems" can happen.

Checked the DT2W overlay and powerhal .. also the 3 additional libs from feb 2016 driver package have been copied .. but build system did not overwrite existing libs/firmware.

Anyway ... made the (hopefully) last builds for the next days.

Pls download again .. same name - just fresh builds - with v145 included.

How do you verify version number? from shell ? Or app ?
My app did show me "[email protected]" of the driver version .. internet confirmed it's v145.

Cheers

 

[osm0sis]

Thanks for checking !

This are the disadvantages of unclean builds .. Very quick - but "problems" can happen.

Checked the DT2W overlay and powerhal .. also the 3 additional libs from feb 2016 driver package have been copied .. but build system did not overwrite existing libs/firmware.

Anyway ... made the (hopefully) last builds for the next days.

Pls download again .. same name - just fresh builds - with v145 included.

How do you verify version number? from shell ? Or app ?
My app did show me "[email protected]" of the driver version .. internet confirmed it's v145.

Thanks again! Working well so far with my last few GPU OC and I/O tweaks!

FKM shows the GPU driver strings in the Dashboard view. Not sure if it polls it from some hal or via command.

Past me says you can just run a strings command to find out quickly: https://forum.xda-developers.com/t/...pdated-09-12-15.3228002/page-12#post-69997209

E.g. in /vendor/lib/egl

# strings libGLESv2_adreno.so | grep OpenGL
OpenGL ES 3.0 [email protected] [email protected]  ([email protected])

Vs. us now

OpenGL ES 3.0 [email protected] [email protected]  ([email protected])

Great to see these finally make it into a modern ROM!

 

[ipdev]

<SNIP>
Got a bit of time this evening to do some testing and will let you know what happens.
<SNIP>

Clean flash using followmsi's updated TWRP (twrp-3.7.0_9-1), no issues installing MindTheGApps.
I happen to have MTG synced so I just ran a new build to try.

A year (or so) ago, I was asked to test something regarding system (rw).
Due to GApps (I prefer OpenGApps), I tested with MTG also.
Since, I keep MTG synced.​

​

No issues installing MTG as a complete clean flash.
Back to back install of Linage and MTG. No reboot in-between.

---

Last night, (20230401) the clean install seemed good save for..
I set animation and duration scale to `.5x` under Developer options.
This created a lag? :WTF:

Even after a reboot.
I changed them back to `1x` and the lag was gone.​

---

This morning (20230402) I updated (dirty flash) to the new(er) (20230402)build.
Skipped installing thirteen-20230401 kernel.

Seemed to be good.
Switched to `.5x` on animation and duration scale(s).
No lag but, at first no notifiable improvement.

Normally you can see a difference right away.
After a reboot, I noticed an improvident. ​

---

Updated (dirty flash) to the new (20230402)build.
Skipped installing thirteen-20230401 kernel.

Note(s):
MTG's survival script (addon.d) worked as intended.

I run personal Magisk builds.
Sometimes Magisk can interfere (f*ck up) more than it should be able to. :sad:

Still testing.

Cheers.

 

[osm0sis]

My current boot script if anyone else wants to try some or all of it out with the latest 0402:

/data/adb/post-fs-data.d/000bootsettings:

#!/system/bin/sh

for i in /sys/block/*/queue; do
  echo 512 > $i/nr_requests;
  echo 256 > $i/read_ahead_kb;
  echo 2 > $i/rq_affinity;
  echo 0 > $i/rotational;
done;

echo 128 > /proc/sys/kernel/random/read_wakeup_threshold;
echo 256 > /proc/sys/kernel/random/write_wakeup_threshold;

echo 1 > /proc/sys/net/ipv4/tcp_low_latency;

for i in /sys/class/net/*; do
  echo 100 > $i/tx_queue_len;
done;

echo 585000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk;

echo 1 > /sys/android_touch/doubletap2wake;

echo 1 > /sys/kernel/fast_charge/force_fast_charge;

 

[NightLord]

My current boot script if anyone else wants to try some or all of it out with the latest 0402:

/data/adb/post-fs-data.d/000bootsettings:

#!/system/bin/sh

for i in /sys/block/*/queue; do
  echo 512 > $i/nr_requests;
  echo 256 > $i/read_ahead_kb;
  echo 2 > $i/rq_affinity;
  echo 0 > $i/rotational;
done;

echo 128 > /proc/sys/kernel/random/read_wakeup_threshold;
echo 256 > /proc/sys/kernel/random/write_wakeup_threshold;

echo 1 > /proc/sys/net/ipv4/tcp_low_latency;

for i in /sys/class/net/*; do
  echo 100 > $i/tx_queue_len;
done;

echo 585000000 > /sys/class/kgsl/kgsl-3d0/max_gpuclk;

echo 1 > /sys/android_touch/doubletap2wake;

echo 1 > /sys/kernel/fast_charge/force_fast_charge;

EX kernel has a feature to limit battery max charge so as to slow down battery wear. Do you happen to know the script to enable it and set it to say 85%?
Unfortunatelly, EX kernel manager, from where you could configure this, force closes on the current ROM (it worked without issues on the 19.1 ROM), and the other kernel managers I tried do not have this setting.

On another note, LOS 20.0 seems to have much higher RAM footprint than 19.1, is that right? With 19.1 I used to have around 1 gigs free memory on boot with BitGAPPS installed, on LOS 20.0 I get between 7-800 megs at best.

 

[osm0sis]

EX kernel has a feature to limit battery max charge so as to slow down battery wear. Do you happen to know the script to enable it and set it to say 85%?
Unfortunatelly, EX kernel manager, from where you could configure this, force closes on the current ROM (it worked without issues on the 19.1 ROM), and the other kernel managers I tried do not have this setting.

I'm not sure about that one, haven't ever used it. You'll have to Google it and/or dig around in /sys and /proc with EX flashed.

Edit: Looks likely? https://github.com/flar2/flo/search?q=battery+life+extender

 

[NightLord]

I'm not sure about that one, haven't ever used it. You'll have to Google it and/or dig around in /sys and /proc with EX flashed.

Edit: Looks likely? https://github.com/flar2/flo/search?q=battery+life+extender

nice find! gotta check whether indeed this is it, thx.

 

[patria o muerte]

Hi, I need some help please. Every time I open the play store a strange icon appears on the display at the top right, as shown in the picture. What can it be?
Thanks.

 

[clarkgable]

Hi, I need some help please. Every time I open the play store a strange icon appears on the display at the top right, as shown in the picture. What can it be?
Thanks.

I had this recently as well. It meant that I couldn't update any of my apps from the Play Store. In the end I had to wipe data and system and set up again.

 

[sh0nuff]

Hey guys.. Updates from 14 to 20 (did a full wipe and expanded my partition) and I seem to have lost the ability to connect to my wifi network (WPA2/WPA3).. Worked fine on Android 7 on this same device (Deb)

When I try to authenticate I get a "Saved/Disabled" error almost immediately.

 

[mihaiaka]

Hi. I have 2x flo.
I've reinstalled both with the latest version. Everything looks/works fine.
I do have a strange situations tho', for which i need your help/guidance.
After the "screen time" passes, the display dims and closed... but after precisely 5 seconds it turns back on. And this keeps continuing in a loop.
This happens on both, so i expect that the hardware is fine. I don't recall this on version 19.1.
Turning the display off via power button or double tap on the status bar, is keeping the screen off, as normal.

Any advice would be appreciated.

P.S. On one of them, i tried the dt2w magisk module mentioned a few posts earlier and it works great.

 

[mayanksingh]

i have a deb device and im getting no sim detected. this sim works fine in other phones. i tried with a fresh flash (lineage 20) too but still same issue. how can i diagnose whats wrong?