yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] tofu:
Does this ROM support microg? I.e. signature spoofing is required. Thx
[ONE Android Development] isitmeor:
i really like this rom, however this rom does not like a dirty flash
[ONE Android Development] Kengat:
I always dirty flash and so far no issues.
[ONE Android Development] ConnerJSP:
Yea, I updated by dirty flashing over the previous build and launcher kept crashing as well as multiple apps... Wiped system and re-flashed which seems to have fixed the problems, but once it's clean flashed it works great.

[MENTION=5727088]Tomoms[/MENTION] I checked your ROM against stock LOS for how they handled MTP for PC, and they are different. It looks like a normal MTP device on stock but a keyboard using yours (?). Still having problems with copying music files: View attachment 4652411

Side note: anyone having problems with lots of google apps? My messages is messed up and google services break certain things (Face Unlock and VM (I know that some developers are at least aware of these two problems)).
[ONE Android Development] Tomoms:
Nope, but it'll support microg starting from the next build.

I always dirty-flash my own updates without problems. I don't even wipe cache nor dalvik-cache.

Lately I've had some problems with MTP as well. Probably the phone is detected as a keyboard because of the kernel patch that allows us to use our phones as keyboards. I'll try to remove it to see if it's fixed, I'll send you a PM with a new kernel to test.

I've never faced any problem with the few Google apps I use.
[ONE Android Development] Jokert129:
How did you install magisk and which version ?

And which xposed installer apk do you have ? you need to download a specific xposed installer apk that is compatible with magisks systemless xposed.

I have both working.

Also i have always flashed it dirty and always worked without problems, even without dalvik wipe.
[ONE Android Development] Prospie:
The screen doesn't turn off when i'm calling someone, i've tried rebooting, but that doesn't work. Anyone else experiencing this? I'm on the november 23 build.
[ONE Android Development] alma23:
Try changing firmware, everything working properly with firmware_fixed on 23rd November build.

BTW [MENTION=5727088]Tomoms[/MENTION], maybe it's a silly question but I'm afraid of losing my data so does this ROM and kernel support encryption?
[ONE Android Development] Tomoms:
I've never had this problem. I don't know if it's firmware-related; for your information both firmware_fixed and the last firmware released for the OPO (the one from the end of January 2016 if I recall correctly) are working 100% fine with this ROM.

I have no idea. It should, though, if encryption is supported by official LineageOS.
[ONE Android Development] tofu:
I haven't tried Tomoms's ROM, but his kernel worked with encrypted microg Lineage (https://lineage.microg.org/).

The combo had some random soft reboots though, dunno if kernel related or not.

But still a word of warning: encryption and dirty flash is a problem attracting combination. I would not even try without a backup.
[ONE Android Development] patp:
I flashed from Sultan LOS 14 and had no problems with my encrypted data partition.
[ONE Android Development] j4ckp0t:
hi mate. i too have troubles with MTP:

- usb mode choosen (MTP for me) in developer settings is not permanent (lost after a reboot. this issue is not present in official lineage build - verified by a friend on his phone)

- the phone keeps disconnecting when used with Android Auto (from MTP to charge only mode, and no way to revert to MTP)

please can you send me the kernel you mention?
[ONE Android Development] Tomoms:
Hello!

Issue #1 is definitely a bug, I thought official LineageOS had got it too, but since this isn't the case, I'll try to fix it and in the meanwhile, I'll add it to the list of known bugs in the first post.

About the other issues we've faced regarding MTP, I still haven't prepared a test kernel because I've found out something that makes me think that the issue is in the ROM, not in the kernel, so I'll build a new ROM to test in the next days. Anyway I'll keep you informed.

[MENTION=7541467]ConnerJSP[/MENTION] could you try to flash Argon kernel v1 on the latest build of my ROM, and check if the device is still detected as a keyboard and if file transfer is still working badly? Don't worry if other things are kind of broken (flashing such an old kernel on a new build of the ROM could break something), all that matters now is to test MTP.

Thank you for your patience :)
[ONE Android Development] j4ckp0t:
Ok, meanwhile I have flashed Franco r57 kernel.

I'll try it ASAP and bring you a feedback.

Thank you
[ONE Android Development] j4ckp0t:
Issue fixed for me with Franco kernel.
[ONE Android Development] ConnerJSP:
*Kernel v1 on 23rd build*

