Hi,
I was wondering if it's still an issue that Samsung isn't releasing their drivers source code and so we can't develop fully functional roms with latest version of android for our Galaxy s3?
What drivers do current roms for the Galaxy s3 are using?
I came across the http://opensource.samsung.com/ site and I'm trying to downlad the source code for a JB build.
Won't I be able to take the drivers from that build and use it with the latest version of android?
I realize this is a basic question and I'm sure I'm not the first to think of this, I just want to understand what's hloding us back.
Thanks!
Related
Hi.
I am a noob, not a techy
just curios - how can your devs build ICS roms when Samsung themselves did not build/create/honed/refined the Vibrant for Android 4?
What I am trying to ask is, how can your devs manage to control the hardware via android 4, if Samsung did not supply the codes/drivers/source?
Thanks
I'm not 100% sure but I think I read somewhere you can use the source code to build a ROM and then they used the Gingerbread bootloader/kernel and from there it's debugging.... again I could be wrong.
I think they took the source, and compile the source with the characteristics of the device. then applications that do not work, modified or exchanged for other versions of other rom, like the kernel, and other modifications, which is why the rom, there are many versions which fix bugs Version earlier after many users try it. (an example of this is the ICS Passion, which is now in its version 13)
Well passion is based on cm9. Which is aosp rom using source code android releases. Basically if you have drivers for hardware and a device tree you can use that source to build for any device.
Wherelse Samsung roms are usually not directly from source but just modded firmware from Samsung leaks. Oems do use close sources drivers though, usually better and get more out of hardware.
Sent from my SGH-T959 using XDA App
Hi
Short and sweet, I am busy getting into ROM development, and as exercise to get a better grasp on what is going on, I mostly dabbled with AOSP until yesterday. I am in the process of porting Cyanogenmod 10.2 to Galaxy S2 (i9100).
While going through the CM instructions, there was a segment on how to extract "proprietary blobs" from CM running on the device in question. This is required as part of the build for hardware specific reasons they did not give too much details about.
I just have one query. Has anyone tried to, or know if it is possible to do this blob extraction from ROMs other than CyanogenMod?
That's all folks.
hello all
i like to develop since 9 years old. Actually i am 24. I don't understand well the basics of Android and propietary devices. I used to install CM on all my family's devices, but always unofficial builds and not selfKANGs. Since 1 week ago, I am trying to build the the CM's 11.0 with no luck. Then i went to official google's developers site of android, and finally i got a system compiled and ready to install.
but now, before to push the flashing key, i am doubting about all... i mean, there'r a lot of steps I havent done:
1. obtain propietary binaries from my actual installation
2. not sure about if built the correct official version or compatible for samsung galaxy s iii (gt-9300)
3. i just wanted to add support for a S3C USB Host HUB for connecting my keyboard and mouse into my S3's micro-usb port.
so, now that i have obtained a lot of curiosity about that world, i want to learn more and more... but haven't anything clear at all.
then, can you please answer me the following questions?
1. why everyone is installing CM in S3? And not official android version?
2. how can I configure and add support to my USB host hub into the correct version of the kernel for the actual 4.4 KitKat software (CM-11.0) of my S3's?
3. can you explain me why can't I compile CM-11 or CM-10.2 with my Ubuntu Server 14.04 ? Lot of errors...
I would have more time to ask and ask, but I need to stop here.
Thanks to all for all the information in the posts I have read until now. And for the future's ones.
See ya,
Abel.
Hi all,
I've been experiencing with Team-Gummy Rom source code for quite some time now. I usually compile from source to get the latest, along with some of my own addition. Lately I've been obsessed with having Android L code running on my Galaxy S4 (qcom) and so I downloaded AOSP source and after some failed attempts I was able to build it with the S4 device package from Team gummy.
So way cool! I may have in my hands the first (maybe not but as far as I know anyway) Android L build on the S4. But before going further, I have a question. In theory if I flash the system.img file produced by the build process and keep the kernel and boot.img from my current install, it should all come together right? Anyone here has an Idea what it would do?
Hi all, i've read other threads about this argument but any of them satisfied me.
I am curious about the steps to do for developing a custom ROM for an unmodded device, so for example taking the android source code and make it work on a device.
In my case, I will use a Samsung Grand Neo (GT-I9060).
How do developers manage to port a ROM to a new device? How do they make device features working? Do they use camera drivers and other drivers to reach this goal?
How to upgrade the firmware to a newer version if no newer version is released by the manufacturer?
Sorry for these nooby questions
Waiting for your answers