Beside the reboots - luckily had none the last couple of days - but the hlte is also draining it's battery very fast now. And even though I bought a new battery only a few month before the issues started it only lasts for ~ 24 hrs these days and that although the mobile is lying idle on a sideboard for 95% of the day.
(And yes, the new battery is really better, because when I put in the old one for the a test it lasted even significantly shorter than 24 hrs.)
Maybe I'm "going back in time" for a test: I still have the lineage-18.1-20210918-nightly-hlte-signed version on file, but would maybe sb be able to help out with an even older version, e.g. beginning of Sep (4th?)?
I tried to revert from lineage-18.1-20211120-nightly-hlte-signed back to lineage-18.1-20210918-nightly-hlte-signed, but without success, as it got into a boot loop after the downgrade. (Though I locked myself out in the beginning as I forgot to deactivate Smart Lock / display PIN, the device comes up and asks for the SIM PIN, but it reboots very shortly after that.)
First post here, I just want to say that I'm truly grateful that jprimero and haggertk were able to keep this Samsung Note 3 alive in 2021!I tried to revert from lineage-18.1-20211120-nightly-hlte-signed back to lineage-18.1-20210918-nightly-hlte-signed, but without success, as it got into a boot loop after the downgrade. (Though I locked myself out in the beginning as I forgot to deactivate Smart Lock / display PIN, the device comes up and asks for the SIM PIN, but it reboots very shortly after that.)
As I still have a spare hlte lying around - though its display is broken and due to a water leakage can't connect to a mobile network any longer - I maybe set it up with LOS as well and simulate a transfer to a "new" phone with all my apps and settings to see how long the battery will last in there, if there's no difference I thin lolz kernel might be worth a try, too - or in the end I have to bite the bullet going for a new mobile in the end ...
Worked like a charm, I just flashed Lolz (non-rooted) and I'm getting much better battery life (max 2%/hour idle consumption) and cooler temperatures (reduction of 2 degrees Celcius).
wich version of LOS 16?First post here, I just want to say that I'm truly grateful that jprimero and haggertk were able to keep this Samsung Note 3 alive in 2021!
I'm noticing quick battery drain as well (8.3%/h idle), it's a fresh install. GSM Battery Monitor says CPU (81%) --> Kernel (Android OS) (59.4%) and LineageOS (7.3%) are the top battery consumers.
I came from LineageOS 16.0 [Android 9.0] which worked fantastically.
Was the battery life good with the September 18th, 2021 release? I can't find an archive containing that version.
I really can't tell when the "battery draining" issue started for me on 18.1. However as I still had the 20210918 18.1 version on file I thought it would be a good test to see if it'd make a difference. (Again: if anybody else has still an even older 18.1 version I'd grateful be if that would be shared with me.)
I think the cure helped somewhat. While moving my profiles, apps, settings to my scratch spare hlte and after that back to my scratched "production" SM-N9005 yesterday evening seems to have helped to increase the runtime (Before ~ 24 hrs, prelimanry now > 2 days). Of course I 'lost' some of my settings during the migrations (e.g. VPN connections, coupled BT devices, FF settings, [local] calendar / contact settings for MyPhoneExplorer, apps installed via F-Droid, ...) however that "clean-up" was even necessarily intended. (That's why I also didn't want to use a tool like e.g. TitaniumBackup). In the meantime I could 'fix' most issues. Only the Amazon Appstore release-188.8.131.52.205427.0_801048010.apk causes me some headaches as it crashes when I started it. Thus I couldn't install my Amazon purchased apps like OSMand+, yet.
Thank you kind sir, youve saved my life, and my hltetmo life's. I was going absolutely crazy.
LOS 16 not 18.1 , maybe issue with last version...Is there someone that made Viber work with microG on this version of LOS?
Tried LOS18 with microG already installed on Note 3 but can't really seem to make Viber work for some reason. Contacted Viber support and they sent me a link where it says that Viber doesn't work on custom ROM, but it works fine on Note 4 with LOS16 and microG...
Looks like you haven't read this thread carefully, because if so, you should have come across my posts related to a similar battery draining issue and how I 'fixed' it ;-)
Clean flash without gapps and test, if no issues flash gapps, or change them..
Frankly I wouldn't just go back to an old backup if I wouldn't have a recent one. My recommendation is to do a clean install and (partially) restore the settings from a recent backup. (You should have a recent backup on-site anyhow to be prepared for a full restore, if anything might go wrong. Paranoid as I am I have several backup types: e.g. my actual TWRP Nandroid in my phone's flash, copies of those to a folder in my phone's SDcard (partition which is not mapped to extend the system) and a copies on my NAS, "system-build-in backups" via Google and Seedvault, and I sync my (local only) Calendar, Contacts via MyPhoneExplorer to Thunderbird. Rare Titanium backups as I find it too complicated in the free version)
|hltekor||SM-N900K, SM-N900L, SM-N900S|
|hltetmo||SM-N900R4, SM-N900T, SM-N900V, SM-N900W8|
Use odin to flash twrp.tar available from their official website, then download lineage zip from lineage website and place on sd card and download mindthegapps "search for lineage gapps you'll find links on their wiki", and finally boot to recovery to install lineage and gapps packages.Hello guys. This is my first time dealing with modifying my phone and I don't have any past experiences. I even made this account just to post this reply. So, please bear with me
I've been following the instructions here https://wiki.lineageos.org/devices/hlte/install and had problems with flashing the recovery with heimdall, it kept giving me this error:
I googled it and found that other users have had the same error https://github.com/Benjamin-Dobell/Heimdall/issues/191# but found no solution. I tried a different USB port and cable, still didn't work.Code:
ERROR: Failed to confirm end of file transfer sequence! ERROR: RECOVERY upload failed!
I assumed that this is some heimdall issue and tried flashing directly with adb by following these steps https://www.xda-developers.com/how-to-install-twrp/ but this time I got "waiting for any device" although my phone appears when typing the command "adb devices"
Googling told me that this is some sort of a driver issue. Maybe has something to do with zadig.exe (that came with heimdall) and the whole driver replacing process?
Now I'm stuck between these two problems, and I don't know what to do. Is there other ways to flash the recovery? Or what can I do to fix the problem with drivers?
Any help would be much appreciated.
in short: yes