Device is still detected as a keyboard, however, file transfer improved: was able to transfer 1,000+ music files in one batch (usually glitches halfway through).

It's quite alright, no major functions were lost, just a minor inconvenience. Thank you, for your efforts :)
[ONE Android Development] Tomoms:
Both the issues are fixed on Franco kernel?
[ONE Android Development] j4ckp0t:
I did a quick test, but:

- USB mode = MTP in developer settings is permanent, even after a reboot/power off-on

- using a pc for file transfer the default behaviour when plugged is charging mode only, but from the drop down menu I can choose mtp mode (using your kernel this was possible only the first time the device was plugged, then charge only)

-android auto is definitely working fine (1hr test, so far no disconnection). No particular settings here: plug the cable and android auto pop up

Btw , thank you for all your efforts
[ONE Android Development] rolfpancake:
Vibration strength

Hey Tomoms, thank you for this awesome ROM. My OPO is working like a charm now again.

I clean flashed the latest version and wanted you to know that all is working fine. No problems with MTP, Wifi, sound, responsiveness or anything. Battery drain is quite low - seems promising.

My only problem for now: I can't change the vibration strength (when receiving messages or getting called). This is not a problem of your ROM alone - I tried other 8.1 and 9.0 ROMs with the same missing settings. I'm pretty sure I was able to configure the amount/length and strength of vibrations in different situations while using the stock ROM. Is it somehow possible to get this setting back?

I read that I could use Kernel Adiutor but wasn't able to push root privileges to this app or get a rooted device. I tried flashing the official Lineage SU addon provided on cyanogenmods.org but this had no effect. Any other way to achieve this?

Thanks in advance! Thank you for your efforts with this ROM :)
[ONE Android Development] Tomoms:
Rule #1: cyanogenmods.org = trash. The only official site of LineageOS is lineageos.org. All the other websites are just spreading a big amount of balderdash, because their authors, most of the times, simply haven't got the faintest idea what they're saying. So the fact that you downloaded the su addon from their website, and it had no effect on your phone, doesn't surprise me at all.

Rooting this ROM is simple: you can either use the official su addon (untested, it should work), or you can use Magisk (tested by many users including me) or SuperSU (I don't know if anybody tested it, but again, it should work).

I can confirm that in Kernel Adiutor you can change the vibration strength, but you cannot set custom values for different kinds of notifications. LineageOS doesn't allow that, and there's nothing I can do about it.

[MENTION=6692087]j4ckp0t[/MENTION] [MENTION=7541467]ConnerJSP[/MENTION]

Ok so the MTP issue is definitely related to the kernel. If you could test some random Argon kernel versions on the latest build of the ROM and tell me which is the last one in which MTP works fine (file transfer works fine and none of the issues mentioned by [MENTION=6692087]j4ckp0t[/MENTION] are present), it'd be really, really helpful. Thanks for you patience and cooperation!
[ONE Android Development] Prospie:
I have flashed the latest firmware released, still having reboots when turning wi-fi on. Do you have a link for the 'firmware_fixed' ?
[ONE Android Development] Tomoms:
I have it in my personal Google Drive folder: https://drive.google.com/open?id=14750t5hT9AiNTELEfljqp2Qfnd0uhbVb
[ONE Android Development] j4ckp0t:
Ma sei italiano, scusa ho notato adesso!

Io ho flashato inizialmente la tua Build del 4 novembre e poi l'ultima quindi eventualmente dovrei provare una versione di kernel antecedente alla 8.

Se hai un'idea su quale puntare fammi sapere, purtroppo non ho tantissimo tempo per fare molti test.

English: i asked which version of argon kernel test
[ONE Android Development] patp:
Getting spontaneous reboot during long phone calls, anyone else?
[ONE Android Development] Syaani:
No. I have talked something like 35 minutes max. How long is long? Which modem are you using?
[ONE Android Development] Prospie:
Thank you for the link! I flashed this firmware in the morning, but half an our ago, the reboot occurred again...
[ONE Android Development] patp:
Around 10 mins, happened twice. Firmware is DI.3.0.c6-00241
[ONE Android Development] Tomoms:
Hello! The new build brings microG support, and the network activity indicators have been disabled :)

I've synced the sources with LineageOS, as usual, and added some minor general fixes here and there.

