yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Tomoms:
Hello! I guess it's time to bring back at least some of the fonts :D

I'll fix this in the next build.

My setup is Gapps-free (I use MicroG), so I'm not facing any Gapps-related issue, have you tried giving a look at this page?

Another thing that comes to my mind is that the ROM + Gapps are taking up something like 99% of the /system space, and now some Google service wants to download some stuff in the /system partition, and since there's no space, it fails. But I think this is unlikely, because the /system partition is read-only and I think not even Google's services have the power to remount it in read-write mode and write to it.

Wrong. I, in first place, use them.
[ONE Android Development] capt.ron:
I also have an absence of emojis since flashing latest ROM. Very smooth running ROM and the GPS gets a quick fix! Thanks for your work [MENTION=5727088]Tomoms[/MENTION]
[ONE Android Development] :
Hi [MENTION=5727088]Tomoms[/MENTION], I just moved to your August 5th 2020 build and all is well... Only I noticed with openvpn that GCM encryption seems to be broken. My provider supports GCM for sure so I know that's not the problem here. Switching back to CBC encryption gets me internet access right away, but on GCM I can't get a single packet through. Here is my kmesg right after attempting to use GCM:

Also thank you for keeping up on Security patches even faster than the official Lineage maintainer, this last August patch is crucial to have ?

Edit: updated to the latest build and the problem persists

Edit 2: now my location seems to be broken as well... I dirty flashed from the 20200805 build. Maybe a clean flash will help
[ONE Android Development] Tomoms:
If you are going to clean flash, please try the first official nightly to see if the VPN problem persists.

I honestly didn't understand your problem because I know nothing about VPNs, but if the problem (as I would bet) exists on the official nightly as well, you can report it to LineageOS.

BTW, are you using Gapps or MicroG or neither?
[ONE Android Development] aevan:
Hello @ Tomoms,

Can't wait to test the next release :laugh:.

Even if I love the project, I can't really use microG today because there's still some features (like Android Auto) that I need and that do not work with it. Maybe one day I hope!

For some strange reasons, the "Ok google model update" problem seems to disappeared by itself, as I am no longer seeing the notification of "download failed" and everything seems to be okay when I use Google Assistant. May be a Google Play Services update has fixed the problem, I don't really know.

I could try a clean install with pico OpenGapps (instead of nano) to see if I've got the problem too. I will give it a try when I'll have the time. But as you've suggested, it's unlikely that even Google apps could have write access to /system partition, as it would implies to grant su privileges or something like that, I think.

See you soon ;)!
[ONE Android Development] :
I'm using microg with bromite system webview.

Spent a whole two days flashing different lineage builds until I landed back on Pie with the same VPN problem. Did some investigating and discovered I was using the UDP VPN protocol instead of TCP. UDP is not optimized for mobile connections, whereas TCP can handle random connection drops without losing internet connectivity to the VPN server and minimizing packet loss.

My internet speed nearly tripled after switching to TCP, and my location works again since that wasn't working due to the VPN connection having no internet connectivity.

Back to android Q!
[ONE Android Development] Tomoms:
Well, at least it's gone :D

So it seems that you found the solution to your problems, that's good :)

A new build with better font support (i.e. no more broken emojis/icons & more supported alphabets) is coming soon (maybe tomorrow). OpenGapps nano should still be possible to use.
[ONE Android Development] hystrix65:
I installed your rom yesterday, good job, seems to work fine! Thank you for your job!
[ONE Android Development] :
Yes all is working well and I have a sense of security being on the August security patch. Thank you again Tomoms! Looking forward to your custom kernel with hopefully maple IO scheduler and smartmax cpu governor support with underclocking ?

Heads up for anyone running microg on android Q:

I had to disable WiFi scan throttling in developer options to get my location to work properly. The latest google maps runs without a hitch now ??
[ONE Android Development] aevan:
Hello [MENTION=5727088]Tomoms[/MENTION],

I am facing a new problem with your ROM (maybe it is present in the official one too) which is related to frontal camera.

In fact, I'm not able to choose it anymore in the standard camera app (and other apps like Reface doesn't detect it).

The regular back camera, however, works normally.

