yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] AAB4K:
Yes, I did try to check logs but didn't find anything thay can tell the issue. Will post logs here soon, when I start my system. I think it can be Activity Manager not working or something.
[ONE Android Development] Tomoms:
Another user of my ROM + Gapps has the same problem you described. Waiting for logs from both of you :)
[ONE Android Development] AAB4K:
Logcat is attached. Hope you can find it helpful.
[ONE Android Development] ImmortAlex:
Data encryption is not working. My conditions:

- absolutely clean flash, with formatting of /system, /data and /cache

- f2fs for /data and /cache

- latest build of lineageos and kernel from this thread, latest opengapps installed at the same time

- SUW is completed, 4x4 pattern is setted, battery is fully charged, then I go to data encryption setup in Settings

- it shows data encryption logo, reboot and then start to reboot endlessly.

Each time it show bootanimation for 4-6 lineageos's "boobles" before reboot.

Official lineageos build work fine in same conditions. I even install magisk from the beginning.

(Official lineageos has another issue: sometimes it show bootanimation forever, and can complete boot only after few hard reboots, but it is another sad story)
[ONE Android Development] Tomoms:
A similar issue has been reported to me by PM but I still haven't gotten any log. If you could help me by providing some logs, it'd be great.

Please set up encryption like you described, then, when you see LineageOS's bootanimation and you feel the phone is about to reboot again, hold the Volume Down button, so that the phone crashes as usual, but it reboots to recovery. Then grab a copy of /proc/last_kmsg and upload it here.

Thanks!
[ONE Android Development] KuldeepShivankar:
Need help

Hi, i've flashed this ROM and it's working fine only one issue is frustrating me my charging cycle stops at random number .. like it'll stuck at 75 and it won't increase even after 5-10 minutes later. Maybe it's Firmware issue? Can you tell me which firmware is good?

Thankyou.
[ONE Android Development] Tomoms:
Perhaps your battery is very old... Does this happen only on my ROM? I'd suggest that you go back to 100% stock (by flashing the last CyanogenOS build) and then reflash my ROM again. This way, you'll update your firmware to the last official version (which is always good to have, even though it has nothing to do with your battery issue).
[ONE Android Development] KuldeepShivankar:
Thankyou for the response. Actually i've changed my battery recently but on Havoc latest i didn't face this issue. But tomorrow i'll flash COS13 and will flash your ROM again. Thanks.
[ONE Android Development] Maverick John:
Where did you get a new battery? I too need one.
[ONE Android Development] KuldeepShivankar:
https://www.mythicallab.in/collections/oneplus-batteries/products/blp571
[ONE Android Development] Maverick John:
Thanks mate. BTW. How's the performance?
[ONE Android Development] manudroid19:
Hi, I cannot get this ROM to work. I format system, data and cache as f2fs, I then install the rom and the Pico OpenGapps (Nano not working due to space).

After installing Gapps, the ROM fails to boot. I see the boot animation for a while, then screen off and it reboots into recovery. I am using twrp 3.2.1-TugaPower.

Does anybody have a clue on what is happening?? Do you use another recovery or partition format layout??

edit: also tried with twrp 3.3.1-K1

edit2: the issue is with latest gapps, using 20200912 pico all went fine
[ONE Android Development] sbhajband:
Please if you have used it how its performance

And how it durability
[ONE Android Development] ImmortAlex:
Looks like your partition was encrypted earlier.

I still have no time to install this ROM once again and get last_kmesg as developer asked.
[ONE Android Development] KuldeepShivankar:
I'm still testing it. It's been only 3 days since i changed it. It's working good. In 25% battery usage i got 1 hour SOT. I'll give my final review after one week.

---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------

