yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Android Development] retiredtab:
@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>
[Nexus 7 (2013) Android Development] ipdev:
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? :unsure:​

---

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

Cheers. :cowboy:

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.
[Nexus 7 (2013) Android Development] 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)
[Nexus 7 (2013) Android Development] followmsi:
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
[Nexus 7 (2013) Android Development] followmsi:
Today is "adreno" day (y)

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 :p
[Nexus 7 (2013) Android Development] osm0sis:
Quick flash and I'm not seeing the the updated GPU string in 0402 🤔
[Nexus 7 (2013) Android Development] followmsi:
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 "git@ID...." of the driver version .. internet confirmed it's v145.

Cheers
[Nexus 7 (2013) Android Development] osm0sis:
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://xdaforums.com/t/marshmallow...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 V@127.0 AU@ (GIT@I96aee987eb)

Vs. us now

OpenGL ES 3.0 V@145.0 AU@ (GIT@Id2569cc314)

Great to see these finally make it into a modern ROM! 🤩🤘
[Nexus 7 (2013) Android Development] ipdev:
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. :cowboy:
[Nexus 7 (2013) Android Development] 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;
[Nexus 7 (2013) Android Development] NightLord:
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.
[Nexus 7 (2013) Android Development] osm0sis:
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
[Nexus 7 (2013) Android Development] NightLord:
nice find! gotta check whether indeed this is it, thx.
[Nexus 7 (2013) Android Development] 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.
[Nexus 7 (2013) Android Development] clarkgable:
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.
[Nexus 7 (2013) Android Development] 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.
[Nexus 7 (2013) Android Development] 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.
[Nexus 7 (2013) Android Development] 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?
[Nexus 7 (2013) Android Development] mihaiaka:
I've reset (to factory settings) one of them and I've started from scratch. Step by step, and checking if the display turns back ON. The issue occurs after I make the change to security > lock screen > NONE. With this, the screen turns ON by itself after 5 sec. Can someone else reproduce this from their side? Could this be solved in a future build? I'm planning to use the tables in the house as a home assistant wall panel (with 3d printed support+wireless charger+ magnets) so I don't really need any security lock screen (not even slide). thank you!
[Nexus 7 (2013) Android Development] patria o muerte:
I solved disabling display wake up in lock screen settings
[Nexus 7 (2013) Android Development] Cobra11Murderer:
I'm having one doozy with this thing I'm not able to load recovery.. it's showing stock recovery installed... Yet I'm running elemental old room.. hmmm no root ideas?
[Nexus 7 (2013) Android Development] h8computers:
I am also looking for this feature, since I use my Nexus 7 as a home automation dashboard which is powered from AC 24/7. I just replaced the original swollen battery. I would prefer not to have to do this every 1-3 years. I don't know how much longer we'll still be able to buy replacement batteries for a 10+ year old tablet.

When I poked around in sysfs I did not see any obvious way to enable/disable charging. Most of my other Nexus devices had a charging_enabled file, but the Nexus 7 doesn't. I found another thread here where someone patched their kernel to hardcode a lower threshold voltage: https://xdaforums.com/t/disable-charging-decrease-charging-voltage-on-nexus-7-2013-solved.3682984/

So probably, my next move is to compile a custom kernel that works with this ROM, make sure it boots, and then add a similar patch on top. However, I don't see a github link for 20.0 in the OP. @followmsi could you please advise on how to build a boot.img that is compatible with lineage-20.0-20230402-UNOFFICIAL-flo.zip ?
[Nexus 7 (2013) Android Development] mihaiaka:
Thank you very much, it worked for me as well.
[Nexus 7 (2013) Android Development] mihaiaka:
I would also love a way to set the charging limit to prolong the battery's life. ACCA doesn't work. Maybe to have an optional kernel with this mod, for the people interested in this.
[Nexus 7 (2013) Android Development] h8computers:
What I saw in the old 2017 thread is that they patched the kernel to modify the FLOAT_VOLT_43V value which is hardcoded into the driver.

However, I found that this LineageOS build does have a sysfs file to override this value, which means the kernel patch isn't necessary. So what I'm testing right now is to use Battery Charge Limit with a custom control file. I have it write 3800 to /sys/bus/i2c/drivers/smb345/0-006a/float_voltage to disable charging, and 4300 to re-enable charging.

It's not 100% perfect but so far, it seems to work well enough for my purposes. Would be interested in knowing if it works for others.
[Nexus 7 (2013) Android Development] NightLord:
I decided to go back to version 19.1, the substantially increased memory footprint of the A13 system itself makes the device hardly usable in my experience even for basic tasks if google play services are installed.

Followmsi, is there a chance you could make a new 19.1 build with the beta Adreno drivers included? It seemed to increase 3d performance quite a bit (7xx points in 3dmark ice storm test vs. 5xx points on the stock driver), might be nice to also have it 19.1, especially if that will be the last version that will actually be usable on this aging device as a daily driver : )
[Nexus 7 (2013) Android Development] NightLord:
now that Im back on 19.1, I was able to check, this is (/sys/bus/i2c/drivers/smb345/0-006a/float_voltage) exactly where EX kernel manager writes the voltage value you set as max charge voltage under the Battery Life Extender option.

