yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] to.xda:
thank you for keeping this device alive...

great work!

I've been using this ROM since early release,

using live display - night mode,

the display is broken at times,

restart doesn't work,

a simple shutdown will fix the issue..

on Sept 10th build,

wifi work okay on normal network..

but won't auto reconnect on hidden network,

it was working on Aug 23rd build..

at the moment,

i just forget the network and manually connect again each time to connect to hidden network..

i found this when looking for solution,

https://xdaforums.com/t/rom-flo-deb-unofficial-lineageos-18-1-2021-09-10.3569067/post-81513309

but it seemed for ten and device specific,

could there be other work around?
[ONE Android Development] jimmy2027:
I did a dirty flash Sep 10th from Aug 23rd build and it looks like I got stuck in the logo. It looks like a clean flash is needed.
[ONE Android Development] Saison2018:
Installed and reboot without problem until now

Your experimental kernel was installed before updating to latest, no trouble for this also.

Thanks
[ONE Android Development] Tomoms:
Well, it is strange that it worked in August and it doesn't now... Anyway, the link you posted is quite interesting, it looks like on those devices a couple of patches in the kernel have fixed the issue, I will check if they are already implemented in bacon's kernel, if not, I will add them.

EDIT: please try this kernel and let me know if it fixes the issue: https://mega.nz/file/900h3Y4C#fexSDeRf2aGR3HYqUuddEmNBQOorM6_s6BO1F1UVZ_I

Nope, there's something weird going on on your side. Check the hash of the file to make sure it is not corrupted and retry.
[ONE Android Development] to.xda:
I've tested the kernel attached,

it does fix the issue..

wifi can normally auto-reconnect to hidden network now,

it's even smoother than Aug build,

I sometimes need to push power button and/or wait a moment before it is reconnected on Aug build,

and it seems like the hidden network is visible too once connected,

It seemed like wifi setting back then, 9/8/7, can't recall..

Thank you for the fix,

it is very helpful..
[ONE Android Development] to.xda:
i happened to need to use wifi hotspot today,

and when i tried it,

client is connected but no internet connection..

after a bit fiddling nothing seemed to work,

and then i found this,

Hotspot not working after Android 11 update. Pixel 3XL. - Google Pixel Community

I'm not sure whether toggling bluetooth on off or the rebooting that fix the issue,

but it's working now..

hope this helps..
[ONE Android Development] Tomoms:
Great, I've merged the fix into the official LineageOS kernel so that users of the official nightlies will benefit from it as well! Thank you for pointing it out, this issue was reported to me several times over the years, and finally we managed to address it :)

Well, strange, I use hotspot quite often and I've never faced any issue. Glad it's working now, anyway.
[ONE Android Development] Deimos666:
I have some question about the camera. The phone is showing the photo in the gallery, but if I transfer the image on the PC they give the "Quantization table 0x00 wa not defined" (IrFanView message).

Also when I try to share the photo on whatsapp or make a photo in whatsapp the photo appear a black screen (after the photo is done).

The phone is just freshly installed and I've rooted it.

Attached the image I've made on the phone.
[ONE Android Development] kekerosberg:
I have a related problem. I am not able to share an image from the gallery to Signal, but when I add the same image from inside the Signal app as a file, it works fine.

Images are not displayed correctly when plugging the phone to a Windows PC. I am however able to copy the images to the PC and they work fine from the PC after that. Very odd.
[ONE Android Development] tofu:
I have three issues, two of which have been already mentioned. All these things worked in previous lineage version (17). Microg Lineage OS has same issues, so this seems to be related to Lineage OS, and not to your kernel or other custom modifications that you might have done. But maybe you know how to fix these?

1. While on video calls, the selfie / front camera is constantly overexposed and pretty much useless. It doesn't matter which app is used (whatsapp, Jitsi, Element etc. etc.).

2. I cannot share images from gallery to other apps IF I start the sharing from gallery. However, I start the sharing process from within the destination app, the sharing works.

-----

this one has not been mentioned:

3. Several dictionaries are missing from AOSP keyboard. Previously Lineage OS had all the dictionaries available that you could think of, now only 7.

Especially Finnish and Swedish are missing.

Only way to get around this, is to push Lineage 17 LatinIME.apk to /system/product/app/LatinIME and replace the current one.