Do you have that problem too on your setup?
[ONE Android Development] :
Front camera works for me on the latest build, I'm running f2fs on /data and /cache, clean install with magisk and microg. Did you dirty flash? Also make sure you're running the latest firmware for the OnePlus One, which should be bundled with the last cm13 build.

I also wanted to mention to anyone looking to maximize their battery lifespan; (especially if you're still running the original OnePlus One battery like I am) Advanced Charging Controller magisk module works wonders. It keeps you from undercharging and overcharging your Lithium Ion battery, and also utilizes the battery temperature sensor to adjust the charging mA to keep the battery from ever getting too hot.

I was able to restore my dying battery and get back to 4-5hrs of screen on time using this magisk module for a year. Food for thought
[ONE Android Development] Tomoms:
No, I can use both cameras with any app.
[ONE Android Development] aevan:
Ok guys, false alert. Sorry for that... I just rebooted my phone and it started to work again. I don't know what went wrong exactly...

Here are some informations about my setup :

- First, I came back to the last official CyanogenOS 13.1.2 (ZNH0EAS2JK) with fastboot image files, so all my partitions were wiped and all firmware stuff (modem, tz, etc.) should be okay.

- I made a first boot to CM 13.1.2 to get things initialized correctly

- I then flashed TWRP 3.4.0.0

- From TWRP, wiped all partitions (/system, /data, etc.)

- Installed the first official build of [MENTION=5727088]Tomoms[/MENTION] (was lineage-17.1-20200805-UNOFFICIAL-Tom-bacon-signed.zip)

- Installed OpenGApps nano

- Booted and used the ROM for some days ^^

- Then, updated to lineage-17.1-20200811-UNOFFICIAL-Tom-bacon-signed.zip when it came out (so no clean flash here, but I think a dirty flash is okay here, as OTA updates should also come on the next releases ;))

I didn't try F2FS for /data and /cache, because I've had a few mishaps in the past with this setup (very long boot with Oneplus logo that got stuck for about 5 minutes, same when booting in TWRP). [MENTION=6870501]ThunderThighs[/MENTION], did you experienced issues like that with your setup?

Thanks for the tip! I'm also still running the original battery so I will definitely try the Magisk module you mentionned :D!
[ONE Android Development] Tomoms:
A dirty flash is totally ok, it's the usual way to upgrade to a new build of any ROM :)

F2fs is 100% safe to use. I'm using it as well, and I've always used it in the past. No issues of any kind :)

I can recommend you the Advanced Charging Controller Magisk module as well - super useful to prevent battery degradation.

EDIT: the new build is coming later today or tomorrow - didn't have time to launch it yesterday.
[ONE Android Development] hystrix65:
I downloaded but i'm not able to install it, I really don't understand how to do it...
[ONE Android Development] :
I used to experience the same issues which is why I stuck with Tomom's last selinux permissive Pie release from like a year ago. Somewhere in between now and then, LineageOS and/or Tomoms seems to have fixed it completely. No more data corruption over time, no more delay for the boot logo. I've just recently tested ext4 against f2fs on Tom's latest Q ROM and there's quite a noticeable difference in speed now.

I'd say go for it, I've been running f2fs on /data and /cache for about a week now without a single crash or mishap! The auto trimming and transfer speeds of large files is nice to have. Your flash storage degrades much slower over time as well

Also I know this is a little off topic; but few people seem to know how well our device can be locked down against local attackers:

The open source OnePlus data Protector app (github.com/tobiaqs/oneplusdp) can lock your bootloader, backup and replace your recovery partition with a blank read-only file that can't be overwritten without root access. It does it on the fly, no reboot required. Ideally you would enable these changes if you're going to a physically insecure location.

If you flash Tomoms' last Oreo build you can utilize vdc cryptfs to change your storage encryption password to one of an infinite character length. I have to enter a 20 character password on my OPO to boot it up.

You can also use a separate password for your screen unlock and combine it with the app "wrong pin shutdown" to shutdown the device after however many attempts (I set 3), safely decrypting the device and requiring the attacker to then figure out the encryption password.

It would be interesting to know of any other Android phone out there being able to seemingly lock/unlock the bootloader on a whim like ours can

