Database Users

Source code building a vanilla ROM

So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...

hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
I unfortunately haven't the answer but I'd like to add that I am curious about this too.

dalingrin said:
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
Click to expand...
Click to collapse
I'll second this and ask that if you do figure it out, please share with the community.

I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.

hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
Check out this wiki from cyanogen:
http://wiki.cyanogenmod.com/index.php?title=Main_Page
On the bottom right you will see an advanced section that explains how to build from source code. (aosp)
Good luck!!! It's definitely not for me, not with kids and a full time job!

Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
rajendra82 said:
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
Click to expand...
Click to collapse

Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.

hallfleming said:
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
Click to expand...
Click to collapse
Nexus One is as Vanilla as it comes. Just straight up Android! I don't think there is anything added to stock 2.1 or 2.2 on the Nexus.

hallfleming said:
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
Click to expand...
Click to collapse
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a developer, I can't personally contribute to the process. But it is interesting to me anyway.

I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
rajendra82 said:
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a deveoper, I can't personally contribute to the process. But it is interesting to me anyway.
Click to expand...
Click to collapse

hallfleming said:
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
Click to expand...
Click to collapse
The first two are attempts to recompile the kernel to put in the ext3/ext4 mimocan fix. The third one I believe is a script for boot logo animation hack to achieve the same thing.
I forgot to mention one more thread:
http://forum.xda-developers.com/showthread.php?t=739823

So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?

hallfleming said:
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
Click to expand...
Click to collapse
I'm guessing not too much. There are somethings that would need to be edited such as handling the capacitive buttons. The i9000 roms handle buttons differently regardless of the kernel so, its apparently an OS level config.
I've been wanting to work on this but I've been neck deep in source code from work.
Here is a good how to: http://forum.xda-developers.com/showthread.php?t=704561

Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App

hallfleming said:
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My point was that given the I9000 rom needs source level changes in order to work as expected(haptic feedback on certain buttons, etc) then running an AOSP build may require some source level changes as well. It may not be as simple as building and flashing.

genokolar's CM7 rom source missing?

why cm7 source are missing.
@genokolar, is there a problem?
reminding: gnu.org/licenses/old-licenses/gpl-2.0.html

i noticed now. there is no rom with source code! oxygen, miui or cm7. how we can trust these ROMs?

Nobody forces anyone to use any custom ROM, if the ROMS have problems or don't behave as they should, someone would find out (and people post comments every day in the dev section), our devices can be equipped with firewalls, loggers etc so that we can check what happens/happened to our phones during the day.

Oxygen source is available, check the post in dzos thread

cm7 source is in their website, Geno just made port. you can get u8800 device and vendor from other source that are in geno git. if i found - you can too it just very complicated

thanks for all replies.
priestx said:
Nobody forces anyone to use any custom ROM, if the ROMS have problems or don't behave as they should, someone would find out (and people post comments every day in the dev section), our devices can be equipped with firewalls, loggers etc so that we can check what happens/happened to our phones during the day.
Click to expand...
Click to collapse
i now no body force us, but what i want is a situation that should be already.
Tommixoft said:
cm7 source is in their website, Geno just made port. you can get u8800 device and vendor from other source that are in geno git. if i found - you can too it just very complicated
Click to expand...
Click to collapse
good news. but u8800-cm7 not an "official" cm7 port, it should has differences.

Android isn't GPL, it's Apache Software License 2.0. You don't have to make the code available for others and you are allowed to use code but not publish the changes.
So as nice as it would be for Genokolar to share the code, he doesn't have to.

at the end he must hear me.
you are did the right thing.
"knowledge grows by sharing"
thanks Genokolar.

[DEV][ROM][Beta] AOKP Acer A500

Closed due to stupid forum rules

Anyone Flash yet???

Why should we donate to you? What's your part in this ROM? However protekk yet posted his ROM here, but as he did use Thor's kernel it was removed! I'll check the github link to see if everything is correct now.

smaury said:
Why should we donate to you? What's your part in this ROM? However protekk yet posted his ROM here, but as he did use Thor's kernel it was removed! I'll check the github link to see if everything is correct now,
Click to expand...
Click to collapse
its just my sig chill look at the top it says where i got this, however it took me 3 hour to get this post up and all the screenshots
BTW this does work cuz im running as i type
i put a footer on now, could you now remove your post, thank you

On github I can't find any source for A500 kernel, please give us a direct link.
Only found device related folder and vendor folder with related configurations and if i'm not wrong they are took from waydownsouth and his team's sources.

Edited
WHY DONT U LIKE IT???

jnktechstuff said:
its just my sig chill look at the top it says where i got this, however it took me 3 hour to get this post up and all the screenshots
BTW this does work cuz im running as i type
i put a footer on now, could you now remove your post, thank you
Click to expand...
Click to collapse
What Smaury was trying to explain to you, is that the AOKP type roms, use kernels that violate GPL. And roms that use kernels violating such license, are prohibited from being posted at XDA, or having direct links to such roms.
If you would read the rules about posting, you would have seen this.
Considering most A500 AOKP roms use Thor's kernel, and his kernel violates GPL, roms cntaining Thor's kernel, or links to it, cannot be posted. Period.
This is why these guys have their own place.
You should remove your post.
MD