I'm still testing it. For now it's working fine. I'll give my final review after one week.
[ONE Android Development] ryanfraser38:
Where can I get the 12th September version of gapps? The website only does the latest version doesn't it?
[ONE Android Development] Maverick John:
Thanks again. Looking forward to it.
[ONE Android Development] ze7zez:
https://sourceforge.net/projects/opengapps/files/arm/
[ONE Android Development] jfbaudio:
I had been pulling my hair out trying to figure out what the problem was... thanks for that. I now have 17.1 working with TWRP 3.4.0 and 20200912 pico
[ONE Android Development] Tomoms:
Hey there, in my download folder on AFH you can find a new build, dated 20200920. It's a minor update; I can't push it via OTA nor update the first post because I'm far from home right now. This new build has got a couple of small improvements for SurfaceFlinger, so screen rendering could feel a little smoother. Anyway, it's a minor update, you can safely skip it if you prefer to.
[ONE Android Development] pranavrocksharma:
How to speed up charging its very slow aslo on kernel auditor no option of fast charge please help
[ONE Android Development] KuldeepShivankar:
Hi, battery is good and i get 5 hours of SOT with youtube and whatsapp. I'm quite happy with the results.
[ONE Android Development] AAB4K:
Hello I had same issue, but OP's custom kernel allows you to change charging speed with Kernel Adiutor. Check his comment here. I am able to toggle my charging speed now.
[ONE Android Development] pranavrocksharma:
in kernel auditor no tab for fast charge can you post screenshot bro
[ONE Android Development] pranavrocksharma:
Please improve charging is too slow only 500mampre
[ONE Android Development] pranavrocksharma:
how did you changed charging speed
[ONE Android Development] AAB4K:
Flash the kernel by OP and it will enable that option in Kernel Adiutor.
[ONE Android Development] oviung:
Hello [MENTION=5727088]Tomoms[/MENTION], lately I'm getting a lot of random reboots. I don't think it's related to the ROM. Probably it's the battery (a knock-off replaced a year ago). I even got a reboot while in recovery. Could you have a look over the last_kmsg before I try the original battery? Thanks! :)
[ONE Android Development] Tomoms:
It really looks like some piece of hardware is failing. The log complains about the internal eMMC memory chip not acting as it should, but I've seen someone on the web claiming it might happen (albeit on a totally different platform) if the power supply isn't good/stable enough. So yes, try the other battery.

BTW, I've been quite silent lately, but don't worry, a huge update is in the works :)
[ONE Android Development] itssomething:
Hi, is it possible to include screenshot button in QS Tile like in the Pie, and maybe with power too in your next build? My power and volume button all broken so i have to use app to do that right now.

Thanks for making this device alive till now, Appreciate it!
[ONE Android Development] Tomoms:
Sure thing, if not in the next one, it'll be present in the following one. So you'll have it soon :)
[ONE Android Development] oviung:
Sadly, the battery did not solve the issue, seems like it's some other HW problem. Finally a reason to upgrade. Gonna search for a Pixel 4a.

As a side note, I also have a problem with the GPS. Testing with SatStat I cannot get a lock. Only network location works. Might be a problem with my setup since I've tried also before installing anything after a fresh install and it got a lock. Does it work for you?

Anyway, thank you for the work that you've done on this device!
[ONE Android Development] Tomoms:
No, you're not alone. GPS is kind of broken and I hate that. I'll soon start working on it because I want to smash the GPS problems and restore its functionality as soon as possible. Good luck with your new device :)
[ONE Android Development] ImmortAlex:
GNSS is not totally broken, at least for me, at least in official LineageOS build. It just won't load almanac and ephemeris data from internet, so after one day of being unused GNSS do cold start and load data from satellites.

I live in suburban area, without skyscrapers and with clean horizon. Cold start lasts for one or two minutes, and my OPO see and use a lot of GPS and GLONASS satellites, and even number of Beidou (China is near), and even couple of Japan and India SBAS satellites (useless, of course). Position is precise.
[ONE Android Development] Tomoms:
Thanks for the feedback. Are you using MicroG or Gapps? Is map navigation using Google Maps/Here Maps/Whatever Maps working (i.e. your movements are tracked by the app while you follow the driving/walking directions)?
[ONE Android Development] ImmortAlex:
I'm using OpenGapps Pico and a bunch of navigation apps, most world-wide known is OsmAnd, others are kinda local (Yandex Navigator, 2GIS).

I'm using GPSTest to view satellites.

It's definitely the cold start without data from internet, a very characteristic appearance of satellites in view and in use, with growing precision (shrinking of circle, you know). Internet is very good here, so it's not a problem with connection.

Never had such problems before, using only official CyanogenMod and LineageOS since the beginning.
[ONE Android Development] Tomoms:
The new update is HUGE

