Please use whatever works for now. I am quite busy in real life so won't be much of help.Hi, I have a TA-1089, i see a lot of replies about the lineage os recovery not working. is the lineage os recovery working now or should I just go with TWRP?
Please use whatever works for now. I am quite busy in real life so won't be much of help.Hi, I have a TA-1089, i see a lot of replies about the lineage os recovery not working. is the lineage os recovery working now or should I just go with TWRP?
Hello!Well, I'm back where I started: TA-1050 in a boot-loop. I was using it in the rain, and it went rapidly downhill to this condition. Having dried it out, I can get it running in Fastboot mode, or in a blank-screen Recovery mode.
I had previously loaded & used LOS 18.1 successfully by doing the following:
INSTALL RECOVERY ROM$ fastboot getvar current-slotcurrent-slot: b$ fastboot flash boot lineage-18.1-20210406-recovery-PL2.imgSending 'boot_b' (36929 KB) OKAY [ 1.135s]Writing 'boot_b' OKAY [ 0.304s]$ fastboot rebootISSUE:Current LineageOS recoveries for Nokia 6.1 will load ok, but the display is blank!!!WORKAROUND: Reboot to recovery:VOL-, VOL- (Factory Reset), PWR(Format Data) PWR, VOL-, PWRVOL- (Format Cache), PWR, VOL-, PWREither tap the screen where the Back arrow is hidden, or reboot to recovery againVOL- (Apply Update), PWR, PWRYou're in sideload mode!INSTALL LINEAGEOS$ adb sideload ~/Downloads/lineage-18.1-20210406-nightly-PL2-signed.zipTotal xfer: 1.00xReboot to Lineage!
Yes, same here, and it's commonly reported.
Thanks, I managed to do the following:
Thanks, I managed to do the following:
1. Reboot to (invisible) Recovery: hold PWR & VOL+
(I had already installed lineage-18.1-20210406-recovery-PL2.img a few months ago)
2. Apply Update / Sideload: VOL-, PWR, PWR
3. $ adb devices: PL2GARD892202000 sideload
4. $ adb sideload ~/Downloads/lineage-18.1-20210406-nightly-PL2-signed.zip
5. Reboot: hold PWR
still seems to boot to recovery mode :-(
6. Reboot to FastBoot: hold PWR & VOL-
7. $ fastboot reboot
Rebooting FAILED (Status read failed (No such device))
fastboot: error: Command failed
8. BUT the phone rebooted to LineageOS setup screen!!!
Unfortunately all my apps & data have disappeared, but I suppose that is expected behaviour...
- No idea on AudioFX issueHello, I have been using this great custom rom (LineageOS 18.1 official) for more than a week, I have found these errors.
-The AudioFX equalizer sometimes does not apply the configuration with Bluetooth headphones, sometimes it crashes without making any changes in the sound update, despite being configuring the application at the moment, the sound does not represent any improvement, so it is a little annoying.
-It does not work to share the screen to the smart tv by direct Wi-Fi, the application closes every time I try to make that connection.
-In very few occasions screen duplication fails to watch videos, leaving the video distorted in full playback.
-Netflix is not available in the play Store, indicating that the device is not compatible with the version (in some unofficial versions of custom rom, Netflix is available for installation from the play store).
-The option to increase the internal storage by high-speed microSD is not available (it is a section that I would like to see it work, since there are some Nokia 6.1 models, which only have 32GB of internal memory, having about 16GB of available memory to install large applications, I personally find that it is a somewhat limited storage).
-It would be great if these problems had a solution
-In the other functions, the device works excellent, a fairly stable rom, well done, achieving better performance than the latest version of the manufacturer (Android 10), which personally, is a version practically poorly optimized for the device, with variety of failures in some of the functions offered by the android version. Surpassing the performance offered by the latest version of android 10 from the manufacturer, the only thing missing is the possible solutions to the problems that I have mentioned in this rom that has spectacular performance.
Your prompt response would be great theimpulson , I have to congratulate you for your great work for the great optimization of the android 11 version for this device.
-Excuse me for my English, it is not very good that we say :/.
Thank you very much theimpulson for responding .- No idea on AudioFX issue
- That's due to outdated libraries from Android 10 being used on Android 11 ROM. I plan to update them from Nokia 7.2 once their stock ROM gets an Android 11 update. That would fix it.
- No idea on that
- That's due to failing CTS which LineageOS doesn't tamper with. I cannot do anything with that.
- I will do something for that, expect the next update to have it.
I agree with ya mate.Thank you very much theimpulson for responding .
-I hope that the CTS failure can be corrected by LineageOS.
-I will be attentive about the possible implementation of the function of increasing the internal memory by high speed MicroSD, the microSD that I plan to use would be the SanDisk Extreme PRO, with a reading speed of 170 MB/s and writing speed 90 MB/s, Speed class: 30.
-I am very happy for everything you have done for this mobile device and hopefully I can continue to support this device until the incorporation of another new version of android is no longer possible, so far, the performance of this rom It's brutal (Excellent performance at all times) .
-I have to congratulate theimpulson again for his great work with the adaptation of the android 11 version for this device (Nokia 6.1 2018).
2. CTS still fails (even tho I don't have magisk installed, therefore some banking apps are not working (only some of them work wich is still nice to see).
8. GPay is also not working (due to CTS failing, maybe???).
Well..yes. I was thinking about that already last night.AFAIK CTS will fail on LineageOS due to two things; an unlocked bootloader and a non-signed device ID. To circumvent this you sadly have to install Magisk. I recommend you find their github repo and follow the install instructions there, as any other place do download Magisk is potentially malware. You need the MagiskHide Props Config in order to spoof the device ID. That should be enough to pass CTS. Also make sure to hide Magisk from any apps that might look for Magisk.
Do this at your own risk, and follow Magisk's documentation closely. Whenever you get an OTA you will also have to go into the Magisk app after the installation and install it into the inactive slot, also you will probably have to reinstall Magisk through patching recovery or boot img.
Well, I also got the dark blue screen when I was taking photos with google's camera app. Yep. It happend from time to time (randomly). This rom needs some more work tho. Especially on bluetooth side and camera.I flashed Lineage 18.1 and then I installed TWRP. When I rebooted to recovery, it'll show a dark blue screen for a bit then go black, but ADB still responds. TWRP only works when booting from USB via fastboot. This dark blue screen also appears when I connect the charger to the phone to charge the battery, but the battery still charges fine.
Also, when I dirty flashed the new update that just came out after already clean flashing a previous 18.1 build, it would go to the boot animation and it would remain stuck there. I waited over an hour and it didn't come out of the boot animation. Thankfully, ADB still responds. I wound up doing a clean flash to the new version and it seems fine after that, though for some reason, Google Play kept throwing off "insufficient space" errors each time I tried to install an app, even though it was a clean reinstall, so after some digging around, I tried a second factory reset and cache clear in TWRP then reboot, set phone back up, then it had no trouble with Google Play after that.
I also experimented trying to boot into Lineage recovery via fastboot, but the phone rejects it for some weird reason and boots into the main OS instead.
One more thing I notice that the Lineage doesn't sense the phone is plugged into a fast charger and it instead charges the battery very slowly.
But I did use what wiki told me to. I used lineage os recovery to flash your rom, not anything else like twrp. Everything went smooth and nice at the begining until I discovered (in LOS 18.1) that bluetooth and camera are buggy, that's it.@CaptSmokey6 @warchild98 kindly read the 2nd post which clearly states that I won't entertain bug reports related to CTS, mods, or non-recommended recoveries. Also, this is the official builds thread. They have already started and they are stable for daily usage. Follow the instructions given in LineageOS Wiki. This device is already quite old and the performance hit that you feel from 17.1 to 18.1 will just increase on future android versions, nothing I can do about that.
I did made an attempt to install via the recommended recovery from the Wiki, but each time I try to boot from that recovery, my phone rejects it and boots straight to the main OS instead and I have used the fastboot method to try to boot from it. But the phone accepts the non-recommended recovery and boots into it without a problem.@CaptSmokey6 @warchild98 kindly read the 2nd post which clearly states that I won't entertain bug reports related to CTS, mods, or non-recommended recoveries. Also, this is the official builds thread. They have already started and they are stable for daily usage. Follow the instructions given in LineageOS Wiki. This device is already quite old and the performance hit that you feel from 17.1 to 18.1 will just increase on future android versions, nothing I can do about that.
Thank you so much to devs ...
About LineageOS
LineageOS is a free, community-built, aftermarket firmware distribution of Android 10.0 (Ten) which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS GitHub repo and if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website
Downloads Links
Official Website
Google Applications (optional) :
MindTheGapps (11.0, arm64)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
LineageOS clean install :
- Follow the instructions at Official Wiki
About the builds
- Device Side Sources are on official LineageOS org
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error and steps to reproduce it
LineageOS available for PL2 also thanks to :
- Google (AOSP)
- The LineageOS Team
- CodeAurora Forums
Beta Testing Telegram Group | Not required but donations are welcome: Paypal
XDA:DevDB Information
LineageOS-18.0, ROM for the Nokia 6.1 (2018)
Contributors
theimpulson, npjohnson
Source Code: https://github.com/LineageOS/android_kernel_nokia_sdm660
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest stock firmware
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 18.0
Stable Release Date: 2020-10-17
Created 2020-10-16
Last Updated 2020-11-12
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.
We can look into it!I noticed, that my device often runs out of memory, so i had a look into swap on zram. I found, that the files provided on the vendor partition contain entries for creating swap on a zram device:
Both/vendor/etc/fstab.qcom
and/vendor/bin/init.qcom.post_boot.sh
seem to do something for setting up zram and enabling swap.
After boot however/sys/block/zram0/disksize
shows "0".
Can swap on zram be enabled automatically?
I enabled zram and swap manually:
Code:echo 1 > /sys/block/zram0/reset echo 2G > /sys/block/zram0/disksize mkswap /dev/block/zram0 swapon /dev/block/zram0
Afterwards my device feels much more responsive, when switching between apps.
Except for doing these steps manually over the adb root shell, there remains one more thing, that might need tweaking:/sys/block/zram0/max_comp_streams
should probably be set to 4 to allow usage of either the fast or the slow cpu cores.