Oh and setting "restrict new USB devices" to on in settings -> privacy prevents someone from connecting to your device and running any commands while it's decrypted
[ONE Android Development] :
[MENTION=5727088]Tomoms[/MENTION] do you possibly have any plans to Port sultan's camera Hal or color os camera Hal to your Q ROM? That would be a game changer.

Also is it possible to allow your ROM to be flashed with the /system partition formatted as f2fs? I remember a few ROM maintainers from the Android MM days simply had to add a line for f2fs in the fstab and add something to the zip flashing process.

Hope all is going well for you!
[ONE Android Development] Tomoms:
New build

The new build is up!

I've reimplemented support for several fonts (please confirm emojis and other icons now work for you), improved a couple of GPS-related configurations (getting a fix is now a bit faster?), and picked a few patches that should improve the responsivity of the touchscreen and the scrolling smoothness.

Please report back whether you feel there's a real improvement or not!

Kernel-wise, I've only picked a bunch of general fixes and security patches.

Sultan's camera HAL is already bundled. In fact, Sultan's camera HAL is used in all ROMs for our Oneplus One since Android 8.0, because for several reasons all the other HALs (the old CyanogenMod/LineageOS hal - which kind of sucked, ColorOS HAL, OOS v3 blobs...) cannot be used anymore.

Having the /system partition formatted as f2fs is impossible, because it is now flashed in block-based mode (i.e. a system.img image is flashed onto the partition). Back in the Marshmallow days block-based flashing was already the default, but one could choose to build a simple system folder (which, being a folder, doesn't have an in-build filesystem) and flash it in a file-based mode. This is the reason why some maintainers were able to allow formatting /system as f2fs. Now the old file-based method is not supported anymore in the Android source code; it might be possible to implement support for creating a system image as a f2fs partition image, but I don't know how to do it and I've never seen anyone who tried to do that.
[ONE Android Development] capt.ron:
Greetings [MENTION=5727088]Tomoms[/MENTION]- I downloaded and installed your latest rom using the built-in installer with no problems. I can also report the emoji issue has been resolved. Thanks for that! Also, in your first LineageOS 17 build I reported a "quick-fix" for GPS but later I noticed a degradation in getting a lock. In your LineageOS 16 builds the gps fix was the fastest my OPO has ever performed. In your new build I initially did not get a fast fix but it did eventually get there and I used my Endomondo app for a little over 2 hours this morning and I can report the location tracking worked flawlessly the entire time. Subsequent testing for gps fix have been fast (not LineageOS 16 fast but fast enough). To me, it always seems the first fix attempt of the day is always the slowest but after the initial attempt then the fix speed increases. Anyway, that's what I've noticed and thanks to you for your work and awesome roms :) Take care everyone!
[ONE Android Development] awtacular:
Thanks for the new build I grabbed it yesterday before you posted it. For some reason my phone doesn't seem to do well on Q roms when it comes to GPS and wifi. I constantly lose wifi and can't get locks with gps even with wifi on and wifi & bluetooth scanning. It's not your rom it's with numerous other Q roms I've tried as well. Previous builds have always worked with various other roms, just not the Q/Lineage 17 builds. My phone hates them for some reason. I'll just stick with 16 build since it seems to work flawlessly.
[ONE Android Development] Tomoms:
Hey, thank you for your feedback. I'll see if there's anything I can do to improve the GPS fix speed. On my first build the fix was super fast. On my later builds I could never get a fix, but my setup with MicroG was quite messed up so probably some permission was missing or whatnot. Anyway, I'm about to perform a clean install of my latest ROM, I'll let you know how fast my GPS fix will be.

This is very strange... Have you tried to go back to 100% stock CM13 (so that you firmware is updated to the latest version and everything is cleaned up) and then to reinstall my Q ROM (or any other Q ROM)?

By the way, I've found the fix for the broken AUX audio output! I'm going to include it in my next build and will submit it to official LineageOS as well :)

I might even prepare a small flashable zip that can be flashed on my current build to fix the issue, so you can get the fix before I decide to rebuild the whole ROM (which is pointless, as I've just released a new build 2 days ago).
[ONE Android Development] aevan:
Hello there :)!

OTA update went well and I can confirm that the emojis problem is gone :D. I can see a lot a alphabets that are supported too (Arabic, Chinese, Indian…). A good test to see that is to open Waze and choose an other voice, then you can see which language appears correctly and which one does not. For my part, I only need latin alphabet so all is right for me :).

