yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] jonske:
howdy, i managed to find my old OnePlus One and its still working fine. it's still running LineageOS 14.1 sultan build from ages ago...

is there any install guide to get it updated to this ROM? is it simply just downloading the zip and flashing it in twrp?

edit: just flashed the zip and the mindthegapps zip and all working fine! amazing that this phone still works after all these years lol
[ONE Android Development] Tomoms:
It turns out that setting ro.debuggable=0 out of the box breaks adb in LineageOS recovery, which is useful for me on the other device I build for, so it is extremely likely that I am going to restore ro.debuggable=1 in the future and provide a flashable zip that will set it to 0 for those who need it.
[ONE Android Development] Tomoms:
To those of you who are severely affected by the camera overexposure bug: please try this build and let me know if it is fixed: https://mega.nz/file/F9NXERAJ#e1pX_jqSsYffyvm-S_d95QLLH3hroepo11rYmbyOqN8
[ONE Android Development] kekerosberg:
I just realized that I have had very few or no overexposure problems with the recent builds. Not sure when this has changed.

I used to get them all the time especially with my banking app and Whatsapp web linking and video calls.
[ONE Android Development] Tomoms:
Probably it's just a matter of luck, because I didn't change anything at all in the last few builds, and it is unlikely that something regarding the camera has changed platform-side recently.

Please try the new build I've linked, use it for one full week or so and let me know the results. I'm testing it right now with WhatsApp and some QR scanning apps as well.
[ONE Android Development] therealresonix:
I have recorded it from the reboot until the error occurred

https://gofile.io/d/QmJt3o
[ONE Android Development] steve8x8:
Perhaps I'll never understand why I should use LOS's recovery when there's TWRP for the device.

As long as the setting survives an OTA upgrade, yet another zip certainly isn't a major issue (but easily forgotten for a fresh install).

In the end it's your baby, you decide. ;-)
[ONE Android Development] Tomoms:
The zip by default won't survive OTAs, but I can devise a way for it to do so. I'll have to think about it.

In the post you quoted, I stated that ro.debuggable=0 breaks adb in Lineage recovery on my other phone (Essential PH-1), which hasn't got TWRP at all (until I find the time to develop it myself), so I am forced to use Lineage recovery.
[ONE Android Development] Tomoms:
Thanks, will look into it.
[ONE Android Development] kekerosberg:
Zero overexposure problems so far with the test build.
[ONE Android Development] Tomoms:
Great. No problems for me either. I'll flash the 2022-03-10 build on my 2nd OPO to see if I can reproduce the issue, or if it has magically disappeared recently as you pointed out in one of your previous posts...
[ONE Android Development] therealresonix:
So I have tried several things and none of them work. My device won't connect to the USB and more importantly, it doesn't show up in device manager, lsusb on Linux, or dmesg. Android Debugging on or off doesn't change anything and also changing Device Settings to default to File Transfer did not work too. It is not the cable because it works with other android phones.

Android-SDK is installed and udev rules too.