So to limit charging to 4.1v, it should be suffice to have float_voltage contain the text "4100"
[Nexus 7 (2013) Android Development] supreme kyo:
on 19.1, tablet was unusable, i was thinking it was the emmc dying.

April 2 ROM dirty flash over 19.1, with system partition format

following options:

TCP algorithm: highspeed

I/O Schedule: Deadline

Remove any animation

Great daily driver, without any problem and for the first time in a long time the auto screen rotation is working!

@followmsi

Thank you, fantastic work.
[Nexus 7 (2013) Android Development] osm0sis:
deadline is a good minimal IO Scheduler, but in my testing noop was still the only one that improved things on my device; I had been wondering if my EMMC was dying too. Either way there must be an IO bottleneck somewhere down the line for us. 🤔

Also note westwood is still supposedly the better TCP Congestion Control algorithm, although I do recall some people liking highspeed over the years too.
[Nexus 7 (2013) Android Development] mihaiaka:
Hey,

I've checked this on both of my tables.

adding 3800 to /sys/bus/i2c/drivers/smb345/0-006a/float_voltage did disable the charging completly. It was 55% and stood 1-2 hours on the wall-mounted wireless charger (attaching with magnets), and no charge happened. With reverting back to 4300 (or rebooting) charging returned.

Now I'm curious if I can automate this, with the home assistant companion app or with Tasker/etc. Do you have any plan/progress on this? I'm thinking to send an "sudo echo '3800' > wherever" via Termux. But Termux with ssh server running is a huge battery drain :(. Maybe a way of converting a batch script to an apk? Or have an actual/separate app to run a .sh script file on app startup?

I'm really curious if this can be done without adding a smart plug to the setup (cause it will ruin the aesthetic, in my case). That option does work great, using it for my Pixel 1 to upload pictures to google photos with syncthing. (via home assistant automation blueprint)
[Nexus 7 (2013) Android Development] mihaiaka:
on the same battery topic, is there any way to build something like this for this tables/OS combo:

And toggle it from the settings menu or Quick Settings tiles
[Nexus 7 (2013) Android Development] NightLord:
How about simply adding 4100 to /sys/bus/i2c/drivers/smb345/0-006a/float_voltage ? Does in not limit charging at 85%? It should have the same effect than enabling that option in this video.
[Nexus 7 (2013) Android Development] mihaiaka:
I can try to see what the outcome is. Currently i don't know.
[Nexus 7 (2013) Android Development] h8computers:
When you say you want to "automate" it: what events do you want to trigger changes to the charge limit?

I was originally setting this value using Battery Charge Limit, but now I'm just hardcoding it at startup time using a Magisk boot script:

adb shell
su
echo "echo 3800 > /sys/bus/i2c/drivers/smb345/0-006a/float_voltage" > /data/adb/service.d/float_voltage.sh
chmod 755 /data/adb/service.d/float_voltage.sh
[Nexus 7 (2013) Android Development] followmsi:
There are fashable zips available .. for all (older) ROM.

adreno_nexus_feb2016.zip

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

As well I placed a copy into TOOLS subfolder on gdrive.

Thanks to @osm0sis !
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 20.0

Fresh builds ..

lineage-20.0-20230418-UNOFFICIAL-flo.zip

lineage-20.0-20230418-UNOFFICIAL-deb.zip

Changes:

- Google security updates -> April 2023

- Latest LineageOS / LineageOS-UL changes for Android 13

Pls check first page for known issues and more information.

Tested flo build with Magisk 26.1 and v2.4.0-MOD_1.2.

Enjoy :p
[Nexus 7 (2013) Android Development] mihaiaka:
That actually worked. It charged until 78% at a normal pace. I left it on the charger over night and it only got to 83% by morning. I will use this for longer and see how the battery is acting.
[Nexus 7 (2013) Android Development] mihaiaka:
Well ... I my mind i was thinking to automate something to toggle between 3800 and 4300 depending on the battery percentage. Nevertheless, the option @NightLord mentioned, with the 4100 value is a direct answer to my initial question from #4146 (few replies above). I will check/add that magisk boot script (method) you mentioned previously, but with 4100.

Thank you everybody for taking the time to write/share.
[Nexus 7 (2013) Android Development] jhford:
Sorry for the late reply. I installed Android system web view, but where is the "default system provided one"? It's not an app on my device. Thanks
[Nexus 7 (2013) Android Development] NightLord:
thanks!

although there is some problem with the zip, (flashing via TWRP goes down without error, but the drivers are not updated nontheless), manually copying the files over the old ones on system partition does the trick.
[Nexus 7 (2013) Android Development] osm0sis:
You need my Recovery SLAM script to get such an old zip to flash correctly in modern recovery: https://xdaforums.com/t/tools-zips-...ices-platforms.2239421/page-152#post-85285435 :)
[Nexus 7 (2013) Android Development] kelvin-dev:
Two prominent bugs i recorded

1. Screen timeout not work on latest build: lineage-20.0-20230418-UNOFFICIAL-flo.zip

2. Google play gets freeze at "processing ..." after INSTALL any app, i tried delete cache and clean system cache: MindTheGapps-13.0.0-arm-20230401_160426.zip

p/s: i love this thread and the contribution efforts
[Nexus 7 (2013) Android Development] osm0sis:
Screen timeout seems to work for me, no issues with app store installs or updates either, but I'm on the official built MindTheGapps arm linked from Lineage's site though.
[Nexus 7 (2013) Android Development] littloliver:
Hello,

There is a bug for me. Apps can't access camera. For example, Glens, and all camera app.

Only opencamera work for me.

Anyone has this problem ?

I didn't have with 19.1
[Nexus 7 (2013) Android Development] colinmcrae007:
Hi everyone! I'm trying to install 20.0-20230418-UNOFFICIAL-deb on my Asus Nexus 2013 LTE using a TWRP 3.7.0_9-1_followmsi version but receive an error E1001: Failed to update system image. Can somebody explain to me what is the problem?
[Nexus 7 (2013) Android Development] doxts:
Hi @colinmcrae007

Have you already repartitioned your device? Maybe that's the issue in this case. It's required for newer ROMs as the system partition is too small. Here is the guide I followed.
[Nexus 7 (2013) Android Development] ipdev:
Newer partition methods. 😉

[TOOL][UNOFFICIAL][PORT] REPIT: for Nexus 7 (2013) [deb][flo]

[xdathread] - Link

[IIIII] CROSS - Custom ROM Scripted Setup

[xdathread] - Link

Cheers. :cowboy:
[Nexus 7 (2013) Android Development] colinmcrae007:
The repartition operation should be done before installing LOS or straight right after, without booting into it?

Sorry, for maybe stupid questions but I'm a little bit new to this))
[Nexus 7 (2013) Android Development] doxts:
Hi @colinmcrae007

Before installing LOS because the system partition is too small (LOS gets flashed into the /system partition)
[Nexus 7 (2013) Android Development] colinmcrae007:
Thanks for the quick reply and explanation! I appreciate this! Have a good one!
[Nexus 7 (2013) Android Development] followmsi:
LineageOS 20.0

Fresh builds ..

lineage-20.0-20230507-UNOFFICIAL-flo.zip

lineage-20.0-20230507-UNOFFICIAL-deb.zip

Changes:

- Google security updates -> May 2023

- Latest LineageOS / LineageOS-UL changes for Android 13

Pls check first page for known issues and more information.

Tested flo build with Magisk 26.1 and v2.4.0-MOD_1.2.

Enjoy :p
[Nexus 7 (2013) Android Development] artigasperez:
Hi followmsi. Thanks for your work. I really appreciate it since a long time ago.

My /data partition is encrypted since several years ago, when your first builds come with support for it, and i have been upgrading LineageOS official image without having any issue, besides the WPA2/WPA3 mixed mode incompatibility, that forced me to publish a new SID with only WPA2.

Now my flox is in 18.1 202305 build. ¿There is a way I can test your builds of LineageOS 20 without losing data?

¿is WPA3 or WPA2/WPA3 mixed mode working in your last build?

Thanks.
[Nexus 7 (2013) Android Development] AlekosB-flo:
Hi followmsi,

Thank you for your persistent effort not only to keep our beloved NEXUS 7 (2013) alive but also to give it new life.

As soon as you informed us about LineageOS 20.0, I decided to replace LineageOS 18, which I had been using until then without problems. So I installed "TWRP-3.7.0_9-1_followmsi", "lineage-20.0-20230322-UNOFFICIAL-flo", "BiTGApps-arm-13.0.0-v1.9_signed" and "Magisk-v26.1" without serious problems . The version "lineage-20.0-20230322-UNOFFICIAL-flo" ran with problems and was very slow.

I installed the following versions "lineage-20.0-20230402-UNOFFICIAL-flo", "lineage-20.0-20230418-UNOFFICIAL-flo" and "lineage-20.0-20230507-UNOFFICIAL-flo" with TWRP only by flashing them. Nexus 7 is running like a sport car.

Again, many thanks.
[Nexus 7 (2013) Android Development] CrucialWerewolf:
Hey there. How did you manage to get yours running fast? I'm running on the latest lineage-20.0-20230507-UNOFFICIAL-flo with the EX Kernel and just runs ATROCIOUSLY slow. I even changed the system format to F2FS instead of ext4 to see if it made a difference, nope. It hangs and crashes the System UI like a lot. It'll run snappy for like a few seconds and then it just painfully slows down.
[Nexus 7 (2013) Android Development] drownboy:
Hi everyone! I`m using this firmware for two months. I`m using magisk\microg and i have heavy battery drain in standby. Also i have bug with screen off - if i turning off security on lockscreen it will constantly light up, unless screen off by power button.

Upd: sns_async_ev_wakelock - 85% of screenoff.