Lenovo K3 NOTE LineageOS 14.1, Nougat 7.1 ROM

GCam Port | Google Camera APK v9.2 (April 2024) Forums Lenovo Device Forums K3 Note – aio_otfp Lenovo K3 NOTE LineageOS 14.1, Nougat 7.1 ROM

Viewing 10 posts - 11 through 20 (of 25 total)
  • Author
    Posts
  • #26505
    Linux User
    Participant

    [quote quote=26447]I have flashed the rom but have issues with the sims. I’m in india and using jio and airtel sims but none of them is working.Hope you can help me with that.
    [/quote]

    With which build are you facing this issue?? daniel_hk’s or Adeveloper79’s build ??

    #26568
    Linux User
    Participant

    I have done everything clean and i tried it maybe 10x and i dont know what to do.

    #26645
    Linux User
    Participant

    [quote quote=26568]I have done everything clean and i tried it maybe 10x and i dont know what to do.
    [/quote]

    What is the problem are you facing here??

    #30262
    Linux User
    Participant

    Hello devs,

    I would like to address some issues to you.

    1- There is a rapid Battery drain. My phone doesn’t lasts long more than 5 hrs.
    2- Phone wakes up on double taps even tho i ve disabled it in settings, so I have always an issue whenever I keep the phone in my jeans random apps starts up. so unfortunately i had to keep pattern lock.
    3- Bluetooth headset doesn’t connects in 1 go, i ve to enable disable Bluetooth several times.
    4- When in Bluetooth mode, sometimes call gets dialled automatically in background when phone is in my jeans & the dialled screen doesn’t shows & cant even cancel the call or restart the phone from power Button, I have to remove the battery & start the phone.
    4- Whenever i reinsert battery time get reset to 1 Jan-18 & sim-card doesn’t detects. I ve to go to recovery mode & install 3g+4g fix for the card to re-detect.
    5- OTA updates are not available so how should i update the OS?

    Please let me know if there any fix that i should perform in settings or its the OS itself problems.

    #12544
    Linux User
    Participant

    Ok, so I installed RENICE V6 custom kernel and that got it done. Amazing.

    #12550
    Linux User
    Participant

    Thanks for the information. Looks like the kernel image on the Lineage ROM is missing with double tap to wake functionality.

    #16909
    Linux User
    Participant

    I believe it’s just the assert() in the updater_script in the ROM which is causing this failure. It is risky to do so, but you can remove the assert() code from the updater_script of the ROM and flash the ROM.

    Why is it risky to do so?

    The ROM might be built only for the device codenames mentioned in assert() file and there by removing the assert() code you are allowing to flash this ROM in any phone. Yes, you read it right, in any phone. If it is not meant for your phone, then IT MAY BE BRICKED permanently. So, TRY AT YOUR OWN RISK.

    #11816
    Linux User
    Participant

    Hi I have installed the ROM prepared by Daniel_H_k on Lenovo K3 Note 50a40 using TWRP 3.# Custom Recovery, everything seems to be working alright. In India the Airtel SIM and Jio Sim were used, Jio sim takes time to register, VOLTE not available. also SMSC has to be fed manually (Which should not be the case). Its only 1 Days since installation. Will keep updated. Installed Gapps Pico 64 bit version. Seems to be working alright. Thank You so much. Looking forward for later releases with VOLTE support.

    • This reply was modified 19 hours, 46 minutes ago by Linux User.
    #16953
    Linux User
    Participant

    Yes, there is an assert in updater script and I could have modified it to allow installation on K50. But I knew its risky. That’s why I didn’t do it :)

    My point was
    1. why does it show the device codename as K50 (this is just for my understanding)? As I’ve read somewhere that K50a40 gets changed to K50-t5 when stock ROM gets updated to MM. But could not find any info related to K50.

    2. My main question was: Which ROM should I use for ‘K50’?
    Any idea?

    #16956
    Linux User
    Participant

    See the /system/build.prop file for more info about the ROM build that you are going to flash in your phone. If you are confident about the build based on the build.prop info then it should be fine to modify the updater-script file to remove the assert.

    As long as you have a NANDROID backup which can always take you to the last working state, it should be fine too.

    It’s for the users I write these disclaimers, because I never know how much knowledgeable they are to get the device back to work even after a soft-brick. In my own devices I don’t think much while doing these minor things, because I always know as long as my custom recovery is working I can get the device to working state.

Viewing 10 posts - 11 through 20 (of 25 total)
  • You must be logged in to reply to this topic.