It would be great if other OPO users confirm or refute the problem.
[ONE Android Development] steve8x8:
@therealresonix Can you connect a mouse to the phone? (You'll need an OTG adapter unless you own one of the few mice with a microUSB connector.)

If that works your USB socket seems to be OK; if it fails that would be a sign of a broken USB connector (unless the OTG is also broken).
[ONE Android Development] Tomoms:
Ah sh*t, here we go again.
[ONE Android Development] steve8x8:
12.0 or 12L? (I suppose there's no thread yet for it?)
[ONE Android Development] Tomoms:
12L. No thread at all, it's in a very early stage, pretty much nothing works yet, it'll take some time before it becomes ready for daily usage.

Plus, it's worth mentioning that I will probably spend a bit less time working on Android development in the next few months. I'll try to keep working somewhat regularly on LineageOS 19.1 for bacon, but I'll be slow. Monthly updates of 18.1 will be released as usual (and April's is going to be juicy!).
[ONE Android Development] ddrddr:
does anyone have any tips or links to how to get viper4android working? also... is it possible now to change the BT settings to a higher quality codec?
[ONE Android Development] pankspoo:
OMG get set ready go
[ONE Android Development] Tomoms:
A new build is available, featuring not only April's security patches, but also some advanced optimizations applied to some critical system components (libgui, surfaceflinger, libbinder, libhwui, libinputflinger).

Enjoy!

Read the second post, it contains a link to a guide to set up V4A.

It should be possible to enable the SBC codec from Developer Settings.
[ONE Android Development] ddrddr:
Thanks. I went through the links last week and labs has been defunct for years now.
[ONE Android Development] kekerosberg:
I lost Magisk during this OTA update. The install script in TWRP was unable to mount /system. Manual install from TWRP also fails with the same error.

Otherwise everything else is fine at first glance. Thanks Tomoms!
[ONE Android Development] Tomoms:
8.76 MB file on MEGA

mega.nz

Taken from their Telegram channel.

Weird, I did not lose Magisk. I'm using v24.1 and not v24.3 (because I always forget to update it) though, maybe there is some glitch in the latest version.
[ONE Android Development] kekerosberg:
Magisk Canary installed fine so I guess it is a bug in Magisk 24.3.
[ONE Android Development] pankspoo:
Can't able to make calls
[ONE Android Development] sumitinhome:
same problem with magisk 24.3. need to manually patch boot img.
[ONE Android Development] Anyoe:
same problem, so i flashed 22.1 in recovery and upgraded to 24.3 in magisk app.
[ONE Android Development] ddrddr:
V4A works with the new file OP posted. Thanks!

on the other hand, all BT codes are still greyed out .... if anyone has any ideas on how to enable them please let us know.
[ONE Android Development] Tomoms:
I'm not sure about this (I've never owned any BT headphones), but it might be that as soon as you actually pair your headphones to the device, the supported codecs become selectable.
[ONE Android Development] Tomoms:
Dear users,

the first builds of LineageOS 19 are being officially released in these hours.

As you can read in the team's announcement, due to one heavy architectural change Google has introduced in Android 12 (i.e. replacing iptables with eBPF for packet filtering), official support is dropped for all devices shipping with a Linux kernel version <= 3.18. Thus, bacon will sadly never see official support on any LineageOS version newer than 18.1.

It is possible, but unlikely, that someone in the future will find a way to get eBPF to work on old and very old kernels, such as our Linux 3.4.

It is also possible that with some hacks that intentionally break packet filtering (i.e. some network-based features, such as isolation, firewalls, and restrictions, will not work), an otherwise-functional build of LineageOS 19 can be created. It seems to me that there is one for the Galaxy S5, but I have to take a deeper look into it.

For the moment, thus, given that I will be quite busy until the end of summer, my development activity for bacon will be restricted to keeping alive my 18.1 ROM: monthly updates with the security patches will be released as usual.

In the end, we have got an awesome Android 11 experience on a 2014 device, which is not bad at all - and not something we should take for granted!

I am as curious as you are about discovering what the future of our OPOs will be like, but right now the only thing to do is to wait.

See you around, cheers!
[ONE Android Development] kekerosberg:
This ROM continues to be awesome for a daily driver bacon. Many thanks for your work, Tomoms.

I'm really hoping that some day the manufacturers would do an open source release of the firmware and binary blobs. Seriously, what would be the harm in that for an 8 year old device?
[ONE Android Development] steve8x8:
@kekerosberg IIRC there had been a successful break-in at their site so someone may have already "saved" the old source trees? ;-)
[ONE Android Development] Tomoms:
This would require a coordinated effort and agreement from the OEM (Oneplus, in our case), Qualcomm (who releases most of the firmware & blobs), Sony (for the camera stuff), and N other companies (the manufacturer of the NFC chip, for example).

The harm is that this effort does not bring more money into their pockets, I guess.
[ONE Android Development] ilmich:
technically speaking we are lucky, because the soc (snapdragon 801 / msm8974) is supported in the new android kernels.

The problem may exist with some devices (such as camera, baseband, vibrator etc etc) that should eventually be readjusted.

It's not a mission impossible, also because the kernel sources exist, so anyone can try to do it (with the right skills)

But surely it should be understood if it's worth it.

I say this because sooner or later the device should still be repartitioned. An updated kernel, if it works, may never be accepted by lineageos etc etc