Concerning the GPS fixes, could you please explain (in a nutshell) what it is intended to? For my part, it always took some time before getting a signal, even with other ROMs, so I got used to that ^^.

Thanks for your report, I will give it a try when I’ll make a clean install :).

Well, the least that can be said is that you’re a security paranoid :laugh:. For now I’ve just enabled file-based encryption (you have to do the code in the recovery too), which is, I think, sufficient for most of potential thieves who, anyway, probably wouldn’t have the brain to steal my data :P.

I didn’t find the setting you mentionned but I think it is enabled by default, because when you connect your device to a new computer you are getting a pop-up message to allow that new computer or not in ADB.
[ONE Android Development] Tomoms:
The Restrict USB setting can be found in Settings > Privacy > Trust. The ADB pop up is a different thing :)

In the latest build I've forced the enabling of GLONASS and set different localized NTP servers in the GPS configuration file.

Getting a fix was very fast for me on my first builds, now it doesn't work anymore (I can't get a fix at all) but as I've explained, my setup is half-broken, I need to clean install my latest build before stating any conclusion.
[ONE Android Development] Tomoms:
Hello,

here's the fix for the AUX audio output bug: lineage_bacon-AUX_fix.zip

You can flash this zip on my builds (and even on official LineageOS 17.1) to fix the problem.

My fix has already been merged into our official device tree, so starting from the next official nightly (and from the next build of mine, of course), flashing this zip won't be necessary anymore.
[ONE Android Development] :
In previous Q builds of yours I've had to wiggle my aux cord and twist it a certain way to get the phone to switch from phone speaker output to aux output. Is this fix related to that?
[ONE Android Development] Tomoms:
In my previous Q builds there was absolutely no way for me to get the AUX output to work. The fix addresses this problem. It is possible that by rotating and twisting your cable, your phone suddenly recognizes your AUX output device as a headset, thus it works. If this is the case, this zip should make AUX output work properly without having to move the cable :)
[ONE Android Development] aevan:
Hello, I never had this problem for my part. AUX works normally with a micro-headset plugged in :).

On the other hand, I've got a problem when I make a call with the external speaker enabled: people hear themselves talk, which is a bit annoying :p.

Is there some people who have the same problem here? I thought there was may be some tweaks to make with AudioFX to fix the problem, but I'm not sure.
[ONE Android Development] Tomoms:
Headsets were never a problem, they've always worked. What didn't work until a few days ago were AUX-connected stereo systems or car radios. That's the issue my fix addresses.

The other problem you mentioned is probably related to my fix for the speakerphone issue. On official nightlies, when using the external speaker during a phone call, the other person can't hear you at all. My fix (which technically hasn't been found by me...) solves this issue but could introduce side-effects like the one you described. I had tried making a few calls with the speakerphone, before implementing my fix in my builds, and no one had ever said they could hear themselves, so I thought it was a safe solution. I'll test it some more and try to find a better solution. Send me a PM if you're willing to try some other possible fixes :)
[ONE Android Development] aevan:
Okay, strange, as my headset is plugged in the AUX input too. But maybe I misunderstand the real problem here ^^.

My tests were made without the last fix you published yesterday (lineage_bacon-AUX_fix.zip). I will make some new tests with that fix applied to see if it improves the situation :).

I keep you in touch ;)
[ONE Android Development] Tomoms:
lineage_bacon-AUX_fix.zip won't affect calls with speakerphone. If you have an issue without the zip, you'll have it even after flashing it.

What I wanted to say in my previous post is that even without my fix, a headset plugged into the 3,5 mm jack would work, while a stereo system would not. With my fix, both things work :)
[ONE Android Development] ImmortAlex:
If we talk about audio anyway... Is there any chances to bring back Hi-Res and ULL audio we had in official CyanogenMod? AFAIR we lost them somewhere when move to Treble-compatible configuration.
[ONE Android Development] ilmich:
H Tomoms, do you accept pull requests on github?!?!

I've some suggestions on camera hal (for example disable the default "zero shutter lag" because help to avoid blur, but often introduces more noise).

Thanks

Michele
[ONE Android Development] Tomoms:
Treble-compatible configuration?

