Related
It's sad that I feel the need to say this... I've searched already or I wouldn't be asking it..
I'm assuming that whenever "they" get the ICS source that it'll eventually be ported to the TP... And was assuming that it'll be much easier porting ICS to the TP since there will already be a GB port and much of it will be "re-usable"? Or is it like starting from scratch all over again?..
Once the source code of ICS is posted the Cyanogen (core?) team will work on making CM8 which will be the ICS version of CM and then the CM-Touchpad team will make it compatible with the Touchpad using the same (if possible) drivers and techniques to do the dual boot with WebOS.
Varemenos said:
Once the source code of ICS is posted the Cyanogen (core?) team will work on making CM8 which will be the ICS version of CM and then the CM-Touchpad team will make it compatible with the Touchpad using the same (if possible) drivers and techniques to do the dual boot with WebOS.
Click to expand...
Click to collapse
That's what I was thinkin.. thanks
yeah, as soon as source is out I think it'll be be hitting this device hard
All I can say is I cannot wait for the source code to be released. I'm way impatient now, thanks to the new teaser dual boot video and chompers android "port".
Sent from my HTC Glacier using XDA Premium App
So after the announcement and the release of the system dump today,by when can we expect full fledged and stable ICS ROMS to come out. Like say CM9
Properly working ROMS will only show up when Google releases the source code. If they do what they did with Honeycomb, and don't release it, then we will never get an AOSP ROM.
Anyone heard whether ICS will be open source or not?
from what ive read on engadget and Android and Me they will release the source code
kuroneko007 said:
Properly working ROMS will only show up when Google releases the source code. If they do what they did with Honeycomb, and don't release it, then we will never get an AOSP ROM.
Anyone heard whether ICS will be open source or not?
Click to expand...
Click to collapse
I've heard that they will release it.
kuroneko007 said:
Properly working ROMS will only show up when Google releases the source code. If they do what they did with Honeycomb, and don't release it, then we will never get an AOSP ROM.
Anyone heard whether ICS will be open source or not?
Click to expand...
Click to collapse
honeycomb wasn't released due to the quality of the source code. i am 100% sure they won't use this excuse for ICS, so yes, there will be an AOSP code drop at some point, my guess is about 2-3 months.
http://developer.android.com/sdk/android-4.0.html
Sent from my MT15i using xda premium
wrsg said:
honeycomb wasn't released due to the quality of the source code. i am 100% sure they won't use this excuse for ICS, so yes, there will be an AOSP code drop at some point, my guess is about 2-3 months.
Click to expand...
Click to collapse
Honeycomb source wasn't released because they didn't want people porting it to phones. I think big red will release the source for both in december
Sent from my CM7 Sensation XE using xda premium
The CM Team has something to say on the topic:
http://www.androidpolice.com/2011/10/19/cyanogenmod-team-there-will-be-no-official-sdk-port-of-ice-cream-sandwich-by-the-cm-team-cm9-will-arrive-when-the-ics-source-does/
Does anyone know of an AOKP build for the nook tablet 16g?
I ask because I like AOKP and in the current state of cm9 development it offers far more settings. If their isn't would it be as simple as compiling the source code with the 2.6 kernel.
It should work if it's working with CM9. The only thing is that it's more work to do and it's not really worth it when there is so much to fix with ICS right now.
Id try from source if I could get the device files and my aokp source would build. Maybe I'll try a quick port for fun.
No.
CM9 is the only ICS based rom in development. I don't know if there are any gingerbread versions of AOKP but if there is, someone could probably port it using the CM7 code.
Keithn said:
It should work if it's working with CM9. The only thing is that it's more work to do and it's not really worth it when there is so much to fix with ICS right now.
Id try from source if I could get the device files and my aokp source would build. Maybe I'll try a quick port for fun.
Click to expand...
Click to collapse
Hey, if you do end up compiling one, be sure to post it so we can try!
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Oh I would love to see an open Kang of ICS, I've been testing CM9 and so far so good is stable but there are some things that need to be fixed for sure.
Sent from my NookTablet using xda premium
I'd love to be able to compile it but for some reason I cant get the source code to compile even an official device and it did work before so my pc is setup. I did do a quick port using the zips but have tons of force closes I need to figure out. I'll play around and see if I can get m5 to work. Obviously it will still have every issue that the current cm9 has.
And AOKP is only ICS
Keithn said:
I'd love to be able to compile it but for some reason I cant get the source code to compile even an official device and it did work before so my pc is setup. I did do a quick port using the zips but have tons of force closes I need to figure out. I'll play around and see if I can get m5 to work. Obviously it will still have every issue that the current cm9 has.
And AOKP is only ICS
Click to expand...
Click to collapse
You should make a thread in development so we can follow your progress/ maybe try and help. I'm excited for this rom because of the limitless customization!
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
I got it to boot just FC after FC lol
Keithn said:
I got it to boot just FC after FC lol
Click to expand...
Click to collapse
Well at list you made it boot, take it from there and keep it up. Good luck!
Sent from my SGH-I897 using xda premium
Got it to boot with no FCs however the screen thinks it's 90 degrees to the side yet the toutchpoints on the screen are accurate for the way its being held.
Port
I did a port of the Kindle Fires AOKP and got it to boot but after going back and flashing gapps it stopped booting past Cyanoboot.
I might try compiling in a Ubuntu vm later.
EDITKeithn do the app previews from the recent apps key look rotated?
I made a thread in general about It, its probably a better place to figure this out. My entire screen is 90° off not just the recent apps lol
Sent from my Nook Tablet using XDA
Hey guys,
Could you explain to me in an accessible way, why the exynos source code is so important for the development of custom roms?
We have a multitude of rooms already, how were they build? If no official sources are available, are custom roms in any way inferior to Samsung stock android (eg lacking hardware video acceleration, heavier battery drain, non-functioning ports/radio, etc. )
Does the code have to be released periodically in a best case scenario by Samsung, ie. with any major android or firmware update, or is it a one-time thing?
And finally, can devs do something with the source code that was recently released by Samsung?
You probably will instantly recognise that I have no programming background, so apologies in advance if this sounds stupid
A simple way to understand is this..
Just how with every new update of windows you need updated drivers to get the graphics card, audio etc working same way we need certain drivers for the chips inside the phone. Since these are designed by Samsung they control the right to not allow others to know the design of these chips. That's why they won't make it open source instead release these drivers so that custom ROM builders can use it.
Currently these drivers have not been released for jellybean so the phone won't perform in optimal way. Till they release it we will be using previous drivers along with clever fixes by the developers.
Sent from my GT-I9100 using xda app-developers app
iamanoopmk said:
Currently these drivers have not been released for jellybean so the phone won't perform in optimal way. Till they release it we will be using previous drivers along with clever fixes by the developers.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks- this really helps. So that means we have the official and fully functional drivers in CM9, but only through workarounds can the devs get them to work in, for example, Jelly bean based CM10?
They are doing the exact same thing in CM10 and CM10.1
They have used old ones and some fixes to compensate. That is why CM10 is smooth but not as much as original JB
Sent from my GT-I9100 using xda app-developers app
So i decided to Start this topic because of actually given destrictions of using and sharing a kernel,which Source Code is closed Source.actually it will affect our device in that way,that only ics could be compiled and shared... So I think we should build a kernel by ourselves,not by recompiling a OEM Source Kernel,but by deving from scratch.All related Files were given by ics Source Code
Sent from my HTC Desire X using xda premium
Our device is said to be fully backward compatible with msm7x27a or 7x25a devices ,in Software and Hardware.So it cannot to heavy to dev own aosp Kernel ,which cozld pass jb or in Future new releases
Sent from my HTC Desire X using xda premium
So really no Dev there,who has enough knowledge to build a kernel from e.g. caf-sources?
Sent from my HTC Desire X using xda premium
greeneyes2910 said:
So really no Dev there,who has enough knowledge to build a kernel from e.g. caf-sources?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
We can build it, but you won't be able to boot your phone with that kernel.
atis112 said:
We can build it, but you won't be able to boot your phone with that kernel.
Click to expand...
Click to collapse
how successful were you with your JB CM10.1 kernel? this must be so frustrating for you
So why are could not boot with such kernel? Every Board have its own made board files e.g. Htc Bravo... The Aosp board files are free build by cyanogen for e.g
greeneyes2910 said:
Our device is said to be fully backward compatible with msm7x27a or 7x25a devices ,in Software and Hardware
Click to expand...
Click to collapse
No, it's not. The SoC is designed to make upgrading a msm7x27a-based device easy; there's no need to alter the rest of the hardware or PCB. So the pin-out (and a few other details) are backwards compatible. This is useful to phone manufacturers, since re-designing hardware and PCB's (and getting it re-certified) is a time consuming affair; being able to upgrade a phone model just by replacing the SoC is a huge time saver and allows manufacturers to introduce a stop-gap upgrade model easily and cheaply.
However, this does not imply any compatibility with the software.Software is cheap to modify, especially in the case of an Android phone.
To draw a (perpetually flawed) car-analogy: Back in the day, you could swap the engine of a VW beetle with the engine of a Porsche with relatively little effort, as the mounting points, engine bay size and drive shaft location were roughly the same. (hardware compatibility). However, this doesn't mean the resulting car has the same performance, handling or fuel efficiency as the original beetle, and the driver had better be aware of the more powerful engine and take approriate caution (But no software compatibility).
Ok that seems clear, but why is it such a problem to bring a kernel aosp ?
greeneyes2910 said:
Ok that seems clear, but why is it such a problem to bring a kernel aosp ?
Click to expand...
Click to collapse
Because HTC (or indeed Qualcomm) made modifications to the Linux kernel, and they haven't disclosed those changes yet. Without those changes, it is nigh impossible to reproduce the kernel as shipped by the current JB rom, let alone make a modified version.
This wouldn't have been such a pain in the rear end if Qualcomm wasn't so restrictive with the amount of information they supply. In order to be able to make a kernel (AOSP has little to do with this), we need the changes HTC (or Qualcomm) made, either
By waiting until HTC releases the source code (Will probably happen at some point, but will take a while)
By reverse-engineering the changes they made to the previous kernel, and porting them to the new 3.4.0 kernel - which is a gargantuan task, and offers little guarantee for success.
We can port a kernel from a similar phone like pico guys did
Yeah something like this was my intension, because such boards or bravo, dhd, desire s, etc, are all don have original kernel sources. so this is exact same to our dx . What makes protou so different to all other devices? anyway, as in fact, that a kernel is compiled from sources (including spezific needed board files etc) it must be possible to recompile a kernel to its sources...
Its ok to wait for HTC Sources already but it also should be clear, that further apis , android os, or real development, would never be possible, when Htc decided that protou will not be upgradeble in future.
greeneyes2910 said:
Yeah something like this was my intension, because such boards or bravo, dhd, desire s, etc, are all don have original kernel sources. so this is exact same to our dx . What makes protou so different to all other devices? anyway, as in fact, that a kernel is compiled from sources (including spezific needed board files etc) it must be possible to recompile a kernel to its sources...
Its ok to wait for HTC Sources already but it also should be clear, that further apis , android os, or real development, would never be possible, when Htc decided that protou will not be upgradeble in future.
Click to expand...
Click to collapse
But it would be really difficult to port a kernel for our phone cuz we have really less no of devs. Even if we had 5 proper devs then we could have made it.
Sent from my HTC Desire X using xda app-developers app
prototype-U said:
But it would be really difficult to port a kernel for our phone cuz we have really less no of devs. Even if we had 5 proper devs then we could have made it.
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
We appreciate the hard work everybody does here, and we are always grateful. Do not feel pressured into doing something just because everybody else wants it
) > Galaxy 3 Android Development > [script] repack-zImage.sh: Unpack and repack a zImage without kernel source, V. 5
So this is nearly exactly what I mean and should be possible with our Kernel
Sent from my HTC Desire X using xda premium
greeneyes2910 said:
) > Galaxy 3 Android Development > [script] repack-zImage.sh: Unpack and repack a zImage without kernel source, V. 5
So this is nearly exactly what I mean and should be possible with our Kernel
Click to expand...
Click to collapse
I assume you're referring to this thread. I fail to see how this will help though, as this is unrelated to the kernel source in any way, shape or form. It merely extracts the initial ramdisk.
But it says that it is possible to decompile a zimage.
So it must be possible to get Board Files from it
Sent from my HTC Desire X using xda premium
greeneyes2910 said:
But it says that it is possible to decompile a zimage.
Click to expand...
Click to collapse
It doesn't.
that s wrong. it is already possible...But that is not needed. all compiled files from kernel should be located anywhere on device