Database Info

[Q] ROM based on Android sources rather than on HTC stock ROMs

Hi,
I'm relatively new to the whole Android business, coming from the Blackstone running Windows Mobile 6.1, where I did some ROM cooking. So probably I don't have that much of an overview yet.
After looking around in the Android development section for this device, I realized that most (all?) ROMs are based upon the HTC stock ROMs.
However I was wondering whether there are ROMs (or projects) with the goal of bringing the stock Android sources to our devices. I'm not that much of a fan of all these modifications the OEMs are including and would like to have as much of a vanilla Android as possible. As seen with the vulnerability of htclogger, this is a justified request as all added (unneeded) stuff is just another weak point.
I'm pretty sure that the vanilla sources won't be enough to get our devices running and there are a bunch of drivers, which must be added to get (full) functionality.
The ultimate goal would be to get some sort of scripts, which would automatically grab the latest Android sources, add the necessary stuff, which is needed to get full support for our devices, and build a ROM, which then could be the base for custom ROMs using the available tools/kitchens.
So, basically, before starting something, which already exists (but I couldn't find), I would like to ask you if you know of something that suits my taste in any sense? Or am I the only one interested in this way of thinking? Is there anyone who would like to participate in this endeavor when there shouldn't be something similar already?
Thanks in advance for any helpful reference in the right direction.
Best regards,
johnpatcher

There are a lot of roms with no-sense options and you have miui and cm7

xyqtt said:
There are a lot of roms with no-sense options and you have miui and cm7
Click to expand...
Click to collapse
Yeah, but all ROMs I've seen so far are based upon the stock ROMs and removed some of the included HTC stuff. There even seem to be some scripts, which would do just that after flashing such a ROM. I would like to go the bottom-up kind of approach.
As great as MIUI and CM7 are, both of them don't support the Sensation officially yet. Furthermore they try to be an alternative firmware/ROM and add a whole bunch of functionality for themselves.
Without looking into their building process, I could imagine that they are using the Android vanilla sources as a base, which would be the kind of thing I want, although I would have to investigate that further. Does anyone know something about this?

CM7 does officially support the Sensation, albeit in Alpha form.
What you want is someone to compile a ROM from source (AOSP) specifically for the Sensation but it would seem no one has taken up the challenge yet. Surprising really, there were 2-3 on the Desire

AOSP on Galaxy Tab 3 10.1

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

AOSP ROMs after Oreo launches?

i'm extremely grateful for all of the ROMs in the development section currently, but i'm kinda bummed there aren't more AOSP ROMs. i know only the developers have the definite answer to this question, but i'm curious to see what everyone else thinks. do you guys think we'll see an increase in ROM development (specifically AOSP) once Oreo officially launches?

IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..

tomascus said:
IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..
Click to expand...
Click to collapse
I am one of the people you mention, although as I stated to you in the slim thread, the limit of my ability seems to be at a command line... I tested numerous builds for nick and reported back with logs to no avail...
If you have a working build of 14.1 which is 'almost stable' why dont you have plans to release it? Surely others could start using your base to make their own roms as you previously stated.
PS not an insult, just a query.

miffymiffy said:
I am one of the people you mention, although as I stated to you in the slim thread, the limit of my ability seems to be at a command line... I tested numerous builds for nick and reported back with logs to no avail...
If you have a working build of 14.1 which is 'almost stable' why dont you have plans to release it? Surely others could start using your base to make their own roms as you previously stated.
PS not an insult, just a query.
Click to expand...
Click to collapse
The main reason is that I try not to release builds with some essential things broken, such as Edge Sense right now, which I consider a major feature for our device. Also, you can understand how terrible Aussie upload speeds are, especially without NBN in my area (coming soon my ass), so upload test builds would take forever.
Anyone is free to see my device tree and kernel anyway on my Github, same username as my XDA one.

tomascus said:
The main reason is that I try not to release builds with some essential things broken, such as Edge Sense right now, which I consider a major feature for our device. Also, you can understand how terrible Aussie upload speeds are, especially without NBN in my area (coming soon my ass), so upload test builds would take forever.
Anyone is free to see my device tree and kernel anyway on my Github, same username as my XDA one.
Click to expand...
Click to collapse
Is the dualsim variant DUGL working on your build ? If it is then i can build some custom roms using yours and slim base..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS

amit_sen said:
Is the dualsim variant DUGL working on your build ? If it is then i can build some custom roms using yours and slim base..
U11 | ⓣⓐⓟⓐⓣⓐⓛⓚ | TabS
Click to expand...
Click to collapse
As I said before in the slim thread, I don't have a dual sim device so it's broken and I can't fix. If you are a dev then I assume you have some skills to troubleshoot the issue.

Actually I don't know why we need this boring looking roms
The stock sense rom is perfect with ultra smooth performance
---------- Post added at 01:26 AM ---------- Previous post was at 01:25 AM ----------
Actually I wanna try
Miui rom ❤

tomascus said:
IMO what's lacking around here, and XDA in general, is the strive to learn. Developers don't appear out of thin air, they have to start from somewhere.
Long story short, long long ago I was also a 'regular XDA user' who didn't contribute much back to the community, all I could do was help people in the Q&A section of the forum.
Fast forward to news that Qualcomm deprecated Snapdragon 800, meaning devices running that would not be receiving Nougat, we were completely disappointed.
What did most people do? Complain, complain, complain. Similar to those people in the Slim ROM thread asking for dual sim support yet not assisting with development itself.
What didn't they do? Do the next best thing and bring up Nougat themselves.
Two others are I were also interested in bringing up Cyanogenmod for our devices but we also lacked quite a bit of knowledge back then.
Lots of trial and error, troubleshooting, and studying later, we were able to get LineageOS 14.1 working on our devices (Xperia Z3 and Z3 compact) earlier this year. From that point on, we have continuously improved it, fixed bugs, and whatever, learning new things along the way.
After we released the ROMs publicly on XDA, many others started using our work as a base to make their own ROMs thus giving some diversity to forums.
The previous experience of bringing up Nougat my other device has greatly assisted me in working on LineageOS 14.1 for the HTC U11 (as well as using Slim as a base) and it is almost stable for daily use. I don't have plans to release LineageOS 14.1, but maybe LineageOS 15.0 when I get that up and running and stable.
TL;DR: idk maybe..
Click to expand...
Click to collapse
I just flashed slimrom and it's pretty stable for me. I'd love to help out. What can I do?

Hi all, a quick thought that fits this topic, I think.
I was wondering if there is any chance we see the U11 Life Android One ROM ported to the U11, when the U11 Life will be out?
I'm asking because I saw this was the case for some Xiaomi devices:
https://forum.xda-developers.com/re...-androidone-7-9-21-xiaomi-redmi-note-t3691907
Thanks in advance !

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.

AOSP Don't seem so open anymore..

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.