haha dang i spent so much time on it, but i dont get it, how does this violate GPL, i used the rom from flexreaper not thor, also i credited people

It's not the rom, but the kernel.
In a short story, GPL basically states that changes to the android kernel must be made public. If a dev does not reveal the kernel source, then the kernel is in violation of GPL. Most decent sites will not host these types, as they do not want legal liability.
Thor is a great dev. Unfortunately he doesn't release kernel source, which is why he has his own site. It's a pity as he really does great stuff.
Kang roms, generally steal code and device trees from other devs, without giving credit to where they took it, and generally claim it as their own. As stated before, most of the kang roms use Thor's kernel therefore are not allowed to be posted. By nature of their practices, they generally are not welcome in a lot of places.
The rules are not stupid. They are in place to protect the devs and the users alike.
MD

Thanks haha I got u now
I will try not to do this again, just trying to learn a become a good developer

[REQUIRED] BETA Testers for my upcoming Kernel

Hello,
Introductions: I am a 15yr old Kernel Developer. Mainly for Samsung Devices. Hacking Kernels and programming is my hobby
I planned to maintain a Kernel for Galaxy NOTE N7000. However, I do not own the device and I want some BETA Testers who can help in testing out my initial Kernel builds.
Testers should-
-Know how to use adb, pull logcats
-And pull dmesg/kmsg logs for me
-Also, do some General Testing
You can have a look at my previous works by clicking links in my sig.
Interested testers, first post in the thread, then send me a PM :laugh:
Looking forward to maintaining some Good Kernels for this device :good:
Cheers, have a good day.

Dangerous lol do you know about the mmc_cap_erase bug for this device?
Tapatalking on my GT-N7000

Even more dangerous if you come to think of that the recovery on the Galaxy Note is baked into the kernel . So when your kernel is borked, your recovery will probably won't work too . Great!

I know about the eMMC bug, and that's the first thing I will get rid of before sending it to anyone for testing.
Edit: please stay on topic
Sent from my GT-I9003 using xda premium

Your gonna brick a lot of phones of people that volunteer you need to get your own note and JTAG unit for resurrecting the many hard bricks in your future... what you need is some donations to get setup and do this properly. I would look into obtaining the funds to do this. Hats off to u for using your skills to build a kernel
Sent from my SGH-I727 using xda app-developers app

TO make things more clear,
I am using Samsungs Update 4 sources(As per Entropy512, it is safe) + clearing eMMC bug to prevent a hard brick.
If anyone wants to test send me a PM.
I do not want to go offtopic anymore, if nobody is volunteering to test. I will close up the thread.
Thanks.
All known Gingerbread kernels for the Galaxy Note and other affected devices listed above
Kernels built from the GT-I9100 Update4 source code release - this includes XplodWILD's CM9 release and my DAFUQ release, hopefully more kernel choices will become available soon
Kernels with MMC_CAP_ERASE removed from mshci.c should be safe - look for it in the listed features of any kernel based off of N7000 Update3. (N7000 Update3 source code without this change made to render it safe is dangerous.)
Click to expand...
Click to collapse
A Sample commit of MMC_CAP_ERASE removed from my GT-I9103 KERNEL which uses same partitioning scheme.
[URL="https://github.com/franciscofranco/GT-N7000-ICS-3.0.y/commit/a1837cda4331d4822d8a3ba3caca8ff0d53f3b64"]Also, this commit by franco.
[/URL]

hey Adi, thanks for coming to our community-- much appreciated ! Developing kernels for the Note has been a challenge.
if you deem it proper release your work openly to our members,
you will know by the number of downloads, and feedback in the thread if your work has been appreciated/accepted/lauded...
i would come forth to test but im not an expert. just a request, be open to feedback - share your focus - safety, overclocking, root , battery or all
thanks again.

rraaka said:
hey Adi, thanks for coming to our community-- much appreciated ! Developing kernels for the Note has been a challenge.
if you deem it proper release your work openly to our members,
you will know by the number of downloads, and feedback in the thread if your work has been appreciated/accepted/lauded...
i would come forth to test but im not an expert. just a request, be open to feedback - share your focus - safety, overclocking, root , battery or all
thanks again.
Click to expand...
Click to collapse
I am always open to feedback! Now a couple of testers are ready to test.
My aim is to make a completely stable kernel, good and smooth , safe for daily use and make this device fly.
I have completely disabled the MMC Brick bug, will send the Kernel for testing to my BETA Testers, once it is good enough for a Release I will post this in the Android Dev. section. I thought of posting this here because I didn't want to pollute Android Dev. section.
Thanks!

make a thread in orignal development section maybe you get much more attention there..
Sent from my GT-N7000 using Tapatalk 2

No offence but you shouldn't have written that you are 15.
Sent from my GT-N7000 using xda app-developers app

SuperMane said:
No offence but you shouldn't have written that you are 15.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Yeah, makes me feel like a complete waste of space !:crying::crying:
Coz I'm 17 with absolutely no real contribution to XDA.

3.10.33 kernel from Nvidia Shield ported to Mi Pad

Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems

reserved

Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).

drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)

Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.

drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.

Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.

so does that mean that there is a chance for cm12+?

Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?

Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.

Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.

drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.

Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.

Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks

rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.

Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia

Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?

drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.