This is a noon question and I appolagize but I figured I would ask anyways. If I were to build the ics myself and flash it would I have any issues getting back to 3.2.2 if I so wished to? I ask because I know the bootloader it picky for the images released for 3.2.2 and have never actually built it myself before. If its not obvious already I own a xoom 4g.
Sent from my ADR6400L using xda premium
Where do you plan to get all the code for all of the hardware drivers? Those are NOT included in the source code.
While we appreciate your enthusiasm for ICS and the developer community. We ask that you do many hours of research before diving into anything near the task you seek to accomplish. To start, you might want to try by flashing between roms, looking at different rom sourcecode, and different driver codes for hardware.
Thanks for the info, like I said I have never done anything like it before. I am kinda embarassed that I didnt even think about the hardware drivers that would be required as well. After doing a little reading on the aosp source site I come to find out an additional bit of information. As of ICS there is more needed than just the source code, there will also be some additional information for the graphics hardware acceleration to work , and the Xoom wasnt mentioned (only the Official Google Devices). Guess I will just sit tight and be happy with flashing ROMs for now. Thanks again.
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
I just got a pixel 3a xl a few weeks ago, my first android device since the donut/gingerbread days. I was looking forward to doing some mods and builds.
After doing some building and looking thru code ,it seems that Android is not so much OS anymore...
I get that security is a factor with the new code, but after trying and building (hit/miss) mostly miss. It seems to be more hacking than modding. If that makes sense..
Anyway just my thoughts about my experience.
Thanks to all developers here we are able to make our devices our own even if big brother don't want us to...
oneprimedroid said:
I just got a pixel 3a xl a few weeks ago, my first android device since the donut/gingerbread days. I was looking forward to doing some mods and builds.
After doing some building and looking thru code ,it seems that Android is not so much OS anymore...
I get that security is a factor with the new code, but after trying and building (hit/miss) mostly miss. It seems to be more hacking than modding. If that makes sense..
Anyway just my thoughts about my experience.
Thanks to all developers here we are able to make our devices our own even if big brother don't want us to...
Click to expand...
Click to collapse
Hi. I just want to understand what you're saying. What about Android or AOSP doesn't seem open to you? Were you able to successfully unlock your bootloader and try a few builds and stuff? What were you unable to do that you wanted to do?
what specifically were you looking for? there are parts that are closed source yeah. mostly the vendor specific hardware drivers. have you tried looking on http://androidxref.com/ for what you need? you can xref the kernel there too.
Hi,
So what are the reasons for the lack of custom ROMs for our device and what can we do about it?
1. Device is new? So is the OP 8 and it already has development going on full speed.
2. It's not that popular, devs don't have it? Could we chip in a few bucks and get a device for one of the recognized developers?
3. Issues with kernel source and device tree from Xiaomi? Is there anything we can do about it?
4. Lack of proper TWRP? Btw. The Chinese TWRP is 130MB+ in size, whereas the proper one is usually 30MB+, I don't trust it at all. I think @mauronofrio is already working his magic and we will have a fully working TWRP soon.
Did I miss something? It's a great phone hardware wise, but the lack of custom ROMs is making it useless for people like us. I'm actually learning how to build custom ROMs because of that, so maybe I could create something, but it's not a trivial task, especially for an old-ish dude with not a lot of time on hand and who's just getting started.
grt67DFqyu said:
Hi,
So what are the reasons for the lack of custom ROMs for our device and what can we do about it?
1. Device is new? So is the OP 8 and it already has development going on full speed.
2. It's not that popular, devs don't have it? Could we chip in a few bucks and get a device for one of the recognized developers?
3. Issues with kernel source and device tree from Xiaomi? Is there anything we can do about it?
4. Lack of proper TWRP? Btw. The Chinese TWRP is 130MB+ in size, whereas the proper one is usually 30MB+, I don't trust it at all. I think @mauronofrio is already working his magic and we will have a fully working TWRP soon.
Did I miss something? It's a great phone hardware wise, but the lack of custom ROMs is making it useless for people like us. I'm actually learning how to build custom ROMs because of that, so maybe I could create something, but it's not a trivial task, especially for an old-ish dude with not a lot of time on hand and who's just getting started.
Click to expand...
Click to collapse
i think you have checks all spots with this thread. Maybe points 2 and 3 has major weight on this situation. We need to flodding poco on social networks to make more aware about this lack of development cause one of poco selling points was devices dev friendly and without proper kernel sources or devices tree, we will be in an dead end very soon. f1 has a lot of active development even 2 years later! i can't believe f2 will be a flawn on dev department...
I think it's Corona stuff, lots of device releases not much man power, why bother fixing source code that will be irrelevant in 3-4 months when android 11 comes out.
I think we have to just wait.
grt67DFqyu said:
Hi,
So what are the reasons for the lack of custom ROMs for our device and what can we do about it?
1. Device is new? So is the OP 8 and it already has development going on full speed.
2. It's not that popular, devs don't have it? Could we chip in a few bucks and get a device for one of the recognized developers?
3. Issues with kernel source and device tree from Xiaomi? Is there anything we can do about it?
4. Lack of proper TWRP? Btw. The Chinese TWRP is 130MB+ in size, whereas the proper one is usually 30MB+, I don't trust it at all. I think @mauronofrio is already working his magic and we will have a fully working TWRP soon.
Did I miss something? It's a great phone hardware wise, but the lack of custom ROMs is making it useless for people like us. I'm actually learning how to build custom ROMs because of that, so maybe I could create something, but it's not a trivial task, especially for an old-ish dude with not a lot of time on hand and who's just getting started.
Click to expand...
Click to collapse
I'm still waiting too
OnePlus is supporting the dev's, Xiaomi don't care.
For 4, if you compress that twrp with rar or 7zip, you can find the real size is about 32MB