yashsingh1/xdaforums huggingface dataset:
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
Pushed new build few minutes ago. Grab it here.

Most of the bugs are now fixed. Good enough to be used as a daily driver. Enjoy!
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Vedanth Padmaraman:
Awesome!! I installed this a few days ago, and it's super-stable. I was actually planning to update to the Official LOS, but then I saw this :p

Absolutely!!
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] LonelyDay:
amazing!
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Vedanth Padmaraman:
Sound is (too?) loud

I have noticed that on both this and the Official LOS 17.1, sounds from the media, alarm and ring/notification streams play pretty loudly, louder that the stock firmware. And when I compared the /vendor/etc/audio_policy_volumes.xml and the /vendor/etc/default_volume_tables.xml files with those of the stock firmware, I did notice that for the three streams I mentioned, the values for the volumes were indeed higher than stock.

I have no expertise on the subject, so I am asking you: is this okay for the phone's speakers, or will they be under too much strain?

And, another implication is that there are times when I find even the lowest volume for my alarm too loud.

Anyway, I edited the files on my phone to use the values in the stock firmware (attached below). But I just thought I should report here.

PS: Out of curiosity, I tried to find /vendor/etc/audio_policy_volumes.xml and /vendor/etc/default_volume_tables.xml on the nokia_PL2 and nokia_sdm660-common device trees on the HyperTeam GitHub, but I couldn't find them. Where are they? Are they extracted by extract-files.sh?

I hope I'm not being a nuisance:p
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
Released new build here

Changelog is there as well. Have fun!
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
Turn off AudioFX
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Rythven:
Issue on both LOS 17 and 18 with Tachiyomi and Clover/Kuroba (image viewing apps). Maybe has something to do with scaling/dpi.

Tachiyomi will not load the image scale correctly.

Clover loading of full quality doesn't work , the image disappears and breaks the swiping feature.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
I am aware of the issue as I use Tachiyomi too. Can't spot what's wrong, so probably they will remain broken for a while. I will try to fix but no promises.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Vedanth Padmaraman:
I updated to a later release, and so I came across this again.

So I tried this, and it didn't work:confused:
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
Pushed a new build today: https://github.com/HyperTeam/android_device_nokia_PL2/releases/tag/20201112

Use OpenGapps Test build from here: https://sourceforge.net/projects/opengapps/files/arm64/test/20201107/
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] conite:
I was following the instructions at Lineage for a clean install. When instructed to install a recovery image, I assumed the boot.img provided with your package was that recovery image. After flashing it, the phone won't boot and both fastboot mode and recovery mode seem inaccessible. Any help?
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
That sounds weird, shouldn't happen unless you did something wrong. I suggest try this TWRP: https://github.com/HyperTeam/android_device_nokia_PL2/releases/download/20201016/twrp-3.3.1-PL2.img
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] conite:
Thanks. I installed the latest LineageOS 18.

But for the life of me, I can't get gapps to install.

Using twrp, I format/wipe, flash lineage.zip, then gapps.zip, then clear the dalvik cache. Then boot.

Am I missing something?
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
After flashing lineage.zip, rwboot back to bootloader, change slot to other one, reboot to recovery and install gapps.zip then. TWRP doesn't changes slot automatically like LineageOS recovery.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] conite:
That did the trick. I've never dealt with a A/B scenario before, which has caused all of my problems.

I guess the current Gapps for Android 11 is not really ready yet. Sign in is a bit wonky with some apps.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Nikonab:
can it update itself?

Great job done, I hope there will be support?

How the firmware update process works. Where can I read more?:good:

Or do you need to flash everything again as soon as a new version appears?
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] warchild98:
First of all, right after you flash the rom..DO NOT FLASH GAPPS yet. Do your first time setup without gapps.

