Database Users

So what is involved in porting aosp to a device?

I'm just curious what's usually involved. I know cyanogen mod does some custom things but ignoring those customizations, what is involved exactly in porting it to a device?
I would assume the major hurdle is driver support. As in the linux kernel compiled/used has hardware support for device x. But other than that, what else?
For ex, with the nook color, what is needed to port it? We can't expect a recent kernel for the nook color from barnes and nobles, but what about the existing kernel used in cm7?
Or if it's not just a kernel issue what are the issues/hurdles. I'm not a developer but just curious from a layman's point of view.
I would think if a working kernel is ready, wouldn't it be just a matter of compiling? I guess I'm curious as to why some say it takes a month or so.

First we need an upgraded kernel to even think about ICS. Then there will also need to be drivers written/rewritten for hardware acceleration and such. Also many other things that will need to be put together to compile even a semi-working rom.
---------------------------------
Sent from my LG Optimus V using Tapatalk

I hope by Xmas, CM team will prevail new ROM running ICS.
I don't care it called CM8 or CM9, as long as it's ICS supporting NC, I'm happy

Slight thread-jacking here, but somewhat related:
Kernel wise, what's the difference between an SDK port vs an AOSP port?

dormido said:
Slight thread-jacking here, but somewhat related:
Kernel wise, what's the difference between an SDK port vs an AOSP port?
Click to expand...
Click to collapse
The SDK is used by devs to create apps so only code relevant to having a semi- working simulator is present. AOSP is the full source code, witch includes everything but it is only built for one device, the galaxy nexus, so there is still much work involved in porting.
---------------------------------
Sent from my LG Optimus V using Tapatalk

One V kernel source code is opened

HTC opened source code of kernel 3.0.16 for One V. It's the same hardware based as our DHD. So I hope now devs can use it to make our custom roms to be fully functional with ICS 4.0.
Who is the first?
http://htcdev.com/devcenter/downloads

FireBlast said:
HTC opened source code of kernel 3.0.16 for One V. It's the same hardware based as our DHD. So I hope now devs can use it to make our custom roms to be fully functional with ICS 4.0.
Who is the first?
http://htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
good news
Sent from my Desire HD using XDA

cool wonder how long before we get a full working ics rom a day or two at most.....

It's not that simple.
While they share the same SoC, they do not have the same board, hence board config files.
The jump from linux 2.6.x to 3.0.x is huge and u can't simply bring in those missing board-spade*.c .h files from the old kernel and expect them to compile. You're going to get a whole lot of compile errors because the underlying linux kernel has gone through so much changes. It's a daunting and massive undertaking.
My money is on devs waiting for HTC to release DHD kernel source for ICS.

[dev][wip]Porting android 4.1 sdk version

Hi,
i am working on a port of android 4.1 (jelly bean) for the play.
like we did with android 4.0
this is going to be easier to port as we can use most files from android 4.0
Nick

progress:
Just got sdk image, 4.1 is rally great on my computer!!!

you sir...are the best!

Sounds awesome as hell. But thought you needed moar moeny to keep developing? Or did you get it after-all?

Will this run better than ICS? and I'm assuming touchpads work? (whatever worked on ICS that is)

Here is a video in this thread showing improvements from ICS 4.0. It shows an increase in FPS and smoothness. http://forum.xda-developers.com/showthread.php?t=1736726
Sent from my R800i using xda premium

Here is the system dump for everyone who wants to port it
http://forum.xda-developers.com/showthread.php?p=27963070

hi,
i still need some money but i have almost enough.
got the system.img unpacked replaced some libs some /bin files and lot of /etc files
hanging on kernel logo (hanging, not rebooting) with logcat: netd1.0 starting

nickholtus said:
hi,
i still need some money but i have almost enough.
got the system.img unpacked replaced some libs some /bin files and lot of /etc files
hanging on kernel logo (hanging, not rebooting) with logcat: netd1.0 starting
Click to expand...
Click to collapse
I was getting the same error when porting.
Is there any specific kernel changes in 4.1?
Sent from R800x

I just looked around the forum, therw are already sdk ports for the one x and an ota update for the gnex. Pretty quick.
Gesendet von meinem Xperia Play mit Tapatalk 2

i was starting to port 4.1 too, and im really sure its a kernel problem.

Kernel isn't a problem.
Can be some libs or some missing files

idea
make the google now launching by using the search button on xperia play.
google search with simple typing on the search button and the google now with hold typing on the search button

you should ask to some help from doomlord

hi,
doomlord can't help as he is an kernel developer and i am kernel/rom developer
he doesn't know very much about developing for roms

It shouldn't be too long before CyanogenMod at least takes a stab at doing JB, so in addition to what nickholtus has already said he's working on, JB shouldn't take too long to make it to us. Given Google's numbering scheme, I would imagine that 4.1 isn't such a monumental change from 4.0 to merit a complete reworking.