About Hi-Res audio, I don't know how to fix it and honestly have no interest in trying, I might consider trying if you can give me some tip about where to start from.

Sure thing. Do whatever you want! If some repo is missing in my Github account, just tell me so I can fork it from LineageOS, or do it yourself and I'll gladly look at your changes.
[ONE Android Development] :
Isn't that what viper4android is for? It's supposed to enable the built-in dac to increase the audio quality and sampling rate. Am I wrong?
[ONE Android Development] Tomoms:
I'd say you are. If the inbuilt DAC was disabled by default, you wouldn't be able to play any kind of music with your phone. AFAIK Viper4Android is just a layer of libraries and software effects.
[ONE Android Development] :
I know for sure that viper4android increases the audio sampling rate above the default. I may be wrong about the dac part. If I remember correctly it was the built in amp that CyanogenMod OS was able to utilize. The last ROM I used it on was Jgcaap's unofficial cm13 with color os hal

---------- Post added at 12:53 PM ---------- Previous post was at 12:15 PM ----------

@Tomoms I clean flashed to your 20200823 build and unfortunately it crashes immediately after entering my storage decryption password, repeatable every time. Rolling back to the previous build and it works fine.
[ONE Android Development] Tomoms:
Will send you a new kernel that you can flash on the previous build soon. You'll have to test whether it works properly or it starts crashing again.
[ONE Android Development] ImmortAlex:
I mean transition from A7 to A8 (LOS 14.1 to LOS 15), when a lot of things changed due to Treble.
[ONE Android Development] scormax:
can i flash original los17 27th build on urs(dirty)
[ONE Android Development] Tomoms:
Nope, I sign my builds with my own key, so if you dirty flash the official one on top of mine you'll end up in a bootloop. Only a clean flash is allowed.
[ONE Android Development] daniga74:
Manual network operator

Hi [MENTION=5727088]Tomoms[/MENTION], can you try to switch on "manual network operator" flag because on the official lineage 17.1 it doesn't work. I collect trace information by "adb logcat" command. Thanks for you effort.
[ONE Android Development] Tomoms:
Hmm... It was broken on 16 but then got fixed. Will check soon!
[ONE Android Development] miltonsaha9200:
Installed the ROM. So far Great. But Bengali Language Font doesn't support. Can you please tell me a quick fix? Otherwise i have to switch the rom which i don't want. :(
[ONE Android Development] Tomoms:
Unfortunately I had to kill some fonts to save system space, to allow installation of OpenGapps Nano. If I bring back support for those fonts, people using my ROM + OpenGapps Nano will be in trouble...

So, no "quick fix" is available. The only thing that comes to my mind is that there could be a way to provide those fonts as a separate, flashable zip file, so that people like you can flash it only if they need it. It's a good idea, but as I've stated it's not something I can do quickly - you'll have to wait until the next build, provided that I figure out how to do that in the meanwhile.

I'm sorry, but as of now there's nothing you can do. If you want Bengali support, you have to change ROM.
[ONE Android Development] miltonsaha9200:
I've tried to place font file in system>fonts. but didn't work :(

But i do need the language support. Let's see if i can find any other way
[ONE Android Development] Tomoms:
I think I've found a clean way to add back only the Bengali font to my builds. If I ran a new build tomorrow, would you be able to try it out?
[ONE Android Development] miltonsaha9200:
obviously :):) I will be delighted to test this out :laugh::laugh:
[ONE Android Development] daniga74:
[MENTION=5727088]Tomoms[/MENTION], in my case default gallery doesn't see the photo when I take a screenshot.

Any news about "manual network operator" ?

regards
[ONE Android Development] Tomoms:
Hmm... I just tried the screenshot thing and you're right, however it does show older screenshots (the ones I took a few days ago). Maybe the mediascanner service is not scanning the folder for new content, and a reboot could help?

About the manual network operator issue: you have to be patient, I have an exam tomorrow, thus in the past days I couldn't dedicate any time to development stuff :)
[ONE Android Development] daniga74:
Reboot doesn't solve the issue. Don't worry, take your time, and good luck for your examination.

---------- Post added at 01:35 PM ---------- Previous post was at 01:35 PM ----------

Reboot doesn't solve the issue. Don't worry, take your time, and good luck for your examination.