Related
http://www.pocket-lint.com/news/38311/android-2-4-april-release-date
in a move that shows there is some kind of cover-up of the mistake of the lack of Android 2.3 devices on the market (aside from the Nexus S) 2.4 will still be called Gingerbread, as the only new feature it adds will be this ability to support dual-core apps on a single-core device.
Click to expand...
Click to collapse
Makes complete sense. Dev's are already using the honeycomb SDK to produce apps made for dual core devices. Google cares more about having the maximum number of apps to be available to as many people as possible rather than having a handful of consumers having the absolute latest edition (and I have to agree with them).
How many stock vanilla android devices are there? Just us and the NS (pretty sure no one gets OTA's the day of except us two). Getting an OS out there for everyone is more important then keeping a relatively small group happy with the latest official build. Besides, the N1 is meant for ROM's. Google want's us to play with them, which is why I own the phone. If you've been waiting for gingerbread, just flash a freaking ROM and be happy.
Gingerbread isn't even that great anyway.
AFAIK Gingerbread suffers different problems:
1. security
2. resets
IMHO google devs are working on them before pushing 2.3 on the nexus one too, making it vulnerable and unstable.
elegos said:
AFAIK Gingerbread suffers different problems:
1. security
2. resets
IMHO google devs are working on them before pushing 2.3 on the nexus one too, making it vulnerable and unstable.
Click to expand...
Click to collapse
Yhea i did read about the resets in NS, i'm using GB on N1 but it never resets on it's own.
commodoor said:
Yhea i did read about the resets in NS, i'm using GB on N1 but it never resets on it's own.
Click to expand...
Click to collapse
The resets may be an issue with the Nexus S hardware, and not with the OS. The Samsung Galaxy S phones have quite a few "issues", just ask any owner of a Captivate. I switched from the Captivate to a Nexus One, it is a much better phone.
commodoor said:
Yhea i did read about the resets in NS, i'm using GB on N1 but it never resets on it's own.
Click to expand...
Click to collapse
I'm on CM7 and getting occasional random resets.
Google announced 27. January that OTA for Nexus S coming in 1-2 weeks, I don´t know why, but maybe we´ll see both Nexus One and Nexus S OTA.
I wish people would stop saying "just flash a GB ROM and be done with it", there's more to it than that. The N1 is sort of a reference design for alot of phones out there. A working N1 GB ROM means solid drivers, solid battery life, solid performance, etc.
I also have an HD2, it's running GB but the battery life (and BT stack in particular) is pretty poor. Devs say they won't be able to improve much until there are more GB ROMs they can pick parts from. First on that list is the N1.
There are more than just us Nexus One users tapping their fingers waiting for Google on this.
elegos said:
AFAIK Gingerbread suffers different problems:
1. security
2. resets
IMHO google devs are working on them before pushing 2.3 on the nexus one too, making it vulnerable and unstable.
Click to expand...
Click to collapse
The "reset" issue is specific to the NS hardware. Samsung screwed the pooch on that one. There are plenty of people here running GB roms with out issue.
But I do believe the security flaws recently discovered to have a significant impact on GB's delayed release.
GldRush98 said:
The "reset" issue is specific to the NS hardware. Samsung screwed the pooch on that one. There are plenty of people here running GB roms with out issue.
But I do believe the security flaws recently discovered to have a significant impact on GB's delayed release.
Click to expand...
Click to collapse
I've had plenty of resets on my N1 with CM7
James Bell said:
I wish people would stop saying "just flash a GB ROM and be done with it", there's more to it than that. The N1 is sort of a reference design for alot of phones out there. A working N1 GB ROM means solid drivers, solid battery life, solid performance, etc.
I also have an HD2, it's running GB but the battery life (and BT stack in particular) is pretty poor. Devs say they won't be able to improve much until there are more GB ROMs they can pick parts from. First on that list is the N1.
There are more than just us Nexus One users tapping their fingers waiting for Google on this.
Click to expand...
Click to collapse
My N1 is running a GB ROM with solid battery life, and performance. I don't know about drivers but everything works perfectly and as it should. Almost like I am running an official build of GB. The reboot issue only seemed to occur on CM7.. oddly. And it wasn't frequent enough for me to care.
I thought the HD2 always had pathetic battery life when it came to Android. Mine's did, until I remembered to install SetCPU. It last all day, which is just what I need.
I mean the AOSP was released for gingerbread, so we can get some pretty stable ROM's. No it isn't as good as an official update, but if I wanted to wait for official updates, I would have bought a desire.
Now I'm not sure about this, but I think most ROM's that are cooked are built using the ASOP rather than modified stock ROM's. It isn't worth waiting and complaining for a 100% optimized OTA ROM when there are tons of temporary solutions.
XSafire said:
I mean the AOSP was released for gingerbread, so we can get some pretty stable ROM's. No it isn't as good as an official update, but if I wanted to wait for official updates, I would have bought a desire.
Now I'm not sure about this, but I think most ROM's that are cooked are built using the ASOP rather than modified stock ROM's. It isn't worth waiting and complaining for a 100% optimized OTA ROM when there are tons of temporary solutions.
Click to expand...
Click to collapse
dont get ya. do you think desire owners arent using AOSP ginger?
XSafire said:
I mean the AOSP was released for gingerbread, so we can get some pretty stable ROM's. No it isn't as good as an official update, but if I wanted to wait for official updates, I would have bought a desire.
Now I'm not sure about this, but I think most ROM's that are cooked are built using the ASOP rather than modified stock ROM's. It isn't worth waiting and complaining for a 100% optimized OTA ROM when there are tons of temporary solutions.
Click to expand...
Click to collapse
I bought the N1 because it was great hardware and, most importantly, because it was carrier free. The ability to root and flash the phone is nice in case I ever feel the need to admin yet another Linux machine, but that was certainly not everyones reason for getting the phone.
madman_cro said:
dont get ya. do you think desire owners arent using AOSP ginger?
Click to expand...
Click to collapse
I simply meant that we receive updates as soon as they are available, and are the first ones to get it. Desire has to wait for HTC to update sense and drivers and all that stuff until they release an OTA.
pfmiller said:
I bought the N1 because it was great hardware and, most importantly, because it was carrier free. The ability to root and flash the phone is nice in case I ever feel the need to admin yet another Linux machine, but that was certainly not everyones reason for getting the phone.
Click to expand...
Click to collapse
Touche, although there aren't many people on these forums with the same intentions. I was simply speaking to the masses.
I don't know why release is taking so long...
My N1 resets randomly on CM7.... but luckily I don't have the wonks!
Google will release it when its ready!
Well to be straight on point i dont think we even have as mush as development as the previous Galaxy S1 . Just look at their android development thread and on the first page itself you can find 3 ICS roms . Two of them usable for daily driver , one is CM9 which is still buggy (So is ours ), I mean to say that we are dependent only on the CM9 team for the ICS and we dont have anyother dev to do that for us .
Your views ?
anshmiester78900 said:
Well to be straight on point i dont think we even have as mush as development as the previous Galaxy S1 . Just look at their android development thread and on the first page itself you can find 3 ICS roms . Two of them usable for daily driver , one is CM9 which is still buggy (So is ours ), I mean to say that we are dependent only on the CM9 team for the ICS and we dont have anyother dev to do that for us .
Your views ?
Click to expand...
Click to collapse
simple reasong
samsung galaxy s2 is a perfec phone with perfect firmware.
reason ppl coming here is to change the looks and play around with their perfect phone when there is nothing else to do.
the reason for no ics is because ICS is still buggy on its own so there is no point making roms untill google fixes the base.
If you desporately want more ICS development, then get developing.
If I had the brains to do, I would do. But I don't, so I can't.
Its pretty hard to develop anything without code. They work with what they have and if what they have is crappy, so yeah.
The SGS1 is similar (or almost exactly the same) as the Nexus S so since source is out for that they just took some stuff there and used it on the SGS1. Makes it much easier. We don't have a phone similar to ours that we can borrow bits and pieces from. They tried that with the Galaxy 7.0 Tab Plus but didn't work out so well.
Actually this is the first Smartphone where I don´t feel the need to change much. It´s already damn good.
zabihjan said:
simple reasong
samsung galaxy s2 is a perfec phone with perfect firmware.
reason ppl coming here is to change the looks and play around with their perfect phone when there is nothing else to do.
the reason for no ics is because ICS is still buggy on its own so there is no point making roms untill google fixes the base.
Click to expand...
Click to collapse
ICS is still buggy? I had daily drivers ics Roms on my nexus s backup in october!
Sent from my GT-I9100 using xda premium
Same here best phone ive ever had so far, only things needed to change
where optical and removed the unneeded apps.
ICS seems nice once it's stable and bugfree untill then........
Not sure I would agree.
I am running the Simplistic ICS ROM RC3 as my daily driver. Everything is super smooth from my limited experience. Granted, these are based on Sammy leaks but it beats the deadlock I saw over on the RAZR forum.
Pretty happy overall.
Very happy with my current rom, so yes I am happy overall with development
Nothing really I would change. Even with ics out, I prefer the majority of stuff touchwiz has. Simple tweaking is pretty much it.
Common guys i think ur not getting me i mean to say that we have less developers
I think it's because the original Galaxy S is older and developers have more experience with the hardware. For example it took almost a year before Cyanogengenmod was available for the Galaxy S.
I have to agree with the OP. Seeing as a galaxy s2 is such a popular phone u wuld expect more aosp roms for ics :L
sent from my iPhone 4S.
haha I bet that confused ya
wurzelsepp3 said:
I think it's because the original Galaxy S is older and developers have more experience with the hardware. For example it took almost a year before Cyanogengenmod was available for the Galaxy S.
Click to expand...
Click to collapse
Damn and they got ICS so easily ?
wurzelsepp3 said:
I think it's because the original Galaxy S is older and developers have more experience with the hardware. For example it took almost a year before Cyanogengenmod was available for the Galaxy S.
Click to expand...
Click to collapse
I tend to agree, the Original Galaxy is more established.
The trouble is, the S2 is sandwiched between the Galaxy S, and The upcoming S3. (Stuck between a rock and a hard place)
A lot of Devs and Users will no doubt be waiting to upgrade to the S3 upon launch, and maybe leave the S2 in the shadow somewhat.
Also unfortunately I would imagine a lot of Developers are staying away, considering some of the Flaming that happens on here.
We shall see. But Overall I'm more than satisfied with the Development.
Regards
Judging the level of development of a device just based on ICS is utterly stupid - did you look at all at the Gingerbread development that happened on this phone?
ICS for the original Galaxy S is a FLUKE. It's almost unheard of for an AOSP bringup to succeed on a higher version of Android than what is released for the phone due to lack of compatible binary blobs for vendor-proprietary parts.
The Galaxy S is lucky and VERY unusual - it has a high number of hardware similarities with the Nexus S, which is by its definition, a phone that has as many components open-sourced as possible. As a result, much of the Nexus S source code was adaptable to the Galaxy S as part of the CM7 bringup process.
The I9100 doesn't have this hardware commonality with a Nexus device. The RIL architecture and interfaces are completely different, the GPU is completely different, etc.
Exactly what I was going to mention. Usually porting or developing on phones is easier when someone else with similar hardware has done it before. You just borrow their work and adapt it. The Galaxy S2 doesn't share its hardware with many other phones. Hell, the whole Galaxy S2 line is super fragmented anyway! You have Tegra, omap, Exynos, different cameras, different specs alltogether.
If you just think of the international version... We're pretty much set apart and in the dark with all the proprietary code that the phone has. If you want a quick development path for your phone, you'll need a phone which has generic hardware or fully opensource code... Which is far from being this phone's case sadly.
Of course a lot of the SGS 1 roms where just cut and paste jobs .
Rom +Theme A then Rom + Theme B does not make two roms .
I am more than happy and the answer has always been you want more roms donate a phone to a dev instead of expecting them to pay for your flashing habit .
jje
It must have something to do with what can be achieved; with the exception of new releases from Google the only areas of interest really are storage space and speed. Both of which are pretty good as stock on the S2 where as development for the Desire was huge as it could be faster and, as stock, had a lack of storage space.
Even if you didn't like the look of TouchWiz you could choose a new launcher rather than rooting and flashing new ROMs.
if you want a regular updates and more development then maybe the phone for you is the galaxy nexus. pure google phone and a phone to get updates straight from the Google itself. I have not gone into the forums over there but i am pretty sure you have proper roms coming out through your ears...And i mean roms probably making that phone even better than it already is..and as being so new still the development for that can only get better...
The same for the S2. once the source code is released then you will see roms coming out and development will for sure will be on the high again and you see proper ICS roms coming left right and center...So be happy with what we have here and do more tweaking to get the max out of the phone instead of wondering if the development is slow or not..
Guys in live you can see the Google I/O conference,
http://www.youtube.com/user/googledevelopers?feature=results_main
Say what do you think about that !!
Good luck for Texasice, DK-Zero-Cool to bring to us the best experience for Our beloved Nexus even after 2 years of good and loyal service
Like we are ever going to get jelly bean... We don't even have a functional bug free ics after almost a year.
We have 90% ICS. Only Camera video recording is outstanding. Same on many other ROMS for other handsets I presume.
BTW, will ICS ever be 100% on Nexus One? What do you think? ICS camera dev seems to be dead
Perhaps if we get 3 years out of owning the N1 we can hold our heads high and be proud enough to move on!
Here's to 5 new Nexus on Nov 5th, and then cheaper Nexus in 6 months after that - so roll on May 2013 I say!
cpm said:
Perhaps if we get 3 years out of owning the N1 we can hold our heads high and be proud enough to move on!
Click to expand...
Click to collapse
^^ This..
I am waiting for the next Nexus device. Im hopping it will have a 5 Inch screen..
same here waiting for the next nexus device and praying it will not be made by samsung since i never had good times with there products
fake_japanese_guy said:
^^ This..
I am waiting for the next Nexus device. Im hopping it will have a 5 Inch screen..
Click to expand...
Click to collapse
ah i was watching Jelly Bean running on GN and it is just so fluid! i was beginning to feel so dare i say jealous, but you guys have totally given me new hope!
If we can hold out a couple of months for the next Nexus we can be proud YES1 :highfive:
Nexus One is our hero. long standing, trustworthy little guy. :victory:
race55 said:
Like we are ever going to get jelly bean... We don't even have a functional bug free ics after almost a year.
Click to expand...
Click to collapse
Try this ROM:
http://forum.xda-developers.com/showthread.php?t=1557606
I have been using for couple of months, I find it functional and stable.
fake_japanese_guy said:
^^ This..
I am waiting for the next Nexus device. Im hopping it will have a 5 Inch screen..
Click to expand...
Click to collapse
Hope there will be a 3.7" top notch as well!
Sent from my Nexus One using xda premium
4.3'' is perfect or 4.5
Sent from my Transformer TF101 using Tapatalk 2
5.3" please. Bigger IS better
Sent from my Nexus One using xda app-developers app
Buy a tablet
Sent from my Nexus One using Tapatalk 2
But that won't fit in my pocket. What I'm planning on is a 5.x phablet and a 10" tablet, both Nexus devices.
Ah well, we can all dream
Sent from my Nexus One using xda app-developers app
As for now, almost half a year, we don't have an ICS stable release and neither we will have it soon, I don't think, in a near future, we will have a JB stable one, although this is just a minor release.
I wish the devs did not agree with me
How do you mean not stable? It's perfectly stable and fast. Only the camcorder does not work very well.
I am going to stay with CM7.2 on my nexus one. It's very stable and efficient. Then when the next device comes out I am going use this as my music player
YoMarK said:
How do you mean not stable? It's perfectly stable and fast. Only the camcorder does not work very well.
Click to expand...
Click to collapse
For me it is very stable but CM9 & AOKP ROMs didn't reached stable requirements yet because they have bugs that are important to fix and crucial for the rom's workflow. They are considered experimental for now (CM team released this week CM9 RC1).
Jelly Bean looks bad ass, especially with project butter and the new voice command.
It is also the reason I have finally decided to move on from my N1 after 2 and a half years of loyal service. The failing battery, the half-functioning trackball, and constantly battling internal storage woes have forced me to move on.
The good news is there is a Galaxy Nexus with my name on it, heading my way right now.
GldRush98 said:
Jelly Bean looks bad ass, especially with project butter and the new voice command.
It is also the reason I have finally decided to move on from my N1 after 2 and a half years of loyal service. The failing battery, the half-functioning trackball, and constantly battling internal storage woes have forced me to move on.
The good news is there is a Galaxy Nexus with my name on it, heading my way right now.
Click to expand...
Click to collapse
Even Google drops the price of galaxy nexus to $300, I will stick with the N1.
I'm really hoping the devs can integrate some of the new things in Jelly Bean to their current ROMs without much extra work. I think it should be possible due to very incremental nature of the update.
That said, I've pretty much accepted that if it is possible, it's highly unlikely they'll be able to integrate the Project Butter stuff from what Google has said about it! Seems it will use massive amounts of system storage and RAM, so that's almost definitely out of our N1's capabilities.
I would be amazed if they managed to get that in there. I still hope they can manage to get Google Now and all the other little tweaks in to a potential JB ROM for the N1.
Indefinite Implosion said:
I'm really hoping the devs can integrate some of the new things in Jelly Bean to their current ROMs without much extra work. I think it should be possible due to very incremental nature of the update.
That said, I've pretty much accepted that if it is possible, it's highly unlikely they'll be able to integrate the Project Butter stuff from what Google has said about it! Seems it will use massive amounts of system storage and RAM, so that's almost definitely out of our N1's capabilities.
I would be amazed if they managed to get that in there. I still hope they can manage to get Google Now and all the other little tweaks in to a potential JB ROM for the N1.
Click to expand...
Click to collapse
Especially the New status bar
Sent from my Nexus One using Tapatalk 2
I am currently using a Galaxy S5 on t-mobile and cannot wait for cyanogenmod to release a nightly build. I see there are a couple of cyanogen based roms available now but there is no working camera. i was just wondering what is wrong with the development issue for a working camera. i love everything about aosp roms and was actually considering switching to a nexus 5 just for the pure android experience, but figured i would hold off a little longer to see whats in store this fall with the next nexus or silver or whatever theyre planning on calling it. its a dumb question i know and i just have to be patient. thanks in advance
btylwalk said:
I am currently using a Galaxy S5 on t-mobile and cannot wait for cyanogenmod to release a nightly build. I see there are a couple of cyanogen based roms available now but there is no working camera. i was just wondering what is wrong with the development issue for a working camera. i love everything about aosp roms and was actually considering switching to a nexus 5 just for the pure android experience, but figured i would hold off a little longer to see whats in store this fall with the next nexus or silver or whatever theyre planning on calling it. its a dumb question i know and i just have to be patient. thanks in advance
Click to expand...
Click to collapse
devs are working hard for it , and don't forget that this device is only months released its totally new, so as you said you have to be patient and let the devs do their jobs
Sent from my SM-G900F using Tapatalk
btylwalk said:
I am currently using a Galaxy S5 on t-mobile and cannot wait for cyanogenmod to release a nightly build. I see there are a couple of cyanogen based roms available now but there is no working camera. i was just wondering what is wrong with the development issue for a working camera. i love everything about aosp roms and was actually considering switching to a nexus 5 just for the pure android experience, but figured i would hold off a little longer to see whats in store this fall with the next nexus or silver or whatever theyre planning on calling it. its a dumb question i know and i just have to be patient. thanks in advance
Click to expand...
Click to collapse
CM doesn`t even have a stable version for Hammerhead (Nexus 5) as we speak
gee2012 said:
CM doesn`t even have a stable version for Hammerhead (Nexus 5) as we speak
Click to expand...
Click to collapse
true but a nexus is pure android...which there is no going wrong with. just tired of the touchwiz/samsung control. even after rooted and debloated and custom rom it seems to haunt me. i just must be patient considering the carrier in which i am currently with does not even offer the 32GB version. even more control issues there. alas i will wait
btylwalk said:
true but a nexus is pure android...which there is no going wrong with. just tired of the touchwiz/samsung control. even after rooted and debloated and custom rom it seems to haunt me. i just must be patient considering the carrier in which i am currently with does not even offer the 32GB version. even more control issues there. alas i will wait
Click to expand...
Click to collapse
I like AOSP too, don`t get me wrong but it becomes boaring to me after some time. And anyone knows Samsung has bloatware installed (which most you can turn off though) so that shouldn`t come as a surprise
btylwalk said:
I am currently using a Galaxy S5 on t-mobile and cannot wait for cyanogenmod to release a nightly build. I see there are a couple of cyanogen based roms available now but there is no working camera. i was just wondering what is wrong with the development issue for a working camera. i love everything about aosp roms and was actually considering switching to a nexus 5 just for the pure android experience, but figured i would hold off a little longer to see whats in store this fall with the next nexus or silver or whatever theyre planning on calling it. its a dumb question i know and i just have to be patient. thanks in advance
Click to expand...
Click to collapse
The issue is there is no camera module or something. I think it will be fixed reasonably soon but obviously there's no way to say for sure.
Sent from my SM-G900F
Will it happen :?
Well support stopped at 4.3 and I'm using the latest lollipop ROM with my S3 (via the latest BlissPop ROM). So I'm sure it will happen.
Sent from my GT-I9300 using XDA Free mobile app
gsms said:
Will it happen :?
Click to expand...
Click to collapse
Coming from Samsung? No f*****g way. But fortunately there are many skilled and committed developers at xda who are working hard to keep our device up-to-date. So I'm sure a few of them will update their ROMs to Android M Sources.
The other Question is, if the (old) SIII Hardware is performant enough for Android M. But from what I read in the news, it shouldn't be too resource consuming.
So, if you are running a ROM and are willing to flash a new version: Things are looking good .
Its looks like a tiny upgrade as well so I'm sure the talented devs on this site can make it happen.
Too early to talking about M
senaferdy79 said:
Too early to talking about M
Click to expand...
Click to collapse
I don't like Android L, that's why...
senaferdy79 said:
Too early to talking about M
Click to expand...
Click to collapse
I think also......:good:
With aosp source code from Google still a couple of months away, I don't see this happen. Even the talented devs that ported 5.0 to our s3 will probably stop here. We may see more stable 5.1.1 ROMs, but I think that's it.
Let's face it. We have a poorly documented/sourced exynos, and our device is over 3 years old. Its been a good run.
gsms said:
I don't like Android L, that's why...
Click to expand...
Click to collapse
you know that android M is 95% similar to android L , few tweaks and improves under the hood but nothing else so dont be so amazed for this update
Try the latest blekota 4.4.4, note 4 rom, it's really look like the note 4.
Samsung dropped support at 4.3 and will not be updating past it for the s3.
They have newer flagship devices in the S family which have taken over.
Custom roms might though.
Sent from a stolen phone!
On the one hand,we are lucky enough to get android L and the developers may stop.But android M is mostly same as L with a few extra features and tweaks.So,fingers crossed.
dkonect said:
Try the latest blekota 4.4.4, note 4 rom, it's really look like the note 4.
Click to expand...
Click to collapse
It is really nice, looks and runs very good but the problem is that after about a month it started running slow, which is weird because I installed about 15 apps at the beginning and then nothing. I flashed unofficial CM12 and it is ok except camera.
Sent from my Lenovo TAB S8-50F using Tapatalk
m-for-i9300
i and another popular dev we're working on m dp for i9300.
for now it's very difficult, if we can get a build for sure it will be buggy (no ril, wifi etc.)
anyway: https://github.com/m-for-i9300
Maybe it's possible with custom roms
We all know somebody is gunna port this to our device. The s3 still sells. Its got a bit of development still and cm12.1. Someone will do it.
Still waitingg
Sent from my GT-I9300
Marshmallow?
I think, we get Marshmallow only with customs ROM's like CM12, CM12.1.
Probably modders can port Marshmallow Rom.And also It will be Cm 13.0.I really liked Lollipop cuz the interface looking great and modern.
I agree with some posts, it's still too early to develop android M for non nexus phones. With patience and colaboration, eventually some developer will... develop android m for the S3.