Could you add the missing dictionaries? Or replace the current AOSP dictionary with the previous one?

(And no, I won't install google keyboard, since I don't use GAPPS)

Thank you for your help already in advance!
[ONE Android Development] Tomoms:
Sorry for not replying, I hadn't noticed your posts. Will read them later and let you know :)
[ONE Android Development] Tomoms:
Unfortunately I cannot reproduce the issue using Telegram. Will try Signal tomorrow.

1. Known bug, I have no idea how to fix it. As a workaround, switch between the front and the back camera or open and close the app you're using until it finally works fine.

2. Read my answer to the other user above.

3. This is due to the fact that in August 2020 a change introduced in bacon's LineageOS device tree has excluded lots of dictionaries from the LatinIME apk in order to save /system space for Gapps. In fact, if you try to replace the LatinIME apk with the one from any 17.1 build newer than August 8th, 2020, you still shouldn't see any additional dictionary.
[ONE Android Development] Tomoms:
New build available, also via OTA, with October's security patches.
[ONE Android Development] chosin137:
Any build after August 23rd is still disabling the ability to connect to wifi although you can see the access point. I tried both Sept and Oct builds on fresh installs without Gapps or other addons as well as multiple access points. Anyone else having issues? Update to include clean flash of Oct 7th Official Lineage seems to work without Gapps or any addons. Puzzling and so random. I like your build more!
[ONE Android Development] EotT:
I'm also experiencing this issue. I also have regulary wifi disconnection, while the connection is of an execelent quality, and I can't reconnect again.

Another issue: since the Septmber update, I'm unable to use LiveDisplay. Pressing the LiveDisplay icon in the quicksettings doesn't do anything. When trying to open the settings of LiveDisplay in the settings makes it crash, with the following error:

A clean flash doesn't fix the issue.
[ONE Android Development] kekerosberg:
I somehow lost Magisk root on this latest OTA update. Magisk installed fine manually via TWRP though.

WIFI, LiveDisplay and everything else is working fine.
[ONE Android Development] Tomoms:
About the WiFi issue: in the last 1-2 months I have applied a couple of patches to our WiFi driver that are not present in Lineage's kernel. Maybe they are causing issues for you two. I'll send you a new kernel to test tomorrow, it would be crucial that you test it thoroughly because you guys are the only ones facing this issue.

About the LiveDisplay crash: maybe something glitched for some weird reason? Try to re-download the build again and re-flash it.

It survived normally for me. I don't know how OTA updates are flashed (never ever tried updating my builds via OTA xD ), but I guess you can see the recovery log with the ouput printed while flashing the zip. Didn't you see the usual Magisk-related lines after the build was flashed?
[ONE Android Development] ImmortAlex:
Magisk not survived for me too. There's nothing in the TWRP's log about Magisk at all, it's addon.d script just not invoked, I think.

It began some time ago, but I didn't remember when. I have no problem just to install it from TWRP at the same time as I install your ROM.

BTW, I'm using good old TWRP 3.3.1-K1.
[ONE Android Development] kekerosberg:
I did not pay too close attention to the flashing process.

I did see a glimpse of an error to mount /data while flashing but I guess this does not help much. I will save the logs on the next OTA update.

This was on the latest TWRP 3.5.2.

edit: also latest Magisk 23.0
[ONE Android Development] Tomoms:
Some time ago (Magisk v22 or v21) Magisk's addon.d was buggy and was never called after updating LineageOS on old arm phones. This was however fixed in Magisk v23, after this release Magisk has always survived for me.
[ONE Android Development] ImmortAlex:
I'm using Magisk v23. See that TWRP version is not the reason too.

Also, OpenGapps addon.d is working.
[ONE Android Development] Tomoms:
Please try this kernel: https://mega.nz/file/QgUWmZaB#_th2QV6LLZZkDdH58Pdm8-LvcStM9IRoj7uPM0BCYQA
[ONE Android Development] Tomoms:
Is Magisk's addon.d script there?
[ONE Android Development] ImmortAlex:
Yes, there's 50-lineage.sh, 70-gapps.sh and 99-magisk.sh files.
[ONE Android Development] sumitinhome:
Well, magisk survived for me when updating through OTA. been on TWRP 3.5.2 and magisk v23
[ONE Android Development] EotT:
I already tried that, it didn't solve the issue.

