• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

LineageOS 19.0 Android 12 for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 ALPHA

Search This thread

Alexfs

Senior Member
Oct 7, 2014
68
29
My friend Html6405, I am very impressed with the work you have been doing for our tablet. You could post a step by step how we can increase the space for the system on our device. I think it would be very useful in the future as we could take advantage of more system resources that you have to limit due to the limited space available.
Thanks again for keeping our tablet alive.
 
  • Like
Reactions: html6405

html6405

Recognized Developer
The question is: Will we have a way around this and install 64bit apps on our tablet?
I'm sorry, this won't be possible.
What I know is:

Starting August 1, 2021, Google Play won't serve apps without 64-bit versions on 64-bit capable devices. Users with 64-bit devices simply won't see 32-bit only apps in Google Play, including games built with Unity 5.6 or older.

"We are not making changes to our policy on 32-bit support. Play will continue to deliver apps to 32-bit devices. This requirement means that apps with 32-bit native code will need to have an additional 64-bit version as well," Google Play and Android product managers note in a blog.
(source: https://www.zdnet.com/article/googl...wners-no-more-32-bit-only-apps-from-aug-2021/)

So let's hope that most app developers still provide a 32 bit version, than we are safe.
 
  • Like
Reactions: phubarr

html6405

Recognized Developer
You could post a step by step how we can increase the space for the system on our device. I think it would be very useful in the future as we could take advantage of more system resources that you have to limit due to the limited space available.
Sure, but I the limited resources (only some animation stuff and rounded corners etc) are only because of our old hardware,
there would be enough system size.
At the moment, a bigger system space is only needed if you wan't to flash gapps bigger than pico (which are also slowing down our device much), or if you plan to flash a GSI, but there are not really interested builders and I don't have time for all projects.
 
  • Like
Reactions: phubarr
Oct 11, 2016
27
19
Welp tried to flash it and just realised that the device volume down button is stuck and always boots to safe mode, any workarounds ? also is it possible to modify the kernel to make the device turn on when the charger is plugged in ?
 

html6405

Recognized Developer
Welp tried to flash it and just realised that the device volume down button is stuck and always boots to safe mode, any workarounds ?
I would try to pull the volume button out of the case, remove possible dirt and stick it back in.
also is it possible to modify the kernel to make the device turn on when the charger is plugged in ?
Yes, but I'm not sure if this is in the interest of all people.
 
  • Like
Reactions: themediapadguy

Alexfs

Senior Member
Oct 7, 2014
68
29
Sure, but I the limited resources (only some animation stuff and rounded corners etc) are only because of our old hardware,
there would be enough system size.
At the moment, a bigger system space is only needed if you wan't to flash gapps bigger than pico (which are also slowing down our device much), or if you plan to flash a GSI, but there are not really interested builders and I don't have time for all projects.
Thanks for your clarification. I know your time is valuable and you have other projects, this tablet is very important to me, and seeing it updated with the latest android version is really magnificent. I just have to thank you for not leaving us.
 
  • Like
Reactions: html6405
Oct 11, 2016
27
19
I would try to pull the volume button out of the case, remove possible dirt and stick it back in.

Yes, but I'm not sure if this is in the interest of all people.
Yes I tried that, didnt work, checked it on hardware level and looks like something is short to ground on the button circuit or a filter has gone bad, Also I think this might spread to the power button as well rendering the device completely unusable. A poll would be nice for people to vote as I have a doubt if these capacitors are dying in this device and could render our device as a brick as I have tried the 300k method and the device did not react. I know you are limited of time but I think it might be a good thing to do ig ?
Anyways if someone else has this problem, press all buttons on the device and it will boot, but to safe mode, to fix that, you can disable the vol down key on software level, there are plenty of tutorials in Google.
 

LightingX

New member
Nov 24, 2021
3
2
Alright, got a list of bugs to help get this out of alpha /Tested on GT8000N/

Settings :
-Quick/Notification bar settings don't adjust the correct way when in portrait
-Cast Screen will put the device into reboot then wifi won't work until you manually reboot again
-Display>Color is simply Empty for some reason
-Status Bar modification not working

UI/UX :
-Flashlight Not working (Error in log cat)
-Lock screen lock is upside down
-Portrait mode to the left don't show the turning icon while on the right shows it on the left side making it hard to reach
-Screen brightness slider is not calibrated
-When an app launches, the app preview icon is blurry

Logcat/Internal errors (all in the Catalog File) :
-Seems to be a problem with wifi , (E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.1168) failed {.code = ERROR_UNKNOWN, .description = unknown error}) happens on idle a lot around once every 2-5 sec
-System server cant obtain CPU frequency count
-Some RIL problem
-Display Config is confused for nits mapping when unlocking the Device
-Touch Controller Giving an error sometimes

