AOSP on Galaxy Tab 3 10.1 - Galaxy Tab 3 General

So, i opened this therad because there no persons pushing and Developing custom AOSP Roms for the Galaxy Tab 3.
I'm opening it here because the Android Developing forum is a bit AFK.
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!

Curious..
superboom said:
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Click to expand...
Click to collapse
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?

chaoskoch said:
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
Click to expand...
Click to collapse
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...

Willing to get my hands dirty...
safariking said:
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Click to expand...
Click to collapse
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.

ush

AnthonyAlmighty said:
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
Click to expand...
Click to collapse
Anthony, I think one thing that is holding people back on this device is a good recovery. The ones available now are painfully slow. I'm guessing there is some power saving mode on the x86 chip that needs to be tweaked to get it performing well. Once that was fixed, it would be a lot easier to experiment with ROMs. -- Bud

Also Interested
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.

Br1cK'd said:
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Click to expand...
Click to collapse
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!

Ideas4ya said:
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Click to expand...
Click to collapse
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret

Meteore said:
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Click to expand...
Click to collapse
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.

mylifeandroid said:
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
Click to expand...
Click to collapse
It's ok I have already seen and tried them :laugh:. I understand the concept of work on something new and the lack of dev it's just that I was surprised because I thought tab 3 was like the others tabs so the development was more evolve.no problem.

Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style

Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
This is true but there is finally a bit of interest and may come up with some new goodies..... the reason they all have the same updater.script is because of the recoveries.... they need a little more work to get them to work with the x86 architecture
Sent from my GT-P5210 using xda app-developers app

Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
Hey PM me with any test builds of the kernels please.
Sent from my GT-P5210 using XDA Premium 4 mobile app

I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!

Calcu said:
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Click to expand...
Click to collapse
Dont understand your post.... the link goes to one of his posts
Sent from my GT-P5210 using xda app-developers app

Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2

Calcu said:
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Click to expand...
Click to collapse
Lol.... I see yeah... I am also in the process of building recovery but its a long time coming. Right now im reading a lot of material on how to build from source as that the route of the prob. Its this damb x86 architecture
Sent from my GT-P5210 using xda app-developers app

Maybe.... we can port something from here
http://www.engadget.com/2014/01/06/micromax/
Enviado desde mi Note 2

Push
If anyone have time, pm me and we can discuss about. I'm not a developer, but we can discuss ideas how to bring cm to the device

Related

Is it possible...

Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
You'd be better off asking the Infuse devs, I doubt any NS dev is going to be able to do anything to help you since they don't have the device to work on. The hardware is pretty similar so it could be doable but you're definitely going about it the wrong way.
DefinitiveX said:
Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
Click to expand...
Click to collapse
it is probably possible but you are likely to run into numerous errors, that is if you even get it to boot !
we just recently got jelly bean a few days ago and it is still improving so using that as base would likely result in a very unstable port.. but you are welcome to give it a try and see how it goes. the worst that can happen is having to go back to stock
if you happen to have a capable PC, you might want to try building your own rom from source! it should be a great learning experience and is much more likely to work compared to a port
DefinitiveX said:
Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
Click to expand...
Click to collapse
not sure about porting but there is a working JB rom on the Dev section
galaxy s line
i believe you'd actually be closer by using the CM10 for the fascinate that just landed yesterday, but i digress. the JB CM10 in the dev section is working better than CM9 for me.
I would definitely like to learn how to build a rom from source. But isn't there a lot of coding involved in that process? If there is, I would have to learn all that as I go. And I'm also going to check the development section right now, as soon as I post this reply. Seeing as I have a Nexus S and not an Infuse(my girlfriend does), I don't check this forum that often. Thank you all for the replies.
There are a few guides around that tell you how to set up the building environment on your PC, and how to sync repos and build for your device.
The complicated part might be fixing errors in your build , but thats how we all learn
Sent from my sweet and buttery Infuse