Thanks, I'm going to try it. I'll report back later.
[ONE Android Development] EotT:
Sadly, it didn't fix the problem for me, still the same issues.
[ONE Android Development] Tomoms:
I'll provide you with new testing material over the next few days.
[ONE Android Development] Tomoms:
File on MEGA

mega.nz

Try this one please.
[ONE Android Development] EotT:
This one almost completely fixes the issues, I had only 1 wifi disconnection yesterday, but maybe that was caused by something else. Today, everything went smooth. Many thanks for the quick fix!
[ONE Android Development] Tomoms:
This is very good news. The issue was caused by some code styling fixes which were supposed to fix misleading indentation (or other ambiguities in code logic) detected by the compiler, but it seems that some of these fixes changed the (correct) logic inferred by the compiler with a faulty logic that was not ambiguous but made the WiFi chip misbehave.

Keep using this kernel, I'll integrate the fix in the next build.
[ONE Android Development] EotT:
@Tomoms I'm having the exact same issues again. I reflashed your modified test kernel, just to be sure, but no difference.

One thing i've noticed with the new kernel (in the beginning, when it was working fine): there were wifi drops, but normally, wifi was reconnected almost instantly. But now, when the wifi disconnects, I'm unable to reconnect again, for at least 20 seconds, up to a minute. Many times when I switch my screen on, wifi isn't connected, and I'm unable to connect.

Edit: It looks to be happening more often when I'm close to a wifi access point. Not sure if that has anything to do with it.
[ONE Android Development] EotT:
Today, wifi was working fine again. I don't know why it is working correctly only part of the time. Other people using the same wifi are not experiencing my issued.
[ONE Android Development] kekerosberg:
Does your WIFI AP have both 2.4 and 5 GHz bands? Could it be using the 5 Ghz band when closer?
[ONE Android Development] EotT:
Only 2.4 is active.
[ONE Android Development] Tomoms:
Give me a few days and I'll send you another kernel to test.
[ONE Android Development] Aslolo:
Hey man, thanks for your awesome ROM, been using it for over a year i believe.

I have an issue that im not sure how to fix, you are probably the best guy to approach for that.

Im trying to access the A11 Bluetooth stack, which should be in /system/bt or /platform/system/bt (different sources say different things) but I cant find the folder in either of the paths, even when checking via adb and recovery (to circumvent the stupid root restrictions of A11). Do you by any chance know where to find said Bluetooth stack?
[ONE Android Development] Tomoms:
Those directories refer to the position of the source files in the Android source tree, not in the compiled ROM! Take a look here. What, exactly, are you looking for?
[ONE Android Development] Aslolo:
Oh, thank you for the clarification, that makes so much more sense!

I've just swapped to a bluetooth headset, instead of a wired one, which supports the sbc and aac codecs, which are also both supported on the OPO/this ROM. Since I didnt know which one is better, I looked at a few guides and explanations, and long story short, I cant really hear much of a difference, so I wanted to check myself how SBC is implemented, since its settings make a huge difference, and it seems to be the better choice for Android. Also there is a non zero chance that using SBC improves batterylife while listening to music, since it requires less computation.

Edit: https://appuals.com/how-to-modify-b...for-greatly-enhanced-bluetooth-audio-quality/

This is what im looking at for SBC mods.
[ONE Android Development] Aslolo:
It seems like at least the bitrate is indeed increased from stock, so I dont think that increasing it by 20 bits/s would yield any measurable result.

Edit: Atleast for 44khz it should still be able to be increased a bit it seems.

#define A2DP_SBC_DEFAULT_BITRATE 454 -> 512

but again, I dont know it that does anything measurable.
[ONE Android Development] Tomoms:
@EotT I still haven't sent you anything because I'm quite out of ideas on what to try next. How feasible is a clean flash for you?
[ONE Android Development] Tomoms:
I have zero experience with Bluetooth audio. What codec are your music files encoded in?
[ONE Android Development] EotT:
I already tried a clean flash, but it didn't solve the issue. I reverted to a nandroid backup now.

The strange thing is, it never (or almost never) happens when I'm outside the room where the wifi accesspoint is located. If I'm in the room, it can happen every few minutes. Very strange.