~(LX) <3
 

Attachments

  • GT8000Ncatlog.txt
    8.8 KB · Views: 14
  • Like
Reactions: html6405

html6405

Recognized Developer
Settings :
-Quick/Notification bar settings don't adjust the correct way when in portrait
-Cast Screen will put the device into reboot then wifi won't work until you manually reboot again
-Display>Color is simply Empty for some reason
-Status Bar modification not working
These things could get solved from LineageOS, it's really also an early on there side.
-Flashlight Not working (Error in log cat)
Yep, I think this is because we have to use camera hal v1 to run on Android 12, maybe I will find a solution for this.
-Lock screen lock is upside down
-> LineageOS
-Screen brightness slider is not calibrated
-Display Config is confused for nits mapping when unlocking the Device
Because of the changed auto brightness behaviour of Android 11 and 12,
our old defined auto brightness array and lux values doesn't fit anymore.
NITS defines how much brightness a display emits, I don't have any values for them and no measuring device.
(We would have to measure stepwise to define the array)
Maybe a will define and test an array from an other device later.
-When an app launches, the app preview icon is blurry
It's the same as on LineageOS 18.1, I'm not sure why, if I build AOSP all icons have a fitting resolution.
-Seems to be a problem with wifi , (E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.1168) failed {.code = ERROR_UNKNOWN, .description = unknown error}) happens on idle a lot around once every 2-5 sec
I don't know what ERROR_UNKNOWN is, I will check this.
-System server cant obtain CPU frequency count
Maybe because of the missing power hal.
Which ones? Had no problems on my n8000 so far.
BTW because we are using old blobs, some log stuff can be ignored as long it works.

-Touch Controller Giving an error sometimes
They can be also ignored, they were alway's there.

But in generell, I will try to fix all important stuff step by step,
it just will take time.
 

html6405

Recognized Developer
Yes I tried that, didnt work, checked it on hardware level and looks like something is short to ground on the button circuit or a filter has gone bad, Also I think this might spread to the power button as well rendering the device completely unusable.
You could send me a picture if you wan't, I'm a professional.
The button costs peanuts from china and is easy to change.
 

Chaonenglx

New member
Nov 16, 2019
3
0
Thank you for your excellent work! Here is a problem that my n8013 can not really power off even if I long press the power button, and it just keeps starting from the "Galaxy Note 10.1" screen. Also, I can hardly enter the TWRP by hold power and volume up. ADB command to reboot to rec and download mode don't work, either.
 

html6405

Recognized Developer
Thank you for your excellent work! Here is a problem that my n8013 can not really power off even if I long press the power button, and it just keeps starting from the "Galaxy Note 10.1" screen. Also, I can hardly enter the TWRP by hold power and volume up. ADB command to reboot to rec and download mode don't work, either.
This weird problem exists since Android 11, I think it's because of the changed boot behavior (and our old bootloader).
It work's sometimes, sometimes not.
There's no solution at the moment to fix this.
 
  • Like
Reactions: phubarr

Chaonenglx

New member
Nov 16, 2019
3
0
This weird problem exists since Android 11, I think it's because of the changed boot behavior (and our old bootloader).
It work's sometimes, sometimes not.
There's no solution at the moment to fix this.
Thanks a lot. But sadly here is another problem that I find my TWRP doesn't work. I reflashed TWRP with Odin, but couldn't enter, only boot screen kept showing up.:cry:
That happened after I got Los 19 flashed.
 

LedgendaryEpics