KitKat 4.4

Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
There will be peace in the middle east first. :banghead:
Sent from my SM-N900V using XDA Premium 4 mobile app
Just because they say it could run on lower end phones doesn't mean it will run w/o lag and so on. I heard the chez won't be getting kit Kat so what does that tell you about the older phones.
Sent from my HTC6500LVW using Tapatalk
The only thing that will run on lower end devices is the new launcher and Google apps. The new ui is supposed to be included in the new launcher and make lower end devices feel and look more like newer ones.
Sent from my ADR6425LVW using Tapatalk
lazarus0000 said:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
The problem with an upgrade to any newer OS on the Charge is the radios. I don't see KitKat and an exception.:crying::crying:
Interesting how they had it where you could use Hangouts as your default SMS App with all the Emoji smileys on phones with Gingerbread including the Charge on the leaked version from the Nexus 5. It was fully working and I tried it. However, now that it's released to everybody through the Play Store, the SMS option is for Android 4.0 Only.
just got kitkat on my razr.... wish I knew how to port, b/c then I would attempt to port this great ROM over to the old Charge....
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2284985
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
I think you're on the right track, though I think I'd stick with CM11 rather than CM10.2.
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
pyroman512 said:
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
Click to expand...
Click to collapse
good luck brother... i'd be glad to test for ya.
some tips that you may/may not already know:
my understanding is that OS 4+ require EXT4 rather than RFS, so it might help to start with a kernel that allows this conversion. there are a few floating around that work.
someone (JT) has successfully (and I guess relatively easily) ported ICS and JB to the charge, the key aspects not working though were mobile data and camera.
I'm told the key road block is the RIL for the kernel in order to get those aspects functioning properly.
as for me, I'd be happy with just a working camera, as the Charge is used by my son as a WiFi-only media player/gaming device. he likes to take pictures/videos, so this is the only thing preventing me from converting it the latest JB port.
again, good luck, and let us know how the progress goes!
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
pyroman512 said:
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
Click to expand...
Click to collapse
As a previous owner of a droid charge, I honestly hope I can squeeze some use out of it as a media device.

looking for interested devs

Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
so basically you have good intentions, no plan and a home server )
what we really need is a unification of all the different but not really different roms and their devs,
then its possible to see a future for long term support for all devices, or at least many.
anyhting else is jsut another project that will or will not die, based on good will and free time of the maintainer, mostly not even reckognized
due to the chaos of fragmented android and even more fragmented custom rom scene.
godkingofcanada said:
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
Click to expand...
Click to collapse
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Click to expand...
Click to collapse
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
godkingofcanada said:
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
Click to expand...
Click to collapse
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Click to expand...
Click to collapse
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
godkingofcanada said:
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
Click to expand...
Click to collapse
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Click to expand...
Click to collapse
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
godkingofcanada said:
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
Click to expand...
Click to collapse
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Click to expand...
Click to collapse
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
godkingofcanada said:
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
Click to expand...
Click to collapse
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Click to expand...
Click to collapse
I think the changes appear good. Less stuff locked away in private, more easily accessible to all. Treble has the vendor stuff available to roms that aren't stock, this will make the kernel tiny and easy to build. One by one the barriers people have to overcome to build their own roms are being taken away.

why we have not any other updates for custom roms like slim and.....?