Hey there! After one month of work, I'm here with a new build, and boy is it a big update!

First of all, the C/C++ system libraries and components are built with the compiler's best performance optimizations. Many of these libraries have been updated (libpng, libjpeg-turbo, sqlite) and/or patches have been applied to optimize them for running on ARM processors (it's worth mentioning a huge SQLite performance improvement). Some bionic standard library routines have been updated and improved, and ART has received some interesting updates as well.

I've also introduced a new privacy feature, picked from some other ROMs: now a toast message is displayed whenever an app tries to access the clipboard. I hope this won't bother you, anyway the plan is to add a toggle to disable this feature in the future.

Device-wise, I've implemented LMKD, which now replaces the old kernel LMK driver, and I've added some patches to improve SurfaceFlinger's (Android's display renderer) smoothness.

The kernel brings several code updates and security fixes, a new default hotplug (bricked hotplug, which replaces Qualcomm's ugly Mpdecision), a new default I/O scheduler (maple), CPU undervolting, Sultanxda's cpu_input_boost (which replaces CAF's CPU boost driver), support for OTG-Y cables, and a load of improvements related to GPU rendering and such.

All in all, this ought to be one of the biggest updates in the history of this ROM, so I'm eagerly waiting for your feedback. Reviews, thoughts, requests, criticism and complaints are always accepted!

Happy flashing :)

Important P.S.:

I strongly suggest that you wipe cache & dalvik-cache before (or after) flashing.
[ONE Android Development] ImmortAlex:
Aaaaand now I found some time to test your build. And once again I got reboot just after entering of encryption key. It's clean install, with formatting system and wiping data, but /data is encrypted already. From last_kmsg I see that problem is encryption, definitely.

Thnx for your work, anyway. Official LineageOS became too official ((( they lost the smell of bleeding edge (
[ONE Android Development] dimzidp:
hello, is there any hope for Magisk hide?
[ONE Android Development] Tomoms:
Are you using f2fs or ext4 for /data?

Unfortunately I can't reproduce the issue nor can I find any similar reports on the web...
[ONE Android Development] ImmortAlex:
f2fs
[ONE Android Development] Tomoms:
Another user reported similar issues with all builds newer than 20200811. So this one should work, and this one should not. Can you try both of them and confirm, please?
[ONE Android Development] ringonne:
Hi. I'm right now with 16. Hoping to get some free time to test 17.1 as a daily driver.

Right now I just have some breaks, other times gets super slow.

Mobile data works perfectly, but wifi sometimes stops. Something strange happens with instagram app ( works super badly with WiFi, I change to mobile data and I need to restart the app ?)

Gps isn't really great, it does work but from few second to few seconds goes inaccurate and then gets back o normal.

I don't have any option to face unlock, should it be available? What about auto face unlock, isn't any work around to get it work?

I had a rom were I could use ACCA to stop charging at 80% and after that the phone started using energy direct from charger. Now the ACCA says the rom/kernel does not support that function

Keep up the good work,

Thanks
[ONE Android Development] hystrix65:
Unfortunately, Google Maps still doesn't work. I get the point, but when i start moving the point doesn't move. I f I turn off and on again the APP, the point moves to the new position, Gps working, but if I move the point doesn't move... Is there a way to fix it? For me Maps is really very important, thank you
[ONE Android Development] Tomoms:
I don't know much about Face unlock, but maybe you don't see it because the Gapps package you're using doesn't support it. IIRC that's a feature of Gapps, not of the ROM.

About the ACCA thing, as far as I know the Oneplus One doesn't support drawing current directly from the charger. Did you really manage to use that feature on some other ROM+kernel? Can you tell me which one(s)?

No, there's nothing you can do. There's something I can try to do, but now I don't have enough time to look into the issue.
[ONE Android Development] ringonne:
Do you know which of the gapps ou other package that can be used to flash in the low free space of the OPO??

I use Accubattery to track my battery, normally is show discharging and negative amps, when I plug the charger show the positive amps charging, and when it was at the target max % it showed 0 and sometimes less than 100mA(basically not using battery).

I think I used in the TugaPower Rom + (probably) thunder Kernel

Edit: Or Fz Kernel ?
[ONE Android Development] ImmortAlex:
Tested and confirmed: build 20200811 start to load after decryption, build 20200823 reboot immediately.
[ONE Android Development] Tomoms:
Ok, I could send you some test kernels to try in the next days. Would you be able to test them?
[ONE Android Development] ImmortAlex:
Yes, of course! Some times I'm not able to test immediately, but in day or two I will do any tests you want.
[ONE Android Development] Tomoms:
Perfect. There's no hurry.

You need at least OpenGapps Nano I think, so you have to repartition your phone... But it shouldn't be too difficult, there's a new tutorial here in which you can also find an automatic flashable zip that will do the job for you.

Anyway, I use AccuBattery + ACC as well, and I still notice the behavior you described. The ACCA app has always said that drawing current from the charger is not supported.
[ONE Android Development] ringonne:
I will try that tutorial next time, with latest update and clean install, but before I will try to get ACCA to work with other rom+ kernel I will report back. GPS in the latest build is more or less stable?

About the gapps, on the Opengapps notes it says "Google removed the Trusted Face (FaceUnlock) feature for security reasons (see this post). We've removed the corresponding code for the FaceDetect and FaceUnlock for all platforms.", I'm assuming they removed for unlock. On the other hand, BitGapps says it has the facelock package. Need to try both.
[ONE Android Development] SairesArt:
Memory corruption

Hey there. Just switched to this ROM with f2fs partitions, up from Android 7.

Loving it so far. Only one problem: NewPipe shows memory corruption on Thumbnails and crashes on the subs page because of the corrupted thumbnails.

Anyone else experiencing this? ( https://github.com/TeamNewPipe/NewPipe/issues/4516 )
[ONE Android Development] Tomoms:
I'm facing the same issue. I've commented the Github Issue you linked.
[ONE Android Development] SairesArt:
Thanks for that :)

Whilst I'm in the process of complaining: A curious crash is also occuring with the preinstalled default Files viewer. But *only* when switched to the list view. You are stuck with Files crashing that way. However, you *do* have fraction of a second to click the list view again to switch it to prevent the crashing.

Unfortunately when choosing media (to upload) this is the page that get's chosen by default. So if you want to upload an image to imugur, you only have a fraction of a second to chose it. As shown in the video attached (Video zipped, since mp4 not allowed). I wonder if another app can be elevated to the position of default file-picker-dialog as a temp workaround...

Lastly, I presume we are supposed to ignore the LinageOS updater, right? It has updates, we should ignore them and stick only to updates released on this page... correct?
[ONE Android Development] capt.ron:
I have also noticed the crash issue with the default files viewer (only when switching to list view). To get the viewer to work again I cleared storage and cache, just can't switch to list view.
[ONE Android Development] SairesArt:
Yes this works, but unfortunately when uploadin stuff in the browser it is the default view that is chosen 。゜゜(´Ｏ`) ゜゜。
[ONE Android Development] Tomoms:
I use LineageOS updater to serve my new builds so if it says there's an update available, you can install it, but this means that you currently are not using my latest build from October 10th, and this changes a lot the way we need to debug the issues you reported in that Github Issue page (yes, I've read your latest comment). Please check which build you are currently using and let me know. Thanks.

This Files crash is most probably present on official LineageOS as well, as I didn't touch anything not even remotely related to that app. We need to confirm this and possibly open a bug report on Lineage's GitLab.
[ONE Android Development] SairesArt:
lineage_bacon-userdebug 10 QQ3A.200805.001 eng.tfonda.20201003.150037

Indeed, you are correct. I missed "Latest build: here." and went to "Mega: LineageOS 17.1 by Tomoms". There I picked the latest build, which was from the 3rd Oct 2020, with the actual latest build being from the 10th Oct 2020.
[ONE Android Development] Tomoms:
Ok, please test the latest build as well, because NewPipe's thumbnails are broken for me as well, but an user reported that the German Ebay app you tried works fine for him...
[ONE Android Development] SairesArt:
Uff, it doesn't want to update >.< Internet is obviously available.

I presume, I download the latest build and dirty flash it... that's the same as an update correct?
[ONE Android Development] Tomoms:
Unfortunately the file storage service I use for storing build is very unreliable, as it changes the direct links to the files every now and then, thus breaking the OTA updater. Download the build, wipe cache and dalvik-cache, flash it and reboot :)
[ONE Android Development] SairesArt:
Updated it, tried it same deal, same crash.

The things about he Ebay App. Not the image displaying itself is the problem, but making or loading images whilst in personal chat.

All images on the listings themselves are fine. But it Chat it's where it faulters.
[ONE Android Development] ImmortAlex:
No problems with Files in list view on official build of LineageOS 17.1.

I think, it's some local problem, may be with particular file or its content. I mean, it can be problem with Files app, but not related to Tomoms' build.
[ONE Android Development] Tomoms:
Please get a logcat immediately after the crash and post it here.

Thanks for the info [MENTION=4417347]ImmortAlex[/MENTION]. However, it definitely is a problem of my builds, but I've looked into it a bit and I can say it'll be fixed in the next build. Also, this issue is probably related to the NewPipe issue and the German Ebay app issue. As soon as [MENTION=6704371]SairesArt[/MENTION] manages to get a log, we'll know for sure :)

EDIT: confirmed, Files and NewPipe crash for the same reason. I promise I'll fix these issues in the next build :)
[ONE Android Development] SairesArt:
Here we go. @11:14 I opened NewPipe, corrupted a thumbnail and caused it to crash.

Then I opened Ebay Kleinanzeigen and in a chat window submited an image, caused it to crash.

Lastly opened the file browser, which was in List view and it immediately crashed.

After this, I took the log.

Many Many thanks for the active development!
[ONE Android Development] SairesArt:
My phone needs to remain rootless for banking (uugh =.=) But I still wanna use Viper4Android.

Following this guide I went to https://zackptg5.com/android.php and got the "Rootless Driver Installer", which should be ROM agnostic, as I understand it.

After flashing it phone is just stuck booting to fast mode. Reflashing the ROM fixes everything, but I'm left without V4A.

Anyone else experiencing this? Are there other methods to get V4A without root?
[ONE Android Development] ze7zez:
[MENTION=5727088]Tomoms[/MENTION] or anybody, do you know how to check which ROM presents itself as "15.1-20200723-UNOFFICIAL-bacon" and does such stunningly large statistics.

The most active version 11267, including the 11171 in China. :confused:

.
[ONE Android Development] Tomoms:
New bug-fixing build available!

All crashes are now fixed in today's build :)

Unfortunately I'm not able to help you, sorry...

Hmm... I have no idea.
[ONE Android Development] capt.ron:
Greetings [MENTION=5727088]Tomoms[/MENTION], I dirty flashed your latest rom and default files viewer seems to be working in good order now! Thanks for the repair!
[ONE Android Development] SairesArt:
Many thanks for the great work! Now it's certainly daily driver worthy. To celebrate the occasion, I exchanged my OnePlus's Display, for another decade of trusty work. Never dug deeper than the simple battery change before. Really pleasently surprised to see everything being modular, except all worn rubber sticky thingies.

As others have reported, the charging speed it capped at 1 Amp. Other OnePlus One ROMS broke the 2 Amp fast charging a bit as well, but it worked under the following conditions: Plug phone in, it charges at 1 AMP. Turn screen on. Turn Screen off again. Now the phone charges at 2 AMPS. I have seen this behaviour in two different (Android 7) ROMS. But in this ROM, it simply is capped at 1 AMP no matter what. Longer battery live is good, but the option for the 2 AMP quick charge would be great.

Sometimes you still come across this seeming Memory corruption in other places, though none result in a crash.

The worst offender is the system's color picker, which is a noisy mess, as seen in the video attached.

Next are the video thumbnails, as produced by the system's gallery, see image below.

Lastly, the app switcher produces the same corruption, but I cannot reproduce it always and only for a split second under the following condition: You minimize an app and it takes a screen shot to display for the app switcher. Now rotate the screen. I guess at this point there exists no smaller, version of the thumbnail to fit the rotated screen, so the app screen shot is resized. When this smaller screenshot is presented in the app switcher, for a split second it is corrupted as well, but it fixes it self half a second later.

None of these issues result in crashes and are thus not critical to fix. Really enjoy the ROM now :]

Root is way to convinient to have >.< I'll try rooting again, maybe this time I'll get lucky in still making the banking TAN app run...