Hey guys,
maybe you know it but Google announced that the Motorola Xoom doesn´t get Android 4.2 official.
But do you think it´s possible to port a rom from the Nexus 10?
Is there still a chance for android 4.2 on our xoom?
Greetings Marcel :cyclops:
There are plenty of threads on this. Head on over to the General section.
CM has promised additional development for the Xoom using 4.2 among others. it is not dead yet!!
team eos
As long as they can get it under 236mb on the system partition it's completely doable. However this thread is totally unnecessary since it's already being discussed in depth.
Related
Hello respected Developers ,
Jelly Bean is released today with some new and important features. Nexus ROM is already available for download. Since Jelly Bean brings updated UI and few new features only it may be possible to port Nexus ROM.
Kindly consider its possibility and reply
Thank you all !
Here is direct download link
http://goo.im/roms/fabolous/maguro/bigxie_JRN84D_rooted_busybox_deodexed.zip
Hmm...so I was right. It can be ported.
Jelly Bean ported to HTC One X http://forum.xda-developers.com/showthread.php?t=1737736
I hope so.
I'm not a Developer, but I hope so :good:
nothing will be done until the source code is released (google said mid july)
Guys, chill. It is best we wait until ics is fully developed with the kernel 3.x before we talk about this. I am sure that this needs ICS as base. I have been researching about this jellybean update the whole day. it is somewhat a small update to the ICS with automatic widget resizing, GoogleVoice (commandable just like siri) and also less lag... this is just like a froyo to gingerbread update as they said in vid reviews.
now our future is on the 3.X kernel:good:
Hi
Did anyone noticed that kernel for jelly bean port on HTC one x.
It is 2.6.xxx
Sent from my GT-I9003 using Tapatalk
neil05 said:
@vishal
You are not the moderator in this forum. So don't act like a mod
Cheers:beer:
Click to expand...
Click to collapse
No, but I am
Thread moved and cleaned. Development section is only for roms/kernels, etc. being worked on with some kind of bootable image. This is not. (First hint was the title ends in a question mark)
Keep it polite guys.
---Jay--- From the Nexus
The porting Guide can be found here
http://forum.xda-developers.com/showthread.php?t=1739561
Thanks Jay
And apologies for posting in wrong section. Everyday we learn something new
Thanks !
Maybe...
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:
chung1213 said:
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:
Click to expand...
Click to collapse
an i9000 stock rom is impossible because samsung wont release one. and jb code is not out until mid-july. let's wait for cm10 to start
Sent from my Transformer Prime TF201 using xda app-developers app
NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.
Vasishta Reddy said:
NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.
Click to expand...
Click to collapse
i9003 will follow, once kernel 3.0 + ics is completely ported and good for day-to-day basis ^^
Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"
vishal24387 said:
Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"
Click to expand...
Click to collapse
K bro,why to waste time in partially working ports lets wait for source code's release .
Vasishta Reddy said:
K bro,why to waste time in partially working ports lets wait for source code's release .
Click to expand...
Click to collapse
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom
vishal24387 said:
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom
Click to expand...
Click to collapse
You're right on that one bro.
Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys
silentvisitor said:
Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys
Click to expand...
Click to collapse
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app
bscraze said:
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Its not about discouraging new rom development. Its about how well we concentrate on each thing to complete it. I am not saying that we should stuck to only one perticular rom development. But remember guys that google will not take a pause for us so that we can complete current cynogenmod rom. New versions of android will contineously come out by google but we must have to think whether we should run behind new roms or should we first build a base kernel 3.x without which every future development will remain incomplete...???
Hi,
This forum is not supposed to accept questions but I didn't find any other forum specific to the A510.
From other thread I see that there is already work on progress for havin CM9 on Iconia up to A500.
Anyone knows of plans for having CM9 on the A510?
Thanks in advance.
that would be great to have a basic ICS, without any implementation of acer stuff !
i don't think there are currently any dev it.
oh yes, that would be great. they're working on a jelly bean release for the a500, but atm there's no developing for our a 510/511 :-(
does anyone know how to propose to integrate the A510/A511 in the cm-work? any offical suggest-page or something?
at the beginning i was debating between the a510 and tf300, and i chose the a510 because it was better in a lot of things. they both got released around the same time (a week apart). but when it comes to android development the a510 gets no love, the tf300 has several ICS custom roms and a couple JB previews. it makes me sad but i still believe the a510 is the better tablet. what makes it even worth is that the older model a500 is getting JB.
mash2k3 said:
at the beginning i was debating between the a510 and tf300, and i chose the a510 because it was better in a lot of things. they both got released around the same time (a week apart). but when it comes to android development the a510 gets no love, the tf300 has several ICS custom roms and a couple JB previews. it makes me sad but i still believe the a510 is the better tablet. what makes it even worth is that the older model a500 is getting JB.
Click to expand...
Click to collapse
same with me. I also thought about asus, but decided to buy the 511.hopefully it's just a matter of time *finger crossed*
SGS2 - CM10 | Iconia A511 - Stock
I've asked this question in the CM's forum, but got no really feedback http://goo.gl/BxSt4
there is an alpha for the a700: http://forum.xda-developers.com/showthread.php?t=1806980
Sent from my A511 using XDA Premium HD app
This thread is about CM9 and the alpha for the A700 is an inofficial CM10.
Mechkilla said:
This Thread is about CM9 and the Alpha for the A700 is an inofficial CM10.
Click to expand...
Click to collapse
yeah, i know. but atm we could gather any cm-info in one thread your right,in future we should differentiate.
SGS2 - CM10 | Iconia A511 - Stock
The universal question to "why no CM on X device" is that no interested developers have the device. CM is a community project where interested developers with the device want to port CM on to it, enjoying the process, however, CM developers don't just go out and buy a device just because users want it supported because well... they do cost money. It's their hobby, not their job
Since I am a newbe I can't post in the dev fourms so I will ask my question here. I sucessfully installed [DEV][CRACKFLASHERS] 4.1 Jelly Bean JRN84D (Gnex)/ JRN84C (SDK) with the WIFI update-crespo-JRN83C-preview-2012063001 but no audio is there a workaround a driver perhaps anything, I like this rom it's super fast on my Nexus S
Chris
This wouldn't belong in development anyway (starting new threads in development is for DEVS ONLY) so it's good you couldn't post there.
If you want everything working you should stay away from SDK ports. It's not what you want to hear but it's the truth. There is no source code to work from so they are often very wonky.
No, there is no audio. You have installed the latest port.
There will not be any audio fix for the port. We will have to wait for the Update from Google.
Sent from my Nexus S using xda premium
You should have read and asked around before flashing this ROM, as the previous users said and I would like to re-inforce this; SDK ROMs lack a lot of things and are not stable at all. They are not recommended, and they are basically good for previews and stuffing around.
If you really want the new Jelly Bean 4.1, then just wait a week or 2 and a stable version will come out, a custom ROM too.
If you want to revert back to a Custom ROM for now I suggest you use AOKP. It's very stable, reliable and easy to use. Make sure you don't flash a Stock ROM as this can cause problems.
Cheers
From what ive seen there is not audio yet. Devs are working hard to get it out and i appreciate it very much. :laugh:
for Xoom roms
Look in the development forum.
There are some issues with partition size that will have to be overcome to get 4.3 or 4.4 on the Xoom.
Bigrushdog, who was one of the main developers of EOS, posted recently about a 4.3 experimental build.
I just want something stable, I cant say Im going to be paying attention to updating new versions. At this point I dont even care if its rooted any more just want it to work the way its supposed to.
Hi,
Without having any (ROM) development skills I have tried to copy/port/compile a Android 4.4 ROM myself. I did not succeed but in the process I have learned a lot in general about ROM development. I'm not aspiring to be a ROM developer, but at this moment I am eager to know what exactly are the bottlenecks in creating a 4.3 or 4.4 ROM.
I have copied, dissected and altered the work of the guys who have 4.4 (partially) running on HTC Desire HD and HTC Incredible S. To my knowledge these devices have a lot in common (for the most part) and, in my mind, should work on SAGA with some tweaks (ACE -> SAGA / VIVO -> SAGA). Replacing text is off course a simplification, but hey, besides the camera, it is almost the same hardware. I guess there is more to it, because I tried several times, but did not get it to work.
I do not expect to solve these issues, but I wonder what holds the (stable) development of a 4.3 or 4.4 ROM. Outdated source code of drivers or kernel or ....
I was thinking of contacting some of the DEVS who are working on the 4.4 ACE and VIVO ports, but I hope someone on this forum can enlighten me.
Regards,
Michael
Ace and Vivo are indeed closest models to saga and very similar,..when ported to saga,
the roms seems ussualy faster,lighter,cleaner, much less bugy than those, ported (especially directly) from other devices,
.. What- most possibly holds the development for this device is the kernel (or its absence)-as often,..
very likely,-when there was a possibility to boot the port, without jumping also, to self porting/modding its kernel,
we would have seen yet quite a few stable KitKat ports,..
Kernel devs for desire s were briliant- but never many,
now, only @kylon remains active- pardon me if i`m not correct ,,