???
This device is too old.
Tab_Triggerhappy said:
This device is too old.
Click to expand...
Click to collapse
Hi
yes but tab 2 can get android oreo or oreo go
Yes, but would you spend hours on a device that hardly anyone uses anymore? I wouldn't.
Developers have moved on to newer devices and/or have other priorities in life.
This tab has been around about 8 years and a lot happens in a persons life (usually).
I would also like a little more updating and maintaining of ROMs for this tab, but I think it's time to get a newer device unfortunately.
If every single electronic device on the planet could be used 1-3 years longer, imagine what that would do for the environment
Well... insecure people with too much money and no brain will always be around :laugh:
Tab_Triggerhappy said:
Yes, but would you spend hours on a device that hardly anyone uses anymore? I wouldn't.
Developers have moved on to newer devices and/or have other priorities in life.
This tab has been around about 8 years and a lot happens in a persons life (usually).
I would also like a little more updating and maintaining of ROMs for this tab, but I think it's time to get a newer device unfortunately.
If every single electronic device on the planet could be used 1-3 years longer, imagine what that would do for the environment
Well... insecure people with too much money and no brain will always be around :laugh:
Click to expand...
Click to collapse
i would:laugh:
yes of course developers have other priorities like @Android-Andi and others i know:good:
new device? i dont know why icant change my tab with any other phones and tabs
Scientists have discovered that fever tab 2 will never be harmful to the planet:angel:
Yes, too much money destroys brain
i also waiting for new updates and flash roms Even in another nine years or more
Yeah, private life and interests changed.
Source is open for everyone, feel free to continue
Android-Andi said:
Yeah, private life and interests changed.
Source is open for everyone, feel free to continue
Click to expand...
Click to collapse
Hi
Does this mean the end of Tab 2 support for always?
ashkineeeeee said:
Hi
Does this mean the end of Tab 2 support for always?
Click to expand...
Click to collapse
Could be of no one continues and only people asking instead start to learn how to compile a ROM.
Android-Andi said:
Could be of no one continues and only people asking instead start to learn how to compile a ROM.
Click to expand...
Click to collapse
Yes
But if people know support of this tab is ended
They do not wait anymore and they may start learning
If you update all your custom ROMs(slim6 and 7 and others) it would be good to we have an updated rom(latest) forever, a flawless update because roms have some problems
Whenever you could! Of course, if you accept
i use your slim 6 and it is best rom but need fix some problem
Nope, no plans to continue on Android and no updates planned
Android-Andi said:
Nope, no plans to continue on Android and no updates planned
Click to expand...
Click to collapse
ok mr andi thanks for your answers:good:
Android-Andi said:
Nope, no plans to continue on Android and no updates planned
Click to expand...
Click to collapse
Your work here is legendary brother!
You made our devices work LOOONG past their expiration date, and for this, I'm(and many others surely!) forever grateful!
I noticed, and am installing, new Slim7(and several others) which made the Wyze app work! now, my ever working Tab 2 10.1" can live its life out as a mobile security monitor!
I must ask tough, have you moved on to other devices? or have you moved on from development all together?
Lastly, would u be so kid as to point me in the right direction to where one would start learning how to compile a ROM for this old device, please??
Again, thank you for ALL of your countless hours in developing stable ROMs for this, and several others!
I wish you all the best in your new endeavors!!
Sorry, I don't have time to write a step by step guide for you, but there's a lot of tutorials on xda and maybe also still the instructions on LineageOS wiki work (not sure how much they changed for newer android versions).
Android-Andi said:
Sorry, I don't have time to write a step by step guide for you, but there's a lot of tutorials on xda and maybe also still the instructions on LineageOS wiki work (not sure how much they changed for newer android versions).
Click to expand...
Click to collapse
Ya i know about LOS wiki but thats for LOS 14 at max"
IIRC oreo needs changes in the kernel or something any idea what is that?
I know you have left development and i would love to contribute and make new roms for this tab!
Only if i know what and how to do
Android-Andi
Any idea or tutorial will be a lot helpful

