For all people out there worried about Android L
update,
Our device specs definitely supports L. The only
problem is the less internal storage we have
As Android L will run only on ART more storage is
required and upgrade will consume more memory.
We will have less internal storage.
One good hope is with Android L a better ART which
consumes less memory (as art was beta in KitKat, it was not completely flawless.
Android L is going to be a major update by Google in recent years,
so Motorola is now testing few builds related to Android L (not the original L as its not released) to see if it can sustain the major update.
But one this is for sure we will have a lot less internal storage I guess.
But in the END in am Confident #Motorola will release
Android L for us. I hope you understood my point.
We will surely get Android L
No idea how Motorola will manage space issue in Moto E. Currently with default apps itself its taking around 1.2-1.3 GB of internal memory . If we change to ART run time available space will become around 200 MB. Not sure how they will manage that.. Hope beta version ART only have this issue
yes it may be a issue with the beta build/...and motorola may change something in the android l for moto e..so that sd card memory can be used and reduce usage of internal..may be...lets see what happens
My hope as always is not with OEMs, but with independent developers who will release a L based custom ROM.
ART and the lack of space in our devices is indeed a problem, let's just see how optimized it becomes on the final build.
Sent from my XT1021
Or may be Android One for moto e next "major" update.
Google’s first super cheap ‘Android One’ phones may debut in September
Read more:*http://www.digitaltrends.com/mobile/google-android-one-launch-september-india/#ixzz3APtbWrTR*
Dhiraj said:
Or may be Android One for moto e next "major" update.
Google’s first super cheap ‘Android One’ phones may debut in September
Read more:*http://www.digitaltrends.com/mobile/google-android-one-launch-september-india/#ixzz3APtbWrTR*
Click to expand...
Click to collapse
Moto E will never get Android One for sure.
raj.amalw said:
We will surely get Android L
Click to expand...
Click to collapse
yes we will
SirRhor said:
My hope as always is not with OEMs, but with independent developers who will release a L based custom ROM.
ART and the lack of space in our devices is indeed a problem, let's just see how optimized it becomes on the final build.
Sent from my XT1021
Click to expand...
Click to collapse
Google will definitely optimise it to take lesser space
Moreover Android L will support permission to SD card
it has been acknowledged in their developer site. so we just need patience
let the time pass.
-Adarsh- said:
yes it may be a issue with the beta build/...and motorola may change something in the android l for moto e..so that sd card memory can be used and reduce usage of internal..may be...lets see what happens
Click to expand...
Click to collapse
Changes in Android L —
SD card permission granted (for apps)
better art (faster and optimised for less space)
So we have more than 90% chance to get L
AnishTS said:
No idea how Motorola will manage space issue in Moto E. Currently with default apps itself its taking around 1.2-1.3 GB of internal memory . If we change to ART run time available space will become around 200 MB. Not sure how they will manage that.. Hope beta version ART only have this issue
Click to expand...
Click to collapse
new in android L
SD card permission granted (for apps)
better art (faster and optimised for less space)
so we will get L more than 90% sure
still let's see
let some time pass.
Everything depends on the final build of L, how much google will optimize art to run on low space devices .That's why it is not still confirmed for E.
OMG
OMG you made me so happy telling that sd card permission will be back..wwooooowwwwwwwwwwwwwwww.....yaaahhhoooooo......
-Adarsh- said:
OMG you made me so happy telling that sd card permission will be back..wwooooowwwwwwwwwwwwwwww.....yaaahhhoooooo......
Click to expand...
Click to collapse
you are welcome
Dhiraj said:
Everything depends on the final build of L, how much google will optimize art to run on low space devices .That's why it is not still confirmed for E.
Click to expand...
Click to collapse
just to create speculation Motorola is not confirming
suddenly after sometime they will confirm and all will say Motorola is such a great company. part of business.
@SidDev said:
just to create speculation Motorola is not confirming
suddenly after sometime they will confirm and all will say Motorola is such a great company. part of business.[/QUOT]
Google one is coming in next month .Final build of L may be in November. In between that Micromax like company will release One based device within 10K INR . So, there will be tough competition for Motorola.
Click to expand...
Click to collapse
Dhiraj said:
@SidDev said:
just to create speculation Motorola is not confirming
suddenly after sometime they will confirm and all will say Motorola is such a great company. part of business.[/QUOT]
Google one is coming in next month .Final build of L may be in November. In between that Micromax like company will release One based device within 10K INR . So, there will be tough competition for Motorola.
Click to expand...
Click to collapse
tough competition will lead to update to make moto e interesting
you think and BTW its Android one and not google one.
Click to expand...
Click to collapse
Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..
Hi, I'm not an Android expert in any way but I'm prototyping an app that runs Tensorflow deep learning models for image processing on this tablet.
I convert various models from Keras to TF-Lite in various modes, trying to find the best-performing method - comparing normal FP32 with quantisation to FP16 and INT8, and running each in CPU mode and on the GPU and NNAPI delegates.
NNAPI is supposed to assign compatible operations to the chip that runs them fastest, ie most INT8 stuff to the Hexagon DSP. Except my timings show 8b models running faster in CPU, or no difference, or worse, like it's always falling back to CPU. Suspicious!
Looking at the ai-benchmark com ranking (sorry, new account, can't do links) rankings and comparing the Tab S6 with a high-performing SN855 device like the Galaxy S10+ shows that their CPU perf is more or less equal, but quantised perf is WAY too low on the Tab S6.
From the paper arxiv org 1810.01109.pdf
...Qualcomm delivers these drivers in the software images provided to its OEM customers, which then in turn determine when and how to include them to end devices: with their initial release or later over the air in subsequent software updates. As a result, their presence and actual version might vary significantly across the phones on the market.
Click to expand...
Click to collapse
This suggests to me that Samsung haven't bothered including the NNAPI drivers for the tab S6! So what, they only do it for the premium products? Personally I'd say a £600 tab is pretty premium.
Am I right about this and if so is there anything I can do? Any way to get the drivers in, a custom ROM that includes them? I'd buy something else but there's not a lot of choice with tablets, this seems to be the most powerful one available. I'd love one with a Kirin 990 but no such thing exists yet AFAIK.
"Qualcomm’s first NNAPI driver for running quantized neural networks on Hexagon DSPs was introduced in the Android
O-MR1, though it was not used in any commercial devices
at that time and first appeared only later in the OnePlus 6
and Xiaomi Mi8 with the next Android version. In Android
P, these drivers got additional support for running float models on the Adreno GPU. Yet, they are currently not present
in the market."
I'd say there is little to no support by OEMs
gottahavit said:
...
I'd say there is little to no support by OEMs
Click to expand...
Click to collapse
The ai-benchmark com ranking list (that i can't link) shows many Snapdragon 855 devices with high performance that can only be due to NNAPI support I believe. But anyway, as there aren't any better tablets about, I wonder if there's a way to make a ROM that adds those drivers? I know nothing about custom Android builds.
Hello everyone i am about to get tab s7+ and i love the table just one question we have root and twrp why there is no custom rom and if i am rooted how to update the software also what do i lose with root what magisk don't fix? Thanks in advance
Hi. I think the lack of custom ROMs is because the device is fairly new - hence - not that popular, additionaly being an Android tablet. I ditched my Iconia A500 years ago and never thought I would go for a tablet again until this gem came out. I would recommend you to try it first for some time and play with it because there are tons of features (literally) in this device that would doubtedly work on any custom ROM in the beginning. At least that's my personal opinion - stick with stock for some time. Samsung have done a really great job! ....And what's more - Android 11 with One UI 3.1 is rolling out these days. It will allow you as far as I've heard to use Google discover on your foremost left screen instead of Samsung daily.
drkalo said:
Hi. I think the lack of custom ROMs is because the device is fairly new - hence - not that popular, additionaly being an Android tablet. I ditched my Iconia A500 years ago and never thought I would go for a tablet again until this gem came out. I would recommend you to try it first for some time and play with it because there are tons of features (literally) in this device that would doubtedly work on any custom ROM in the beginning. At least that's my personal opinion - stick with stock for some time. Samsung have done a really great job! ....And what's more - Android 11 with One UI 3.1 is rolling out these days. It will allow you as far as I've heard to use Google discover on your foremost left screen instead of Samsung daily.
Click to expand...
Click to collapse
great advice you changed my mind and I am running a dual booted oneplus 6t and I won't do stock. But like you said tons of stuff on this gorgeous tablet. especially dex l have never used it that is awesome okay have a great day C-ya.
imzaki1994 said:
Hello everyone i am about to get tab s7+ and i love the table just one question we have root and twrp why there is no custom rom and if i am rooted how to update the software also what do i lose with root what magisk don't fix? Thanks in advance
Click to expand...
Click to collapse
A general thing to lose with root for all Samsung devices would be those Knox-related stuffs, namely Secure Folders.
I've been trying to boot a GSI on the tablet but up to now all attempts have failed. The tablet refused to boot, despite there were no problems with the flashing.
I personally don't really care about those Samsung features as I've very little use of them at the moment. I bought the tablet mainly for its size and its 120Hz display, but after using it for a while, it seems the tablet's stock firmware is indeed not good enough (especially with the Android 11 update) and unless there be plenty of hope for custom ROM/GSI, you'd better off getting a recent version of iPad Pro 12.9 inch for nearly the same price, if rooting is not important.
LSS4181 said:
A general thing to lose with root for all Samsung devices would be those Knox-related stuffs, namely Secure Folders.
I've been trying to boot a GSI on the tablet but up to now all attempts have failed. The tablet refused to boot, despite there were no problems with the flashing.
I personally don't really care about those Samsung features as I've very little use of them at the moment. I bought the tablet mainly for its size and its 120Hz display, but after using it for a while, it seems the tablet's stock firmware is indeed not good enough (especially with the Android 11 update) and unless there be plenty of hope for custom ROM/GSI, you'd better off getting a recent version of iPad Pro 12.9 inch for nearly the same price, if rooting is not important.
Click to expand...
Click to collapse
Sorry but could you possibly share what's not good about the firmware? I've never used such a feature rich device before and everything runs smooth as butter, I'm using it as screen extender for Win10 laptop, Chromecasting, Samsung Secure folder with encryption, deeply integrated with all Samsung apps, I connected my 2TB NTFS external HDD with Paragon's NTFS plugin that allows NTFS write operations, home Internet runs at impressive speeds (50 and more MB per sec download), I draw a lot and the only thing that I've changed is the launcher. Of course if custom ROMs support all of these features it would be perfect!!!
drkalo said:
Sorry but could you possibly share what's not good about the firmware? I've never used such a feature rich device before and everything runs smooth as butter, I'm using it as screen extender for Win10 laptop, Chromecasting, Samsung Secure folder with encryption, deeply integrated with all Samsung apps, I connected my 2TB NTFS external HDD with Paragon's NTFS plugin that allows NTFS write operations, home Internet runs at impressive speeds (50 and more MB per sec download), I draw a lot and the only thing that I've changed is the launcher. Of course if custom ROMs support all of these features it would be perfect!!!
Click to expand...
Click to collapse
You're right about the other features. For office/productivity works this tablet is an excellent choice.
On the other hand, this tablet's performance is very disappointing when it comes to gaming. I'm currently dealing with some touch-related issues when playing games (none of which would be a fatal issue for office/productivity), and comparing to my old tablets, I was expecting much more performance according to its specifications.
I think the tablet was never meant for gaming at all to begin with, however the specifications.
I'm working on a lineageos 18.1 bringup but this is the first time I'm dooing this, so I don't expect it to work very well. I'm fairly new to android development but recently I got official maintainer for resurrection remix for the oneplus 6 and 6T.
Here is my current progress, I will make the vendor repository next:
GitHub - Bush-cat/android_device_samsung_gts7xlwifi: Samsung Galaxy Tab S7 + (gts7xlwifi) Device repo
Samsung Galaxy Tab S7 + (gts7xlwifi) Device repo. Contribute to Bush-cat/android_device_samsung_gts7xlwifi development by creating an account on GitHub.
github.com
GitHub - Bush-cat/android_device_samsung_gts7xl-common
Contribute to Bush-cat/android_device_samsung_gts7xl-common development by creating an account on GitHub.
github.com