however, it is sad news for our opos :(
[ONE Android Development] ImmortAlex:
IMHO, it will be more than enough for OPO to stay with 18.1 until LineageOS team merge security updates for Android 11. It give us three (?) year of more or less secure life and then... I think most of OPOs will be dead at that time.
[ONE Android Development] BIGFAAT:
Hi @Tomoms and first thank you for the great work. I have a small request: any chance that you can get a look over 802.11r/k? This feature has been broken for ages on this phone and is the only device i have refusing to work/connect within my networks beside the chipset/driver/kernel being compatible for it. Not even "legacy mode" (phone ignoring the whole FT stuff) while 802.11r is enable on the router is working. Greetings!
[ONE Android Development] Tomoms:
Yes, I can look at it. "phone ignoring the whole FT stuff": what does this mean? It's the first time I hear of 802.11r/k.

Do you know of any other msm8974 device on which this feature works? On bacon, does it work on stock CyanogenOS?
[ONE Android Development] BIGFAAT:
It means that normaly, if not supported for a reason or another, the phone should simply work like any legacy device (basicaly connecting only with wpa2-psk, ignoring the /FT extension). And yes, if im not wrong the samsung s5 have the same snapdragon and have the capability. I never used the phone on stock rom, but google seems to show people with the same trouble running on stock using 802.11r/k.
[ONE Android Development] Tomoms:
Hello, I've uploaded a new build with May's security patches + an updated SQLite database engine :)
[ONE Android Development] steve8x8:
@Tomoms I'm impressed by how (not) long it took you to get this built and tested ;)
[ONE Android Development] Tomoms:
The LineageOS dev who takes care of merging security patches on the 18.1 branch pushed May's very quickly. After this is done, it only takes me ~1 hour to merge them, build and try the new build :)
[ONE Android Development] Cipcino81:
Hello guys,

I need your help: I have a big problem on Android auto, with both official lineage 18.1 and tom's version.

I am from Italy

Android auto works ok except one app : phone app. All other apps works. The phone app screen do not displays and I can't make phone calls or view my contacts. The only screen displayed is black with a white text that tells me that phone permission need to be set, but that permission is already set by default on Android auto app. I have attached the screen.I can only call by voice command, that works and the phone calls are ok, but I have no visual interface, and I am also unable to close the phone call since I have nothing on screen. In the past this happened to me. The solution was to erase cache and data on Android auto app, but now it did not work. I have tried to erase Google play services cache and data too but to no avail. I have a OnePlus one phone with lineage 18.1 (android 11) and my car device is a Pioneer AVH-Z9200 DAB. Android auto version is 7.4.620993-release.

The problem occurs both connected wired and wireless.

Pacchetti:

Google: 13.16.8.23.arm

WhatsApp: 2.22.8.3

Maps: 11.27.2

Deezer: 7.0.2.75

Android Auto: 7.4.620993-release

Google Play Store: 30.3.21-21 [0] [PR] 445437866

Waze: 4.82.5.1

Google Play Services: 22.15.14 (150308-441847897)

Google Play Libri: 5.22.1_RC04.444360368

VLC: 3.4.4

Autorizzazioni:

phone: on

contacts: on

location: on

sms: on

microphone: on

calendar: off

call_log: on

What can I do to make it work ?
[ONE Android Development] Tomoms:
Which Gapps package did you install? MindTheGapps (as recommended) or OpenGapps?

Please grab a logcat after you see that screen on the car's device. If you can only grab a log using adb from a computer, you can easily grab it even a few hours after reproducing the issue, but in this case take note of the exact hour you reproduced it, as it will help me to find the relevant part of the log.

If we manage to identify which permission is missing and what package is requesting it, we should be able to grant it with a simple adb command.

EDIT: in case anything is unclear, feel free to PM me. As you might have noticed, I am Italian as well.
[ONE Android Development] Tomoms:
Sorry for leaving you without a reply for so long. Can you grab a kernel log (dmesg) after trying to connect to your network? Everything in the kernel & WiFi driver configuration seems to be configured correctly, I cannot understand why it is not working...
[ONE Android Development] BIGFAAT:
No problem, i will later on :)
[ONE Android Development] Tomoms:
What hardware are you using, by the way? Cisco access points?
[ONE Android Development] BIGFAAT:
Diverse Mediathek and Ath10k APs running OpenWrt.
[ONE Android Development] Tomoms:
Ok, send me the logs when you can. I'll do my best to better understand what is going on. BTW, are you rooted? It would be nice if you were, as I could ask you to make some modifications to system files on-the-fly without having to go through the recovery and flash zips.
[ONE Android Development] BIGFAAT:
I will come back to you once i have some time for this :D
[ONE Android Development] BIGFAAT:
@Tomoms Here are a bunch of logs (debug) made with matlog: https://cloud.ofsg.eu/s/G6d569xg53ZW9rJ And Phone is now rooted in the case we want to try stuff out.

