Related
my question thus becomes:
Once we get ICS officially from Motorola (and I'm guessing it'll be Android 4.0.4 and not 4.0.3 or whatever), and Jelly Bean is already floating around, will it be possible to then have some ROMs made or built for JB that will work automagically on the Atrix 2, or will the updated kernel in JB become a big hassle/issue that prevents us from using it at all, barring that nobody will most likely crack that bootloader anytime soon...?
tl;dr version: Once ICS is official for the Atrix 2, can JB ROMs be built and usable or, will the updated kernel and whatever just be yet another wall on this fortress?
I just picked up an Atrix 2 and I find it to be extremely fast and so far pretty much rock solid stable. I rooted it, installed CWM, did a Nandroid backup of the 2.3.6 stock installation for safe keeping and then installed Remus 2.0 and it's just insanely responsive and everything works as expected.
But I just watched the Google I/O keynote to see what all the fuss about JB is about and I can see it's pretty amazing considering it's an incremental upgrade for ICS more than anything else, but the performance improvements are crazy so, I'd hate to think that Motorola would work on JB for us and yet not get around to releasing it till well into 2013 which is just a bit insane.
For such a company, Motorola is so behind the curve it hurts. I do love this device, however, it's utterly fantastic for me and I plan to keep it for some time, but obviously it's more than capable of running ICS/JB from the gitgo - now it's just "ok, when?"
Thanks...
br0adband said:
my question thus becomes:
"ok, when?"
Thanks...
Click to expand...
Click to collapse
As per official information - update for ICS - Q3 of 2012 (which actually already started), more precision date - unknown
I don't think you read my post very comprehensively - I didn't nor was I asking if ICS is coming and when it'll be out as we already know that based on Motorola's schedule announcement.
I know ICS is coming, I know it's between July (like, right now) and September (which means between right now and the end of the year given Motorola's somewhat inefficient release schedules of past years.
What I'm asking again is:
When ICS is out, and when I've got it installed on this Atrix 2, is there a possibility that Jelly Bean will be ported over to this Atrix 2 considering they're very similar OSes that most likely will use the same bootloader, or ... ?
In other words, after ICS is available, are we looking at a 2013 release of Jelly Bean for the Atrix 2, if it even happens, or will it be up to talented folk in the developer community to make the best of ICS as given by Motorola?
Hope that's more clear... I don't know how else to ask the question, honestly.
I'm no dev... but I did sleep in a holley day inn last night...
The locked bootloader means that the bootloader can only load the official Moto released kernel. JB will have a new kernel so the only way to get JB is when/if Moto releases it.
That's all I wanted to hear, at least from one other person as a confirmation. Nothing surprising, but somewhat of a disappointment I suppose.
/me kicks Motorola in da shinz, hard... then does it again...
I wouldn't be so sure that it's never going to happen. People have accomplished CM9 and AOKP (both ICS ROMs) on the Razr, Droid 3, and Droid Bionic (all of which atm are still on GB) that uses the GB kernel (and just about all of those ROMs are flashable on the A2, just without a working radio). So there's a good chance that the same thing will happen with ICS to JB, and since it's an incremental upgrade then I think it would be easier to do.
cogeary said:
I wouldn't be so sure that it's never going to happen. People have accomplished CM9 and AOKP (both ICS ROMs) on the Razr, Droid 3, and Droid Bionic (all of which atm are still on GB) that uses the GB kernel (and just about all of those ROMs are flashable on the A2, just without a working radio). So there's a good chance that the same thing will happen with ICS to JB, and since it's an incremental upgrade then I think it would be easier to do.
Click to expand...
Click to collapse
Yes, this is true. What most seem to not realize or maybe even know, is that the jump from GB to ICS was huge in the kernel space because honeycomb was completely jumped over and skipped in the phone space. What this means is that all of the upgrades from HC were merged into the ICS kernel, so the jump from Gingerbread to ICS was a huge one. The jump from ICS to JB will be much smaller, and it will have a lot more performance tweaks and increases from ICS. So this should be more doable. The real issue is that we need the ICS kernel first to start looking into JB.
Yeah I intentionally qualified my reply since I'm not familiar with the enhancements that went into the GB, ICS and the JB kernels...
I would have expected that the project butter enhancements in JB would have required significant kernel level changes. I take it that the kernel level work to support project butter happened with the ICS release... and now the UI layer in JB is more or less just leveraging that foundation.
apinkel said:
Yeah I intentionally qualified my reply since I'm not familiar with the enhancements that went into the GB, ICS and the JB kernels...
I would have expected that the project butter enhancements in JB would have required significant kernel level changes. I take it that the kernel level work to support project butter happened with the ICS release... and now the UI layer in JB is more or less just leveraging that foundation.
Click to expand...
Click to collapse
No You may have misunderstood, just a little.
The jump to JB from ICS will be smaller.... Than the jump from GB to ICS. Yes there are a going to be some hefty changes for project butter, but only in in the performance and virtual space areas of the kernel, since every thing in the android app space is handled by the jvm, so there are a lot of enhancements to how the virtual space is handled, that is really what project butter does, as well as the changes in kernel to do that. Now Project butter also changes the vsync timings in the OS as well, and I am pretty sure we can port or figure out some of the changes and make some of that up in ICS as well.
We will most likely be able to run JB "ROMS" without ALL the project butter enhancements once we are on ICS, but that will be more than likely not until closer to the end of the year that we will begin to see some ported ROMS for JB that are capable of running on this phone.
It would be nice to see that... I like Moto hardware but the locked bootloader can be a bit of an annoyance.
Hey.
I've been on jb roms since they came out for desire s and have been using ics before that. However... ics roms have been in beta stage since ever and have not really advanced in terms of having stable or even working main functions. Well this is because of the fact that our devs did not have kernel sources. There have been words that kernel source release would solve all our major issues like front cam and others. But kernel source has been released and I'm seeing a decline in our forum's traffic and in development. I know i's partly due to many original members leaving. But I also hear that devs are facing difficulty in making the kernel. So I want to ask, will we ever have fully stable ics or jb roms or is this not a possibility?
Sent from my Desire S using xda app-developers app
Sorry for the tone, but this is a pretty pointless thread (IMO) there are already several others in a similar vein that exist and as we don't have a time machine and can't see into the future....although speculation appears to what the majority of threads contains these days....
This is now unfortunately an old device and as you rightly pointed out lots of the forums previous users have moved on to bigger and better new devices so the forum traffic was always bound to fall. We still have several devs that are developing for this device so don't do them a dis-service by suggesting that no progress has been made. Just look at the CM, AKOP and JB source build threads for examples.....
Since the release of the kernel source - progress has certainly been made, just look at the tweaked kernel we can now use, in which we are now able to UV & OC not to mention that the wifi tether issues are now resolved... everything takes time, so be patient....or learn to code yourself and help out!
ben_pyett said:
Sorry for the tone, but this is a pretty pointless thread (IMO) there are already several others in a similar vein that exist and as we don't have a time machine and can't see into the future....although speculation appears to what the majority of threads contains these days....
This is now unfortunately an old device and as you rightly pointed out lots of the forums previous users have moved on to bigger and better new devices so the forum traffic was always bound to fall. We still have several devs that are developing for this device so don't do them a dis-service by suggesting that no progress has been made. Just look at the CM and AKOP threads for examples.....
Since the release of the kernel source - progress has certainly been made, just look at the tweaked kernel we can now use, in which we are now able to UV & OC not to mention that the wifi tether issues are now resolved... everything takes time, so be patient....or learn to code yourself and help out!
Click to expand...
Click to collapse
I fully understand the devs' hard work and their dedications. That's not what this thread is asking. It seems to many devs that they are still having a hard time adjusting ics and jb to our device even upon kernel source release. Despite the prior speculation that things would be much easier with kernel source. So I was bringing the problem forth to see if it is possible for us to have stable ics or jb roms. No need to be all defensive. Just want an objective discussion
Sent from my Desire S using xda app-developers app
custom roms are rearly FULLY stable. there is always a little bug here and there. but since the release of the official ICS and the latest kernel source ICS roms are getting mature at last. and if you're still not satisfied, wait a month more. or flash the official ICS and have a really stable rom now.
JB is another story. there is no native kernel source for it and i doubt there will ever be.
I totally see where you are both coming from. The kernel source was released over a fortnight ago.
I agree with Ben, in respect we should appreciate what the current devs have given us etc etc,
But I also agree with skim, I am quite surprised that with the kernel source released, AOSP still hasn't got a functional kernel based on our Saga build. (Andromadus is using a kernel port)
I was hoping for at least ICS AOSP to be working by now, but I guess that is not the case
The forums have certainly gone a lot quieter now, and I suspect by the end of the year, even more of us will leave
But back to the original point, I wish that things could pick up like they were this time last year, but sadly that will never happen.
I have no intentions of insulting any devs, I truly appreciate the work they have provided us, and I haven't contributed anything particularly useful, so I am in no position to do so, but this is just how I feel.
When I look through forums like the S2, I envy the development... even after a year, ROMs are still on full scale, with so many choices to choose from...
Sent from my GT-P1000 using Tapatalk 2
Unfortunately Oly I don't think that you can compare the DS to the SGS2. We unfortunately were never a main stream device (like the SGS2), we sadly missed the boat, with the Sensation coming out shortly after our release, I reckon that the focus went from DHD to Sensation and the limelight never really shone on us long enough to get a main stream following.
The Samsung onslaught appears to unbeatable currently sadly even the One series hasn't really made a dent.
We must all accept the inevitable that our device (Desire S) is by fact outdated with the phase of how fast mobile technology comes. That said, sooner or later, our thread will surely die.
It is with great appreciation that our devs are prolonging the inevitable. Most will surely be having new devices comes these coming months. I too will be leaving the scene as a new device is surely coming at hand in two months time.
Everything in our life changes. One must be oblige to flow with it. If not, one will be left alone and at lost.
P.S.
For an answer for the OP. THERE WILL BE a stable JB/ICS ROM as long as a dev will be willing to still work on it. If not, then THERE WILL BE NOT.
Long answer short: we will never know unless there will be one.
Moral of this post: learn to accept the truth that you have to move on to a new device if you really want to have a stable up-to-date ROM, even past JB.
Sent from my HTC Desire S using xda app-developers app
Well, that was philosophical!
Sent from my HTC Desire S using xda app-developers app
Skanob said:
We must all accept the inevitable that our device (Desire S) is by fact outdated with the phase of how fast mobile technology comes. That said, sooner or later, our thread will surely die.
It is with great appreciation that our devs are prolonging the inevitable. Most will surely be having new devices comes these coming months. I too will be leaving the scene as a new device is surely coming at hand in two months time.
Everything in our life changes. One must be oblige to flow with it. If not, one will be left alone and at lost.
P.S.
For an answer for the OP. THERE WILL BE a stable JB/ICS ROM as long as a dev will be willing to still work on it. If not, then THERE WILL BE NOT.
Long answer short: we will never know unless there will be one.
Moral of this post: learn to accept the truth that you have to move on to a new device if you really want to have a stable up-to-date ROM, even past JB.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Haha I don't know about you man... but I'm a student and learning to move on to a new device is not as easy as it sounds. I'm stuck with a contract until next April. So ill be sticking around here till then xD
Sent from my Desire S using xda app-developers app
I think custom roms have advantages, but it's not easy for the devs to make them perfect.
If i compare the stock ROM of x10mini/pro with custom cm6/7 ROM, the stock ROM sucks...
SteveO_ said:
I think custom roms have advantages, but it's not easy for the devs to make them perfect.
If i compare the stock ROM of x10mini/pro with custom cm6/7 ROM, the stock ROM sucks...
Click to expand...
Click to collapse
htc stock rom ( sense ) , indeed, the best stock of all android. I've been using samsung, motorola and sony, but nothing is better than sense.
anazhd said:
htc stock rom ( sense ) , indeed, the best stock of all android. I've been using samsung, motorola and sony, but nothing is better than sense.
Click to expand...
Click to collapse
At the moment i'm using stock rom (sense) too, cause my prefered custom rom has still a problem with battery drain...
As soon this is fixed, i'll go to ICS DS again...
But at all, the ICS stock rom is working very nice...
Fallout v4.4.0 is pretty stable to me, been using since a while now.
Tonight i'll try Fallout 5.0, let's see how it is... :highfive:
MIUI 2.8.x or 2.9.x
I recently flashed MIUI 2.8.17 and its been a joyful ride! It is very very stable. I had to reboot only once so far and that is an intermittent bug. BT/WiFi/Tethering/Camera etc. etc. everything works! (hard to find that in an ICS ROM)! Its my daily ROM now.. :good:
Fallout 5.0
I got myself S-off and rooted 2 days ago.
The first custom rom Ive tried is Fallout 5.0. Only one day into my test and it's very stable and fast compared to stock gingerbread.
I'm very pleased with it so far :good:
anazhd said:
htc stock rom ( sense ) , indeed, the best stock of all android. I've been using samsung, motorola and sony, but nothing is better than sense.
Click to expand...
Click to collapse
My Gingerbread stock rom experience made me root my phone. I kept getting the white screen with the green HTC logo and no matter what I did it always came back. I have now tried out about 5 or 6 custom roms and this issue no longer appears. Of course there are other issues, some of which are serious. But there are ROMs which are in general more than good enough for day to day usage. I currently use ICE-DSv5 but for example Fallout v4.4 is stable (v5 is not stable for me but it is for a lot of people).
If you are interested you can look at my other thread here called "My First Rooted Phone" for an overview of my experiences so far.
Blindbean and Codename are great JB roms, not fully stable, but good to work with.
Yes. I flash every recent roms so I know how they are. I started this thread to get an idea of if it is possible to have a stable rom. The devs have been struggling with major bugs since early this year and we're still stuck with the same bugs we had prior to the release of the kernel sources. I do know it is a difficult process. But wanted an answer from a dev. Is it possible for us to have working front cam, proper video playback, etc. ? This isn't complaining btw just wanted an answer other than "be patient. Be thankful. It's good enough"
Sent from my Desire S using xda app-developers app
if you want stable flash rooted stock. it has everything you mentioned. combine it with tweaked kernel and you have even more...
Does that have any impact on the devs working on CM10 for our device? Or is that just cool, some other devices have stable CM10.
Seriously?(sarcasm)
Different devices have different source code which wouldn't really help our devs get a stable build if CM10. Right now our device doesn't have stability for jb, but I would expect it in the future. If we are to get a really good stable job ROM, we need our source code to be released.
If I helped you, push the thanks button for goodness sakes!
I've got ZERO expectations on us getting a fully working CM10 or later variant for our phone. I've resigned myself to the fact that CM7.2 is about as good as my phone is ever going to get.
I think we eventually will get it but at this point I don't expect anything.
Hopefully Tonyp will port the Stock ICS ROM from the O2x and Arcee will finally give us CM10. Rumor has it he is just trying to make it stable before bringing it here, but for all we know he's probably having trouble porting it over.
Anyone know how much smoother and faster CM10 is with the actual HW accelerations? I'm on the Paranoid Jellybean Hackfest and I honestly don't see much difference in fluidity than on my Galaxy S Blaze Running a full functioning CM10. We only have a few bugs, and not even the worst ones like random reboots or audio noise which some are experiencing with a full ROM.
Sent from my LG-P999 using xda premium
New2my8125 said:
I've got ZERO expectations on us getting a fully working CM10 or later variant for our phone. I've resigned myself to the fact that CM7.2 is about as good as my phone is ever going to get.
Click to expand...
Click to collapse
Pretty much what he said. Or we'll get it mid next year. I'm done expecting that we'll get it. This phone is still awesome with cm7, and I'll probably have moved on to a different device anyway next year ;p.
I'm certain this has been brought up before Several thousand times, but I gotta ask again...What is it that drives people to constantly flash new Roms/updates every couple days or even weeks?
I have been running cleanRom 3.0 and having no issues, no bugs, GREAT battery life. Why would I change that? I know CleanRom 5.0 has come out, but what would be the point to update if 3.0 is working perfectly and spot on?
Is it that people get bored?
Is it that people wonder what is different?
just makes me wonder.
Im guilty of this myself. I believe a rooted debloated with a theme of your choice is the way to go
iSheep... iSheep... Meowww that's Apple
see whats different, see customizations, battery life, other random usually rom exclusive features.
ive probably flashed 75% of the roms available for this device just to see what theyre all about.
it helps me help other people, and helps me make my device my own.
most of the times its out of boredom and i restore my daily driver rom
Because updates to the ROM = possibly better phone
I prefer stability but I like changing stuff on my phone. I'll stay on a rom for a few weeks and not change a thing but the entire time I'll want to flash something even if I have no reason too smh Ultimately, I'm just not satisfied with what ships out the box.
Sent from my SCH-I535 using xda app-developers app
The grass is always greener.
Sent from my SCH-I535 using xda app-developers app
I used to flash weekly with my OG droid, over the years I have slowed down to once a month or so. I have 4 android devices so thats still a lot of flashing. I am always in search of the perfect rom, haha whatever that may be. faster, smoother, bells and whistles. I don't even know.
To have the latest and greatest rom.
Bug fixes and improvements. Plain and simple.
I've been trying to find the best Rom for what I do every day, but there are always little problems that bug me on every Rom. I damaged Clean Rom 5.0 and have finally stopped the daily flashing. This is as close as I well get to the prefect Rom.
Sent from my sexy phone using XDA Premium
And I get what everyone has said. BUT for those of us that prefer performance (i.e. great battery life, no issues/bugs, fast speeds) over "new'ness", once you find a Rom that gives you the best of all worlds, why would you even worry about the latest? I have been on CleanRom 3.0 for since a couple weeks after it came out. ONLY reason I went to it was because I wasn't happy with the 4 Roms I tried before. Those 4 Roms I tried prior all had bugs or poor battery life that I wasn't happy with. Now that I am Happy with EVERYTHING, I dont plan on changing.
And don't get me wrong here, I know that just because I am satisfied and not wanting to flash doesn't mean that others will be content with that. Nobody needs to tell me that. I'm not trying to debate, just trying to see how others here think.
Because it is great to see the capability of your device by exploring different roms and it is so darn addicting.
Sent from my SCH-I535 using Tapatalk 2
Because the majority of us here at XDA who root our phones and flash ROMs are tech junkies. Technology is like a drug to many of us. We are never content and always need the next fix, whatever the latest and greatest may be.
CleanROM 5.0 is built on the latest Jelly Bean leak, which has many improvements over the Ice Cream Sandwich base that CleanROM 3.0 is built on.
mmmmm rom flashing!!!!
1Android said:
And I get what everyone has said. BUT for those of us that prefer performance (i.e. great battery life, no issues/bugs, fast speeds) over "new'ness", once you find a Rom that gives you the best of all worlds, why would you even worry about the latest? I have been on CleanRom 3.0 for since a couple weeks after it came out. ONLY reason I went to it was because I wasn't happy with the 4 Roms I tried before. Those 4 Roms I tried prior all had bugs or poor battery life that I wasn't happy with. Now that I am Happy with EVERYTHING, I dont plan on changing.
And don't get me wrong here, I know that just because I am satisfied and not wanting to flash doesn't mean that others will be content with that. Nobody needs to tell me that. I'm not trying to debate, just trying to see how others here think.
Click to expand...
Click to collapse
I'm like you in that I don't want to potentially compromise the stability and functionality of my phone without significant incentive. For me the incentive was new functionality and increased performance. I've only flashed three roms other than stock.
CleanROM 3.1 was the first ROM I flashed, and as you said, it's stable with great battery life and pretty smooth. The smooth operation of my phone is what made me cautious about jumping to the first JB leak. Instead I kept track of the CR, stock leak, and Jelly Beans threads and read up on the bugs and issues.
Ultimately what I was reading about Google Now and Project Butter made me realize that I really wanted Jelly Bean and the few known issues in JB leak #2 were not enough to stop me from flashing Jelly Beans Build 2. I don't regret that decision, Jelly Beans is a cool rom with a nice AOSP theme, ran really smooth, and generally gave me good battery life (depending on what I was running). Also Google Now is really really cool.
Then I was reading about AOSP roms like LiquidSmooth RC9 and SlimBeans 3.1 that were about the come out. It seems like those teams had dedicated developers who were squashing existing bugs. With the remaining bugs pretty much known, but the ROMs otherwise stable I decided to give LiquidSmooth a shot. The motivation here was to really rid myself of all the stuff Samsung had running in the background, with touchwiz it seems like there are a million things classified under "Android System" when trying to diagnose a battery drain. With AOSP when I look at battery stats Screen and Cellular Calls are the only apps that really make a dent. I also like the clean styling, functionality, and flexibility of the AOSP lockscreen and UI in general.
Unless I encounter any other problems I will probably wait for a stable AOSP 4.2.1 rom to come out so I can try the new features there and hopefully some bug fixes for the bluetooth audio issues in 4.1.2.
I m coming from a tbolt i now have a verizon s3(unrooted so far) n I m guilty of "being in search of a perfect rom". What drove me to search was claims of better battery life, quicker and stable. What drove me back to my daily driver(skyraider) was frequent reboots( while googlemaps), applications not working(slingbox in particular ) inability to view video(live streams from my church).
I m currently doing research for the perfect rom for my S3 as I just activated the s3 yesterday (n I'm missing having a rooted phone) and I m resisting the urge to root!
pcar1947 said:
I m currently doing research for the perfect rom for my S3 as I just activated the s3 yesterday (n I'm missing having a rooted phone) and I m resisting the urge to root!
Click to expand...
Click to collapse
I give it three days before you root/unlock or no later than the weekend. Regardless: root, unlock, and backup your IMEI!
Sent from my SCH-I535 using xda app-developers app
bug fixes
new features
security updates
Compulsion
fun
hacking/tinkering instinct
Customization
because we can
If you are happy where you are at then don't sweat flashing new stuff.
SlimSnoopOS said:
I give it three days before you root/unlock or no later than the weekend. Regardless: root, unlock, and backup your IMEI!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'll second backing up your IMEI... being a total noob I researched and backed up everything I could, and I'm glad I did, second Rom I flashed sent my phone into permanent roaming. Following the stickies here made the fix simple.
Sent from my SCH-I535 using xda app-developers app
If everything works it just means you aren't running the latest and greatest.
You must tweak your phone until something breaks.
Then you search for the next fix.
It is the path that must be followed.
Hi guys, there's a lot of 4.2 ROMs floating around the forum at the moment and I've tried them all. Unfortunately, I feel like I can never get the same level of buttery smoothness as I have in 4.1.2. Even the AOSP 4.2 ROM in the forum doesn't give me the same level of user experience as in the vanilla 4.1.2 AOSP ROM I'm using now. And I'm not talking about features or bugs, I'm talking about the overall experience of using it, like browsing, scrolling through lists like in Instagram or xda, dropped frames, etc.
Just to be clear, I'm not trolling. I just wanted to know if I'm really the only one who feels that unlike in previous versions, 4.2.1 is truly not made for the Nexus S. Let me know what you think below.
Cheers!
Sent using the xda mobile app
Somewhat I do agree BUT we can bring all that smoothness back pretty much easily
DJBhardwaj said:
Somewhat I do agree BUT we can bring all that smoothness back pretty much easily
Click to expand...
Click to collapse
Can you site an example on how we can do that? I've tried all of the currently available 4.2 ROMs and they just feel clunky compared to 4.1.2. Even the recent apps list appear faster and with less stutter in 4.1.2.
Sent using the xda mobile app
Once we are done with solving all the bugs, we can work on patches to remove lags.
Probably because 4.2 is just a port.
Sent from my Nexus S 4G using xda app-developers app
apatal said:
Hi guys, there's a lot of 4.2 ROMs floating around the forum at the moment and I've tried them all. Unfortunately, I feel like I can never get the same level of buttery smoothness as I have in 4.1.2. Even the AOSP 4.2 ROM in the forum doesn't give me the same level of user experience as in the vanilla 4.1.2 AOSP ROM I'm using now. And I'm not talking about features or bugs, I'm talking about the overall experience of using it, like browsing, scrolling through lists like in Instagram or xda, dropped frames, etc.
Just to be clear, I'm not trolling. I just wanted to know if I'm really the only one who feels that unlike in previous versions, 4.2.1 is truly not made for the Nexus S. Let me know what you think below.
Cheers!
Sent using the xda mobile app
Click to expand...
Click to collapse
4.2 is a port and way more than what Nexus S was designed to handle. Still, I found it really snappy and only sipping battery compared to 4.1 and even CM10. Only multitasking chokes it, but that can't be helped.
sumeshpremraj said:
4.2 is a port and way more than what Nexus S was designed to handle. Still, I found it really snappy and only sipping battery compared to 4.1 and even CM10. Only multitasking chokes it, but that can't be helped.
Click to expand...
Click to collapse
You are really unaware of what NS can handle.
My 2 years old LG Optimus One P500; an MDPI ARMv6 arch device which comes with froyo and can only be updated to GB runs on smooth JB.
NS is way far more capable than that and in the coming future we will prove that too. :victory:
apatal said:
Hi guys, there's a lot of 4.2 ROMs floating around the forum at the moment and I've tried them all. Unfortunately, I feel like I can never get the same level of buttery smoothness as I have in 4.1.2. Even the AOSP 4.2 ROM in the forum doesn't give me the same level of user experience as in the vanilla 4.1.2 AOSP ROM I'm using now. And I'm not talking about features or bugs, I'm talking about the overall experience of using it, like browsing, scrolling through lists like in Instagram or xda, dropped frames, etc.
Just to be clear, I'm not trolling. I just wanted to know if I'm really the only one who feels that unlike in previous versions, 4.2.1 is truly not made for the Nexus S. Let me know what you think below.
Cheers!
Sent using the xda mobile app
Click to expand...
Click to collapse
I was happy with JellyShot 0.8 for couple days then with Vanilla 4.1.2 which I used since release, used the same kernel. I tried couple 4.2 for the NS, but everyone felt clunky until JellyShot, I also loved the quick toggles and MMS features.
But I feel you, since 4.1.1 Google images behaved very well and smoother then AOSP compiled stuff.
apatal said:
Unfortunately, I feel like I can never get the same level of buttery smoothness as I have in 4.1.2. Even the AOSP 4.2 ROM in the forum doesn't give me the same level of user experience as in the vanilla 4.1.2 AOSP ROM I'm using now.
Click to expand...
Click to collapse
Same here. I tried greenblue's AOSP 4.2.1 and like the "new features", but I always return back to the stock 4.1.2 ROM. It feels more robust somehow, even with the same kernel.
I´m running on Rasbeanjelly 4.2.1 since it comes out and i´m very satisified with it. I expected nothing more of the Nexus S but i love to hear that there will possibly be improvements in future.
For the last couple of days I've been flashing my device with various roms. 4.2.1. mostly. Everytime I flashed a new rom which was supposed to be smooth fast and super nice it turned out it was slow, sluggish, choppy and not working as a smartphone should. Crt animation is ****ty among every 4.2. Rom i tried. It's delayed, slow and not in the right pace. Lockscreen does not work properly. Scrolling through the lockscreen is laggy. Quick settings are sometimes laggy. I just hate to say it but I think 4.2.1. is really not meant for the nexus s. I just returned to vanilla rom with minimum modifications (flohimself rom) and I love what I see. Everything is fast, fluent and working properly
Sent from my Nexus S
Yeah. Same experience here. I guess you can't just beat the experience in using actual AOSP ROMs with all sources and proprietary binaries available. Still, appreciate the efforts of all the devs who have been trying to keep our humble device in the cutting edge... even if said edge is a bit dull at the moment.
Still I want to remain optimistic that things will only get better in the future in terms of the 4.2 ROMs.
What do you guys think? Could we achieve the same level of user experience of a 100% AOSP ROM even without Google's support?
Sent using the xda mobile app
apatal said:
Yeah. Same experience here. I guess you can't just beat the experience in using actual AOSP ROMs with all sources and proprietary binaries available. Still, appreciate the efforts of all the devs who have been trying to keep our humble device in the cutting edge... even if said edge is a bit dull at the moment.
Still I want to remain optimistic that things will only get better in the future in terms of the 4.2 ROMs.
What do you guys think? Could we achieve the same level of user experience of a 100% AOSP ROM even without Google's support?
Sent using the xda mobile app
Click to expand...
Click to collapse
I think we can :victory:
I thought that everything is possible. But the more i use my phone the more I think that the stock firmware is simply the best for it. The more new features the faster your phone will become sluggish and unbearably slow. I've been on cm10 for a while and I thought it was fast. I was wrong. I'm now typing from a vanilla rom and that's the way it should be. I just wonder how long will my phone be so fast and snappy. Maybe after couple of days it will become as slow as the other roms leaving me with the opininion that android is simply crap? what do you think?
thanks to all dev for 4.2.1 rom !!!
You all should use a HTC Hero for a week and you'd realize that your phone runs great. If your phone runs so poorly on 4.0+ it's probably you because I see enough people say their phone flies. 4.2 is a bit clunky, but it's also a port. A port takes time to get the kinks out. I thought 4.2 actually ran fine. But I also had a click and wait hero and Windows Mobile phones before this. The lock screen is the main fail on it for a variety of reasons. Some apps are definitely not optimized for 4.2 as well. Beyond that it seems fine. It will get better. I've already had to suffer through this on so many phones, just be patient.
~Nexus S 4G~AOKP JB~Matrix Kernel~
apatal said:
Yeah. Same experience here. I guess you can't just beat the experience in using actual AOSP ROMs with all sources and proprietary binaries available. Still, appreciate the efforts of all the devs who have been trying to keep our humble device in the cutting edge... even if said edge is a bit dull at the moment.
Still I want to remain optimistic that things will only get better in the future in terms of the 4.2 ROMs.
What do you guys think? Could we achieve the same level of user experience of a 100% AOSP ROM even without Google's support?
Sent using the xda mobile app
Click to expand...
Click to collapse
Unfortunately using actual AOSP ROMs will always be better, so everything based on 4.2 will always be less than 4.1.2. I am using the great 4.2.1 ROMs here and enjoying them but they are less than using actual AOSP ROMs.
A reality we have to accept since our beloved NS has been dropped by Google...
dpeeps74 said:
You all should use a HTC Hero for a week and you'd realize that your phone runs great. If your phone runs so poorly on 4.0+ it's probably you because I see enough people say their phone flies. 4.2 is a bit clunky, but it's also a port. A port takes time to get the kinks out. I thought 4.2 actually ran fine. But I also had a click and wait hero and Windows Mobile phones before this. The lock screen is the main fail on it for a variety of reasons. Some apps are definitely not optimized for 4.2 as well. Beyond that it seems fine. It will get better. I've already had to suffer through this on so many phones, just be patient.
Click to expand...
Click to collapse
Oh don't get me wrong, I think my phone runs great, especially with the vanilla 4.1.2 AOSP ROM I'm running right now. This is also the reason why I believe my complaints with 4.2 ROMs are not because of "me", as you say. Because if I do cause the poor performance on my phone, I would experience the same issues regardless of what ROM I am using, which, as I mentioned before, is not the case. < via xda app>
nexususer1 said:
I thought that everything is possible. But the more i use my phone the more I think that the stock firmware is simply the best for it. The more new features the faster your phone will become sluggish and unbearably slow. I've been on cm10 for a while and I thought it was fast. I was wrong. I'm now typing from a vanilla rom and that's the way it should be. I just wonder how long will my phone be so fast and snappy. Maybe after couple of days it will become as slow as the other roms leaving me with the opininion that android is simply crap? what do you think?
Click to expand...
Click to collapse
I think that's why we're on a nexus device, to get the pure Google experience. The only thing the nexus s needs that's not stock it's backlight notifications, and the gnex solved it with the notification led. Let's just admit that this is an old phone, and the nexus 4 is probably where we should head towards. Probably won't find anything for such a great deal for a while. It'll last us as few years for sure.
Sent from my Nexus S using xda app-developers app
apatal said:
Oh don't get me wrong, I think my phone runs great, especially with the vanilla 4.1.2 AOSP ROM I'm running right now. This is also the reason why I believe my complaints with 4.2 ROMs are not because of "me", as you say. Because if I do cause the poor performance on my phone, I would experience the same issues regardless of what ROM I am using, which, as I mentioned before, is not the case. < via xda app>
Click to expand...
Click to collapse
It wasn't intended as a dig. There are several people though that report 4.2 running fine. This would tend to indicate that there would be something specific to what a user does that would cause the phone to run in a way that made it unbearable. Typically that will be related to some specific application(s) causing an issue due to not being updated. Most problems I saw with 4.2 were very similar to what I saw when we got ics before many apps ever updated and some never did and I'd imagine there are still people using apps that haven't been updated since gb. Definitely 4.2 is nowhere near perfect on our phones though and is running very much like a port and they clearly lagged some stuff up.
~Nexus $ 4G~AOKP JB~Matrix Kernel~