Senior Member
Jun 14, 2018
96
23
Woah... Going from android 7 to 12 is a jump. My first experience from android 12 would be a tablet too old to remember ...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Update 28.12.2021:
    • Created workaround to fix shutdown / reboot behaviour with Magisk
    • Fixed video recording with camera's
    • Fixed Torch (flashlight)
    • Fixed hardware button gestures control
    • Fixed GPS week rollover issue
    • Set swappiness to 60
    1
    Hi,
    I'm using this rom and I intend to keep it until we reach the final version or the arrival of the Version with Android 12L
    I hope that there will be a version from LineageOS, otherwise I would have to fork the Android 12L repos and also have to port everything, but we will see.
    1 - Even without Magisk the lightning on the screen still exists. (I only used magisk to install the Viper4 Audio Module, but I figured out how to install the module's drivers without magisk via a ZIP file via TWRP.)
    Thx for your report, good to know.
    2 - The device restarts when I plug in the headphone.
    Ah ok, I will test this soon and bring a fix.
    3 - Sometimes the screen goes dark and you have to force the restart.
    I've never faced this, maybe you could create a dmesg when this happens?
    4 - The pen response still seems slow, I have to press more for the writing to come out.
    But I have to congratulate the great work you have done for our device.
    The PEN should work exactly as it did on LineageOS 18.1, nothing related changed.
    1
    Ah, honestly I don't wanted to push this update to everyone, only for myself.
    But good to have your report, that the screen lightning bug got worse with this attempt...
    OK,
    Glad I can help in any way. You do a great job. I wanted to have knowledge to contribute more. It would be nice if more developers were interested in our device, it is still very good.
    I'm glad you didn't abandon us!(y)(y)😊
    1
    hello,
    i correctly flash la rom on my n8020 with TWRP 3.5.2 but don't boot. The tablet return to twrp. I tried with different versions of twrp and different zip but nothing. Any solutions? thanks
    Hmm do you see the LineageOS animation at all?
    Did you try to install the ROM clean?
    Which ROM was installed before?
    1
    lineage 19 not boot
    No erors from TWRP. The flash look ok but dont't boot
    Does it stay at the Samsung Galaxy Note 10.1 boot picture or does it reboot into TWRP?

    It could help to force a reboot if it stay's like this, give it some attempts, some people reported that they can't boot out of TWRP.
  • 11
    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 version of LineageOS 19.0 for our Samsung Galaxy Note 10.1 devices.
    At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.

    This is a early ALPHA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!

    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
    • Bluetooth
    • Audio
    • Graphics
    • Cameras
    • Sensors
    • GPS
    • Wifi
    • 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...
    • Video recording with both cameras
    • N8020: RIL
    • Random reboots
    • Maybe more
    • Screen lightning bug
    • SD-Card can't be formatted as internal storage, this will cause a bootloop
    If you don't like it, reboot into recovery and type the following command:
    If you are going to use BitGapps,
    here you can download them:
    BitGapps, arm, 12
    For the others, you can use microG in future.

    If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
    In some cases the sim card becomes unusable while typing in the code.

    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

    XDA:DevDB Information
    [ROM][12.x][N8000/N801x/N8020][ALPHA] LineageOS 19.0, ROM for the Samsung Galaxy Note 10.1

    Contributors

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

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

    Version Information
    Status:
    Alpha

    Created 2021-11-18
    Last Updated 2021-12-28
    4
    Update 29.11.2021:
    • Fixed GPS
    • Fixed sw decoder issue
    • Fixed deep sleep bug, deactivated sec_keyboard dock service for now
    • Enabled 1704 MHz overclocking (1600 is still set as default)
    • Fixed Kernel to support NetGuard
    4
    Update 23.11.2021:
    • Fixed Bluetooth
    • Brought Livedisplay entry in settings back
    • Fixed partly Tethering
    3
    Update 23.11.2021:
    • Fixed Bluetooth
    • Brought Livedisplay entry in settings back
    • Fixed partly Tethering
    Thank you for all your hard work! I'm running this ROM currently and so impressed by the smoothness and speed throughout. Thanks again!
    3
    Settings :
    -Quick/Notification bar settings don't adjust the correct way when in portrait
    -Cast Screen will put the device into reboot then wifi won't work until you manually reboot again
    -Display>Color is simply Empty for some reason
    -Status Bar modification not working
    These things could get solved from LineageOS, it's really also an early on there side.
    -Flashlight Not working (Error in log cat)
    Yep, I think this is because we have to use camera hal v1 to run on Android 12, maybe I will find a solution for this.
    -Lock screen lock is upside down
    -> LineageOS
    -Screen brightness slider is not calibrated
    -Display Config is confused for nits mapping when unlocking the Device
    Because of the changed auto brightness behaviour of Android 11 and 12,
    our old defined auto brightness array and lux values doesn't fit anymore.
    NITS defines how much brightness a display emits, I don't have any values for them and no measuring device.
    (We would have to measure stepwise to define the array)
    Maybe a will define and test an array from an other device later.
    -When an app launches, the app preview icon is blurry
    It's the same as on LineageOS 18.1, I'm not sure why, if I build AOSP all icons have a fitting resolution.
    -Seems to be a problem with wifi , (E WifiVendorHal: getWifiLinkLayerStats_1_3_Internal(l.1168) failed {.code = ERROR_UNKNOWN, .description = unknown error}) happens on idle a lot around once every 2-5 sec
    I don't know what ERROR_UNKNOWN is, I will check this.
    -System server cant obtain CPU frequency count
    Maybe because of the missing power hal.
    Which ones? Had no problems on my n8000 so far.
    BTW because we are using old blobs, some log stuff can be ignored as long it works.

    -Touch Controller Giving an error sometimes
    They can be also ignored, they were alway's there.

    But in generell, I will try to fix all important stuff step by step,
    it just will take time.