Download here.
[ONE Android Development] ghufronaka:
[MENTION=5727088]Tomoms[/MENTION] may i have gallery2 apk in this rom? Or where can i download it? I want to put it into mm rom.
[ONE Android Development] pa1281:
[MENTION=5727088]Tomoms[/MENTION] does this include idrophecy's tweaks like network traffic and one tap wifi,data?

Is neon kernel based on sultan's kernel?

Any plans of OTA for your ROM?
[ONE Android Development] Tomoms:
1. Nope, but I can try adding them if you want.

2. Yes, it is.

3. No.

1. On my phone, the camera app takes the photo, saves it and then kind of freezes for one second. Then it restarts working normally.

2. True, but I haven't got the faintest idea why. I'll try to fix it as soon as possible.
[ONE Android Development] JJohnson1988:
I'll get a logcat for you tomorrow. My app freezes for a few seconds, then disappears after a photo is taken (but no photo is actually taken).
[ONE Android Development] pa1281:
[MENTION=5727088]Tomoms[/MENTION]

1. Nope, but I can try adding them if you want.

If you could add ,it would be a great addition to the ROM.

It has very useful features.
[ONE Android Development] JJohnson1988:
https://drive.google.com/file/d/0B5Ckg0fu7GLMM2d2a2NvOHJqS1k/view?usp=drivesdk
[ONE Android Development] pankspoo:
Rom is not working good on latest kernel v11 lags very much but when i switched to v9 below its superb on stock settings
[ONE Android Development] Tomoms:
Although this doesn't make any sense, I might know why on certain devices this happens. I'll give you a new kernel to test soon.
[ONE Android Development] pankspoo:
I tried to change settings also but it not helped. Can u add more governor like smartmax?
[ONE Android Development] Tomoms:
Did you dirty flash my ROM on top of some other ROM? If so, what was that previous ROM?

Also, can anyone report here whether HDR is working correctly for them or not? Thank you.

P.S. A new build will be released within a couple of days.
[ONE Android Development] JJohnson1988:
Clean flash.
[ONE Android Development] Mr.Ak:
Wanna hear a fun fact? It is actually there,taken and saved! Check your DCIM folder,you should be able to find that pic at the end.

It is a standard lineage os bug.For me,it fixed after some usage.

Till then,you can use Bacon camera.
[ONE Android Development] JJohnson1988:
Thanks, I had no idea.

Does Bacon Camera bypass Sultan's camera HAL?
[ONE Android Development] zalamandra:
No
[ONE Android Development] Tomoms:
There's a new build available, it brings some small, new optimizations applied to several parts of the Android OS and the latest Neon kernel is already in-built (for the complete changelog please refer to Neon's thread).

Enjoy!
[ONE Android Development] Mr.Ak:
Thanks!

Do you plan to add your 3.10.xx CAF kernel in upcoming builds? :D
[ONE Android Development] Tomoms:
Not anytime soon, but it might happen in a distant future, when it'll be more polished.
[ONE Android Development] secretkloud:
Excellent!

Flashed the build a few hours ago and I must say I'm impressed. All the issues I had running ViperOS just went away.

Thanks a lot!
[ONE Android Development] Tomoms:
Thank you for the kind message! I'm glad the ROM is working fine ;)
[ONE Android Development] Angrydr0id:
An excellent work. Thanks.
[ONE Android Development] Angrydr0id:
The Pin Quick Lock isn't working. Thanks for your job.
[ONE Android Development] Jokert129:
Since the 11th December update i have a very weird situation.

The last thing i remember doing before this issue occurred : cleared the device with sdmaid and updated adaway host files and rebooted device

So the issue is, after a reboot, doesnt matter when why or what, just after any reboot the phone just becomes bricked. It bootloops but before even launching the system which is something i never experienced before. It shows the initial logo of 1+ and text "powered by android", then it vibrates once and restarts, then shows the logo again, vibrates and so on. It is possible to access TWRP and fastboot.

So first time it happened i tried many things, from flashing the 11th update again dirty, to clearing up dalvik and normal cache. Then i wanted to see if fastboot is possible to launch, and it was. So after seeing that fastboot is launchable i just cleared the cache again and rebooted, it booted into the system normally ( after taking a while because it was dirty flashed ).

Today Youtube vanced had an update, i updated the app and was prompted to reboot, and so i did. The phone became bricked again. I then tried the same steps over and over ( dirty flash, clear cache ) but nothing seemed to work.

