LineageOS 18.1 Android 11 for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 Beta EOL

Search This thread

html6405

Recognized Developer
Update 06.01.2022:
  • Fixed shutdown / reboot behaviour with installed magisk
  • Set swappiness to 60
  • Didn't changed anything related to the screen lightning bug in this builds.
But I will upload another build for the n8000 (lineage-18.1-20220106-HTML6405-n8000_TEST.zip), @jsmidev would be great if you could test also this build and compare them.
Depending on the screen lightning bug and the power consumption.
Every tester is welcome.
Now we have 2 different attempts, the best solution will stay so far (less buggy and better power consumption), at the moment we're using the second attempt.
 

jemm27

New member
Jan 9, 2022
3
0
Hi,
Can anyone help me understand as to why I am unable to connect to my wifi after installing the rom? That's the only issue I have after installation for my N8010
 

html6405

Recognized Developer
Hi,
Can anyone help me understand as to why I am unable to connect to my wifi after installing the rom? That's the only issue I have after installation for my N8010
Asnwered here already:
 

jsmidev

Member
Sep 27, 2016
43
10
I had left my n8000 with around 30% charge. After around 8 hrs it seems dead. Not turning on. No charging indications. Holding the power button for some seconds also didn't work. I had the Dec 14 update and was downloading the latest update, which I paused due to slow network. Any suggestions?
 

html6405

Recognized Developer
I had left my n8000 with around 30% charge. After around 8 hrs it seems dead. Not turning on. No charging indications. Holding the power button for some seconds also didn't work. I had the Dec 14 update and was downloading the latest update, which I paused due to slow network. Any suggestions?
Hmm could it be that your battery is < 3V?
Then it could take a while until it will be recognized again.

How long was it connected to the charger?
It may help, if you disconnect the battery shortly.
 

jsmidev

Member
Sep 27, 2016
43
10
Hmm could it be that your battery is < 3V?
Then it could take a while until it will be recognized again.

How long was it connected to the charger?
It may help, if you disconnect the battery shortly.
Didn't work this time 😕. It seems I'll have to bid farewell to you and this great endeavour. I have put it on charge for some time to see if something happens. Let's wait.
 

Alexfs

Senior Member
Oct 7, 2014
158
86
Didn't work this time 😕. It seems I'll have to bid farewell to you and this great endeavour. I have put it on charge for some time to see if something happens. Let's wait.
Hi
I've been through a similar situation. I thought I lost the device. But it turned out to be only the charging cable that was bad.
There was another situation where I could only recharge by putting it in download mode.
Don't give up.
 

jsmidev

Member
Sep 27, 2016
43
10
Hopefully it will boot up again, my fingers are crossed.
Charged it overnight for around 4 hrs. Not fixed, but there's some sign of life! Now it turns on when pressing the power key but keeps restarting itself after showing the initial Samsung Galaxy Note logo. There's some hope, and it seems the issue is something related with power and battery dept.

Update: It is booting to odin mode too now. Disconnecting the battery for some minutes didn't work. I'll try the same for longer duration after charging it again.

Also can I charge this with the battery cable disconnected?
 
Last edited:
  • Like
Reactions: 新郎官

html6405

Recognized Developer
Charged it overnight for around 4 hrs. Not fixed, but there's some sign of life! Now it turns on when pressing the power key but keeps restarting itself after showing the initial Samsung Galaxy Note logo. There's some hope, and it seems the issue is something related with power and battery dept.
Could you check the charging current with an USB amperemeter?
Maybe your cable is defective...
restarting itself after showing the initial Samsung Galaxy Note logo. There's some hope, and it seems the issue is something related with power and battery dept.
I woudn't try this too many times, if there's really less charging current, it could kill your battery.
Also can I charge this with the battery cable disconnected?
If you have a battery charger, you could load it extern.

But I'm a little bit scared, this would be again typical signs of a defectife eMMC,
if you can try to boot, download mode but can't boot into recovery...