PS: Absolut nothing is appearing in the router logs (debug) in matter of the opo.
[ONE Android Development] Tomoms:
Can you grab a kernel log (dmesg) too, please?
[ONE Android Development] BIGFAAT:
My bad, just uploaded the kernel log in my cloud.
[ONE Android Development] BIGFAAT:
So i was playing around with 802.11r/v on my OpenWRT devices, because since yesterday we got an ipad that refuses to work too. Beside the "apple" recommended settings, once wpa3-sae is used as an option together with wpa2/FT and classic wpa2, the ipad and the opo refuse to connect.

So certain devices are broken once you invoke wpa3 together with the whole fast transition stuff, even if they - like the opo - are not wpa3 capable.

Why the ipad is derping around, beeing a modern device... *facepalm*

Edit: just in case, i opened a thread in the OpenWRT forum and will probably contribute later on an issue on their github, once more informations are available.
[ONE Android Development] Tomoms:
Hello guys. I have accidentally nuked all the git history of my whole LineageOS 18.1 build tree... I have to sync everything back again and compare folder by folder, to detect uncommited/unpushed changes. If June's build is released a little later than usual, you know the reason... It's really a hassle but I've got no other option than to do it.

Thanks, I will look into the issue ASAP (might take a few days). I'll keep you informed.
[ONE Android Development] BIGFAAT:
Thank you and take your time, we all have enough stress in our day to day job. For now i have a workaround spliting each ssid in wpa2/FT and wpa3/FT.
[ONE Android Development] Tomoms:
Sorry for not getting back to you. I have found something interesting that is worth trying. You'll hear from me in a couple of days at most.
[ONE Android Development] Abhi_T:
@Tomoms : Is there any chance of OnePlus One device receiving the Lineage 19.1 Unofficial build from you? Many would be looking forward to it. Appreciate your efforts.
[ONE Android Development] Tomoms:
Remount system in read-write mode:

su
mount -o remount,rw -t auto /

Edit this file: /vendor/firmware/wlan/prima/WCNSS_qcom_cfg.ini either using vi in an adb shell, or by pulling it on your computer, editing it and pushing the new version back, or directly on your phone... The way you want.

Modifications to be performed:

At line 37: change gRoamingTime=0 from 0 to 10 (yes, 10, even though the comment seems to suggest only to use 1 or 0 as values)

At line 150: change CcxEnabled=0 from 0 to 1

You seem like an advanced user who knows what he's doing, but I'm going to explicitly recommend you to be careful not to add spaces before/after the '=' sign :)

Reboot after performing these edits and let me know.

