Related
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
Hi to everyone reading this
I am a fairly long time user of xda, usually just lurking and watching threads as they go along, but have now decided to try my hand at developing a rom or two for our (unfortunately) long forgotten villec2, since everyone seems to develop for the S4 variant. I have seen android 5 ported to the S4 variant, and I would like to know if what I am trying to do is at all possible, and if it is, if anyone can point me in a starting direction.
What I am trying to accomplish, is to get a working (bootable, not much else) rom that can boot up on my phone, and then from there add drivers/modules (unsure about naming conventions used in android, coming from a java/C++ background) for the different phone functions as I learn more about the system. So far, I have not found much on upgrading device trees / vendor files (not even exactly sure what these are for since most I see are completely different, even for the same version of android) from 4.4 to 5.0.1, and if I should simply write many of these files from scratch. I know this is a huge en devour, and I am in for much frustration, but I am doing it for two main reasons. One, everyone seems to have forgotten the villec2 device, and I feel like I will still be using it for quite a long time, and being able to use the latest and greatest in android technology will be quite nice to say the least. And two, I am doing it for learning, broadening my own experience with android, since I have yet to really write my own rom, I have only done a few rough builds from other people's repositories like cm.
At this point, I have a AOSP build environment from the master branch, have not yet done a build from it, and would just like any nudge someone can give me in a starting direction. Would it be possible to obtain some of the files I need for android L from my current device,, which is running a android 4 variant? Should I look elsewhere for these files?
niekz said:
Hi to everyone reading this
I am a fairly long time user of xda, usually just lurking and watching threads as they go along, but have now decided to try my hand at developing a rom or two for our (unfortunately) long forgotten villec2, since everyone seems to develop for the S4 variant. I have seen android 5 ported to the S4 variant, and I would like to know if what I am trying to do is at all possible, and if it is, if anyone can point me in a starting direction.
What I am trying to accomplish, is to get a working (bootable, not much else) rom that can boot up on my phone, and then from there add drivers/modules (unsure about naming conventions used in android, coming from a java/C++ background) for the different phone functions as I learn more about the system. So far, I have not found much on upgrading device trees / vendor files (not even exactly sure what these are for since most I see are completely different, even for the same version of android) from 4.4 to 5.0.1, and if I should simply write many of these files from scratch. I know this is a huge en devour, and I am in for much frustration, but I am doing it for two main reasons. One, everyone seems to have forgotten the villec2 device, and I feel like I will still be using it for quite a long time, and being able to use the latest and greatest in android technology will be quite nice to say the least. And two, I am doing it for learning, broadening my own experience with android, since I have yet to really write my own rom, I have only done a few rough builds from other people's repositories like cm.
At this point, I have a AOSP build environment from the master branch, have not yet done a build from it, and would just like any nudge someone can give me in a starting direction. Would it be possible to obtain some of the files I need for android L from my current device,, which is running a android 4 variant? Should I look elsewhere for these files?
Click to expand...
Click to collapse
Have you seen this thread?
http://forum.xda-developers.com/showthread.php?t=2581659
I know it's not for C2 but maybe you can find some info there or someone can give you some advice
Sent from nowhere over the air...
I have checked out the thread, but unfortunately most of these guides refer to an already made vendor/device tree, which does not yet exist for the c2 (for android 5 anyways). Ill likely need to write my own it seems. Sadness..
Hi!
i really excited for this thread. i have a villeC2 and its very sad that phone just update at 4.1. its a really great phone whit much potential... if i can i help you but i don't know everything about compile roms. but i can try the rom like a beta tester. i really glad to do that. so.. if you continue whit this, i help you like a beta tester contacte me.
You can examine recent posts c2 development cm11 kitkat and offical pacman pages.
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
https://forum.xda-developers.com/ch...ide-how-to-port-lollipop-marshmallow-t3283452
https://forum.xda-developers.com/showthread.php?t=2707438
i think we should port HTC Sensation roms
i dont know what's the difference between C2 and Sensation kernels . but i saw viperC2 and SAM rom files is the same
---------- Post added at 17:39 ---------- Previous post was at 17:06 ----------
https://forum.xda-developers.com/showthread.php?t=2178042
When I the I had nexus 5 there used to be loads of content in xda be it roms or mods. Now for the pixel 2 there is no custom rom to begin with. I understand the stock Google oreo is as good as ever but still the basic tweaks would add much more to it.
Is there any specific reason for this? May be Google's security is much complicated in oreo to implement changes in the stock rom?
I was just looking for dual speaker ring, status bar tweaks.
I hope to see more soon as well. Now that Verizon phones are on board for rooting there will probably be more devs getting their hands dirty.
Not to mention there are still only a few phones running Oreo. Right now it's just basically pixel owners. So all the mods made for other phones haven't been ported or upgraded.
I'll have this phone for the next two years I'm hoping there will be more with time.
I haven't even been able to get debian, Ubuntu, or Kali to work along side this phone yet. Proot and chroot don't seem to be working as they should. I tried 3 methods. Linux deploy, termux ,and using the nethunter module. Guess I'll just keep at it until New methods are found.
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
One plus because of the price
Sent from my Google Pixel 2 XL using XDA Labs
Sman999 said:
Is there any specific reason for this? May be Google's security is much complicated in oreo to implement changes in the stock rom?
Click to expand...
Click to collapse
The a/b bootloader partitions... No dedicated recovery.... Blah blah blah too much for me to understand but basically it's screwing with devs.
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
I guess oneplus or Samsung. The later cuz the design is awesome but software experience is poor so if the software is improved it ll be awesome Samsung. ?
I wondered the same thing but then it dawned on me, I only rooted/ROM'd devices to run something that's a vanilla build of Android. That's what this is. There's a few nitpicky things that I would love to have but for the most part, I'm happy with it.
main reason for me is the PRICE.. if it was just priced same as the nexus 5, . thats why oneplus devices are being so favored
teh_lorax said:
I assumed the Pixel line would just replace the Nexus line for modders. Sadly, that couldn't be further from the truth for either the Pixel 1 or 2. Which phone(s) have all the devs moved to?
Click to expand...
Click to collapse
pixel devices are no where near as easy to get roms on. Not only is the device tree clustered, but a b partitions, the trend of users demanding security, the expensive price of the device, the changes to the build process, and how Verizon royally made blobs more complicated contributed too.
I have brought up a few device tress before but I definitely had to debug the most for pixel 2. Theres an entire new flashing method and it doesn't help ramdisk is in system now.
Now after all that negativity, I can tell you I know of 4 roms actively working on roms. And two of them booting, including my shameless plug in p2xl forums of ABC Rom working with plenty of mods.
I'd say the good times are on their way, once one rom goes up more will pop up instantly.
Let's hope this helps start the domino effect.
https://forum.xda-developers.com/pi...sp-tamien-8-1-opengapps-t3727948/post75108624
Surge1223 said:
pixel devices are no where near as easy to get roms on. Not only is the device tree clustered, but a b partitions, the trend of users demanding security, the expensive price of the device, the changes to the build process, and how Verizon royally made blobs more complicated contributed too.
I have brought up a few device tress before but I definitely had to debug the most for pixel 2. Theres an entire new flashing method and it doesn't help ramdisk is in system now.
Now after all that negativity, I can tell you I know of 4 roms actively working on roms. And two of them booting, including my shameless plug in p2xl forums of ABC Rom working with plenty of mods.
I'd say the good times are on their way, once one rom goes up more will pop up instantly.
Let's hope this helps start the domino effect.
https://forum.xda-developers.com/pi...sp-tamien-8-1-opengapps-t3727948/post75108624
Click to expand...
Click to collapse
Good to know you're busy helping us all with our crack flashing addiction. I can't wait for the goodies to start. Thank you and all the other devs. I've been waiting to unlock my bl because of lack of roms. Is bajasaur still in the game? I haven't really seen him since my note 3 days.
bmwh0r3 said:
Good to know you're busy helping us all with our crack flashing addiction. I can't wait for the goodies to start. Thank you and all the other devs. I've been waiting to unlock my bl because of lack of roms. Is bajasaur still in the game? I haven't really seen him since my note 3 days.
Click to expand...
Click to collapse
Ironic you should ask..I helped him come back to the game today you could say lol
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.
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