yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Tomoms:
True, but since quite a few builds, that checkbox should be disabled by default. @iTz_Sahan , you might have enabled it accidentally.

Already implemented in a build that I sent to a user for testing, did not fix the issue. Very strange, I'm looking into it now.

No, from now on I'll only focus on 18.1, but I'll still provide a couple of 17.1 build with the security patches that will come in the following months.

Just flash it back using fastboot.
[ONE Android Development] M4Master96:
Does that mean you moved to 18.1 ?

last time I checked XDA, you were still on 17.1 and so just want to confirm :)

BTW, is it possible to add DT2S anywhere on homescreen (can be a separate toggle just like tap to sleep on status bar) on 17.1 ?

I am on 6th Feb build of LOS 17.1 right now (using your ROM almost since August 2019) but didn't saw this option anywhere so I hope I didn't miss it.

If possible, requesting you to kindly add the option atleast in 18.1 if you are moving away from 17.1 ?
[ONE Android Development] Tomoms:
Yes, I'm now on 18.1 :)

That feature is probably hard to add both on 17.1 and on 18.1. I don't even know where to start from. Can you tell me the name of a custom ROM that has got it? It might help me. But don't get your hopes too high...
[ONE Android Development] Tomoms:
Encryption is finally fixed! I can't upload the new build to SourceForge because the uploading server is broken right now, so you can download the new build here: https://mega.nz/file/s9lmkRhD#TYnKWclOpZfD80hkkwQiCAeIMfGx-L7T0yLwYuK4xWk

You only need this if you want to enable encryption, otherwise you can stay on the previous build and update when the next one, featuring March's security patches, comes :)
[ONE Android Development] ffff2:
HavocOS should have it, but I don't know if it was present in the build for bacon.

Actually I think the tap on the homescreen feature was part of their default launcher not the ROM itself
[ONE Android Development] Tomoms:
Yes, this is the reason why I think it's not straightforward to port it to Trebuchet.
[ONE Android Development] M4Master96:
I think custom ROMs having that feature use their own launchers and not modified Trebuchet

ElementalX kernel had DT2W but that was when the device was locked.
[ONE Android Development] Tomoms:
New 17.1 and 18.1 builds coming soon, with March's security patches and possibly something more.
[ONE Android Development] Djiban:
Hi evryone, I do confirm that I cannot get data back on 18.1, when I come back from airplane mode. Sent Log to @Tomoms , thx for his support.

anyway, I still need time to get signal and data when I turn the phone on. Maybe something is bad on my device, or my install
[ONE Android Development] hystrix65:
Ok, I've decide to upgrade to 18.1.

Few questions before I start (I'm getting old I don't remember many steps...).

First of all, I've TWRP 3.2.2-0 installed, should i update it? And how? I don't remember how I did it. Now, when i reboot from recovery, it shows what you see in the photo, what should i do?

Second question: in your opinion is it better to use OpenGapps, MindtheGapps os BitGapps? Now, with 17.1, I'm using OpenGapps.

Thank you
[ONE Android Development] Tomoms:
Update your TWRP to the latest version: https://dl.twrp.me/bacon/twrp-3.5.0_9-0-bacon.img.html

Flash it with fastboot: fastboot flash recovery twrp.img

Don't use BitGapps. Choose freely between OpenGapps and MindTheGapps. I haven't tried either, so I can't really advise you.
[ONE Android Development] capt.ron:
I used open gaaps that @Tomoms highlighted on first page and it seems to work fine. Also, I just flashed the twrp.img within the existing twrp on your phone and it seems to perform fine.
[ONE Android Development] kekerosberg:
I have had problems flashing TWRP from TWRP so I would recommend against it. Updating via fastboot has always worked fine.
[ONE Android Development] hystrix65:
As far as I remember, some months ago I tried to update from TWRP and I had many problems, i Think i will try with fastboot, thanks. I hope to remember how to do it... :LOL:

Edit: First step done... TWRP upgrade done!
[ONE Android Development] capt.ron:
I guess I'll start using fastboot method also (to be safe). Thanks @kekerosberg for the suggestion👍😊
[ONE Android Development] Alvin50:
I cannot install your 18.1 ROM in my Galaxy J5/2017 neither with TWRP nor with OrangeFox. Both abort saying they cannot install a ROM signed for Tom Bacon as my device is J5y17lte... How can I overcome this or it's definitely wrong what I'm doing?