In the EOL stage the eMMC's sometimes behave really crazy, they can't do anything for hours,
then suddenly download mode works again, but you can't flash (or you can flash sometimes but the files weren't stored etc)..

But to make this clear for myself, what happens if you disconnect the battery, reconnect it and try to charge it?
Will the battery icon be shown or what happens?
 

jsmidev

Member
Sep 27, 2016
43
10
Currently the situation is like this:

Boot loop as before. I can boot to odin and twrp too. But when booted to twrp it shows the initial twrp logo screen and again restarts and then keeps restarting.

Shows that big empty battery image for a while when charging first time after disconnecting the battery. Then it's the boot loop.

Unfortunately I don't have usb amperemeter etc 😕.

The cable looks fine as the battery image shows for a while indicating that it's charging. Also the sequence of events seems to show that the issue isn't with the cable. The device was idle at 30% charge when I left it, and when checked back it was dead. Didn't look like it was due to a normally discharged battery as it should last longer. Normally I lose maximum 5% charge in an idle state for that duration.

In fact I had a couple of such unexpected power off incidents in the past few days. But it turned on after holding the power button a few seconds. In both incidents the battery showed 11% after powering on, without charging.

I'm also thinking about flashing the stock rom to see if it recovers. Should that work?
 

html6405

Recognized Developer
Currently the situation is like this:

Boot loop as before. I can boot to odin and twrp too. But when booted to twrp it shows the initial twrp logo screen and again restarts and then keeps restarting.

Shows that big empty battery image for a while when charging first time after disconnecting the battery. Then it's the boot loop.

Unfortunately I don't have usb amperemeter etc 😕.

The cable looks fine as the battery image shows for a while indicating that it's charging. Also the sequence of events seems to show that the issue isn't with the cable. The device was idle at 30% charge when I left it, and when checked back it was dead. Didn't look like it was due to a normally discharged battery as it should last longer. Normally I lose maximum 5% charge in an idle state for that duration.

In fact I had a couple of such unexpected power off incidents in the past few days. But it turned on after holding the power button a few seconds. In both incidents the battery showed 11% after powering on, without charging.

I'm also thinking about flashing the stock rom to see if it recovers. Should that work?
Ok, if your data isn't important, you can try to flash with Odin.
This also could confirm if your eMMC is broken.
 

jsmidev

Member
Sep 27, 2016
43
10
And finally it seems it's the end of life for my beloved n8000, as @html6405 mentioned.

Tried flashing stock rom, recovery etc. using odin. When rebooting it showed the welcome screen of the same old twrp and returned to boot loop suggesting that it's not taking anything anymore...

RIP.

Had been personally attached to this great device, my first smart/touch device, which had been with me since 2014. That's 8 long years. Brilliant!

Unlike many other users, I'd been using this as my primary tablet till its end.

I may not be taking it to the service centre, rather would like to keep it with me for memory.

And the brilliant performance has made me confident about Samsung. Hopefully I'll get a Samsung Galaxy Tab S6 Lite soon.

And my heartfelt thanks to @html6405 and a couple of other developers who kept it alive and healthy throughout these years ♥️♥️. Except for that username @html6405 , I don't know who you're or where you hail from, but I'm thankful to you on behalf of my n8000. @lirokoa, @Don Carnage too.

It's sad to have to bid farewell to this endeavour and this community. But everything has the end of its life.

Hopefully I'll be around here with my new device.

Thank you all once again. Hats off to your commitment and dedication.

It had been a great journey with all of you!
 
Last edited:

ssnnmm

Member
Dec 13, 2021
10
0
The latest version of ROM (20220107) greatly shortens the standby time (no SIM card is inserted, only WIFI is connected) ...
 

dazzawill

Senior Member
Mar 13, 2011
95
6
Can someone please confirm one way or another that the GPS and in particular, the Compass works correctly in this rom, as I use my N8000, primarily for mapping. I tried the LS16.0 last year and whilst the Rom is fantastic, these issues were a deal breaker for me on that rom. Thanks
 

dazzawill