Then i tried the one thing, which is just launch phone in fastboot mode, reboot again to twrp, clear cache and boot phone. Now it works again.

Now i have no idea why launching fastboot solves the brick, nor if its the actual launching fastboot or the combination of all things together ( dirty flash, clean dalvik ) but i am scared to experiment on it, also scared to reboot the phone because i fear it may brick forever and i will have to buy a new phone.

Is it Hardware related or could it be software ? I mean my sim card and phone calling doesnt really work on the phone anymore ( its too old so the phones receiver just broken ) but that is phone related.
[ONE Android Development] Syaani:
Wait what? Whatsapp's video recording and video preview just got fixed by itself O_o Earlier it was bugged and now it works just fine. This is the 20181015 build and I haven't changed anything.

Edit: or it worked one time and then broke again.
[ONE Android Development] Tomoms:
WhatsApp video recording/preview was never broken for me.
[ONE Android Development] Syaani:
Yeah, I know. Maybe our OPOs are different. Also I might try to wipe internal storage next time I update. That has solved some media related issues in the past when I updated from Marshmallow to Nougat. Let's see.
[ONE Android Development] skinke280:
Wow this rom is amazing! No issues so far and great battery life. Thanks a lot for this.
[ONE Android Development] Tomoms:
Hello, I've uploaded a new build of the ROM :)