Kind regards
[ONE Android Development] sumitinhome:
of course you are doing definitely wrong. This rom is made for Oneplus One. It cannot be installed in samsung j5. Roms are device specific man.
[ONE Android Development] Dashur7:
Hi @Tomoms , I tried flashing the latest 18.1 build as of today and it flashes without any errors on the latest TWRP. After I boot into the ROM, with or without Gapps, the screen is blank and there are glitches on the screen when I repeatedly press the hardware navigation keys. I tried grabbing a log with adb logcat but the device isn't being detected by the adb. I can still change the volume and access the power menu. The device is also detected by my PC but can't access the files because the default USB config is no file transfer. I managed to copy the dmesg file after rebooting back to the recovery; have attached it in the post.

---EDIT---

I also tried installing the 17.1 build and it's working fine; if that helps :)

https://pastebin.com/ZGDY16dY
[ONE Android Development] Tomoms:
Unfortunately, the last_kmsg is useless in this case; it is only useful to debug a kernel crash that leads to a reboot of the phone. What we would need here is a logcat. Can you try grabbing one again, by running adb root beforehand? If I am not mistaken, that should allow you to grab a log even when you can't manually enabled USB debugging & USB file transfer.
[ONE Android Development] Dashur7:
Got it. I'll try it out as soon as I get some free time.
[ONE Android Development] hystrix65:
Ok, done! but I had to go back to 17.1, many home banking apps didn't work with 18
[ONE Android Development] Alvin50:
Thank you for your reply: in the changelog I didn't see any reference to a specific device, and was fooled thinking it were a generic ROM. Usually there's an easy to see banner where suitable devices are listed.
[ONE Android Development] Tomoms:
Just under the thread's title there's the subforum hierarchy banner which shows that we are in the Oneplus One's subforum :)
[ONE Android Development] Alvin50:
NOW I see it... You are right, but a better advertising could help who, looking to a lot of articles, usually finds this in the incipit... Let's say that, from the graphical viewpoint it's scarcely capturing the reader's attention.

Kind regards.
[ONE Android Development] Tomoms:
New 18.1 build available. 17.1 is coming in a few days :)
[ONE Android Development] Dashur7:
Hey @Tomoms , I disabled the developer settings on 17.1 to try this out. The adb root command needs to find the adb device, which isn't detected as the debugging is turned off. I also tried enabling the developer options but keeping the default settings; same problem. After a little reading I found out that the persistent settings for adb are stored in one of the files in /data/property/ I tried pulling it via adb in recovery mode but it seems to have a single file post Android 9 with all of the settings merged. Is there any way else I can grab the logs?
[ONE Android Development] Djiban:
I did the OTA, if you want any feedback, let me know.
[ONE Android Development] Tomoms:
Yes, there's a simpler way: in the next days I'll prepare a flashable zip that, during the booting process, will auto-save the logs somewhere in the /data partition, because I need it for my personal testing purposes. I'll share it with you.

Is it me, or the new build feels a bit smoother than the previous ones?
[ONE Android Development] SamVVaeck:
Hey everyone, I have been following this thread for a while to see when it gets almost fully stable. Are there any bugs left at this point aside from the 5GHZ hotspot?
[ONE Android Development] sumitinhome:
no major bugs in my view.. using 18.1 as my daily driver for a month now
[ONE Android Development] Tomoms:
A new 17.1 build with March's security patches is available! It'll be available via OTA tomorrow.

EDIT: available via OTA now.

GPS fix might be a bit slow sometimes but I think I will improve it at least a bit in the next days. WiFi screen mirroring without external devices such as Chromecasts and similar tools doesn't work but it's normal, Google killed the feature and now it is only available on newer devices. Some people face issues with mobile data & network signal but I, just like many others, cannot reproduce the issues.
[ONE Android Development] lilcourv:
Yes the new build feels smoother to me too
[ONE Android Development] Fabien70:
Hello

Thank for job.

I flash 18.1 without problème, all is good. But i Just have a bug, I can't configure anyway short and long press menu button.

Before i can configure it and I did not do anything special and now i can't do it.

I wipe cache and dalvik cache, no success.

Thanks for help.
[ONE Android Development] Tomoms:
Setting

Settings > System > Buttons. I can see the option there, can't you?
[ONE Android Development] Fabien70:
Yes I allready do this but that no change