[ROM][REQUEST][POLL] Should i develop a rom for the Tab S6??

Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
#reserved 1
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
TiTiB said:
I would LOVE to have LOS on my Tab S6 (SM-T860) WiFi-only tablet!
Don't even care about stuff like fingerprint, external keyboard, Widevine, Bluetooth, any 'functionality' similar to what Samsung 'provides' like, you name it.
I've spent sooo much time, and a few dollars, trying to get preinstalled stuff to *not* work! but still be able to boot—Knox bull****, anyone?
And having telephony **** on my WiFi-only tablet, either. Something that has baffled me for years is why a 'custom' ROM for a Wifi-only device has software that trys to interact with nonexistent hardware, using up cpu as it continually tries...on a bit of a rant, there.
So yeah, I'm all in. FWIW, I helped write the instructions, and did a *lot* of testing for rooting the Tab S5e, so I ain't scared to test out stuff; check it out, here:
https://forum.xda-developers.com/tab-s5e/how-to/galaxy-tab-s5e-sm-t720-root-t3947806
Click to expand...
Click to collapse
Thanks for the info about the S5e, i was unaware of how well it is supported.
I would definitely do stuff like fingerprint, widevine, Bluetooth (PEN) and stuff.
But idk about those keyboards samsung offers and how they function since i cant test it on my own.
Same goes for the LTE but im pretty sure i can just use the same blobs.
BTW anyone has a firehose package for the tab s6 by chance???
I too would love LOS in this device. Samsung UI is cluttery, lagging (on mine), and an absolute mess. My PocoF1 gives me better Honkai Impact 3 (a gatcha action fighting game) performance than this tablet, and the poco is an SD845, with lite LOS. So yeah, I'd love to have this. My warranty is void anyways (because samsung decided so I haven't done a thing to void it), so it'd be great to have a reason to take advantage of that.
Chiming in for a plea to get a Lineage build for the Tab S6.
Such a gorgeous piece of hardware beset by such a ****ty software implementation. Why does Samsung insist on abusing its customers? I'd gladly pay for a Lineage or AOSP rom for our device.
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Thargorsson said:
Alright, a little update:
Kernel is done -> link found below
It has to be handled with care as of now. Installing it on my running rom resulted in a crash when unlocking the device. A quick factory reset fixed the problem but keep that in mind when installing this on your device.
Rom will follow up hopefully till next month - but i cant promise anything.
T-860:
https://dl.keksla.wtf/boot_t860.img
T-865:
(uploading)
Click to expand...
Click to collapse
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
ykkfive said:
i would love to have custom kernel for samsung rom, but i don mind if you can make enhancements to the kernel like under volt or to solve the graphics lagging issues. it was just tiny changes involved in the past to make it work for both stock and LineageOS but for android 10, i have no idea
i have long inactive in both rom and kernel developments and i doubt how long should it take to get familiar with changes from android 7 to 10
ps i am still on pie, too lazy to upgrade due to my csc is tgy, which lacks updates as usual, and i dont wanna reinstall everything as to switch to dbt and to re-enter all my passwords
btw, may i ask if the stock android 10 fixed the problem with fast scrolling? i have experiences lags and graphics distortions with the samsung browser which was way toooooo unacceptable for a top device like tab s6
Click to expand...
Click to collapse
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Thargorsson said:
nope, sadly we still suffer from those issues on Q .
I dont have any good knowledge of how to apply those undervolts as i never done it before (lineageos requires stock govenors for official) but if you can point me to the correct commits i can look at it
Click to expand...
Click to collapse
oh...
there were some cpu/voltage tweaks for the same cpu before for my old devices. and for our tab s 6 there are a few devices with the same cpu like one plus. you can search the cpu model in github and then you can find the code name of it and those devices which use the same cpu. i used to get those tweaks for modifying kernels for my previous devices. however for our 855, sadly there's no port for the samsung devices afaik, so you may need to make some more changes in order to port them
---------- Post added at 05:54 ---------- Previous post was at 05:35 ----------
just found this one https://github.com/kdrag0n/proton_bluecross/releases
it should be a 855 with some oc according to the change log, but unfortunately i couldnt load the changes with my browser so i couldnt find the relevant commits
may be you can take a look at that
Thargorsson said:
Hi all,
i own a Tab S6 T860 (non-lte) for quite a while now, about 6 months.
There are some downsides like the horrible unbuffered screen tearing that you'll get with fast-scrolling, but the overall device is pretty premium-sided, and it's got a decent processor, a great display (color/resolution wise) although im missing 2160p in youtube.
Question is as i (until now) didnt bothered developing for a new device, since i had my hands full with the MiPad4, some alcatel devices and are Maintaining official LineageOS for three legacy devices, should i develop for this one if the community still wants it.
The lead-dev of the MiPad left it so im thinking about developing for the Tab S6 now.
I would only develop LineageOS, starting with 16.0 then doing 17.1 and then 18 but idk how long it would take, since ive no real knowledge of the newest platforms and how they are built, so i'd be reading/trying out stuff a LOT before some release nightlies. The "latest" i developed for was the MiPad4 with a sdm660 btw but i mainly do legacy (e.g 8953/8952/8926).
So please leave your feedback or any other opinions/questions, if we reach a decent amount of people who still want it i'll start right away when im back home from my vacations on 18th.
Best Regards!
Edit: Since theres no real telegram group, and i MAINLY talk via telegram i made one so you can contact me quickly.
https://t.me/joinchat/Bn6f-VKeQfZfiKXo69h3Mw
Click to expand...
Click to collapse
I'm in at 17.1 level and up. Don't want to go back...
YES! Yes please please please! I have been dreaming and hoping LOS would come to the Tab S6 for SO long now. So yes, please make a rom for it. Please.
I would love to have LOS rom support on the Tab S6! The lack of Lineage OS support was the one thing holding me back from purchasing the Tab S6, compared to the Tab S5E, but I wanted the faster processor, storage, and larger memory capacity.
That said, if you develop a working LOS rom, that would be a huge win for all Tab S6 users!
I don't think there is a person on XDA with the tab S6 that would not want to see a custom lineage Rom built. I do want a working Spen though. Im on stock 10 One UI 2.5 and samsung is extremely slow at releasing the kernel source code for the 860. Its definitely worth it to use to build one if you can. Thanks for developing on the tab S6.
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Still On The Fence.
lucgardos said:
LOS for T-865 ?! Yes, absolutely
P.S: Working pen would be great of course.
Click to expand...
Click to collapse
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
DeanoD said:
I would support a ROM for this device, but I am leery about past issues and previous devices. I had 3 smp600 units, and all three were beaten to the edge with constant testing of all the ROMS I could grab. But, only ONE of those tabs choked on something from a pure LOS build. Then it hit a brick wall. I could never find a way past a Nov 18 build. So, now with two smt870 units, I will tread lightly. And, big question: WHY are we STILL stuck with ODIN for this process? I know nothing of the process of coding and writing these great ROMS, but having to drag out a WINDOWS laptop to update my android device seems like many steps backwards. I have no NEED for a laptop save for praying for Odin to even run properly. Wish there were better ways for us old farts who've forgotten more tricks than new ones have been taught. But, I am on board to get the Sammy off of my tab. Thanks for your errors.
;-DeanoD
Click to expand...
Click to collapse
Well if your not rooted you dont need odin you can install official release update. If you mean to install custom rom like lineage you again dont need odin after you install TWRP.
Actually, on debloated rooted stock ROM I don't see any problems so far..Device is holding it solid and sound.
Flavour of Lineage is absolutely welcome, but personaly I wouldn't use it because a lot of bugs and non functional addons.
Personally...this tablet without pen is like Ferrari without fuel.
Rooted debloated stock is miles ahead of Samsung's incompetent shadow apps. But even as stripped down as I can make it, the ROM still lags and burns battery in the background. I've tried everything and can't get this beautiful expensive piece of hardware to perform to its specs. I respect others who love it as is, but I've never gotten comfortable with the pen and just want a light, fast tablet with a beautiful screen that doesn't overtax its battery.
I'd switch to Lineage on this device in a heartbeat.
this project still alive? seems dead for me.

Categories

Resources