I appreciate all the time you spend investigating the problem. If you can't find a solution, then that's ok. It's anoying, but it's still useable. Maybe it will be solved when I switch to an Android 12 based rom (if such a rom will be made available for the oneplus one). Nevertheless, I'm quite happy with your rom, despite the wifi issues.
[ONE Android Development] Tomoms:
What I would have suggested is a clean flash of the official nightlies, instead of my ROM, to check whether the issue is present there as well. If you have the time and the will of doing it, let me know what you find out.

The behaviour you described is indeed very strange...
[ONE Android Development] EotT:
Ok, I'll try that. I'll keep you posted. It can take a few days to find some time to do it.
[ONE Android Development] Haripesch:
I've got a similar wifi connection issues since the september update. The test kernel didn't resolved the problem.
[ONE Android Development] Aslolo:
MP3 mostly, but that doesnt matter since they have to be reencoded anyway, even when using AAC as the file and as the bt codec, it still reencodes for transmission.
[ONE Android Development] Tomoms:
Try a clean flash of the official nightly if you can, I need to know if the issue is present there as well.

Actually, it does matter, as far as I know. An MP3 file has a bitrate of 320 kbps (at best), so you will not notice any difference when you re-encode it using SBC compared to Android's standard bluetooth codec. You could even use a BT codec that supports 2000 kbps, but if the audio stream contains 320 kb of information per second, the rest of the supported bitrate is basically wasted - it cannot provide any added value.

SBC and AptX codecs become useful when you are playing high quality music (e.g. flac files). A standard flac file ripped from a standard 16 bit, 44.1 kHz audio CD has got a bitrate that reaches 1411 kbps, so in this case maximizing the bitrate of the bluetooth codec used for re-encoding is a good idea, as it means minimizing the information that is lost.

This makes sense to me, and explains why you don't notice any difference. However, I am no big expert in the field of digital audio, so if you know this stuff better than I do, don't hesitate to correct me!
[ONE Android Development] Aslolo:
This is true, but you have to remember that the OPO only supports AAC and SBC (and aptx isnt necessarily better than SBC. Im playing mostly 320kbit/s MP3 so its capped for AAC, but SBC has potential for up to 512kbit/s. When AAC misses some packets or drops bandwidth it just cuts out, while SBC takes bandwidth out of the upper tones to keep the connection stable. This essentially means, the more bandwidth we have, the more we can lose before quality drops. But all that is a very technical analysis for a completely different topic, since im mostly comparing both codecs for battery usage, because of the fact that in my usecase the max bandwidth should basicly always be a given :D
[ONE Android Development] Haripesch:
Wifi works fine for me with the latest official nightly.
[ONE Android Development] Tomoms:
Please keep using it for a few days if you can, to confirm the issue is gone (@EotT initially thought the issue was gone with my test kernel, but the problem appeared again after a couple of days).

In the meanwhile, @EotT please try this new kernel: https://mega.nz/file/QtkEzKSL#HtMZ6g4Txq6WTmlRkrx6Zew7nSbQUV_aIVjVrh5P89I
[ONE Android Development] Tomoms:
A new build is available!

It brings November's security patches and a fix for an issue that caused stuttering playback of HD videos in some apps.

EDIT: @EotT any news?
[ONE Android Development] MaestroCharan:
Jan 16 build

Clean flash

Snap cam and others camera apps crashing on HDR image capture!

Is this normal?

I just came from Ideophracy rom so I'm not much aware of how things going here.

Please confirm if anyone else with same issue.

Thank you all for your support. :highfive:
[ONE Android Development] secretkloud:
[MENTION=5727088]Tomoms[/MENTION]

I also noticed something. Not sure how long ago it's been happening (probably the last couple of builds), but MX Player only uses SW decoder. HW and HW plus are no longer available. I honestly don't know if it's the ROM or an MX Player update that did this. Could you maybe take a look?

Thanks a lot...
[ONE Android Development] geokilla:
Do you have the custom codec installed?
[ONE Android Development] secretkloud:
Initially, no. Then I installed it and it made no difference. All playback still used SW decoder and drained battery....
[ONE Android Development] F3AR:
Yeah the latest build is much smoother than the previous ones. At least is considerably lower than last builds. Im positive about the future builds. Thanks to the Dev.
[ONE Android Development] secretkloud:
[MENTION=5727088]Tomoms[/MENTION]

Again, thanks for your ROM. It's just right as for my daily driver.

I think the video playback issue I reported earlier is ROM or kernel related. I installed another video player and still couldn't get HW codec to work. I might try another kernel, buthaving to reflash every isn't something I'm up for right now.

Can anyone confirm this issue?
[ONE Android Development] Tomoms:
Do you face problems when streaming with the Less frequent notification sound feature disabled? I keep it disabled because I don't need it and listen to music every day, without any issue.

It's a known bug, I remember photos being saved despite the crash. Read the first pages of this thread, we discussed about this issue, if I recall correctly.

VLC plays 1080p videos (recorded with the OPO) with forced, full HW acceleration without issues on my phone. I'll try MX Player right now.

EDIT: I have installed MX Player and the MX Player ARMv7 NEON codec pack. The "HW+" decoder plays my 1080p@60fps and @30fps videos just fine.

Nice to know! Thanks for leaving your feedback :)
[ONE Android Development] secretkloud:
Sigh....