One press = menu allways
[ONE Android Development] capt.ron:
@Tomoms, could you take a look at this error message that pops up when I try to connect my opo to the head unit screen (in my car) using the Android Auto app. The actual app works fine on the phone but the connection to car screen is failing. Your 16 and 17 versions did work previously. Thanks! (I'm using version 18)
[ONE Android Development] EotT:
I upgraded today to 18.1, and wow, this build is smooth! It's running smoother than the 17.1 build! Many thanks! (y)

I have 2 questions:

1. When using the status bar slide gesture to dim the brightness, it doesn't go all the way down, but stays at something like 20%. Is there any way to use the gesture to make it go all the way down to the minimum brightness?

2. As far as I can see, I can only configure tap and long press behaviour of the menu button. For the home button, in addition, it's also possible to configure double tap behaviour. Is this also possible for the menu button?
[ONE Android Development] bleistik:
Hi,

I did an OTA update to lineage-18.1-20210309-UNOFFICIAL-Tom-bacon-signed.zip, from a fresh install of lineage-18.1-20210227-UNOFFICIAL-Tom-bacon-signed.zip with magisk installed. Update was successful but the reboot only showed the boot animation for some minutes and then rebooted to recovery. I'll attach the last_kmsg.

thanks for Your efforts

Bernd
[ONE Android Development] ImmortAlex:
Installed your latest 18.1, opengapps 20210130 pico, Magisk canary. Everything works smooth and fine, encryption on f2fs too ;)
[ONE Android Development] Tomoms:
Maybe you could try to restore the default setting, reboot, and change it again. I've changed that setting as well and it's working as expected.

I cannot look into this issue without a log.

1. I can confirm the issue but I have no idea how to fix it. If you weren't using an unofficial version of LineageOS I'd suggest that you file a bug on LineageOS's Gitlab, but they don't accept bug reports from users who use unofficial builds, even if the issue is clearly not related to any of my modifications. I'm in contact with all the LineageOS devs, I'll talk about this bug with them.

2. It doesn't seem to be possible.

Bonus point for you for providing a log together with your issue report! Thanks :)

Unfortunately the log you provided doesn't help much - when the device reboots to fastboot mode or to recovery, it's one of those rare cases in which the problem, albeit causing a reboot, occurred at OS level, and not at kernel level. In these cases the magic debugging zip I wrote about some days ago would be useful - the problem is I haven't created it yet... I'm super busy these days :)

Try re-downloading the zip file manually and flash it, then reflash Magisk (v22) as well.

Welcome back!
[ONE Android Development] dankovac1999:
Hello,

[Lineage 18.1]

I was wondering if it's possible to change number of qs tiles from 9 to 6 like pixel has. I haven't found any settings, so maybe it's hiding from me 😁
[ONE Android Development] capt.ron:
@Tomoms, would the app "Logcat Tool" be appropriate to capture the Android Auto error?
[ONE Android Development] Tomoms:
I've never heard of it but I guess it would work. Just open it after the error appears and save the logcat to a file.
[ONE Android Development] EotT:
I'm using gravitybox now to fix above problems. That works, but it feels a bit like overkill just to fix that, and it needs xposed framework. I was hoping it could somehow be changed/added in the rom. But it seems that it should be added or fixed by the LineageOS dev. Fingers crossed. Thanks for your answer.
[ONE Android Development] Tomoms:
Of course it can be added in the ROM, but it needs to be done by someone who knows how to do this stuff (it's probably not that difficult, but I'm afraid I would not be able to do it).
[ONE Android Development] EotT:
I might have found what you have to change to reach minimum brightness by using the brightness slider:

In PowerManager.java, you can see that the value of config_screenBrightnessSettingMinimumFloat is used, unless it is invalid (meaning it's value = -2), in that case, the value of config_screenBrightnessSettingMinimum is used.

I did a search to find where those values are defined, and I found them in config.xml. The value of config_screenBrightnessSettingMinimumFloat = -2 (meaning it is invalid), so the value of config_screenBrightnessSettingMinimum is used, which is 10. I think that you need to change this value to 1 (or 0?).

Or you could also change the value of config_screenBrightnessSettingMinimumFloat to 1. I think this is preferable, because no extra logic is applied to the value.

(ps. this is the first time ever I've looked at the code, so I might be wrong).
[ONE Android Development] capt.ron:
Hope this is helpful @Tomoms. If not I'll try again.
[ONE Android Development] capt.ron:
Sorry, here's log
[ONE Android Development] pranavrocksharma:
where is sbc hd option i am not able to find it in dev options and in bluetooth option too
[ONE Android Development] Tomoms:
Good job, thank you for the insights! I'll take a look at that code ASAP and will try to find a solution.

What kind of USB accessory are you trying to use? Brand? Model? Any other possibly relevant information?

After you connect your headphones, head to Developer Options > Bluetooth audio codec.
[ONE Android Development] capt.ron:
What kind of USB accessory are you trying to use? Brand? Model? Any other possibly relevant information?

@Tomoms, not so much an accessory as just an app (Android Auto) with a capability to project the map screen to the "head unit" on the car dashboard screen via charging cable. Sort of like adding an additional display to a computer. I'm using my OPO and original charge cable to connect to the head unit via the USB port in the car. When connecting to the car it immediately fails but charging current is still working. It's suppose to launch Android Auto to the car display screen (and did work on earlier versions of your ROMs and all factory roms). I've tried changing the USB preferences on opo and also enabling/disabling USB debugging mode. Also tried different cables with same result. Anyway, thanks for your time!
[ONE Android Development] Tomoms:
I need someone who could perform a clean install of my ROM and test a few things. Expect many broken builds, so I'm looking for people who do not use their OPO as their daily driver. PM me if you're interested :)

Please try again after flashing this kernel: https://mega.nz/file/FpFQWJhS#zB3UyUHs7vKmuyi8opbnJrk3MNcCqJpiMmLpyiMWpW8
[ONE Android Development] capt.ron:
Darn, test kernel didn't do the trick. Anyway, I appreciate your effort and don't want you to spend a bunch of time on this. I think it's a widespread problem with custom ROMs, jmo
[ONE Android Development] akki4554:
Can I dirty flash over 17.1 latest official nightly? Dont want to loose data.
[ONE Android Development] Tomoms:
People say it works, but I've always thought it wouldn't. You can take a nandroid backup from TWRP and try, so in case of failure you can roll back to the official nightly and restore your data.
[ONE Android Development] capt.ron:
What Gapps package are you using?

Open_gaaps_arm_11.0_pico
[ONE Android Development] Tomoms:
I've read that sometimes, in the past years, OpenGapps, especially in the early stage of their development (such as now, for R), were lacking support for Android Auto and that error would appear. MindTheGapps, on the contrary, usually worked. So that could be a possible cause for the issue.
[ONE Android Development] capt.ron:
That's interesting @Tomoms. Do you think m-t-g would require a clean flash along with rom or can I just flash in twrp?
[ONE Android Development] Tomoms:
Unfortunately, switching to another Gapps package requires a clean flash...
[ONE Android Development] Tomoms:
I don't know if you're still using my ROM and/or you have the time to give this a try, but if you're still having this issue (reboot to recovery), it'd be nice if you flashed this zip on top of my latest build, then let the phone reboot to recovery, and then finally pulled a copy of /data/debug.logcat.txt and shared it with me. Thanks!
[ONE Android Development] EotT:
I don't think that's necessary. Remove the gapps.sh file in /system/addon.d (to prevent gapps getting reflashed after a rom flash), dirty flash the rom again (to remove all gapps traces) and you should be good to go. Now you can flash another gapps package.
[ONE Android Development] Tomoms:
Nice suggestion! I hadn't thought of this. If Gapps packages don't write anything to /data - and I believe they don't - this should allow switching packages.

@capt.ron this is for you :)
[ONE Android Development] capt.ron:
Thanks guys! I tried to delete gaaps.sh and got a "read only" error. I'll have to look into this or just clean flash (which I really don't want to do)
[ONE Android Development] sumitinhome:
this error is obvious if you are not rooted. try deleting that from twrp while system is mounted.
[ONE Android Development] boosterjuan:
Hi! is this Rom kernel based on 3.4 or 3.10? I'm interested because would be nice to integrate 3.10 kernel into Ubuntu Touch or SailfishOS. I don't have knowledge in porting, but maybe we can let it know to Ubuntu Touch or SailfishOS mantainers that there is a newer kernel, which in Linux it's very important.
[ONE Android Development] Tomoms:
3.4. There was a port of 3.10 for the OPO, but it was far from perfect. If my days were made of 48 hours I would spend some time to update it and possibly fix it, but unfortunately this is not the case...
[ONE Android Development] bleistik:
I'll try tomorrow.
[ONE Android Development] bleistik:
Here it is.
[ONE Android Development] bleistik:
If I remember correctly, it is MindTheGapps-11.0.0-arm-20210103_125223.zip
[ONE Android Development] Paulroberts:
Do i need to use a specific gapps to restore my apps backup from google, currently the lineageos setup is running?
[ONE Android Development] Tomoms:
Try to wipe /system, reflash my build + my latest MindTheGapps package: https://sourceforge.net/projects/lineageos-for-bacon/files/gapps-11-arm/