lightningdude said:
It shouldn't be too long before CyanogenMod at least takes a stab at doing JB, so in addition to what nickholtus has already said he's working on, JB shouldn't take too long to make it to us. Given Google's numbering scheme, I would imagine that 4.1 isn't such a monumental change from 4.0 to merit a complete reworking.
Click to expand...
Click to collapse
I hope OP's successful as I'd flipping love to get a JB ROM on my phone with its supposed speed increase.
Although, I'm still waiting on this magic Linaro stuff which doesn't look like it'll deliver

We will be able to get JB working as well (if not better) than ICS once official source code is released mid July

i am porting the galaxy nexus version now.
as it is better then the sdk (leaked ota build)

nickholtus said:
i am porting the galaxy nexus version now.
as it is better then the sdk (leaked ota build)
Click to expand...
Click to collapse
Awesome

4.3 kernel sources released! grab them here

http://www.sammobile.com/2013/11/05/samsung-releases-android-4-3-kernel-source-for-galaxy-s3/

Wow man latest news isn t it?? Using Internet Explorer??

And? Could you explain a bit in how it help us?
Thanks.
Enviado desde mi GT-I9300 usando Tapatalk

It means we can finally have custom kernels woooooo
Sent from my GT-I9300 using XDA Premium 4 mobile app

Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?

ahmedmelm said:
Well, I downloaded the source kernel and I need a clear way how to compile it smoothly. I wonder whether I can flash the kernel via Odin or CWM to a rooted stock I9300XXUGMJ9 firmware or not. Will it work? Any walkthroughs?
Click to expand...
Click to collapse
http://source.android.com/source/building.html
Read everything on left hand side
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
http://source.android.com/source/building.html
Read everything on left hand side
Click to expand...
Click to collapse
That's way cool. But any matter to accelerate the process? Would really compiling this kernel and pushing it to existing ROM work?

What do you think source code is exactly? What is it you think you want?
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?

granets said:
I know this is not a Q&A thread but could I ask? Does this release of source kernel code mean, that Samsung finally released the source code for the dreaded mali GPU driver and the FM radio blobs that we so need to make CM roms fully functional and smooth?
Click to expand...
Click to collapse
No. Read following for explanation.
dhiru1602 said:
Blobs are userspace components which correspond to the HAL (Hardware Abstraction Layer). It is this layer which is responsible for communication between the kernel and the operating system. GPU kernel driver is opensource, but the GPU HAL is closed source. This is the case with all the devices, but on our device, much more components of the HAL are closed source like FIMC, FIMG, HWJPEG, TVOUT. Samsung doesn't release the source code for this components because it doesn't necessarily have to. Without the source code, we are forced to use the compiled binary which may or may not work properly. Since we are left without options, we often mess around with the Android framework, making dirty hacks to get them to work. We will not be able to futureproof our device with newer versions of Android unless we have the source code since making edits on compiled binaries is not possible and hence we have to wait for official releases so that we could get newer binaries (blobs). Here is the list of all the blobs that we use on our device. Having proprietary code is not uncommon, but Samsung doesn't release the source code for essential parts of the OS like Graphics subsystem, OMX and DSP, which makes things more complex provided there is no documentation for the SOC, nor they are wiling to help developers.
Click to expand...
Click to collapse

dhirend_6d said:
No. Read following for explanation.
Click to expand...
Click to collapse
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited

granets said:
Thanks for the explanation. So basicaly those kernel sources don't mean much. And I was so excited
Click to expand...
Click to collapse
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.

rootSU said:
They mean as much as every other kernel source release. We still dont have everything we need to make AOSP work properly, but we can now get custom kernels for 4.3 touchwiz roms.
Click to expand...
Click to collapse
These include the latest mali r3p2. So we have now userspace binaries + kernel source drivers. It makes this possible, which is awesome. It's coming for all exynos4 devices.

[Q] cm 10, 10.1, 10.2,11, firefox os porting to sgy possible after stable cm9?

Would it be possible to port jellybean based CMs, CM11 and FirefoxOS after a stable cm9 wit the new drivers that Broadcom relased for our chipset??

ardon8292 said:
Would it be possible to port jellybean based CMs and FirefoxOS after a stable cm9 wit the new drivers that Broadcom relased for our chipset??
Click to expand...
Click to collapse
its possible if broadcom 'release' the drivers i think.

by new drivers i mean the new cm9 stack they gave us...

Broadcom drivers are already released. We are currently waiting for a stable CM9 build from the developers. We hope they will make their best and in the future there might be support for newest CyanogenMod builds, like 10 or even 11. Let's hope everything goes well.

dimsar2013 said:
Broadcom drivers are already released. We are currently waiting for a stable CM9 build from the developers. We hope they will make their best and in the future there might be support for newest CyanogenMod builds, like 10 or even 11. Let's hope everything goes well.
Click to expand...
Click to collapse
If they release the drivers that allow CM10 and above to be compatible with SGY. The current drivers are only useful for CM9.
Sent from my CM7 GT-S5570I