Related
Hello all, I'm new to the Nexus. I get mine next week. I was wondering with Honeycomb 3.2 supporting smaller screen devices, do you think we will see Honeycomb on the Nexus? Some of the pull with Honeycomb is it'll get faster updates. But didn't know if there was an advantage?
I have and HTC Evo 4g and a Samsung Galaxy Tab 10.1 wifi. I love Samsung products so I'm going all Samsung now. Although my computers at home are iMac and MBP, I just like Android better.
Sent from my GT-P7510 using Tapatalk
djchad72 said:
Hello all, I'm new to the Nexus. I get mine next week. I was wondering with Honeycomb 3.2 supporting smaller screen devices, do you think we will see Honeycomb on the Nexus? Some of the pull with Honeycomb is it'll get faster updates. But didn't know if there was an advantage?
I have and HTC Evo 4g and a Samsung Galaxy Tab 10.1 wifi. I love Samsung products so I'm going all Samsung now. Although my computers at home are iMac and MBP, I just like Android better.
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
No I don't think so. Honeycomb is for tablets only.
Also the fact that the source code is not available makes it even more difficult to get on to a phone.
Ice Cream Sandwich is meant to be one OS that will run on both tablets and phones. Honeycomb in my opinion will be done very soon. Everything will be on Ice Cream Sandwich.
That is what I figured. I would not be surprised if larger tablets didn't skip 3.2 and star working on 4.0 ....unless 3.2 is just a slam dunk to regression and rollout.
I love my Tab10.1 and am sure ill love the Nexus. I use SPB Mobile Shell 3D on all devices. So makes for a great cross device experience, regardless of version of the OS.
Sent from my GT-P7510 using Tapatalk
Via Google. Who's ready for CM9?
YES
yes yes cant wait!!
it's only for the maguro = Galaxy Nexus
the other devices profiles are not included with this release
AllGamer said:
it's only for the maguro = Galaxy Nexus
the other devices profiles are not included with this release
Click to expand...
Click to collapse
I doubt that'll stop porting being done pretty quickly.
Can't wait for a rom to be available for the amaze!
Hope to see something cool for the Atrix 4G. Probably won't happen any time soon, but a man can dream.
Can not wait till it finds it way to my device.
Surely this will reach the Galaxy S2 before the end of the year? Have an upgrade due next month and as much as I want ICS I can't justify upgrading to the Galaxy Nexus as it's just not good enough, so think I'll wait for S3 and hope that Cyanogen ports this over ASAP! Will definitely donate a nice amount to the cause.
im hoping it reaches my gs2 asap
worth the wait!
Google really seems to be embarrassed by the HC source, but glad to see that they kept to their openness promise.
I want my 2.3.5 update for my S2 and then I want ICS by jan-fep.
Can anyone familiar with the dev-scene comment on whether this will help in porting ICS to GSII ? Last I remember, the problem with SDK port was with the graphic driver (Mail400) and the source-code release for sure does not help on that front!
its about time!
let's get it on!
Yessssssss!!!!!!!!!!!!!!!!!!!!! Finally!!! Xmas today!
Still waiting working on my phone
How does the development for other devices (than Galaxy Nexus) look like from this point:
1) someone said there are no "profiles" for other devices - does it mean that Google has still to release something in addition to this source to make it usable for the developers, so that they'll be able to make custom ROMs like CM for other devices?
or
2) the developers can handle it without that "profiles"?
And of course I understand the devs have to collect all device-specific code like drivers etc.
--
Tom
Nice!
10chars
AllGamer said:
it's only for the maguro = Galaxy Nexus
the other devices profiles are not included with this release
Click to expand...
Click to collapse
Have you read the information on the source page?
News Source Code Available for Android 4.0
The source code for the Android 4.0 platform and software stack has been released! This release allows OEMs to begin preparing Android 4.0 for installation on new and existing devices, and allows hobbyists, enthusiasts, and researchers to develop custom builds. For information on how to obtain the software, visit our Getting the Source page.
Click to expand...
Click to collapse
Sent from my Zio using xda premium
Awesome. What a treat.
Yeah let the roms coming!!
Has anyone looked at what it would take to port CM9 to this tablet yet?
I would love "ICS" on my 7.0 plus!! Please!!
Sent from my Epic 4G running CM9 using xda premium.
As I understand Samsung is releasing ICS during the fist quarter, no release date yet.
I don't think developers are interesting in working on it until it's released. I'm running ICS on my phone, Samsung hasn't released the drivers so the developers have put in a lot of hours and hard work, it's not perfect but getting close. The battery life was terrible at first due to not having the proper drivers but over time it has gotten pretty decent. A working GPS is also an issue, again due to lack of proper drivers. I think the main difference ICS will never be released for my phone unlike our tabs.
GTOJim said:
As I understand Samsung is releasing ICS during the fist quarter, no release date yet.
I don't think developers are interesting in working on it until it's released. I'm running ICS on my phone, Samsung hasn't released the drivers so the developers have put in a lot of hours and hard work, it's not perfect but getting close. The battery life was terrible at first due to not having the proper drivers but over time it has gotten pretty decent. A working GPS is also an issue, again due to lack of proper drivers. I think the main difference ICS will never be released for my phone unlike our tabs.
Click to expand...
Click to collapse
I agree, it would be a waste of time for the devs. Patience....
Sent from my HTC Glacier using Tapatalk
Agree. Am running the port of CM9 on my NC and while it's sweet and interesting...waiting for the official release is the way to go as its so close.
I seriously doubt samsung will release ICS for our g-tab Q1. If we're lucky it will be Q2, but i'm thinking worst case scenario Q3.
bdds13 said:
I seriously doubt samsung will release ICS for our g-tab Q1. If we're lucky it will be Q2, but i'm thinking worst case scenario Q3.
Click to expand...
Click to collapse
I believe they have stated q1 numerous times I'm new to samsungs so I'm not completely sure if they are true on their release dates. It seems to me it would be a waste of time for the devs to even bother until ics is officially released
Sent from my HTC Glacier using Tapatalk
ringnutz said:
I believe they have stated q1 numerous times I'm new to samsungs so I'm not completely sure if they are true on their release dates. It seems to me it would be a waste of time for the devs to even bother until ics is officially released
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Samsung has a laughably bad reputation as far as updates go, if they aren't the worse then they are close to it. I would like to see ICS hit Q1 but I will expect it sometime this summer or fall.
Sent from my Galaxy Nexus using xda premium
Codiusprime said:
Samsung has a laughably bad reputation as far as updates go, if they aren't the worse then they are close to it. I would like to see ICS hit Q1 but I will expect it sometime this summer or fall.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Not to derail but you can argue that all android manufacturers are slow with updates, Samsung gets a lot of attention because they sell a lot of phones.
With that said, Samsung is painfully slow and I think this device stands little to no chance of a Q1 update, just my opinion.
Sent from my Galaxy Nexus using Tapatalk
Whenever a carrier, (e.g. AT&T, TMobile, Sprint, Verizon) gets involved, the updates slow to a crawl. In all fairness to Samsung, they've been pretty good with updates to the 10.1. I've seen an update to 3.1 and 3.2 since I bought mine on launch day, and they were fairly quick. Mind you, I'm taking into account the fact that Samsung had to put touchwiz on Honeycomb and fix some of the issues that were left behind when Honeycomb launched. We've also seen Samsung move rather quickly to resolve issues on the 7Plus, including an update that dropped last night that is supposed to fix the SOD issue. All in all, Samsung has been good about updating its wifi-only devices, so while I'm confident that the phones will miss that Q1 deadline, I have high hopes for the tablets.
I hear you but talk to original galaxy tab wifi owners who are still rocking GB.
Hmmm, there was an ota last night?
On topic, I would cm9 on this device. Fingers crossed.
Sent from my Galaxy Nexus using Tapatalk
The reason I asked this is not so much that I can't wait for ICS. It is more derived from wanting an ASOP-ish experience. I am also thinking about the future. OEMs are usually good for the first year of supporting the devices they make. Then they start to fail claiming that the device is not "compatable" with the latest version. I have an old HTC hero that my son uses as an MP3 player. It is running CM7 and the OEM claimed that it would not support gingerbread, heck they even have an ICS port for it.
CM seems to have a good record of keeping supported devices working. I am sure that once ICS is released for the 7 plus there will be custom builds available.
lrs421 said:
I hear you but talk to original galaxy tab wifi owners who are still rocking GB.
Hmmm, there was an ota last night?
On topic, I would cm9 on this device. Fingers crossed.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I am an original galaxy tab owner still rocking GB. (I've flashed ICS, but I decided to rollback until the camera issues have been solved and more of my Gameloft purchases are updated for ICS compatibility,) I'm not overly upset that Samsung didn't update it to ICS, but that may just be a personal thing.
Samsung started rolling out an OTA last night that will be pushed to all devices over the next two weeks.
rkmj said:
I am an original galaxy tab owner still rocking GB. (I've flashed ICS, but I decided to rollback until the camera issues have been solved and more of my Gameloft purchases are updated for ICS compatibility,) I'm not overly upset that Samsung didn't update it to ICS, but that may just be a personal thing.
Samsung started rolling out an OTA last night that will be pushed to all devices over the next two weeks.
Click to expand...
Click to collapse
Official GB? Last I checked the original galaxy tab 7 owners were still rocking Froyo, officially.
Sent from my Galaxy Nexus using Tapatalk
lrs421 said:
Official GB? Last I checked the original galaxy tab 7 owners were still rocking Froyo, officially.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Official GB. If I were still on Froyo, then I'd be quite upset at Samsung.
lrs421 said:
Not to derail but you can argue that all android manufacturers are slow with updates, Samsung gets a lot of attention because they sell a lot of phones.
With that said, Samsung is painfully slow and I think this device stands little to no chance of a Q1 update, just my opinion.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
They are not only slow but also the updates themselves are notoriously bad and it usually takes a long time for bug fixes. Samsung's software development side is really not that great.
You are right though, as of right now all of the manufacturers suck pretty hardcore. It's pretty ridiculous really, hopefully they get better with releasing fewer devices.
Sent from my Galaxy Nexus using xda premium
rkmj said:
Whenever a carrier, (e.g. AT&T, TMobile, Sprint, Verizon) gets involved, the updates slow to a crawl. In all fairness to Samsung, they've been pretty good with updates to the 10.1. I've seen an update to 3.1 and 3.2 since I bought mine on launch day, and they were fairly quick. Mind you, I'm taking into account the fact that Samsung had to put touchwiz on Honeycomb and fix some of the issues that were left behind when Honeycomb launched. We've also seen Samsung move rather quickly to resolve issues on the 7Plus, including an update that dropped last night that is supposed to fix the SOD issue. All in all, Samsung has been good about updating its wifi-only devices, so while I'm confident that the phones will miss that Q1 deadline, I have high hopes for the tablets.
Click to expand...
Click to collapse
Yes, it is key to not forget the carrier influences and also bear in mind that carrier-specific variants of, e.g., the Galaxy S2 were not within the scope of Samsung's ICS in Q1 announcement.
My previous phone was the Epic 4G. It was the first US carrier variant to receive official Froyo and Gingerbread updates but it received them well after the "stock" Galaxy S model (GT-I9000, I believe) received them.
So in other words, when looking at Samsung's update record, remember to compare apples to apples. Nexus One got its official Froyo upgrade in May of 2010, I think. The GT-I9000 got its official Froyo upgrade in August. Gingerbread was released in December of 2010 on the Nexus S. I believe the Nexus One got its upgrade in January of 2011 and the GT-I9000 got its GB upgrade in March of 2011.
All in all, not too shabby for Samsung. It's only when you factor in variants (which have all been customized to various degrees which require OS customization) and carrier agendas (I believe AT&T let its phones languish on 2.1 for a good while to not have them be competitive with the iPhone, which was AT&T exclusive at the time) that Samsung's rep starts to take a turn.
The I9000 vs Captivate is probably the clearest example of the negative effect a carrier can have on update releases.
The I9000 and Captivate were close enough that it took developers here very little time (days maybe? weeks at most...) to begin running I9000 releases on the Captivate. However, it took on the order of nine months from the I9000's GB release before the Captivate officially received Gingerbread.
Similarly, Samsung has only been slightly behind other tablet vendors in Honeycomb updates for the Tab 10.1, mainly due to being the first vendor to include a custom skin - but "behind" has usually been at worst 1-2 months of delay.
Similarly, the I9100 is scheduled to receive ICS in March and Sammy seems on track with that. However, the I777 (AT&T variant) probably won't see official ICS until 2013...
For the 7.0 Plus - for the developers the Tab does have, I think polishing the current HC releases is the top priority. Honestly, ICS offers far less compared to HC than it does compared to GB, and right now, there's some major work to be done on the 7.0 Plus thanks to Samsung being asshats with regards to AR6000 driver source code.
rkmj said:
Official GB. If I were still on Froyo, then I'd be quite upset at Samsung.
Click to expand...
Click to collapse
Yep, mine was GB right out of the box! Love this little device!
Mines has 3.2 with honeycomb. Not sure what version that is.
The CyanogenMod team will be dropping support for devices with the older processors including the Nexus One & the Bravo (many more, too).
I think this means The CyanogenMod team will start focusing one more devices with dual-core processors. I think.. including the Blaze 4G. What do you guys think.?
Sent from my bathroom.
Not unless we get a SGS4G in the hands of a dev, or convince one of them to grab it over something else.
Didn't know the S3 chip is old lol. My brother has a Galaxy S3 and honestly in everyday performance this phone does not fall behind and often surpassed the S3. I tested both phones in a bunch of games and tasks. The number of cores on a phone is a bit overestimated.
Sent from my SGH-T769 using xda premium
i don't think we will get an official update from the cyanogenmod team!
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_FAQ
while the CPU for our phone came out almost 2 years ago, it's capable of running ICS just fine... the T989 is proof of that, it's virtually identical to ours. What we need is the kernel sources for this phone for ICS and that can only come from Samsung. Once that is released, setting up ICS should be easy. Hell, we could just copy the majority of the T989 (T-Mo SGS2) source tree for CM.
dr4stic said:
while the CPU for our phone came out almost 2 years ago, it's capable of running ICS just fine... the T989 is proof of that, it's virtually identical to ours. What we need is the kernel sources for this phone for ICS and that can only come from Samsung. Once that is released, setting up ICS should be easy. Hell, we could just copy the majority of the T989 (T-Mo SGS2) source tree for CM.
Click to expand...
Click to collapse
sounds good!! hope we get it soon!!
We need to buy about 2 phones for testing some custom android apps we've built.
Does anyone have suggestions on what the best phones for testing would be?
I was thinking something with HTC sense on it, and something with stock android on it. Both need to be able to s-off and root easily.
erm... the google dev phones (nexus) ?? Personally I use galaxy nexus most for this kinda thing
For any kind of software testing, you need to know how it will function on both the latest and greatest devices, as well as the oldest hardware you intend to support.
I'd think for the price of two top-tier 2012 phones, you could buy 1 top of the line current phone, one from last year, and one from 2 years ago. Possibly also include Sense, Touchwiz and vanilla android.
Something running GB and something running ICS/JB. Many phones are still on GB so a used device running GB would be useful to test on.
Test it on emulator first?
jianC said:
Test it on emulator first?
Click to expand...
Click to collapse
Yes for sure it's the first thing to do,but not always if it works on emulator it will work on specific phone
Nexus one and galaxy nexus. Then you've got gingerbread and jellybean covered
If you need a newer phone for testing , the Galaxy Nexus is an obvious choice .
If you need a older phone ( old hardware ) to test yous apps , have a look at Nexus 1 or HTC Desire , it can run flawlessly 2.2 , 2.3 and 4.0.4 . I have a Desire on ICS ( BCM ) so I can tell .
willpower102 said:
We need to buy about 2 phones for testing some custom android apps we've built.
Does anyone have suggestions on what the best phones for testing would be?
I was thinking something with HTC sense on it, and something with stock android on it. Both need to be able to s-off and root easily.
Click to expand...
Click to collapse
HD2? ROMs range from Android 2.1-4.1 (AOSP, AOKP, CM), Sense 2.0-3.5 (one discontinued Sense 4 alpha), TouchWiz + GB, Xperia Arc GB, MIUI etc. It's also got similar specs to a low-range phone nowadays so that would be a good choice I think. In addition, a One X probably.
HTC One X?!
Samsung galaxy nexus
Sent from my Galaxy Nexus using xda premium
Galaxy nexus its official hands down
Sent from my evo 4g using xda premium
It seems it is indeed no contest there.
Does the Galaxy Nexus come with Sense by default? (It's been a while since I've looked into these. Last Android phone I owned was a droid bionic and before that the htc hero.)
We definitely are going to support gingerbread, so we'll need a little bit of an older phone too. I'm sure breaking it up like that into 3 or so phones is ok, as long as they fall under budget.
And yeah, the dev tests with emulators, but I'm QA on this project so I get to play with them real-world once he's done and find more bugs.
Nexus S and a Galaxy Nexus,
Will do the job well:thumbup:
Sent from my GT-S5660 using xda premium
willpower102 said:
It seems it is indeed no contest there.
Does the Galaxy Nexus come with Sense by default? (It's been a while since I've looked into these. Last Android phone I owned was a droid bionic and before that the htc hero.)
We definitely are going to support gingerbread, so we'll need a little bit of an older phone too. I'm sure breaking it up like that into 3 or so phones is ok, as long as they fall under budget.
And yeah, the dev tests with emulators, but I'm QA on this project so I get to play with them real-world once he's done and find more bugs.
Click to expand...
Click to collapse
GNex is a Nexus phone, so why would it come with Sense?
Anyway, the best choice is still the HD2 IMO. You can test it on all versions of Android from 2.1-4.1 and it's incredibly cheap, with specs which are not too bad (1GHz Snapdragon with 576MB RAM) for the price. If you can get the app to run smoothly on the HD2 the likelihood is that it will run on any newer phone.
IMHO you have yo use a stock device.. nexus as all the docs suggest. Custom ROMs have additions substitutions and tweaks that in a dev sense are not baseline. Although the differences are minimal or should be. Better to play safe. So nexus s and galaxy nexus.. Google provide stock ROMs for these in dev device downloads.
Sent from my Galaxy Nexus using xda premium
Noted. Thanks.
And yeah, that's cool that some of these phones support plenty of roms, but I don't want to be flashing 3 different roms every time the dev iterates a new point (v.2) update. I'd rather have 2-3 phones ready to go. (seems lazy, but I've got a lot of other work to do to
We got a droid (motorola timestamp issues), a Galaxy Nexus, and an hd2. So the hd2 comes stock with windows mobile? This is strange to me.
willpower102 said:
We got a droid (motorola timestamp issues), a Galaxy Nexus, and an hd2. So the hd2 comes stock with windows mobile? This is strange to me.
Click to expand...
Click to collapse
Well, the hd2 does have a lot of support, but when the top threads in the device specific forum warn of how unstable and beta-ish android development is on this phone, then I'm not really as excited as I was. might end up returning this one.