Related
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
I have recreated the romer tool. The purpose of this tool is to replace certain files to make D2 roms work on the droid 2 global. To use simply install my file after installing a droid 2 rom via recovery. This version is designed for ginger-blur based roms such as apex and liberty. Do not flash over aosp roms such as cyanogenmod and liquid. I am currently working on creating a aosp romer tool. Do not use on froyo eaither, as this will temporarily brick your phone. I have tested on both apex and liberty, and sensors,gsm,data, and phone are all working. Please enjoy
Disclaimer: I am not responsible for what you do to your phone. If your phones does not do what you like, becomes 100% useless, or explodes killing your wife and children, it is not my fault. I can garauntee that my file is safe, and works perfectly for what it is designed. Make sure to check before you flash a d2 rom that it does not contain a d2 kernel. This could permanently brick your phone! Just be careful
Download v2.2:
http://dl.dropbox.com/u/46535328/D2G-GingerBlur-Romerv2.2.zip
Thanks:
Thanks goes to fabolous for apex , which is were the majority of the files for my romer comes from.
ChangeLog:
V1.0: original, based off of GRD Rommer.
V2.0:completely remade with no more GRD remains.
V2.1:Liberty tweaks put in build.prop.
V2.2:moto boot logo and boot animation added. I can remove this if it is disliked.
Comments:
Has anyone tested out the aosp romer. I would be happy to fix things or add things as people like. I will gladly update this if anyone wants, I have just been working on other things. I have been taking a look at cm source code, and app development. Also eaither one of these will work on Droid X roms. Haptic feed back will not work though.
P.S. If you download this, and enjoy it, please press the thanks button.
**********************************************************************************************************************
This section is for my romer tool having to do with porting the new 2nd init roms or anything that is based off cyanogenmod 7 or aosp that is originaly designed for the droid 2 or Droid X. I have tested it and can approve that it will work for miui,liquid, and cm. I am not liable if this does anything negative to your phone. To use just flash over an aosp rom for the droid x or droid 2 and enjoy on your global. For now the only thing that does not work is gsm. If i can fix it I certainly will.
Thanks: I thank revnumbers for his cyanogenmod builds, as this is were I took the proprietary files for the d2g from.
Comments:
If any of you want me to add something, or try to fix something, please post and I will see what I can do.
Download/Aosp Romer V1.1:
http://dl.dropbox.com/u/46535328/D2G-Aosp-Romer_V1.1.zip
Thanks:
Thanks goes to RevNumbers for his cyanogenmod 7 build, which is were the majority of the files come from.
Change log:
V1.0: Original, fixes phone,cdma data,keyboard,camera,sensors,etc...
V1.1:Fixes su/root permission error.
Comments:
Don't worry if the phone does not receive signal immediately. It takes it a minute.
I accidently set the permissions for su binary wrong. V1.1 fixes this.
! I would HIGHLY not recomend using anything built of of the D2G's romer !
The reason for that is because that method of porting is considered vastly inferior AND because it had many bugs in it because of it. The romer team from Get R Done also had a lot of strife in it and a lack of knowledge. A straight update of the files will not work well.
It needs redone, not updated.
Thanks for the advice aceoyame . I have tested it, and it works, but I do not know what problems may arise from it. I will work on redoing it
also, if you have the time could you describe the problems into more depth of what is wrong with team get-r-done's flashing process. I am not quite as well educated in the art of writing an updater script as you are I am sure.
Well the biggest issue with a romer vs natively porting is that you have too many files that are for one type of rom vs working for others. The romer will only do Gingerblur based as you have it (that's if sensors and everything else works). It will not do any aosp based roms (liquid, CM, MIUI, etc.) The libs are way too different. If you wanted you could make an AOSP romer and Gingerblur romer. Just pointing out the flaws in it.
Thanks for replying ace. I natively ported liberty on another forum. The reason why I made this is so people can just flash it over any liberty gb rom, instead of me having to make an update for each individual version. I have only tested it on liberty, and on liberty sensors,backlights,gsm,phone,keyboard,and data are all working. I would guess that would apply to any gingerblur based rom. I knew that it would not work on cm,liquid, and miui, and did not really care since thanks to you and other devs we already have those roms made for are phone. This is for those roms that only exist on the d2 and not the d2g
Well grats on fixing the sensors then! Rewriting the romer is something we've been wanting to do but could never get around to it. If it is 100% bug free on liberty than it should work for any gingerblur rom. You got sensors to work which was the big issue with the GRD one then you at least fixed something! I would just test the hell out of it and if it works then you probably hammered out any bugs they had with it. An AOSP one would be nice for the other roms. Feel free to put this on Rootzwiki and the other forums.
Thanks, I will make a asop version when I get the time.
Just one caveat: I have done searches (read: multiple).
How in the world does CyanogenMod get to all of the supported devices? All of a sudden once CM9 is released, for phones/tablets moving from CM7 to 9, does it go out to all devices or what? Does it need to get ported from the source for each and every individual device? In general, how is CM updated and how does it get out to the officially supported phones/tablets?
Cyanogenmod ROMs do indeed have to be ported to each individual device and maintained. Once a device receives official support from the Cyanogenmod team, daily changes made to the AOSP source code (tweaks and bugfixes by the various contributing devs) are automatically compiled by a "buildbot" and released at the end of each day (thus these builds are called "nightlies"). These nightly updates are then made available for download through the Cyanogenmod website and through ROM Manager. Once code updates reach a certain plateau, a "final release"-worthy balance of features and stability, the build is released separately as a "stable" build (such as CM7.1), though you can still download it from the website or from ROM Manager just as with the nightlies. CM9 will eventually receive the same treatment and be released in the form of nightlies and stable builds.
Further (highly recommended) reading can be found here: http://www.cyanogenmod.com/blog/the-current-and-future-state-of-cyanogenmod-nightlies
Has anyone seen John Connor?
so the nightlies don't have to be ported, but every major revision does?
hugabu said:
so the nightlies don't have to be ported, but every major revision does?
Click to expand...
Click to collapse
No.
"Porting" is just a word used for the process of making the rom work on any certain device.
So to answer your question, once the work of porting CM to the certain device is done, that port is used as the base for both the stable and nightly builds.
Look at the analogy of when a new phone comes out, case manufacturers create a mold to use to make their cases fit the certain phone, and that mold is used to make all kinds of cases. Same concept
As of 8/25/12, this project is officially discontinued. All information below is for archival purposes only and will not be supported henceforth.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
INTRODUCTION
Now that Fattire has lifted his request that everyone build their own zips, I've decided to make available the nightly builds I've been generating. I've got an OS X system cranking out a new build every night at midnight, so there will always be an up to date zip available!
Credit for this rom goes to Fattire, Dalingrin, keyodi, nemith, arcee and the the other hard working people over in the development thread, as well as the the CyanogenMod developers and anyone who's done work on the Nook Color. I wish I could list everyone by name but there's so many great people who've made contributions I can't even begin to do so. I'm just building zips from the source; we'd be nowhere without the contributions these great developers have made to this community.
As nighty builds, these zips may not always work. I'll try to remove any zip found to be broken, but you know the drill: All files provided here are to be installed at your own risk. I'm making built zips available, but no warranty is expressed or implied by the hosting of said zips. I'll provide what support I'm able to, but that doesn't mean that there aren't potentially unknown bugs. If you have questions, you should check the development thread or try the #NookColor IRC channnel on irc.freenode.net.
As posted by Fattire slightly further down, anyone feeling adventurous should definitely consider building from source rather than downloading the built zips. Here's his two cents:
fattire said:
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
Click to expand...
Click to collapse
However, if you're not quite sold on setting up a development environment but you still want to try the goodness that is Ice Cream Sandwich, proceeed on down to the...
DOWNLOADS
Without further ado: The Ice Cream Sandwich zips!
Ice Cream Sandwich Nightly Builds.
The rom does not include the google apps, so you can/should flash the lastest version of those, which is available here.
Finally, I've hosted a few flashable zip files to make small tweaks to the rom. These are all located in the misc. folder on my server. Below is an explanation of each zip and its purpose.
MISC FOLDER INFO
If you notice that some apps are missing from the market, this may be due to the fact that these ICS builds for the nook do not include support for apps which request phone permissions. Although this ideally would be fixed by developers not requesting phone permissions for their app unless it absolutely needs to be phone-specific, you can also fix it by flashing the telephony-permissions-fix.zip file located in the misc folder. You will likely want to flash this file immediately after flashing your rom.
Secondly, if you prefer the old bootanimation from the galaxy nexus, you can also flash the fix-bootanimation.zip located in the Misc. folder, which replace the new CM9 animation it with Homer_S_xda's fixed version. Thanks to Homer for the fix!
NOTES ON INSTALLING TO SD
I've fixed Verygreen's sd installer image to work with ICS -- you should no longer have to flash SP1 first, or rename the gapps to gapps-gb. If you test out this image, please let me know how it works for you! More recently, Leapinlar has stepped up in helping to fix the image further, increasing its size to allow for the larger size of the new nightlies. Thanks to him for his help -- It's available for download here. Huge thanks to Verygreen for helping me to figure out what needed to be fixed -- in the words of HacDan, "He's not just super helpful, he's a genius". Once you've got the new image, you can use Verygreen's original instructions from his thread on SD Installs, replacing "cm7" with "cm9" where necessary.
IN CONCLUSION
Please remember to thank the developers working on this project, as they've done seriously awesome things for us in an amazingly short amount of time. If you have questions/comments specifically regarding my zips, please post them here, but if you have more general questions regarding Ice Cream Sandwich on the NC you may want to head on over to the development thread. Finally, if you're really enjoying the rom I'd strongly recommend that you try setting up a build environment and building your own zips -- even though I'm making prebuilt ones available they're no substitute for the experience gained by getting familiar with the build process yourself, and Fattire has done a great job of making it an extremely accessible and rewarding project.
Thank you!!!!
What bugs can we expect as far YouTube, flash player. Boot loop . A breakdown of what to expect and not to expect. I don't expect anything but like to know for flashing
And you can build too!
Want to build ICS from raw source code yourself?
It may be a good learning activity, and will certainly make you more self-sufficient. Hundreds have built ICS for Nookcolor successfully, and understanding the process will make you an Android ninja-- PLUS you can try features and bug fixes as-yet-unaccepted-into-the-mainstream build.
Take a look at:
The ICS NookColor Build WalkThrough
So awesome!
Youtube missing in latest gapps ?
I installed the latest nightly with the gapps and found youtube app is missing ?
Thanks for sharing! I love nook color devs community! You did an awesome job!
Brilliant work! I upgraded from CM7 and all my existing apps that ive checked worked no problem, it kept all my settings too! Speed-wise I would say its very close to CM7, i use ADW EX in preference to trebuchet, and it just flies!
One thing ive noticed is that NFS shift doesnt behave properly when using the tilt sensor to steer, its axis sensor wants the tablet to be in portrait orientation when the screen is in landscape. Hard to know if its the games fault or the sensor. If thats all there is to complain about this early in the development then the future looks promising
rajazeeshan said:
I installed the latest nightly with the gapps and found youtube app is missing ?
Click to expand...
Click to collapse
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Dual boot ?
I currently have a dual boot environment setup so I can boot into stock (primary boot partition is currently CM7). Does anyone know if this still supports that ? Anything specific I'd have to do with the install then ?
TIA
Thanks a bunch for hosting these nightlies.....let the fun begin!
I just want to point out for the sd-card users using verigreens 1.3 boot image to setup cm7 to run off of sd card and retain stock for various reasons.
That process will also work for ICS/cm9. Currently, you need to flash update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs.zip first. It's found in the ics/cm9 dev. thread: http://forum.xda-developers.com/showthread.php?t=1370873
Then, flash Samiam's nightly builds otherwise you will get stuck in a boot loop right now.
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
I'm gonna stay on cm7 for a while. But I love the progress were seeing with ics.. thanks guys
pavlos46 said:
Ok just tested it and it works great.
Youtube works just not HQ, although I have to admit that for non HQ the quality and smoothness is very high.
Flash Player doesn't work but I think that has to do with 3D H/W acceleration.
Maps wifi location doesn't work allthough it did work on the normal version of the gapps so something is amiss there.
And I am also experiancing alot of hyper sensitivity especially when using two finger actions.
Otherwise all is well.
Click to expand...
Click to collapse
What version of the gapps did you have where the wifi location worked? If you link me to that I can see if there's something missing from my gapps zip.
YouTube is incompatible from the market. Actually, it appears any device I have that runs ICS is listed as incompatible.
youtube app missing in gapps
Samiam303 said:
I think you can just get it in the market, I removed it to save space. Let me know if you have a problem downloading it.
Click to expand...
Click to collapse
Unfortunately thats not the case when I search market it doesn't list YouTube app and when I
Google it takes me to mobile YouTube app in market that is not compatible with this device.
I salute you all dev. gurus.
Hat off and thanks for the ICS
Awesome thanks so much!
Hey,
awesome awesome work, thank you very much!
I have a slight problem with the GApps, though: I came from update-cm-9.0-0-encore-emmc-sneakpeek1-fullofbugs and just updated over that with some ics-apps installed. Unfortunately, I do not remember which ones.
Now after the update all my apps are there, but the home screen wiped (not so bad), but my Google Account vanished and I cannot add a new one. Neither in the Settings, nor by opening GMail, Talk, whatever. These will just crash.
Any suggestions?
Thanks again for all your work and energy, I really appreciate that.
Greetz,
Felix
ZenoGia said:
Awesome thanks so much!
Click to expand...
Click to collapse
+1 .
Hello XDA-Developers.
Some of my friends in the phone/wireless communications business (including a PhD) tell me that custom ROMs are unsafe and there could be written in the code spyware such as keyloggers that can steal your data and do other things of the sort in the background. Cyanogenmod (and AOKP maybe) seem to be pretty safe, and I am running it on my i897, but the Legend is not supported anymore and the latest official ROM I can get is Gingerbread on CM7, which is very slow and seems to have issues. However, I have found these UNOFFICIAL Cyanogenmod/AOKP ROMS made by others:
http://forum.xda-developers.com/showthread.php?t=2353659
http://forum.xda-developers.com/showthread.php?t=2222597
http://forum.xda-developers.com/showthread.php?t=1905588
http://forum.xda-developers.com/showthread.php?t=1562595
2.2 ROM
http://forum.xda-developers.com/showthread.php?t=866849
Note: Don't know if this matters, but all the ROMs save the last were not made by Recognised Developers.
These ROMs (I haven't tried some of them yet) run very smoothly on the Legend and are almost as good as a daily driver.
So can I trust these ROMs because they are based on CM/AOKP but are unofficial, or is the security compromised as it was unofficially done by a member? I would like answers from a technical point of view, not speculation such as 'devs usually have no intent', etc. Don't get me wrong, I may be paranoid, but I truly appreciate the amazing work that devs here are doing, but the possibility of security issues, especially with Linux and open source, is of my concern.