Senior Member
Mar 13, 2011
95
6
Nevermind. I tried the rom and although the gps seems ok, the Compass is not. The compass is not showing correct positioning and is extremely erratic. Its a shame cause the stock rom is just too old to run most apps and this rom as fantastic for everything else
 

Top Liked Posts

  • There are no posts matching your filters.
  • 72
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    *
    */


    Hi,

    here you can find my preview build version of LineageOS 18.1 for our Samsung Galaxy Note 10.1 devices.
    At first I want to thank @forkbomb444, @rINanDO, @ChronoMonochrome for all your work which helped me a lot to bring this up.

    This is a early BETA build, so don't install it if you want a completley stable rom and don't report my already listet bugs!

    I'm working nearly every day on our N80xx devices, because LOS18 runs much smoother than LOS17.1, I will continue here.

    When you have BitGapps installed, you have to reflash them after every update!

    Here you can see how far everything is working for now.

    N8000, N8010, N8013, N8020:
    • Boot
    • Audio
    • Bluetooth
    • Graphics
    • Cameras
    • Sensors
    • Wifi
    • GPS
    • USB
    • Video playback (HW/SW)
    • Tethering via USB, WIFI and Bluetooth
    • consumerir transmitter
    • Stylus with gestures and hovering icon
    • sec keyboard dock
    • RIL on N8000 (mobile connection)
    • much more...
    • Screen Cast, Chromecast did work, Samsung TV not
    • Main camera sometimes can't take a picture (reopen app or lower resolution)
    • Random reboots
    • N8020: RIL works 90%
    • Screen lightning bug, nearly eliminated
    • SD-Card can't be formatted as internal storage, this will cause a bootloop
    You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
    Or you try GPS Server Optimizer app for a faster 3D fix.
    For both methods you need root rights.
    If you are going to use Gapps,
    here you can download them:
    Open Gapps
    For the others, you can use microG in future.

    Do you like my work?
    Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
    I'm doing this in my free time and it also costs a lot of money to buy hardware.

    donate

    Wanna improve your sound configs?
    Now you can use my app to access all boeffla sound configurations.

    XDA:DevDB Information
    [ROM][11.x][N8000/N801x/N8020][BETA] LineageOS 18.1, ROM for the Samsung Galaxy Note 10.1

    Contributors

    html6405
    Source Code: https://github.com/html6405

    ROM OS Version: 11.x R
    ROM Kernel: Linux 3.x
    ROM Firmware Required: TWRP 3.4.0
    Based On: LineageOS
    Selinux: permissive, this only makes sense as soon the ROM is stable.

    Version Information
    Status:
    Beta

    Created 2020-12-21
    Last Updated 2022-04-15
    14
    This ROM is alpha, nobody can force me to bring any updates,
    I'm doing this in my freetime, so be thankful if you get something.

    I will proceed here as soon as I will have time, I didn't have LOS16.0 completed and I'm working hard to provide you a stable ROM.
    LOS 16.0 is our major version, on LOS18.1 is much more work todo and much more framework hackings to get LOS18.1 as good compatible as possible.

    I'm overtaking many things I make for LOS16.0 to 18.1, but this take's time.
    I hate it if I get stressed, so please be patent or do it by your own,
    this takes really much time, debugging, try things and so on.
    9
    Update 15.01.2020, N8000:
    • Fixed a problem with mobile data
    • Improved GPS, but it's still not perfect
    • Another stability fix
    Only via OTA.
    8
    Update 14.01.2021:
    • many stability fixes in kernel
    • many net back ports to improve kernel compatibility
    • improved performance
    • fixed audio and video recording
    • fixed samsung doze
    • Volume button wakeup crash fixed
    And again, don't forget to reflash BitGapps...
    7
    Update 11.01.2020:
    • Fixed LiveDisplay
    • Fixed GPS
    • Some optical improvements
    • Linked Magisk.zip for easy rooting
    • Some other small fixes
    If you update via OTA, don't forget to reflash the BitGapps if you had them installed,
    otherwise it wont boot.