After you do that, reboot into recovery, flash gapps and factory reset your device (this way you avoid android setup wizard force close message). After this, reboot and do your first time setup. Next, flash latest magisk and install magisk hide props right away (don't forget to tick the option with hide from various detections). Reboot, then open your terminal app and set your fringer print. Reboot again and enjoy your certified device status in playstore.

Or you can skip installing magisk and see if it works this way.

As for me...I can only get "certified device" status in playstore by flashing magisk and setting device fingerprint.

Don't know why, but it only works with this.

I don't mind having magisk installed, in fact. I use it anyways.

These are the steps I took. I hope it works for ya
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
Thank you very much @warchild98 for responding and for sharing these indications to have the device certified.

-It would be great if at some point the failed CTS that generate these inconveniences can be restored.

Greetings @warchild98 :D.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
hi @theimpulson, sorry to bother you again, unfortunately I have to inform you of a new error in the android operating system that did not happen before.

-The screen recorder stopped recording the internal audio of the system, unfortunately there is no sound and this problem was generated since the last update :(, so you can take a look at this error.

I would be very grateful for your prompt response @theimpulson.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] warchild98:
You might go to a previous version and stay on it till @theimpulson will sort it out.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
I will try to go back to the previous update.

-I was investigating and there was a developer named (Raghu varma) who in one of his previous unofficial versions of android was able to implement without any problem the increase of internal memory by high-performance MicroSD.

-So I proceeded to publish this case to the gerrit and this was what the developer Nolen Johnson told me (Not a bug, 4.4 FBE devices don't have the necessary kernel side stuff for this. Haven't sen anyone that's ported it yet.

Won't be added most likely).

-Everything will depend on whether @theimpulson can try to implement this function, which it seems from the kernel is not so easy to implement because the device is not prepared to receive said function or at least that the developer can achieve said implementation.

-What do you think about this information?

I would be very grateful for your prompt reply @warchild98
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
hi @warchild98, I found a method to increase the internal memory with the MicroSD, but you need to have USB debugging activated and have adb on the computer.

-Have a high-speed read / write MicroSD with at least 64GB of total memory.

These are the commands.

-adb shell

-sm list-disks

-sm partition disk: The ID of the MicroSD, private (without the comma)

-sm partition disk: 179.64 mixed 50, to have two partitions, one in internal storage and the other as portable storage.

In my case it works and it passes the applications to the microSD, but in large applications that have to download their data when accessing the application, storage errors are generated at the end, it may be because I have not migrated the data, but I did not I dare to carry out this procedure, since I do not want to reinstall the android version in the event of failure :(. but the good thing is that applications can be passed without major complications.

By chance you have tried this method @warchild98.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] warchild98:
I didn't tried it yet. Thanks for letting me know tho.

I'll give it a try some time.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] warchild98:
Well...that is most likely not achievable at this point.

I don't think the kernel is ready for the job.

However, a port would be awsome.

I mean the devs can at least make a flashable zip with a test kernel for us to test that out.

That doesn't mean they would/should.

Would be a really nice idea tho.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
Hi @theimpulson, I tell you that I have been using your version of android 11 (LineageOS 18.1) for more than two months, the performance reminds me of the manufacturer's android 8, really spectacular.

I never thought that in android 11 it would have the similar performance in the call of duty mobile game when I was using that version of the manufacturer at that time, this shows that by optimizing an android version very well, the device can regain its performance with the version that came from the factory (at that time, android 8).

It is incredible how poorly optimized the manufacturer's version of android 10 was (latest version, in which I had the opportunity to try the latest update, leaving the performance in nothing, a really poor and disappointing performance) on this device.

-Apart from the bad experience of android 10 by the manufacturer, I have to congratulate you again for the really incredible work @theimpulson for giving a new life to this device in question, in a nutshell friend, you are a great programmer :D. Thank you very much again for continuing to give life to this device, you can see the great effort that you have put into the Nokia 6.1 (2018) to achieve excellent performance in a device that has been on the market for some time.

-Related to the errors that I have found, the only problem that has been presented to me is the screen recorder that stopped recording the internal audio (problem that I notified in GitLab), hopefully it will be solved in this update that will come out in a few more hours .

-By how the situation looks, it is possible that the device performs very well the version of android 12 and even up to version 13, although if said version requests more ram, it is possible to migrate to versions in GO edition and with This maybe the device can support up to 3 more versions.

Excuse me @theimpulson for my English again, it's not very good :(
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] gouthamram:
Performance & optimizatation of this rom is easily noticable from stock one...iam using most of roms from my another devices also but no one is making better than this... @theimpulson work is really great & appreciatable....
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
-Hi @theimpulson, thank you very much for the implementation of high speed MicroSD adoptable storage.

What a great news...

Query, by chance you have to perform some type of additional procedure, such as making a mount or it is not necessary.

how about this great news @warchild98, @gouthamram.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
I did modify the mount points, mount type, and mount flags as well if that's what you are curious about.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] zuhaibsarwar:
I need help to install twrp permanently in my Nokia 6.1 2018 Pl2 1043 .i have already unlocked bootloader currently using 5.9.1 Infinity | UNOFFICIAL
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
Nokia 6.1 Plus (DRG) is now also officially supported and this thread will be used for the same as well. Downloads will be up within a week (whenever the bot generates the build). Sources are also on the official organization in case someone wants to build himself.

Edit: DRG wiki link: https://wiki.lineageos.org/devices/DRG
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] CarbonGTR:
Ayy! Glad I could help out with testing :)
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
Sorry to bother you again @theimpulson, but to configure only the microSD as internal storage, it is necessary to apply these mounts that I mention for this function to work correctly.

