Related
Now I know this is a ridicilous idea as it defeats the whole purpose, but would it be possible to port gingerbread to xoom, or is there already a gingerbread rom that would work. The bootloader was unlocked in under two hours so could cyanogenmod be ported like it has been to the nook color. I absolutely love honeycomb, and think it is superior to gingerbread, but seeing it on the xoom would only further its abilities. If any developer would be up to the worthless but awesome challenge, or simply has an intriguing idea, please reply.
well i cant say i know much about porting. but all of these honeycomb tablets (correct me if im wrong) are directly based on the ventana development kit. or at least extremely similar. so. my advice is start here. there are some 2.2 + 2.3 builds to play with.
http://developer.nvidia.com/tegra/devkit-ventana
I will take a look in a while, and if I make any progress, then I will post back.
haha, i will have to make sure to get rid of boot.bin. Not really in the mood for flashing a new bootloader.
All the needed image files are here.
Wow, this tegra development kit is absolutely amazing. It includes all the drivers and software for the nvidia tegra 2 platform. I am going to play with this software, and see what I can do. I'm not very patient, so do not expect anything but if I ever get anything working I will post back. Kind of interesting that nvida would release froyo and gingerbread builds for a platform that is as you said almost identical to the xoom,gtab, and other "honeycomb" tabs.Well, hopefuly honeycomb aosp will be released eventualy. Anyways thanks for the link.
Thanked ya
so im using the ics rom and looks great. I know its an alpha build so there aire things to polish. But im having nightmares about ics been like honeycomb when it came out...apps not working, games not been supported yet, the same thing that happen from 3.0 to 3.1 to 3.2 everything had to be repatched to work. I'm seen games doing the same thing. Dead space worked fine on 3.2 now it works like in 3.1 the screen only works in portrait mode. Modern Combat 3 doesn't even load,gta 3 closing every minute (like game loft games from 3.1 to 3.2) I just hope that when the official from gets a release...everything is patched to work. I don't hate pics but am afraid I'll have o wait 3 months to things to work.
jerses said:
so im using the ics rom and looks great. I know its an alpha build so there aire things to polish. But im having nightmares about ics been like honeycomb when it came out...apps not working, games not been supported yet, the same thing that happen from 3.0 to 3.1 to 3.2 everything had to be repatched to work. I'm seen games doing the same thing. Dead space worked fine on 3.2 now it works like in 3.1 the screen only works in portrait mode. Modern Combat 3 doesn't even load,gta 3 closing every minute (like game loft games from 3.1 to 3.2) I just hope that when the official from gets a release...everything is patched to work. I don't hate pics but am afraid I'll have o wait 3 months to things to work.
Click to expand...
Click to collapse
I think it will take awhile for app developers to get up to speed with ICS but more of them will have the incentive to do so as all devices will eventually be running on it.
Yes I just hope that doesn't take more than 3 months...in time of a devices that is an eternity. Why does everything have to be patched or re downloaded to work every update that comes out. But I guess I'll have to go with the flow and accept ics as my new Savior
jerses said:
Yes I just hope that doesn't take more than 3 months...in time of a devices that is an eternity. Why does everything have to be patched or re downloaded to work every update that comes out. But I guess I'll have to go with the flow and accept ics as my new Savior
Click to expand...
Click to collapse
Well, think about it, this is a new version of the Android operating system so not everything is going to be compatible out-the-box. Remember, PC operating systems are the same. When you upgrade from Windows XP to Windows 7, some applications that were fine on XP just don't work properly on 7 and it's up to the application developer to fix it for the new version.
Same with Android. Google provided the ICS SDK a while ago so app devs have had a while to make their apps compatible before ICS was actually released, but sometimes people just don't have as much time to do stuff like this as we would like so we just need to wait patiently for the devs to fix their apps. (Of course, if it's a paid app, emailing them for a timeline isn't out of the question).
Welcome to being an early adopter.
jerses said:
so im using the ics rom and looks great. I know its an alpha build so there aire things to polish.
Click to expand...
Click to collapse
This is where you went wrong. There's not just things that need polish, there's things that still need to be developed. Betas are for polish. They're still in nightly phase right now, its expected that there be a laundry list of imperfections and outright non-functioning features. They're also missing some rather important code (the binaries for a few things) meaning its still going to be a while before some things like the cameras can even begin to function. Additionally, we rely on app developers transitioning to ICS support. This will take time.
Have patience. We are in the early, early phases. ICS is proving to be more powerful than I ever imagined (its ridiculously fast) and with some time it will be refined quite well.
Cubanluke88 said:
This is where you went wrong. There's not just things that need polish, there's things that still need to be developed. Betas are for polish. They're still in nightly phase right now, its expected that there be a laundry list of imperfections and outright non-functioning features. They're also missing some rather important code (the binaries for a few things) meaning its still going to be a while before some things like the cameras can even begin to function. Additionally, we rely on app developers transitioning to ICS support. This will take time.
Have patience. We are in the early, early phases. ICS is proving to be more powerful than I ever imagined (its ridiculously fast) and with some time it will be refined quite well.
Click to expand...
Click to collapse
Im nota worried about this rom inknown devs are hard working and will make aun awsome ir nota better ics rom. What im worried mis about apps support. I just hope it doesnt take that mucho like hc did.
jerses said:
Im nota worried about this rom inknown devs are hard working and will make aun awsome ir nota better ics rom. What im worried mis about apps support. I just hope it doesnt take that mucho like hc did.
Click to expand...
Click to collapse
Regarding app support, please see my earlier post and please understand that it is down to each individual app developer to update their app, as it is with EVERY operating system, the ROM team can do nothing about this.
Hi All
Seems to be a bit backward to not be able to post in the development section, but rules are rules I suppose.
I bought a Xoom a couple of months ago and put on Moray on a UK wifi Xoom. Very impressed and jumped onto ICS with the initial ICS release then played about with nightlys up to version twelve today.
OTG still not working for me, it crashes USB watcher OTG as well.
Music app does not get mentioned, but its terrible. Only small icons and no proper options ?
Camera and Mic were not tried as they are obviosly broken due to missing binaries.
It also seems backward to have widgets only on the apps page.
Battery options made the battery read zero, then made it disappear from the tray as well.
Browser does seem slicker, but back to Moray and its not a huge difference to be fair.
Have issues with various Apps. This makes sense as they still need to get up to speed with ICS. But it does concern me when people say its the best thing ever, when nothing can work as advertised. HW videos are hit and miss. I am also sure I read a while back that ICS would be all singing, why do I need a Ext mount app to write to an external card, same as OTG ? I thought that this would be part of the main build ?
So from my own personal experience, its a change, but until you have a full package with working apps, hardware, then I think people need to calm down with their plaudits for ICS.
I think I will leave the nightlys for a while, but it was great to try, and thanks for the guys putting the effort in making/updating these things.
I'm going to say this with as much respect as I can:
You have zero idea what the development section is about with statements like that.
Stick to stock software if you want a device that works as intended.
Development and custom roms always have caveats and pitfalls.
Thanks for stopping by!
Regarding not being able to post in dev section - it's for development only not questions and a lot of new users start new threads and ask a lot of questions! It makes sense the way it s.
You have to remember that these are alpha builds which are not supposed to be complete or fully working. A lot of devs wouldn't even put these out at this stage because of instability issues. But I am SOOO glad that the EOS team have decided to share these awesome ICS build with us because it may take weeks or even months to get to a full build release or an official Moto release. I know you aren't trying to bash the devs but I have to disagree with your opinions. I love ICS so far. It's fast, fluid and looks great.
Agreed with the widget option. Think the HC way was better but it's a minor issue compared to the speed improvements.
In essence though, I think if the full product is what you want you should stay away from alpha or even beta builds. Stick with full or official releases. Most people who test these roms understand this.
Sent from my Xoom using xda premium
aside from the camera and the mic i have had zero problems with anything i do on the xoom on a regular basis.
if it's an alpha build, it's a hell of an alpha build.
the only thing was it took me a bit to get all the gapps working and to the most current versions
Hi
Well my point was I don't have to be a Dev to know when things are not working. OTG is not working, and this is not a statement saying it has to, but merely a way of reporting it.
Nobody has mentioned the battery dissapears if you change the settings.
People seemed to be obsessed with Google Maps working, but since this is a great media player the bugs seem to be getting left out of the threads.
Now I know there is a lot missing, but why no OTG support built in ? Is this just a Motorola thing ?
I think there has to be a devils advocate here, everyone saying its fast is great, but if you are just using this as a browser, then its not a great indication about how good ICS is.
And to the chap who said I had no idea about Dev things, you are 100 % correct. But this is not aimed at anyone doing the nightlys, this is an ICS comparison. I am sure if Motorola release a version of ICS! Then it would get mentioned, how there are also some annoying new things not hardware or nightly release related. As I said the Music player is abysmal, the widgets is hidden away. The apps selector looks smaller, and some other little things.
So all I am trying to say is yes it seems faster, but since its only partly there, and we shrug when things don't work correctly, does not mean that is is the best thing ever. When we have a full version and all the binaries are working, then we will see the real speed ?
xoom68 said:
Hi
Well my point was I don't have to be a Dev to know when things are not working. OTG is not working, and this is not a statement saying it has to, but merely a way of reporting it.
Click to expand...
Click to collapse
I haven't tested it but others in the thread have and say it's working.
Nobody has mentioned the battery dissapears if you change the settings.
Click to expand...
Click to collapse
It's in the official bug tracker.
Now I know there is a lot missing, but why no OTG support built in ? Is this just a Motorola thing ?
Click to expand...
Click to collapse
At this point the ICS builds are all straight from source so not a moto thing but see above.
So all I am trying to say is yes it seems faster, but since its only partly there, and we shrug when things don't work correctly, does not mean that is is the best thing ever. When we have a full version and all the binaries are working, then we will see the real speed ?
Click to expand...
Click to collapse
That's all well and good but if that's the way you think then stay away from alpha and beta builds. If you are only interested in the full working product wait for official release.
Sent from my Xoom using xda premium
Worst thread ever.
Alpha build!
Thanks for replying.
I don't know what defines a working OTG, but with Moray I used USB Mount watcher and I mounted a 1tb HD no problem. I thought I would not need an app, but no joy. This time when I tried the App it says it was built in. But it hangs at any attempt to identify the HD. Another mount app sees the HD, but can't mount it.
The battery thing I just noticed in the bug tracker, but no one mentioned it in the thread.
No one mentions the poor ICS music player or widgets.
I just see people obsessed with calendar and Google maps ?
And to all saying Alpha Build....considering Motorola never added OTG support to HC, but the custom roms did. My point is who is to say they will add it to ICS. I thought it was supposed to be standard. If people have to Root their device to get OTG and towrite to External SD. We have not come that far forward. And in fact the threads I readprevious to buying a Xoom had people waiting months for updates, are people really expecting a Motorola Ics within the next 6 months. This alpha build will not get any better until there are binaries, soapart from a few settings tweaks, it will stay Alpha for a long time I reckon.
I understand you saying stick to stock, but the built in things to ICS are poorer in relation to HC, I suppose no one mentions things in case they appear to be rude, but I think its better if people know the negatives as well, as it just seems to be people with Ice Cream tinted glasses at the moment
xoom68 said:
I understand you saying stick to stock, but the built in things to ICS are poorer in relation to HC, I suppose no one mentions things in case they appear to be rude, but I think its better if people know the negatives as well, as it just seems to be people with Ice Cream tinted glasses at the moment
Click to expand...
Click to collapse
Again though, this is an alpha build so you cannot expect this to be fully working or all "built in" functions to be bug free.
If the current builds don't work for your daily needs that's fair enough, wait for a more complete build. But you cannot burn ICS on the strengths, or weaknesses, of an alpha build.
Sent from my Xoom using xda premium
Be happy that we are the only tablet that has a ICS build to be bug free enough to be a daily driver for a good portion of users.
(Wifi, GPU acceleration, netflix work perfectly, browser is very much improved)
I can't post in the development section either.
But a thread like this is just the place to boost my post count.
---------- Post added at 08:56 PM ---------- Previous post was at 08:55 PM ----------
Ten characters.
Honestly, all I can really say to this... one step at a time, one day at a time.
You, as well as others, must understand and respect the fact that the developers here are putting in their own free time and effort to bring us these ROMs and extras, at absolutely no cost to you, the user.
Trying to tear apart tons code that has already been written to troubleshoot, fix problems, and test is hugely tedious and very time consuming.
Right now, I suggest not trying to put the cart before the horse. Simple things like asethetics, minor functionality (I.e. OTG, etc.) that is not crucial to the operation of the device is going to have to wait.
Important parts, like 3G/4G radio functionality, Google apps, video playback - the essentials come first.
Truthfully, I would not waste my time reporting the smaller issues, we know that they are there. When the developers get the foundation built and stable enough to work with, THEN will they ask for help with bug reporting and suggestions and such. No need to overwhelm the developers at this stage of the game.
Just my 2 cents.
xxspark89xx said:
Honestly, all I can really say to this... one step at a time, one day at a time.
You, as well as others, must understand and respect the fact that the developers here are putting in their own free time and effort to bring us these ROMs and extras, at absolutely no cost to you, the user.
Trying to tear apart tons code that has already been written to troubleshoot, fix problems, and test is hugely tedious and very time consuming.
Right now, I suggest not trying to put the cart before the horse. Simple things like asethetics, minor functionality (I.e. OTG, etc.) that is not crucial to the operation of the device is going to have to wait.
Important parts, like 3G/4G radio functionality, Google apps, video playback - the essentials come first.
Truthfully, I would not waste my time reporting the smaller issues, we know that they are there. When the developers get the foundation built and stable enough to work with, THEN will they ask for help with bug reporting and suggestions and such. No need to overwhelm the developers at this stage of the game.
Just my 2 cents.
Click to expand...
Click to collapse
Thank you for the great work you are doing on this. I can see that it can be slow going but you seem to be making good progress.
Last night, +Steve Kondik took to twitter to vent a little bit:
"CM has been getting a lot of crap lately for taking so long with a release. Guess what? It's not that easy. We don't just call something stable unless we mean it. *Also, RC1 is soon!* The most stable devices will get the RC first. The system we've put in place should allow other devices to catch up quickly. More details later this week "
Now to combat the obvious questions:
# As Steve stated, this will not be for all CM9 supported devices. The Nexus S and Galaxy Nexus can be considered safe bets, but the final list won't be available until release day.
# As always, the proper day of release is difficult/impossible to predict, but we anticipate a code freeze going in place tomorrow at the earliest.
# Yes, this means we will actively be running two separate RC phases (CM7 and CM9). Bug's should be reported to the issue tracker once the release is made, not in the comments on our posts.
# There has been a lot of talk surrounding Linaro in CM. While CM 9.0 won't ship with all the patches on gerrit, quite a few of them are already incorporated and others are sane enough that they will likely be there. There are still some issues surrounding the updated gcc used for the Linaro patches that don't play nice with AOSP.
# Nexus One: For the time being, the N1 will not be supported. We can get it to build/boot/run, but the hacks required break Google's CTS, so until that is rectified, you won't see any build with CM's official stamp of approval.
CM9 News
And from a followup a few hours later:
******
+Ricardo Cerqueira sat down with XDA recently for a developer interview
To piggy back on our comment about the N1 and CTS, Ricardo describes why we don't just shrug off that requirement.
Because it opened a can of worms that can’t be closed again. Getting it to work needed some very ugly workarounds that directly go against Google’s compatibility document for ICS. An app developer targeting ICS as a minimal version for his apps has the right to expect some functionality to be guaranteed on a device that claims to be ICS, that wasn’t (and isn’t) true for ICS builds with these hacks. That’s one the main reasons CM9 does not officially include a bunch of devices that are “working.”
...and some users understand that, but a lot don’t, and they’ll submit error reports on those apps, or they’ll rate it badly at the Play store. This is not a hypothetical scenario, it has happened whether we like it or not, asked for it or not, CM’s userbase is large enough to matter, even if you don’t count derivatives. We have a responsibility not to cause that kind of grief to app developers and we did. With all the mostly bull**** talk about fragmentation, we actively contributed to a break in the platform, no matter how small. That’s not a good thing :X People SHOULD know these builds contain hacks, but you’ve surely realized by now that they don’t
******
dookie23 said:
....so until that is rectified, you won't see any build with CM's official stamp of approval.
Click to expand...
Click to collapse
so.... is that ever gonna get rectified
charlie_su1986 said:
so.... is that ever gonna get rectified
Click to expand...
Click to collapse
I wonder what are the hacks he mentioned in the post. Was it the hboot hack, m2sd hack or swap partition...etc?
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Kannibalism said:
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Click to expand...
Click to collapse
Don't get me wrong, I love seeing the talented devs make awesome progress on kang'ing CM9 and things are coming together nicely. What I am getting at is not whether Cyanogenmod is releasing a CM9 rom officially for the Nexus One, but it's what Ricardo Cerqueira said about the hacks breaking Google CTS. This could mean that apps might not run or worse yet, FC's for no reason.
Now, the real questions are, what are these hacks Ricardo was talking about and is that gonna get rectified?
the hacks they talk about could be small stuff like ta camera fix etc since vendors do not always release new drivers.I would say that the nexus one is using a few hacks for drivers in order to make everything work better
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
decoherent said:
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
Click to expand...
Click to collapse
I agree with this post i would put the blame on google for not pushing the vendors for the broadcom drivers since android is open source after all but once again great works by our devs and thanks for letting us experience the latest versions of android on our devices
EDIT: i must admit that i have better devices to use than the nexus one but the community keeps me coming back for more
Sent from my Nexus One using xda premium
I've got a question I tried to answer myself, but I couldn't resist to post it on the forum.
Is the ICS leak a great step forward for all Atrix users ?
For those who wanted HWA, fingerprint scanner, working camera, of course it is... But is it a step forward for the release of a STABLE CM10 with a STABLE kernel ? This question is more open to a debate than a simple answer.
This leak didn't provide any option for those who have the wrong tegrapart (Mine is OK), or a lapdock, or those who use Chrome and want a generally reliable ROM (Stability, I/O perfs, battery life). They have to make a compromise but we still didn't reach THE ROM(s) that makes everybody happy.
The missing thing to get the ROM(s) that will make us all happy is the kernel source... Why didn't we get it with the ICS leak ? Well let's exclude this question from this thread and maybe talk about it after this debate is (almost) closed.
Personally I'm happy to have this new ROM, it's fast, smooth etc. but my lapdock is still borked so I'm really frustrated not to have this awesome tablet display that works with EVERYTHING but not MOTOROLA's own peripheral... Damn it !
So, what's your case ? Of course you may have found satisfaction with the ICS leak, but are you as frustrated as I am to be this close to the ultimate goal ?
The debate is open, I hope I broke the ice for some people who are in my case and feel like forgotten.
I think that leak does not come with the source code. Thus there will not be any practical improvement right now.
Or, most likely ever. I doubt things will go much farther, and I'm usually the optimistic one
no chance
nope, i think the ics leak was just a one off leak from what motorola actually got round to doing before they abandoned the project, which personally is really bad the roms are just crappy (no offence to developers but the lack of resources means they will always be crappy), everyone says the roms are good but every ics rom iv used is awful, overheating, bugs, battery life sucks, cameras lag, and doesnt compare to a stable cm7 which works completely fine and does everything ics can do anyway.. hmm... i guess everyone just keeps giving themselves false hope, although the possibility of a stable ics is much more than the chance of jellybean & as for the cm10/jellybean thing dont get your hopes up the signs of HWA are non existent and i really dont think they ever will be unless somebody makes a kernel from scratch which for a mobile device would take endless hours of work and testing each boot would probably get your through about 50 atrix phones from hard bricks etc... and i dont think our developers have the time or money to do so... even with donations.
its just not worth it, the atrix is a dying breed if you dont like cm7 then buy a new phone, its that simple, confuses me why everyone acts like cm7 is some sort of bugged crappy software that doesnt work? yet its still a very stable software.
i think everyone should stop concentrating on ICS and jellybean until we actually hear news that will be helpful to creating a stable build and in the mean time focus on improving cm7 with mods and other things, right now cm7 is basically abandoned and the thing its been abandoned for has been on hold for around 3 months.
Pixelguy said:
nope, i think the ics leak was just a one off leak from what motorola actually got round to doing before they abandoned the project, which personally is really bad the roms are just crappy (no offence to developers but the lack of resources means they will always be crappy), everyone says the roms are good but every ics rom iv used is awful, overheating, bugs, battery life sucks, cameras lag, and doesnt compare to a stable cm7 which works completely fine and does everything ics can do anyway.. hmm... i guess everyone just keeps giving themselves false hope, although the possibility of a stable ics is much more than the chance of jellybean & as for the cm10/jellybean thing dont get your hopes up the signs of HWA are non existent and i really dont think they ever will be unless somebody makes a kernel from scratch which for a mobile device would take endless hours of work and testing each boot would probably get your through about 50 atrix phones from hard bricks etc... and i dont think our developers have the time or money to do so... even with donations.
its just not worth it, the atrix is a dying breed if you dont like cm7 then buy a new phone, its that simple, confuses me why everyone acts like cm7 is some sort of bugged crappy software that doesnt work? yet its still a very stable software.
i think everyone should stop concentrating on ICS and jellybean until we actually hear news that will be helpful to creating a stable build and in the mean time focus on improving cm7 with mods and other things, right now cm7 is basically abandoned and the thing its been abandoned for has been on hold for around 3 months.
Click to expand...
Click to collapse
Its not that simple. Once you've had a taste of Android 4.X, its nearly impossible to go back. I'm stuck on Epinter's CM10 because of that, every time I try switching back to a CM7 based rom I find it randomly jittery and with a lot of small annoyances. Both of which I never noticed before trying Joker's CM9.
Even when I switched from CM7 to CM9, I remember CM7 was more or less perfect in its current state. Work stopped on it because there's not much else that can be done with it. Its hit its peak, and for those not spoiled by the more polished versions of Android it is indeed the ideal rom for our device. That does not mean work should stop on ICS/JB, though. The big issue we have is the kernel, of which there are several projects in the works to port kernels from other devices. Its something that'll take (a lot of) time, but long term it'll be much better for our devices than making barely noticeable changes to Gingerbread roms.
With that said, you are right in that the ICS leak is more or less useless without source code. Crappy battery and display issues on some variants of Atrix completely ruin it.
Having the kernel source would solve many issues, but after Motorola abandoned the device it's very unlikely they'll commit any more resources into releasing the half working source code. Of course we'd like to see the source released as it existed under development, but from what I understand, the the source that gets released isn't always exactly the same as what they work with when they compile it and things like extremely helpful comments in the code get removed because of things like NDA's. And although many of the libs and drivers can be extracted from the ROM, the code to use them has been lost.
As it stands, the Atrix Rebirth Project is probably the best chance for seeing a fully functional kernel source for ICS and beyond. But as has been pointed out already, interest in the device has been dying, and even if the project does manage to make it happen, it's not going to happen overnight.
Jotokun said:
Its not that simple. Once you've had a taste of Android 4.X, its nearly impossible to go back. I'm stuck on Epinter's CM10 because of that, every time I try switching back to a CM7 based rom I find it randomly jittery and with a lot of small annoyances. Both of which I never noticed before trying Joker's CM9.
Even when I switched from CM7 to CM9, I remember CM7 was more or less perfect in its current state. Work stopped on it because there's not much else that can be done with it. Its hit its peak, and for those not spoiled by the more polished versions of Android it is indeed the ideal rom for our device. That does not mean work should stop on ICS/JB, though. The big issue we have is the kernel, of which there are several projects in the works to port kernels from other devices. Its something that'll take (a lot of) time, but long term it'll be much better for our devices than making barely noticeable changes to Gingerbread roms.
With that said, you are right in that the ICS leak is more or less useless without source code. Crappy battery and display issues on some variants of Atrix completely ruin it.
Click to expand...
Click to collapse
hmm i used pinters cm10 for a week and went back to MROM cm7 and customised it to my liking with ICS themes and text changers, looks just like ICS runs just as smooth as a buggy JB rom, thats the problem the performance of CM10 roms without HWA is about the same as a good CM7 rom... just with a few features like google now which nobody really uses anyway, although i understand where your coming from when it comes too the UI and animations on JB roms they are very nice but id rather sacrafice them and have a phone that will work 100%
I'm very naive to the inner workings of android
I also returned to mrom from epinters cm 10 and icsrom because of lack of camcorder or terrible battery life.
Now with mrom I have a very smooth launcher and all apps working. I do miss jellybeans nice interface, but what are the more fundamental improvements that gingerbread lacks? Besides feeling outdated and old of course :/
Sent from my MB860 using xda app-developers app
Zero usefulness. Novelty item at best.
It's interesting to read opinion of no-developers is it something useful or not. Only developers could say something about it. Also most of you are so pessimistic, complaining that developing is dying.
xda-developers is for site and forum for developers. If you think that developing is dying, come on, do something about. Join Atrix Rebirth Project, start to learn how to develop kernel and rom. There is a lot of guides here and on Internet. Instead of spending time on forum and waiting that someone else do it for you and for free. If you don't have time to learn, contribute on another way: support developers, donate money or device, try to find solution, use your contacts to get leaked sources...
The easiest way is to buy a new device and start complain after a while
I have been very pleased with the stock GB rom. I have a Nexus 7 and an old HTC Aria, both running the latest version of JB and, other than a more up-to-date appearance, there's really nothing I can't do on the Atrix that I can do on the JB devices.
Its amazing what the developers have been able to do with the HTC Aria. It has very little memory, but they have created virtually unlimited program memory by using an extended partition on the SD card. The Aria also runs JB almost flawlessly.
If JB could run on the Atrix 4G the way it runs on my Aria, I would use it. But from what I've read, it has a long way to go. I am not even sure I would even be able to root my Atrix, which has the latest GB update from Motorola.
Sent from my MB860 using xda app-developers app
Slymayer said:
I've got a question I tried to answer myself, but I couldn't resist to post it on the forum.
Is the ICS leak a great step forward for all Atrix users ?
For those who wanted HWA, fingerprint scanner, working camera, of course it is... But is it a step forward for the release of a STABLE CM10 with a STABLE kernel ? This question is more open to a debate than a simple answer.
This leak didn't provide any option for those who have the wrong tegrapart (Mine is OK), or a lapdock, or those who use Chrome and want a generally reliable ROM (Stability, I/O perfs, battery life). They have to make a compromise but we still didn't reach THE ROM(s) that makes everybody happy.
The missing thing to get the ROM(s) that will make us all happy is the kernel source... Why didn't we get it with the ICS leak ? Well let's exclude this question from this thread and maybe talk about it after this debate is (almost) closed.
Personally I'm happy to have this new ROM, it's fast, smooth etc. but my lapdock is still borked so I'm really frustrated not to have this awesome tablet display that works with EVERYTHING but not MOTOROLA's own peripheral... Damn it !
So, what's your case ? Of course you may have found satisfaction with the ICS leak, but are you as frustrated as I am to be this close to the ultimate goal ?
The debate is open, I hope I broke the ice for some people who are in my case and feel like forgotten.
Click to expand...
Click to collapse
Yeah right ! talking about this leak ... is a >small< step foward !
Just imagine Michael Montuori out of here, Or the Bill ?! epinter !? Faux, or jocker that has made a wonderfull job and the other in the early days of the atrix .... all source code builder out of this atrix family at once !
Well ... Motorola doesnt have a great support for the moment ! as their Blur OS is ****ty slow ! :S
I own a Car dock, A HD Multimedia Dock and a great lapdock !
I approve that this is still frustrating (and i know the devs out there are NOT getting Paid enough for a better work than MOTOROLA itself,) that motorola own product doesnt have support yet ! but still have on a direct DHMI cable straight to the tv !! WTF ?!?!!
Well, its not going to change anything here, i mean this thread ... but .. well .. you know ! YEAH its awkward and " fais chier bordel" hahaha
Our devs are GREAT but unfortunately, we still need that damn MOTO support for their drivers source for the new OS :S
Meanwhile
sathelate said:
Well, its not going to change anything here, i mean this thread ... but .. well .. you know ! YEAH its awkward and " fais chier bordel" hahaha
Click to expand...
Click to collapse
I would even say "Bordel à couilles de constructeur de mes deux !". I'm writing this using my lapock... On my tiny screen, with my main screen at 45° so I can still read what I'm writing. I dreamt about WT3.0 with working LAPDOCK, it would have been so gorgeous, but it's currently not happening. "Nique cette merde !", I'm buying a Windows Phone next year when the ecosystem gets more apps and stuff. The news are getting warmer for this OS ! The amazing keyboard made in WP7/8 will replace my lapdock I use as a keyboard.
Development IS actually dying, look at the Atrix 4G development section where there used to be several ROMs under active development there are now just a few. Nearly everything that can be done has been done with the exception of what the Atrix rebirth project is doing. But there is no guarantee of success. If you have the money or a device to donate to the rebirth project, great, by all means go for it. Maybe one of the other tegra based moto devices might help a bit too. Unfortanately I think it's pretty hard to hold any level of optimism for the device after such a long string of let downs.
Sent from my MB860 using xda app-developers app
I see the ICS leak as interesting but not overly useful.
Now, if they'd also leaked the source code, I don't doubt that the devs could have created a fully-features and stable ICS/JB within a couple of months. However, with no source for such a buggy leak, we're reliant on a few people trying to create a kernel almost from scratch. I wish them well, but I'm not holding my breath...
When you feel like the development is hopeless , waste all of your time and try fixing things yourself get a new phone.
BravoMotorola said:
When you feel like the development is hopeless , waste all of your time and try fixing things yourself get a new phone.
Click to expand...
Click to collapse
Like you? And you think that you're smart. That's exactly what vendors wish, get a new device. Bravo
Edit: With your latest posts in Atrix forum you're the same as maggedo or member with Atrix in name. Ups, you have Motorola
How long N4 will be the best device for you? What I see not so long
I think it's interesting how people work:
First everyone was crying about the fact, that Motorola left us out in the cold and now that we have a actually really good leak, people cry that it's not good enough... That's just sad. The leak is useful and it's a big step into the right direction. A lot of people put in hours of work for you (and for FREE!!!), to make this leak better. All you need is PATIENCE. Be grateful that some devs stick to this EOL-device and provide great work for us.
-Just my 2 cents-
Sent from my MB860 using Tapatalk
BravoMotorola said:
When you feel like the development is hopeless , waste all of your time and try fixing things yourself get a new phone.
Click to expand...
Click to collapse
And... What about people who can't get a new device ? I bought mine like 6 months ago, it was for my birthday and I can't waste money on a newer phone like this.
But there must be some kind of "break-even" ahead.
How many hours of work and energy may be put from the most "valuable brains" into the leak (without having sourcecode), until they must decide: "enough is enough, it just will never turn out as "stable"?
From what I've understood there exists some good chances that maybe some day valuable parts of the XOOM kernel get migrated to the Atrix (see respective thread under development area).
May the last remaining devs of a dying device - whose work I greatly respect and appreciate! - join forces and turn more efforts into porting the xoom?