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.

Ice Cream Source Build?

Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it

It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170

Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App

Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)

You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App

Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App

hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.

You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.

Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App

Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827

not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together

Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.

I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App

DREAMteam Froyo source code

Hi there,
I'm trying to build some froyo rom for g1 from source. The problem is that lot of stuff lying here is old, unusable slow or hopelessly broken. The only rom that seems to work is hxxp://forum.xda-developers.com/showthread.php?t=1273549
[Rom][2.2.3 AOSP] DREAMteam Froyo v2.0.0 [9/3/2012]
The kernel source can be easy found by Ezterry
hxxps://github.com/ezterry/kernel-biff-testing/tree/ezgb-2636-v1.5.2-20111106
but I can't find any (git) repo or hint how the "DREAMteam" guys built it. :crying:
Thanks in advance for any hints,
ptau

pm the devs
Sent from my HTC Vision using xda premium

All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Sent from my GT-I9300 using xda app-developers app

xillius200 said:
All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Click to expand...
Click to collapse
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau

ptau said:
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau
Click to expand...
Click to collapse
Well I got in touch with tval aint spoke to him for a while. He said a repo was never made for DREAMteam froyo and the way in which it was created some by pushing files not everything was coding, there was not much point in a repo and he has not got around to it lol and I totally agree with him. So best thing would be to compile a rom from plain AOSP and begin to modify it yourself, this way you learn and better understand rom creation. Plus doing it straight from AOSP will give you the updates you want and in most ways will actually be better ^^ If you want any help I could always introduce you to a few devs see if they would be willing to help ^^
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^

99%
xillius200 said:
As far as I remember when it was first started they never had a repository and unless it has changed they still do not lol ill email tvall later lol seems Ldrifta is gone.... :'( if not you can always just compile a normal aosp and then customize it to your liking and speed helps you learn on how to speed up roms that way unlike having an already fast rom of which you learn less from.
Click to expand...
Click to collapse
Thanks. After I looked in the zip, I thought something like that.
Seriously, you don't need speed with this hardware.
Think of cheap, stable, not battery eating
and hackable ARM11 development platform
After that incident with kernel.org they removed all the old android repos
so I have hard times to find the G1 pieces again. ezterry rocks. The kernel
changes are in his git, I could tweak+build the kernel with all the
modules I needed.
Let's see how to get the aosp together ...
(any hints greatly appreciated
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^
Click to expand...
Click to collapse
I know, but my German is much better, I swear :angel:

Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..

tvall said:
Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..
Click to expand...
Click to collapse
Thanks for the email with tips.
I try to document the building process here:
hxxps://sites.google.com/site/aospdream/
As always, any hints or help from anybody are greatly appreciated ...
Thanks,
ptau

[KERNEL]Nexus 7 Compiled from Kernel.org Source

Hi All!
I have been trying to compile a Kernel for Android from Kernel.org Source. Avidly awaiting a Nexus 7 I got straight to work. I have created a zImage. I have been trying to document the process but rather than type it again I have been doing it here. If someone with a Nexus 7 wants to give this a go I would be very much grateful. This is an ongoing process. I have included the file and necessary instructions here...
It looks like I cant post external URL's .... YET! If you want to post here or PM Me I will send you the links.
If someone could test this for me it would be greatly appreciated.
Thanks

I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)

Bogdacutu said:
I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)
Click to expand...
Click to collapse
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.

JamesSawyer said:
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.
Click to expand...
Click to collapse
Okay then, I can do that. I assume you can PM links?

You might be able to state the URL address in your post for your kernel. I'd test it and I guess others may also.

Hi All,
I have someone from Neowin who is going to post the links for me.
At the moment my guide and files are all disjointed I am trying to organize it better.

Great idea! I'll look around your thread @neowin.
What supposedly differences are there from the native android kernel and one compiled using the code from kernel.org?

Personally I just like playing with Bleeding Edge code. You would get all the latest features from source as well as bug fixes most end users wouldn't see. Performance is to be determined, Battery life and CPU performance etc. Its also quite a little Niche that I like been a part of if it all works and comes off.

The kernel you're compiling most likely won't work if you don't even have the machine definitions nor the drivers for your nexus (seeing that you have taken the source directly from kernel.org)
The best of testing a new version would be to backport it but doing so takes an incredible amount of time and considerable skills.
Envoyé de mon Nexus 7 en utilisant Tapatalk

I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.

JamesSawyer said:
I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.
Click to expand...
Click to collapse
You need to have proper board files, proper drivers (device-specific ones) and tons more. I don't think it will work without those. Then chances are it's not going to compile properly; it will throw tons of errors. After you get it to compile, you have to get it to boot. After you get it to boot, you have to get it fully-functional (not necessary if this is a test kernel). So unless you have gone through it all, I don't think it'll work.
BUT I may be wrong.

It compiles no problem, That's what I am wanting people to test :good:

JamesSawyer said:
It compiles no problem, That's what I am wanting people to test :good:
Click to expand...
Click to collapse
Ready to test! Check that neowin thread, but all the links I've tried lead to 404

vrutkovs said:
Ready to test! Check that neowin thread, but all the links I've tried lead to 404
Click to expand...
Click to collapse
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.

JamesSawyer said:
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.
Click to expand...
Click to collapse
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha

poondog said:
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha
Click to expand...
Click to collapse
I am trying to ha! :highfive:

Do you have your 3.4 Kernel? Do you have notes how you built it?
Edit: Updated to include 3.13rc8

I have done some more merging from latest Mainline and Flo Kernel from Google. Its building as we speak. Time to head to Tesco.
Hopefully what I have done will get rid of a compile time error I was having.
Has anyone got the ones I made previous to boot. I have my Nexus 7 on the way as of today so I will be testing it on my own sooooon!! :good:

http://linux.jamessawyer.co.uk:8000/
A bit more easy to remember. There are some test builds and experimental stuff on there too. I might do requests if anyone wants me to make a build for their device let me know. Rather than the Nexus 7 2013. I only did that because thats the device I am getting

The link is down

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.