-If it is necessary for it to work correctly, it is recommended to use the adb shell or the device terminal.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
I assume you are asking me how to use adoptable storage. This might help: https://fossbytes.com/android-sd-card-internal-storage-adoptable-storage/

You don't need to run any commands or anything. Everything can be done using the GUI options present.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
Hello @theimpulson, sorry for bothering you again, I have tried the new function, it has improved by approximately 35% compared to before, in my case corruption has been generated when transferring the files to the MicroSD converted as internal, only 2 files remained intact, previously all files were corrupted.

-With regard to transferring applications, it works excellent if they are small in size, including user data that was previously completely lost and the application required reconfiguration.

-The problem starts with the installation of large applications from google play, previously large applications could not be installed in any way from the microSD converted as internal memory forcibly (Google indicated that there was an error in the download) , Now that error does not appear, but it is downloaded twice and unfortunately the obb files and part of the apk installation are damaged and indicating that there is an error with the download of the files, this happened to me with the call of duty game mobile, so unfortunately the function itself does not work as it should.

-The good thing is that it has improved but it gives serious problems with the installation of files of considerable size.

-I was trying another game, Need for speed: NL racing, as it weighs about 67MB, I had no problems with its installation, the additional files were downloaded from google play but it got stuck in the installation process and did not advance further, but before it would download the data over and over again without installation success.

-There may be a part of the code that is generating this error, with some adjustments in the code that at the moment I do not know, this function could work 100%, it would be great if you could check the installation of applications that contain obb data from google play and with it you can reproduce the error that is being generated.

-Here I publish the logcat, including a video in the process of downloading the game (What will be shown will be in Spanish).
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] zuhaibsarwar:
Are we getting lineage 19 ?
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] MartJI.V.:
Hello @zuhaibsarwar, because of how the version of android 11 (lineageOS 18.1) is running, which closely resembles the manufacturer's Android 8 performance, it should support it without major complications, of course this version of android 12 could consume a little more resources from hardware, but it should have a performance 8% better than the manufacturer's android 9 if a good optimization is applied, although this percentage can improve.

-Regarding a next version, depending on the aesthetic changes, it could maintain the performance achieved in the previous android, in this case the possible version of android 12 (LineageOS 19), but if another version were to be given, it is very likely that the adaptation of a GO edition is required so that the support of the device continues, in the best of scenarios, it could withstand up to 3 more versions of the GO edition.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
Work on it has just started. I will wait till the ROM source is ready to be built without any issues. Oh but we will, it is possible for sure.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] warchild98:
Not worth it since data corruption might occur. Btw, I'm using an 128GB SD card. I am storing most of my data on this SD card tho. But still, the latest update improved performance a little bit. I don't use adoptable storage since I don't need this feature.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] zuhaibsarwar:
Thanks I appreciate it . btw Raghu Verma uploaded AOSP extended today but facing download issues
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] LuminousMazim:
Hello thank you for, finally bring the Official LOS to DRG Nokia 6.1+ ! I have some bug with the first build, is a minor one (some not so minor) but i hope it's easy enough to included a fix in the next build.

- Battery stats not working, it just show "Battery data isn't available."

- Microphone in call is not working (need inspect a bit more) one time i got call they can't hear my voice. Microphone outside call worked fine as recording app. I suspect this tied with OK Google feature since i remember back in some ROM disabled this feature make the mic working.

- Fingerprint Device is Pixel 5, I don't know this is a bug probably intentional. But i found a bit weird about this. Almost all A11 DRG rom have Pixel 5 fingerprint on it. But why? Specially on Offical LOS which doesn't get the benefit of Pixel feature like other "Pixel like" rom. Not complaining just a bit curious why. My bad read an old email