I see lots of Gapps-related errors in the log, that's what makes me think it's Gapps' fault.

Feel free to use whatever package you prefer. I, however, would suggest using the latest MinTheGapps package I've built today (link above or in the first post).
[ONE Android Development] Saison2018:
I feel also that new build feels a bit smoother than the previous ones.

My OnePlus One is mostly used as a spare phone and to cast to TV but I was able to get close to one week of battery (most in sleeping mode) as I was able at the beginning of your 18.1 builds. This was not the case with some previous builds, with exactly same applications and usage.

Thanks a lot for your hard work.
[ONE Android Development] bleistik:
Did as you suggested, and it works. I'm awaiting the next OTA update:).

Thanks for your work.
[ONE Android Development] gil80:
Hi.

Is it possible to dirty upgrade form LinageOS 17.1 (your custom rom) to 18.1?
[ONE Android Development] Tomoms:
If you disable decryption (in case you had enabled it in 17.1) and remove any lockscreen protection mechanism (pattern/PIN code/password), it should be possible. Then, once you have upgraded, you can re-enable these things.
[ONE Android Development] gil80:
Do you get performance degradation after a while? With every ROM I try, after a few days, the phone becomes really unresponsive. In addition, I have to go through so many USB cables because there's a problem charging the phone. it keeps getting disconnected.

Edit: Disabled PIN lock. Flashed the new ROM and after about 10 minutes on boot animation, the phone reboots to TWRP.
[ONE Android Development] Tomoms:
Wipe /system, reflash the ROM, flash a compatible Gapps package (look at the first post, there are a few listed there. If you were using OpenGapps on 17.1, go for OpenGapps as well on 18.1).

The charging issue can be worked around by downloading Smartpack Kernel Manager and setting a fixed charging current in the app. No performance degradation here, never had it on any ROM.
[ONE Android Development] gil80:
What is the fixed charging current you recommend?

Is there any other way to flash this ROM without wiping system?
[ONE Android Development] Tomoms:
When you flash any ROM, /system is wiped automatically, except that the addon.d survival scripts are run beforehand, to ensure that Gapps/Magisk don't disappear. We don't want Q Gapps to survive because we want to replace them with R Gapps, that's why I'm telling you to wipe /system before flashing (so that the addon.d scripts, which are stored in /system, are deleted before they are called). So what's the problem with wiping /system?

If you want to charge your phone slowly, without heating up the battery (which helps expanding its life cycle), you can set a low charging current such as 800-900 mA. That's what I use on a daily basis.
[ONE Android Development] gil80:
Trying to avoid setting up everything again and also avoiding reinstalling all the apps and setting them up as well.
[ONE Android Development] Tomoms:
I didn't tell you to wipe /data! I told you to wipe /system. That does not remove your apps & files.
[ONE Android Development] remedya:
There has today been a successful experimental build of bacon 18.1 at Buildkite
[ONE Android Development] gil80:
oh ok.

So, I removed the PIN lock.

I wiped system.

I flashed the rom

rebooted back to recovery mode

flashed the pico gapps from the link in the 1st page

flashed magisk_v22

rebooted

after boot, I can't unlock the phone. It requires pin code. I enter the pin code I always had, and the screen scrolls up, as if it's about to unlock, then it becomes locked again.
[ONE Android Development] Tomoms:
Reboot to TWRP and remove /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key, then retry.

EDIT: with "retry" I meant "reboot and see if it works now", you don't need to reflash everything again.
[ONE Android Development] gil80:
No such files exist.

But now I get boot loops. I can see the post-boot screen and then it reboots again.

Is there an order I need to flash? I start with the rom, then gapps, then magisk v22.
[ONE Android Development] zeinGTG:
try format data , and then only flash the room - format data again - reboot system, wait till u get to the setup screen and go to twrp again, now u can flash gapps and magisk

try it
[ONE Android Development] Tomoms:
I'm afraid you have to wipe /data. New changes introduced in Android 11 break something deep when performing an upgrade, I had thought that one way or another an upgrade would have been possible, but now I guess there's not much we can do about it.
[ONE Android Development] mrhamed:
can you provide direct link to download please? did you work on this build? if yes, do you have long term plant to support us?