You should read this: https://xdaforums.com/t/rom-r-bacon...-lineageos-18-1-may-6th.3693223/post-86800763
[ONE Android Development] BIGFAAT:
I will try it in a few days since im actually forced to use my bacon as a security camera. Residual light amplifier works quite well on the old cam.
[ONE Android Development] Tomoms:
No problem, keep me updated :)
[ONE Android Development] Tomoms:
Hey people, I have started the boring job of restoring my LineageOS 18.1 source tree, after the mess I made. It'll take a few more days for me to finish, but anyway, the Lineage team is having issues merging June's patches for Lineage 19, so I guess they won't start working on implementing them in 18.1 before they get 19 sorted out. So there are actually two reasons why June's build is delayed :)
[ONE Android Development] sumitinhome:
i have just one request tom. Can you add one handed mode to this rom???
[ONE Android Development] Tomoms:
Point me to an Android 11 custom ROM (not necessarily available for bacon) that has got it, and I can try to implement it.
[ONE Android Development] sumitinhome:
This is kinda sad, i searched a lot but couldn't find a custom rom on 11 with one handed mode. I guess this explains why we don't have it in this rom. :(
[ONE Android Development] kekerosberg:
I recall that LineageOS had one handed mode in previous releases. I don't know when or why it was dropped.
[ONE Android Development] sumitinhome:
yeah as far as i know i have seen one handed mode till pie release.. don't know after that.
[ONE Android Development] Tomoms:
After a long wait, here it is! June's build, with the latest security patches. This build also features a new design for Toast messages, more material-like and similar to how they look on Android 12 :)
[ONE Android Development] Pap0ose:
Many thanks
[ONE Android Development] Abhi_T:
@Tomoms I am yet to try it. Downloading it right now. But yes thanks in advance and as always appreciate your efforts.
[ONE Android Development] indhimaga:
updated to the latest version today [18.1] but i lost the root capability...

And from TWRP it shows

"! Cannot mount /system

Unmounting partitions

Rooting again with v24.3 still the same... downgrade to v22 its success within TWRP but nothing after reboot, still no root...
[ONE Android Development] Tomoms:
v24.3 doesn't work well with OPOs, I agree. I have faced the same error. Just use the latest v25.0. It works fine here.
[ONE Android Development] Tomoms:
I haven't heard from you ever since, did you have the chance to try my modifications?
[ONE Android Development] BIGFAAT:
Sadly not. The phone is still in use as a security camera.
[ONE Android Development] Tomoms:
Hello! I'd like you to flash this kernel on your OPOs: https://mega.nz/file/4tkTCKII#jOwO5rbVuKJ4fLYNd18c_XStt5k2805fH-R3st40rVo

This is not experimental nor unstable, it works just as good as the kernel that is built into the latest build. There is just one change I will explain in detail later, not to influence your perceptions.

Please use it for a couple of days and then report back whether the phone seems to perform slightly worse, slightly better or just like before.
[ONE Android Development] tpuserhp:
To me, it seems internet speed is faster.
[ONE Android Development] kekerosberg:
I'm sorry I can't give an unbiased answer. I could not mount data in TWRP so I ended up doing a complete wipe and clean install. Feels faster but the clean install also plays a role in that.
[ONE Android Development] Tomoms:
Don't worry, I am sorry you had to clean flash... Maybe a fsck would have been sufficient...

BTW, I've fixed a couple of SELinux policy issues and merged the fix into the official device tree. Very small issues for sure, but it's nice that we have gotten rid of them :) The fixes will be implemented in July's build of mine.
[ONE Android Development] brwntree:
hi - newb here. Had a many dirty flash of lineage on my opo from 16 but recently had wifi disconnect issues & thought it was time for a clean flash of 18.1 with a data/apps migrate. This worked well but other app issues cropped up but b4 a real clean reflash ifound ur build (thx!) and so dirty flashed this over the orig 18.1 and reflash magisk. All turned out great but for app issue & then noticed wifi wont connect at all (failed to conn to network) to my reg hotspot in the car. So decided to reflash super clean ur build + mindgapps + magisk. This cleared up app issue but wifi still wont conn to hotspot. Just wondering if anyone had any ideas to try b4 restoring back to orig 18.1 - would flash this new kernel be worth a try as well? tia
[ONE Android Development] Tomoms:
Do not flash that kernel, it won't have any effect. Try to get a logcat after trying to connect to the hotspot in the car. Keep note of the time (hours and minutes) at which you reproduced the issue, it'll make it easier for me to find the relevant messages in the log. It's very strange that it worked on official 18.1 but it does not on mine...
[ONE Android Development] brwntree:
Hey thanks. Yea, alas I did already flash the kernel & indeed it made no diff. Also not sure how to undo it now lol but it did flash OK & seems stable so far so ican catch up on that later. Also I discovered my older car hotspot device actually works OK. Both devices run the same 15.5 os just the newer one has this issue. I grabbed two logcats - failure on newer & success on older device to help compare. Is it OK to attach those files directly here? TY
[ONE Android Development] Tomoms:
Yes, it is ok. But the newer kernel kills all debugging logs generated by the kernel (this could lead to less debugging overhead, thus less wasted CPU cycles <- for anybody reading this, this is the only change present in that kernel, and it is why I was asking if there was a noticeable performance improvement or not), thus your logcats contain no kernel-related debugging, which could or could not be an obstacle in the debugging process of this issue. Show me these logs, then I'll tell you whether they are good or not. In the latter case, you'll have to reflash the ROM (to get rid of my newer kernel and replace it with the standard one, which has got debugging enabled) and grab the logs again.
[ONE Android Development] brwntree:
I was abit overzealous & it even hindered! I will attach what I got - 1) starts at 14:03:30 and is the broken log & 2) starts at 15:13:30 and is the working log. No prob if I have to reflash ROM & log again. ty