EDIT: Want to added point but didnt want to spam more post.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] cl3izv:
Can you make a guide? I can't install it, i just unlock bootloader and flash stock rom android 8.1
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] zuhaibsarwar:
Any progress about lineage 19 ?
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Cellulario:
I'd like to report that flashlight doesn't work with any third party camera. It works with the default camera app but it doesn't with other apps such as Open Camera and Google Camera. Can you please fix this? I flashed the latest build from LineageOS website, I assume this thread is the same. I did a clean flash from scratch formatting everything.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] theimpulson:
Please provide logcat captured while reproducing the issue
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Cellulario:
Thanks for your quick reply. The camera works just fine it's just that when I have flashlight enable, either automatic or always-on the flashlight doens't do anything, no flash. I attach here the log while I am taking a foto with open camera with flashlight on (which didn't work) No error message just this "LightsService: Light requested not available on this device. 2"
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Cellulario:
sorry for double post I couldn't attach the log file
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Cellulario:
Why the camera always as some kind of HDR effect on phtos even if I disable it, I tried lineage os camera, google camera and open camera. HDR crappy effect is always there no matter what :-( Is it a bug you can fix or is it Android itself?
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Cellulario:
@theimpulson here is a detailed list of the anomalies I found.

Lineage os camera works fine

Any other camera app has problems, I tried: Google Camera, Open camera and FV-5:

1) Flashlight doesn't light up, neither in auto nor is forced

2) Open camera with alternative flash algorithm can trigger the flash only if always-on and it's not in synch with the shutter so it is useless

3) Photos always seem to have the nasty HDR effect (I wonder how people can use it)

I attach the full logcat where first I take a photo with Lineage camera, where flashlight works, and secondly with open camera, where flashlight doesn't.

log

drive.google.com

I also attach a photo where you can see the ugly HDR effect despite it was disable everywhere.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] XAedgeS:
Hello, I would like to report a bug about mic or so.

If I join a Discord channel voice , the device will just freeze (like volume button will not recognized, or I cannot kill any app completely, etc), then straight up crash the whole system (throw me to the boot logo, which will stay there indefinitely until force restart by holding down power button). Also it's not a hit or miss, every single time I did that it crashed the system too.

Any other app like Facebook Messenger, Telegram, or normal phone call all work well.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] XAedgeS:
Shoot, I forgot to attach log, the log for upper problem is here. I log it start at when I open Discord until the phone crashed to bootloop.

Log
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Jann F:
@theimpulson thanks for your work!

I have a problem with the recovery as I only get a black screen after booting to it.

I already opened an issue on the Lineage gitlab and put some dmesgs in there.

recovery on PL2 (Nokia 6.1 2018) only boots to black screen. (#4170) · Issues · LineageOS / issues / android · GitLab

Expected Behavior After flashing the lineage recovery via "fastboot flash boot $recovery" and rebooting to recovery I expect the recovery screen...

gitlab.com

There seems to be different display revisions for PL2 and the dsi kernel module in the lineage recovery throws stack traces and timeouts.

Maybe you can have a look into it?

I have two devices that behave exactly the same.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Jann F:
Ping, maybe @npjohnson could have a look into it since he's listed as maintainer too?
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] npjohnson:
It requires a newer DRG firmware, that simple.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Jann F:
How to get that newer DRG Firmware?

If you tell me how, I'll test it and make a PR for the Wiki. :)

Edit: it's not the DRG (6.1+) I'm talking about, it's the PL2 (6.1) on last/latest firmware.

dmesg is in the Los bug tracker with you mentioned.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Jann F:
@npjohnson can you please have a real look onto it?

This is not an DRG issue, but an issue with the PL2 dsi driver. The PL2 was on latest/last firmware already.
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] allbellerose:
Hi, i've been running lineageos on my 6.1 plus since the day it was released as officially supported, i love it, mostly, i did an update once, and i had to factory reset the phone to do it, and since i still have issues with apps loosing their settings, i wanted to update to latest build to see if it was fixed. i used the update function in the settings, when it reboots, it loops a few times then end up in recovery with either try to boot again or factory reset. Am i doing something wrong? i would really like to not have to reinstall everything again

i don't know if my update problem is related, but right now, anything from fdroid, like newpipe, otp+, and a bunch of others i tried just do not have persistant settings: if i close the app, and reopen it, it lost every settings i put, that includes fdroid.

most apps from aurora store works, so i got around the opensource stuff that don't work. i don't have any gdapp, and would like to never have them.

the build i use is the: RQ3A.211001.00110035887

edit: typo
[Nokia 6.1/6.1+/6.2/7/7+/7.1/7.2 Cross Device Devel] Jann F:
@npjohnson can you please have a real look into this?

It is a PL2 issue and not DRG and if you have a look into the dmesg in the LineageOS Bugtracker, you see what I mean.

As I said, I am on the latest official PL2 Firmware when trying to use the LOS recovery.