It is up-to-date with LineageOS, and it also brings several improvements under the hood: touchscreen responsiveness optimizations, better scrolling, better network throughput, improvements for WiFi power consumption (I've imported them from a newer device, they might be useless on our OPOs, but anyway!)... And probably something else that I forgot to mention!

Argon v10 is bundled in the ROM.

This sounds so weird!

The only thing that comes to my mind is that the phone bootloops on the kernel splashscreen because it cannot mount the /cache partition (I find it really unlikely, though): this would explain why a cache wipe solves the issue. Anyway, even if this was the case, I'd have no idea why the cache partition becomes corrupted so often.
[ONE Android Development] andyqp:
AndroidFileHost does not return any mirror for this version. I see that more than 30 people have already downloaded it... Is anyone else able to download it now?

Thanks,
[ONE Android Development] ConnerJSP:
I am not able to download it either; no mirrors found.
[ONE Android Development] jamsblast:
me neither are able to download it, and wanted to try the rom :(
[ONE Android Development] AksHay1994:
No mirror found! ??
[ONE Android Development] Tomoms:
Try again later or tomorrow. I'm sorry that the ROM isn't available right now, AFH might be having some problems. By the way, if anyone has downloaded the file, they are allowed to mirror it and post the link here. Otherwise, I'll take care of re-uploading the file as soon as possible. Happy new year to everybody!
[ONE Android Development] TriboDoP:
Link: https://androidfilehost.com/?fid=11410963190603885439

---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------

Sorry doesnt work!
[ONE Android Development] skinke280:
Happy New Year Tomoms and thanks for your hard work!
[ONE Android Development] Tomoms:
AFH seems to be working again now.
[ONE Android Development] Milan34119:
I still can't download the latest build.
[ONE Android Development] patp:
Getting a few spontaneous reboots with this build. No pattern I can see. I have rooted now, how can I diagnose?
[ONE Android Development] Tomoms:
I have mirrored it on Mega: https://mega.nz/#F!ZpE32Sha!hsAvmHPobEgWJIV24xZmsA

If you are talking about full reboots (i.e. the phone vibrates, shows the Oneplus logo and then Lineage is loaded), I need the /proc/last_kmsg file. Read the last 3 lines of this post: https://xdaforums.com/showpost.php?p=77966087&postcount=267
[ONE Android Development] colgor:
Hi, recently installed this rom. Only one problem so far. The hardware button lights don't come on since installing. Tried reading thru the pages but didn't see any mention of this.
[ONE Android Development] Jokert129:
i cleaned like 1.6 GB of trash ( mostly app cache ) with sd maid and tried to reboot the phone ( my phone was being very slow, keyboard was buggy and unresponsive ) and it soft bricked. Then i tried to do the same steps as before ( dirty reflash, clean cache and dalvik, boot into fastboot ) nothing seems to help it. I then went into the file manager in TWRP, did nothing in there ( i was trying to click everything i could to figure out a way to boot the phone ) and it somehow booted to system.

I then downloaded the latest build ( 29th ), did a twrp backup ( i always do one before dirty flashing ) and flashed the new build, deleted cache and dalvik after that too. Ofcourse the soft brick happened again and no method that i tried before helped either. I then remembered you talking about possible cache corruption or perhaps permission problems, so i went into TWRP file manager and just opened the /cache folder, without doing anything else there.

I also clicked the option to copy the log to sd card, maybe there could be any information regarding the problem ? I could send you the log privately just if you are curious or interested, but i doubt it will tell much.

After that it somehow booted into system and now the phone is working normally ( not slow, keyboard responsive and fast ).

Dont take this too much into attention as i will most likely buy a new phone ( this one is getting old ), just providing you some information you might ( or not ) find useful or interesting.

Also is there perhaps a way to "soft reboot" a device ? I had such option in APM+ module for xposed framework but it now doesnt work anymore. Basically the phone looks like it can reboot but only if its a soft one. The weird out of nowhere "soft crash" that still happens ( although rarely now ), does reboot the phone normally ( for example im watching a youtube video, then i suddenly just see a lineage os boot animation and the phone boots, it could be possibly related to the fact that its Youtube vanced magisk module ).

And just to throw a weird bug, not sure to what could that be related, when im watching youtube and i think it happens when i use volume up/down buttons or when i use it with combination of screen rotation ( switch my phone angle at the same time clicking the volume button ) the screen becomes out of place regarding what is being displayed, but not where the screen actually is.

Its kinda of weird, the whole display changes its position a bit down, like somebody dragged the image in photoshop down but the visible borders are still there, so across the half of the display i see a line, and above the line is the bottom of my display and below the line is the top of my display. Not sure if i explained it correctly, but whats weird is that the displayed image is not the same as where the display actually is.

So the display stays where it is at, just what i see is moves. Usually clicking the "home" button ( to go to launcher ) and locking and unlocking device ( power button ) solves the issue.

Not a crippling bug, it happens rarely.
[ONE Android Development] Tomoms:
The recovery log you copied to sdcard isn't useful. IIRC it's only useful when debugging TWRP.

Soft rebooting could be also called "dirty rebooting": it's not recommended, as unexpected things could happen after a soft reboot (bad performance, crazy battery drain...). I think I remember that back in the Lollipop/Marshmallow days, when I was using CyanogenMod or some other custom ROM, after a soft reboot a pop up message would appear, telling me that a soft reboot had happened and that such weird things could happen after a soft reboot, thus I was suggested to fully reboot the phone to avoid problems. Hence, I don't know if there's a way to soft-reboot the phone, but even if there was, I wouldn't recommend it at all. The soft reboots you experienced are probably caused by YouTube vanced: I remember that some time ago, another user was having problems with the ROM (he too was having soft reboots, IIRC), and the logs confirmed that YT vanced was the cause.

The screen bug is something I've faced a few times as well, I have no idea why it happens but anyway, as you pointed out, locking and unlocking the screen fixes it.
[ONE Android Development] Milan34119:
I had a reboot this morning
[ONE Android Development] Milan34119:
So the ROM works great for me. However I faced a few times random reboots. I attached serveral logs and last l_kmsg files. I can provide more information if necessary.
[ONE Android Development] rolfpancake:
Thank you very much for the fast response and sorry for the delay. It worked perfectly and I could set the vibration strength to 25% which is enough for me.

As others mentioned I'm also getting random reboots one or two times a week. As the boot time is almost zero it doesn't really affect my usage of the device. But I still hope it can be fixed in the future. :)

You rock :good:
[ONE Android Development] Tomoms:
Thanks for the logs. I'll see what I can do.

Great! Thanks for letting me know.

Anyway, I've uploaded the first build of the new year! It's a small update that has been built using Google's latest compiler, and it features January's security patch and Argon kernel v10.1.

Enjoy!

EDIT: it seems to me that performance is not as good as before on today's build, specifically, apps take more time to open. I'm already trying to fix this, but let me know if you have the same feeling.

EDIT #2: there's definitely something wrong with the new build. Do not flash it.

EDIT #3: things are normal again now. I don't know what's going on guys, you can flash the new build and tell me your opinion, but keep a copy of the latest build on your phone so you can roll back to it in case of problems.
[ONE Android Development] Milan34119:
Thank you. I really appreciate your kindness and effort that you put in your ROM and Kernel.

I don't have any performance issues with the latest build. Apps open and close as fast as in the last build.