LineageOS 19.1 (Android 12L) for GT-N8000 GT-N8005 GT-N8010 GT-N8013 GT-N8020 BETA

[Alexfs]

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.

 

[html6405]

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.

 

[html6405]

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.

 

[themediapadguy]

How much should I thank you for this. Absolute mad lad you are. Thank you for keeping this dead device alive.

 

[themediapadguy]

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]

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.

 

[Alexfs]

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.

 

[html6405]

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

 

[themediapadguy]

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]

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

 

[html6405]

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.

-Some RIL problem

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]

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.

 

[html6405]

Update 01.12.2021:

• Enable default power hal for all
• Fixed tethering completely

 

[Chaonenglx]

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]

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.

 

[themediapadguy]

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.

not a button issue, disconnected the button and still persists.

 

[Chaonenglx]

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.
That happened after I got Los 19 flashed.

 

[LedgendaryEpics]

Woah... Going from android 7 to 12 is a jump. My first experience from android 12 would be a tablet too old to remember ...

 

[LedgendaryEpics]

Hey, I have n8013 but I don't really see the files for it, just 8010, where can I find?

 

[html6405]

Hey, I have n8013 but I don't really see the files for it, just 8010, where can I find?

Just use the n8010 files, this is the international WiFi version.