Means something else is wrong somewhere. I'll take a deeper look.

Thanks for the response..
[ONE Android Development] Tomoms:
A new build is available. Just some minor updates to the OS, including the latest monthly security patch from Google. Enjoy!
[ONE Android Development] geokilla:
Dirty flashed the January 21st build and using it for an hour so far, this is what I have experienced:

Notification sounds do not work in all apps, regardless of whether "Less Frequent Notification Sound" is enabled or disabled

Music.apk can play MP3 files for the time being, as does RTHK radio streaming

Do you need a logcat? Not sure if it will help.
[ONE Android Development] Tomoms:
Is there a specific set of apps whose notifications don't trigger any sound (e.g. WhatsApp messages never ring, but Telegram's always ring) or is it kind of random? A logcat, taken in a timespan during which a "silent" notification arrives, might be useful indeed.
[ONE Android Development] geokilla:
Been 2 hours now... MP3 music playing doesn't work anymore. None of my notifications are working either. Not for text messaging, nothing.

What kind of logcat app do you want? Any specific way you want the logcat?
[ONE Android Development] alma23:
Lockscreen Blur not working on clean flashed 20180121 build.
[ONE Android Development] Tomoms:
It's working for me (after a dirty flash). I don't really know how to help you, try a dirty re-flash.
[ONE Android Development] alma23:
Tried dirty re-flashing already with no luck, I'll wait and try dirty flashing next build, I can definitely live without lockscreen blur lol

Thanks for your answer and for your amazing work!
[ONE Android Development] geokilla:
[MENTION=5727088]Tomoms[/MENTION] Yeah it's not working, even after dirty flashing again. I'm going to have to flash back to the previous ROM ASAP. Do you still want a logcat of me trying to get the MP3 music trying to play, and of the notification sounds? If so, how should I get them?
[ONE Android Development] Tomoms:
Before flashing an older ROM, try flashing an older kernel, such as Neon v16, and see if the issues are gone.
[ONE Android Development] geokilla:
You may be on to something. Everything seems to work as it should again!

Edit: After using it for the rest of the day and getting back from the gym, it seems like I spoke too soon. MP3 music playing didn't work half the time. Here's the scenario:

Less Notification Sound was enabled

Play MP3 music via Music app

Get notification sound, either from WhatsApp, text messages, or my rest was over and time for my next set

Music cuts out and it refuses to play again half the time

Rinse and repeat half the time till it magically decided to work for the rest of my workout

This is very frustrating. Should I flash back to January 8 build [MENTION=5727088]Tomoms[/MENTION]?

Turns out Instagram videos don't play properly either. Still on January 21st build with Neon v16.
[ONE Android Development] tariqaziz348:
Great work:good:

It will be very appreciated if u fix the HDR Bug.
[ONE Android Development] Bladehawkz:
Not specifically sure if it's this build, but my video capture is busted for both the camera app and snapchat. I'll reflash along with some previous versions and see if it's fixed.
[ONE Android Development] Aslolo:
I noticed that Bluetooth Dual Channel turns off after every disconnect, is it possible to enable it permanently?