Related
Okay everyone. I am working on an optimized 2.6.27 until we can get .29 ported over. But I figure, since I am fairly new to the kernel world, how can we get started porting this bad boy over? I have been looking through the source code but am somewhat lost as to where to get started. I figure if we are able get this going we can make a github account and have the progress set up for everyone. All you devs wanna join in?
chuckhriczko said:
Okay everyone. I am working on an optimized 2.6.27 until we can get .29 ported over. But I figure, since I am fairly new to the kernel world, how can we get started porting this bad boy over? I have been looking through the source code but am somewhat lost as to where to get started. I figure if we are able get this going we can make a github account and have the progress set up for everyone. All you devs wanna join in?
Click to expand...
Click to collapse
Seems like I just read someones already got a github setup. Can we branch instead of running 2 accounts if this is the case?
I am also very new to the whole kernel. I think I have actually only compilied 3 succesful linux kernels in my short life. Attempted others, but I usually get lazy or run out of time.
Kcarpenter said:
Seems like I just read someones already got a github setup. Can we branch instead of running 2 accounts if this is the case?
I am also very new to the whole kernel. I think I have actually only compilied 3 succesful linux kernels in my short life. Attempted others, but I usually get lazy or run out of time.
Click to expand...
Click to collapse
If someone has made a github project please let me know. I havent made a 2.6.29 github project yet. I am currently doing one for 2.6.27.
I created a 2.6.27 repo this morning when the source was released. And I've checked out 2.6.29, just haven't set it up in github.
Really?
What's the difference between the android kernel and the regular linux kernel? It seems their version numbers are closely related. So why not go up to the newest stable (2.6.32.5)?
lazydev said:
What's the difference between the android kernel and the regular linux kernel? It seems their version numbers are closely related. So why not go up to the newest stable (2.6.32.5)?
Click to expand...
Click to collapse
It's not that simple. For starters we have to copy over the drivers for our phone and make sure they compile correctly. On top of that HTC modified quite a bit of the kernel. Porting it over will happen but it may take some time. Like I said before I am new to the linux kernel deal but I do know it is more difficult than it seems.
I'd say a completely functional port will take roughly 2 weeks time for a hobbyist. I'm not sure though as I'm still new to messing with linux kernels. I'm looking into a port of my own. Debating 2.6.29 or porting the android specific bits to a newer linux kernel. Chances are porting the hero specific stuff to the android 2.6.29 kernel source will be much simpler. It sucks I'm on my laptop at work and it isn't running linux so no compiling, diff patching or coding for me tonight. I wish I was a bit more profficient with C programming too. I guess now I have a good reason to do just that.
lazydev said:
What's the difference between the android kernel and the regular linux kernel? It seems their version numbers are closely related. So why not go up to the newest stable (2.6.32.5)?
Click to expand...
Click to collapse
edit: didnt release chuckriczko answered your question..
obelisk79 said:
It sucks I'm on my laptop at work and it isn't running linux so no compiling, diff patching or coding for me tonight.
Click to expand...
Click to collapse
Maybe it's time to start carrying around a LiveUSB distro of Linux on a flash drive
gu1dry said:
Maybe it's time to start carrying around a LiveUSB distro of Linux on a flash drive
Click to expand...
Click to collapse
no kidding... I wasn't expecting to wake up to a new release. Of course I could just run linux on my laptop and call it a day
Yeah, the reason it's better to start with .29 than jump to .32, because a lot of the work has already been done for us in .29. In fact, if you really investigate the kernel source they released, vs the kernel on our phones, you'll notice that HTC has already backported some of the .29 changes in the android-msm-2.6.29 branch into the source they released, which was *not* initially the case in the kernel that they shipped.
What we need to do to get .29 actually working, is the opposite: forward-port the HTC changes for hero/c into the .29 source.
FYI: got an initial codebase that compiles, but does not boot yet:
http://github.com/jhansche/kernel_msm/commit/19a2d673867a8e11b98cce399ed89c94811ebf77
Started from android-msm-2.6.29 branch, with a few modifications that HTC made in our code, ported over (not all of them, mind you). If anyone has any suggestions for debugging why the kernel doesn't boot, I'm glad to hear them If I had a serial debug cable, that would be useful, cause then it would work as a serial console. But for now all I have to go on is the fact that it dies *before* ram_console can be initialized (even with early-init enabled).
I've also disabled several pieces of hardware in the interest of just getting a clean compile -- namely headset, 3.5mm audiojack, EID mddi client (lcd panel) has not been copied over yet, and some other stuff.
maejrep said:
FYI: got an initial codebase that compiles, but does not boot yet:
http://github.com/jhansche/kernel_msm/commit/19a2d673867a8e11b98cce399ed89c94811ebf77
Started from android-msm-2.6.29 branch, with a few modifications that HTC made in our code, ported over (not all of them, mind you). If anyone has any suggestions for debugging why the kernel doesn't boot, I'm glad to hear them If I had a serial debug cable, that would be useful, cause then it would work as a serial console. But for now all I have to go on is the fact that it dies *before* ram_console can be initialized (even with early-init enabled).
I've also disabled several pieces of hardware in the interest of just getting a clean compile -- namely headset, 3.5mm audiojack, EID mddi client (lcd panel) has not been copied over yet, and some other stuff.
Click to expand...
Click to collapse
Great work! As I said before I am new to this linux kernel stuff and don't think I can help but I am cloning the repo so I can take a look anyway.
Any progress with getting it to boot?
Any update on this project?
I have also been curious about this for a couple of days, just didn't want to sound pushy to the devs... hope theyre seeing progress.
theoottesen said:
I have also been curious about this for a couple of days, just didn't want to sound pushy to the devs... hope theyre seeing progress.
Click to expand...
Click to collapse
I checked the githup out. still doesn't boot
Yeah, I've been hitting a brick wall trying to get some kind of indication that something is happening... On .27 I lucked out by somehow getting it to go past the ram console, then reboot, so I could see the panic messages on /proc/last_kmsg. But in .29, I can't even write directly to the ram console memory space in a pure_init section. The problem is that there's no way to know how far it's getting in the boot process. So we're really just booting blindly.
On top of that, the android-msm-2.6.29-nexusone branch has non-QSD8k bugs (that is, if you select that it's an MSM device, not a QSD device, it won't compile without fixing stuff in their acpu code for arm11, MDP22 code paths, etc. it's like the nexusone branch was only ever tested with scorpion, not arm11 (even though it has the board files for sapphire, so you would expect it to compile for sapphire)
maejrep said:
Yeah, I've been hitting a brick wall trying to get some kind of indication that something is happening... On .27 I lucked out by somehow getting it to go past the ram console, then reboot, so I could see the panic messages on /proc/last_kmsg. But in .29, I can't even write directly to the ram console memory space in a pure_init section. The problem is that there's no way to know how far it's getting in the boot process. So we're really just booting blindly.
On top of that, the android-msm-2.6.29-nexusone branch has non-QSD8k bugs (that is, if you select that it's an MSM device, not a QSD device, it won't compile without fixing stuff in their acpu code for arm11, MDP22 code paths, etc. it's like the nexusone branch was only ever tested with scorpion, not arm11 (even though it has the board files for sapphire, so you would expect it to compile for sapphire)
Click to expand...
Click to collapse
So if I understand correctly, the devs that worked on the kernel for the Nexus One got lazy and never tried to see if it compiled on the Sapphire?
If they were developing the kernel for the nexus id hardly call them lazy for not taking the time to check it on other devices.
Not really a technical question but I was wondering what we "noobs" and devs that aren't working on the 3.0.8 kernel can do to speed up or help in the development (we're all in this together right!?) Donations may help but are there any builds we can test with alogcats or just repetitive labor that manpower can aid in? If so feel free to put it here. One tip, guides to non intuitive stuff would help because like I said there are a quite a few noobs lurking (me included). Hopefully this is in the right thread I was contemplating putting it on the general but I wasn't sure.
I'm sure if they needed our help they would ask as they know many of us want to help. Best thing to do is just be patient and not bug them.
I guess you can help by flashing the build posted in the cm9 thread and reporting any bugs that haven't already been reported.
Sent from my SGH-T959V using xda app-developers app
This is a terrible way to get on the good book. Just fork bhundvens github repo. Make changes that work or look good, then push a pull request, then you'll be good.
Also, its called Aries not aires
Sent from my SGH-T959V using xda premium
Sit tight, let Bryan do his thing, and enjoy it when it gets here.
Sent from my SGH-T959V using xda premium
gregcapps said:
Sit tight, let Bryan do his thing, and enjoy it when it gets here.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
A passive approach works too
Educate me what is Aries?
Bitcloud30 said:
Educate me what is Aries?
Click to expand...
Click to collapse
It is the proper Kernel for ICS which is more stable and offers better battery life. More specifically it is the machine type of the phone. Currently all builds are herring.
it's not a "Proper Kernel" per se.
Just the team hacksung people created a generic kernel to work with for all the Galaxy S 1 devices. Well, there are alot more devs over there and that's what's officially supported by CM. So now we are trying to merge into the official Galaxy S CM kernel.
Correct me if I'm wrong but Aries is the processor that our phone runs on it is hardware not software meaning it is a physical component that can't be changed by flashing any files
Sent from my SGH-T959V using xda app-developers app
anoymonos said:
Correct me if I'm wrong but Aries is the processor that our phone runs on it is hardware not software meaning it is a physical component that can't be changed by flashing any files
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
nope, the processor is hummingbird. too many codenames. :silly:
also known as Exynos which is what anoymonos was getting confused with.
One of the big reasons to get on a kernel based on the Aries source is that it makes it a lot easier to move forward with AOSP releases. Right now, "our" kernel is a bit of AOSP, a bit of Samsung stock, a bit of TeamAcid work, a bit of TeamHacksung, a bit of..., so every time something comes up, it is a "custom job" to add it. I won't say that getting closer to mainline code will make JB a slam dunk, but without it, it would likely be lipstick on the pig.
Aries and Herring are Board Names (think motherboard).
Exynos and s5pc110 are Processor Names (both are SoC with the RAM in a PoP configuration).
Herring is the board name used for the nexus one and nexus s in Google's AOSP Samsung source.
The main board definition file for herring is: mach-herring.c
When Samsung worked with t-mobile, at&t, verizon, etc... to make Galaxy S phones, they basically reused the AOSP Samsung kernel for multiple devices. For instance, if you look at our UVKJ6 kernel drop, you will notice ifdefs in there for VIBRANTPLUS (Galaxy S 4G), KEPLER (Captivate), DEMPSEY (Infuse 4G), and a few others.
Aries is the main board definition file for the stock kernel is: mach-aries.c
Even though the board name is still herring. Ger.
They basically copied mach-herring.c to mach-aries.c and made their changes in mach-aries.c.
The Aries kernel, like jeffsf mentioned, is a kernel made by teamhacksung to be a combined kernel for galaxy s devices, and they use mach-aries.c and the aries board name.
If you get the stock kernel drop for any of these other devices in the same kernel drop from their respective drop, there will be subtle differences between each kernel drop. (crazy huh?)
And every file that samsung touches gains tens of lines of ifdefs, sometimes conflicting, as well as code that was '#if 0'ed out because they didn't code it right and left some other variable definitions without also '#if 0'ing them as well leaving nasty build warnings.
If you don't know anything about embedded devices, linux kernel development, or kernel debugging, just lay back and chill. We're getting close, just some nasty rough edges to clean up.
If you do have one or more of those skills, join us in #teamacid.
As it stands right now, most of the problems are GPIO issues. I am having a rough go at figuring out our GPIO configuration for this phone. Everytime I think I figure out something I find that I am wrong.
Also, to make things harder and more confusing, unlike the stock kernels, the aries kernel puts the GPIO pin configuration right in mach-aries.c, where as stock kernels put them in include/mach/gpio-settings-<devicename>.h... :sigh:
Hopefully m4xm4n and jeffsf can give me a hand with this stuff.
It would be nice if some teamhacksung members could give a hand and some guidance.
bhundven said:
Aries and Herring are Board Names (think motherboard).
Exynos and s5pc110 are Processor Names (both are SoC with the RAM in a PoP configuration).
Herring is the board name used for the nexus one and nexus s in Google's AOSP Samsung source.
The main board definition file for herring is: mach-herring.c
When Samsung worked with t-mobile, at&t, verizon, etc... to make Galaxy S phones, they basically reused the AOSP Samsung kernel for multiple devices. For instance, if you look at our UVKJ6 kernel drop, you will notice ifdefs in there for VIBRANTPLUS (Galaxy S 4G), KEPLER (Captivate), DEMPSEY (Infuse 4G), and a few others.
Aries is the main board definition file for the stock kernel is: mach-aries.c
Even though the board name is still herring. Ger.
They basically copied mach-herring.c to mach-aries.c and made their changes in mach-aries.c.
The Aries kernel, like jeffsf mentioned, is a kernel made by teamhacksung to be a combined kernel for galaxy s devices, and they use mach-aries.c and the aries board name.
If you get the stock kernel drop for any of these other devices in the same kernel drop from their respective drop, there will be subtle differences between each kernel drop. (crazy huh?)
And every file that samsung touches gains tens of lines of ifdefs, sometimes conflicting, as well as code that was '#if 0'ed out because they didn't code it right and left some other variable definitions without also '#if 0'ing them as well leaving nasty build warnings.
If you don't know anything about embedded devices, linux kernel development, or kernel debugging, just lay back and chill. We're getting close, just some nasty rough edges to clean up.
If you do have one or more of those skills, join us in #teamacid.
As it stands right now, most of the problems are GPIO issues. I am having a rough go at figuring out our GPIO configuration for this phone. Everytime I think I figure out something I find that I am wrong.
Also, to make things harder and more confusing, unlike the stock kernels, the aries kernel puts the GPIO pin configuration right in mach-aries.c, where as stock kernels put them in include/mach/gpio-settings-<devicename>.h... :sigh:
Hopefully m4xm4n and jeffsf can give me a hand with this stuff.
It would be nice if some teamhacksung members could give a hand and some guidance.
Click to expand...
Click to collapse
Hopefully you get the help you need. Hey here's a dumb question, could you not call the manufacturers of the phone and ask them what the gpio config is?
IIRC the gpio functions are part of a proprietary code source. So no Samsung will not tell you.
eollie said:
IIRC the gpio functions are part of a proprietary code source. So no Samsung will not tell you.
Click to expand...
Click to collapse
The GPIO pins are signal pins on the SoC that allow you to connect external devices to the main cpu.
It is actually specific to the board because each phone have different connected devices (such as lcd panel, wifi, touch screen, etc...).
The GPIO pins and interrupt signals are all documented in the S5PC110 User Manual, but the pin layout in that manual is specific to the reference board it is describing. Each phone/device has its own GPIO layout and it is specific to the schematic.
Sure wish we had a vibrantplus schematic.
airfluip1 said:
it's not a "Proper Kernel" per se.
Just the team hacksung people created a generic kernel to work with for all the Galaxy S 1 devices. Well, there are alot more devs over there and that's what's officially supported by CM. So now we are trying to merge into the official Galaxy S CM kernel.
Click to expand...
Click to collapse
OK...maybe not a "proper" kernel technically , but certainly a whole lot closer to what to we need to have a better experience with the newer versions of android os.
Sent from my SGH-T959V using xda premium
you aren't wrong. I just explained it a bit.
@othern00bs
Here is a simple way to put it for the others who are confused
CyanogenMod Team made kernel = aries = more polished = newer kernel version = we can get regular kernel/version updates because the team acid members won't have to manually port them = potentially Jellybean in the long run (as soon as ICS is polished)
TeamAcidMTD kernel = herring = older version ported to work with ICS = needed to port again for JB = buggier = degraded bat life = manually having to port each change and CM version
bhundven said:
Sure wish we had a vibrantplus schematic.
Click to expand...
Click to collapse
What, the 2426 pages of S5PC110 manual aren't enough bedtime reading for you?
(No, the page count is not a joke.)
Well, I agree that getting Some Hacksung member on IRC should help you.
The Nexus S has the same CPU as our phones, same storage, same screen and they get OTA updates right to jellybean. What is the difference between that phone and ours that would make using their ROM's to help with our phones?
One of the reasons the x86 platform has been so successful is that there are thousands of pages of requirements that make most versions of computers running with an x86 CPU "look the same" to an operating system. For example, the video card always has to implement the same set of instructions and the same way to draw things on the screen.
Unfortunately, phones aren't as generous.
While other phones use the same CPU, they often use different chips to handle things like the keyboard, screen, audio, GPS, phone radio, WiFi, Bluetooth, USB,... Each of these requires a different driver (the code that lets the kernel "talk" to the chip in a standard way). Remember Windows 9x when every time you bought a new mouse, video card, or whatever you had to search for the right driver?
Worse than that, there are hundreds of pins on the CPU and no "wiring diagram" for the devs to work from. Some of the big puzzles the devs are working with are figuring out which pin goes where when making these drivers connect up right. Not only is it knowing which pin goes where, but is it rising edge means "1" or falling edge, should the pin be inactive high, or low. How fast can the device take data?
Then are the "proprietary bits" -- this is the biggest "lie" about devices claiming to be "open source." Even though parts of the device may use Linux or have source available for the dev to look at, some things are just "binary blobs" that the manufacturer wrote themselves, or obtained from the chip vendor and added to their device. No source is available. In some cases, they can be re-used with a later kernel version. In others, they are just "too old" and you're stuck because they don't implement certain instructions that a newer kernel needs, or implement it in the "wrong" way -- think trying to use a Windows 95 driver with Windows 7 -- It just isn't going to work.
For the SGS4G, some of the proprietary bits we are stuck with include:
Boot loaders -- the code that runs when the phone starts up that knows how to read the flash and start the kernel
RIL -- The code that runs the "phone" radio
GPS
TV Out
WiFi Calling
I know I've got all three of the Samsung source drops for our phone on my machine, as well as two versions of kernels from AOSP (semi-official Google source), two versions of Linaro, mainline Linux, CyanogenMod, Team Hacksung, and a few more, all of which include drivers for several phones similar to ours. It chews of a bit of disk space, but sometimes can provide insight.
We can't "just build JellyBean" as there have been some very significant changes in the kernel between the 2.6.35 version we have now, and the 3.x line that JellyBean needs to run. For example, how "events" are handled by the kernel has changed. These are things like pressing a key, so they are sort of important to get right.
Thanks. I was just cruising around looking at Sammy phones and saw that and it looked similar specs. I know all about drivers/pcs/different devices/chips used in things, run a repair shop fixing electronics/pc's, I do reflowing, reballing, etc. Just didn't realize they made the Nexus so different. That's fine, I'm happy with the Remi ICS for now.
So... you can remove and replace bga chips?
Sent from my SGH-T959V using xda premium
Once someone tries and screws it up, please send the remains to bhundven so he can trace out the circuit board
(Joking on trying it, not joking on Team Acid being able to benefit from a destroy-able SGS4G.)
There's a galaxy s 4g main board on eBay right now ending in like 20 min currently at about 5 bucks
Sent from my SGH-T959V using xda premium
So, first of all, I'm not entirely sure if this thread belongs in this category, but since it's something pretty wide, I guess it wouldn't hurt.
So I'm looking into flashing Linux into a phone (an sgs2, more precisly). I'm not talking about chroots under android and etc, I'm talking about actually flashing grub, the kernel and every other files that would usually come with a desktop distro. I'm toying a bit with Gentoo, see if I can recompile the whole thing for ARM before probably ending up bricking my device.
Anyways, I want to know if anyone has every tried flashing the whole thing into a phone, be it android, windows phone, etc, and what would you guys think about it.
I'll be trying with an android phone, since it pretty much uses the linux kernel, and so drivers shouldn't be too much of a pain in the ass to recompile. Might also keep the original boot loader until I feel good enough about completely eradicating the base software that the hardware was designed for.
any thoughts/advices/insults/mind farts on the subject welcome
did you hear about Ubuntu for android project? it's based on GB 2.3.6 but ATM i think the project is stuck. you can see more information on Ubuntu page I'm subscribed to information about it 'cause I will love Ubuntu running on my S2 too. but I heard nothing about other available project from other people
Sent from my GT-I9100G
Great Question! that's something about which I am interested as well. However, I think you might try looking around the "Hardware Hacking" thread or post your question there maybe? I'd like to, but I can't...since I am a NOOB!
---------- Post added at 01:11 PM ---------- Previous post was at 12:30 PM ----------
crzr said:
did you hear about Ubuntu for android project? it's based on GB 2.3.6 but ATM i think the project is stuck. you can see more information on Ubuntu page I'm subscribed to information about it 'cause I will love Ubuntu running on my S2 too. but I heard nothing about other available project from other people
Sent from my GT-I9100G
Click to expand...
Click to collapse
Yea that's awesome, I think I saw a couple of videos on youtube with some guys showing Ubuntu running on their phone
I will do it. I will post if something new comes. But I am happy right now with ICS/JB roms. I'll wait for their Ubuntu for android release if they decide to make possible Ubuntu for android phones
Sent from my GT-I9100G
crzr said:
I will do it. I will post if something new comes. But I am happy right now with ICS/JB roms. I'll wait for their Ubuntu for android release if they decide to make possible Ubuntu for android phones
Sent from my GT-I9100G
Click to expand...
Click to collapse
yea, i think the OP had in mind to bypass android? perhaps? and to use the phone's hardware/kernel parameters in order to boot linux onto it
ilmostro7 said:
yea, i think the OP had in mind to bypass android? perhaps? and to use the phone's hardware/kernel parameters in order to boot linux onto it
Click to expand...
Click to collapse
Yeah, I meant getting ride of the underlaying OS and flash linux in place of it.
I think ubuntu uses chroot under android, I haven't seen anything about flashing it into the device.
What I have in mind is not just flashing it on android phones, but about any piece of hardware decent enough to run it (although the existing drivers on android phones would help).
Right now I'm toying a bit with the cross compiler, but I haven't really started any serious project about making it happen.
You can flash backtrack
Yea, that's why I suggested, initially, to take a look at the "Hardware Hacking" forum...otherwise, you can learn about Systems Programming --maybe a good start might be Programming Embedded Systems, 2nd Edition
With C and GNU Development Tools
By Michael Barr, Anthony Massa
Publisher: O'Reilly Media
Released: October 2006
Pages: 336
btw: sorry, I can't post links, but you can google on how to get started
also: HIT THE THANKS BUTTON IF I HELPED YOU, too
I've made several attempts at the chroot method of adding Linux to an android device with good results. My ultimate goal is to have my android device load and run Linux when i plug it into a docking station so i can use it as a computer. Back to the topic at hand, to add Linux as the native OS instead of android. I would start by building a root file system for android and attempt to copy it over the existing android rootfs. The process would be identical to building the chroot Linux rootfs. The next thing to do is to acquire the kernel source and re-compile it so you can have all of the modules / drivers you want. I would say that this would be standard and easy peasy stuff right up until you got to the X11 and video hardware acceleration.
If your going to try this, I would look for a device that has the following:
1) Kernel source available - make sure there are good instructions on how to configure and compile
2) Device is easily unlock-able and root-able
3) Has a micro SD card slot
So, first of all, I'm not entirely sure if this thread belongs in this category, but since it's something pretty wide, I guess it wouldn't hurt.
So I'm looking into flashing Linux into a phone (an sgs2, more precisly). I'm not talking about chroots under android and etc, I'm talking about actually flashing grub, the kernel and every other files that would usually come with a desktop distro. I'm toying a bit with Gentoo, see if I can recompile the whole thing for ARM before probably ending up bricking my device.
Anyways, I want to know if anyone has every tried flashing the whole thing into a phone, be it android, windows phone, etc, and what would you guys think about it.
I'll be trying with an android phone, since it pretty much uses the linux kernel, and so drivers shouldn't be too much of a pain in the ass to recompile. Might also keep the original boot loader until I feel good enough about completely eradicating the base software that the hardware was designed for.
any thoughts/advices/insults/mind farts on the subject welcome
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2162316 this can help you?
Sent from my GT-I9100G using xda app-developers app
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.