NFC - Epic 4G Q&A, Help & Troubleshooting

I'm really looking forward to this feature. Both of the Nexus S phones have it, and I'm hoping we get it in either a OTA from Sprint/Samsung for Gingerbread, or from CyanogenMod or other ROMs.

Original Android <3ers! said:
I'm really looking forward to this feature. Both of the Nexus S phones have it, and I'm hoping we get it in either a OTA from Sprint/Samsung for Gingerbread, or from CyanogenMod or other ROMs.
Click to expand...
Click to collapse
WE don't have the hardware for NFC built into our phones, but there is NFC sdcards.

Related

Ice Cream Sandwich Spotted on SGSII

http://www.gsmarena.com/samsung_galaxy_s_ii_running_android_ics_rom-news-3274.php
Great news! We can only hope our neglected E4GT gets some ICS love soon too.
EDIT: Apparently it's been said this is just an ICS launcher...
Still some pretty cool mods though hey! I wouldn't mind the fast switch program he had. Its the same one I got on my galaxy tab 10.1 ICS will get here eventually amd when it does I hope it changes the android expereince with lots of eye candy and fun features. Hope it really takes advantage of our 1gig ram and fast internal storage and is coded specificly for duel core cpu's. How sweet would thay be !
Our phone is neglected? It's been out for a month. Hardly time to consider it neglected.
TurboFool said:
Our phone is neglected? It's been out for a month. Hardly time to consider it neglected.
Click to expand...
Click to collapse
I think they are talking in general the SGS2 has been out for a few months now it's just new for the US market.
there is a ICS launcher that looks just like that and the status bar is wrong i think its the launcher with a themed bar
I could not careless about the ICS Sprint would push to us. I want the ICS that the devs bring us.
cidica said:
I think they are talking in general the SGS2 has been out for a few months now it's just new for the US market.
Click to expand...
Click to collapse
No, I mean our phone!
Figgen AT&T version already has Cyanogen mod!
I can only hope that ICS performs as well as the video shows.
Definitely a cool mod though!
When ICS does come out, will this end up for sure on our E4GT?
tweeker404 said:
Definitely a cool mod though!
When ICS does come out, will this end up for sure on our E4GT?
Click to expand...
Click to collapse
Nope
Sent from my Samsung Galaxy S2
WhiteZero said:
No, I mean our phone!
Figgen AT&T version already has Cyanogen mod!
Click to expand...
Click to collapse
Its because its gsm
Sent from my Samsung Galaxy S2
Just enjoy your phone. With the heavily customized interface, don't expect ics until summer 2012. It is what you signed up for.
Sent from my SPH-D710 using Tapatalk
I won't see a upgrade untilled 2013.
Sent from my SPH-D710 using XDA App
Google WANTS Ice Cream Sandwich
It was my understanding that Google wants as many devices as possible to be upgraded to Ice Cream Sandwich as soon as possible to push developers in to moving their current applications to this platform and that Google basically wants previous versions including Honey Comb to go the way of the Dodo or the Dinosaur. So this could mean that we would see an upgrade fairly quickly for our devices so as to reduce fragmentation.
Blu3Fr0g said:
It was my understanding that Google wants as many devices as possible to be upgraded to Ice Cream Sandwich as soon as possible to push developers in to moving their current applications to this platform and that Google basically wants previous versions including Honey Comb to go the way of the Dodo or the Dinosaur. So this could mean that we would see an upgrade fairly quickly for our devices so as to reduce fragmentation.
Click to expand...
Click to collapse
You are setting yourself up for disappointment. The definition of insanity is doing the same thing over and over expecting a different result. ICS updates will start going out in middle 2012.
Sent from my SPH-D710 using Tapatalk
ravizzle said:
Its because its gsm
Sent from my Samsung Galaxy S2
Click to expand...
Click to collapse
Yes, sadly the CDMA and WiMax radios add a few hurdles.
Someone posted this on engadget as an idication that the epic touch 4g would get ICS. Frankly I'm not sure how they determined that from the link.
HTML:
http://device.sprintpcs.com/Samsung/SPH-D710/EJ14.rdf
boe said:
Someone posted this on engadget as an idication that the epic touch 4g would get ICS. Frankly I'm not sure how they determined that from the link.
HTML:
http://device.sprintpcs.com/Samsung/SPH-D710/EJ14.rdf
Click to expand...
Click to collapse
All that tells us it they're working on an update (which we already knew, since they have known bugs they're trying to resolve), and it's full of placeholder text. The only version is mentions is 2.3.3, and we're on 2.3.4. So clearly not an indication of any actually useful information.
TurboFool said:
All that tells us it they're working on an update (which we already knew, since they have known bugs they're trying to resolve), and it's full of placeholder text. The only version is mentions is 2.3.3, and we're on 2.3.4. So clearly not an indication of any actually useful information.
Click to expand...
Click to collapse
Thanks - I couldn't figure out why they thought that link had anything to do with ICS.
Of course if they really wanted a shock and awe campaign tomorrow, just imagine if the top 10 Android devices all got an update to ICS tomorrow
I would rather have to wait a bit for good ROMs than have everything the first week so we don't have to listen to the "Where's the Jelly Bean update " talk. My phone is perfect and will only get better. Its not like every CM7 nightly is perfect. It takes a lot of nightlies to get a stable release. I have been flashing all of the Nexus releases....last nights was great though...patience people
Sent from my SPH-D710 using xda premium

Whats up with Google and the Nexus

You know when you buy a nice shiny new Nexus, you'd expect to be leading the way in the Android version race...
But what the hell is Google doing with the Galaxy Nexus? Handsets are still at 4.0.1 and 4.0.2... but the Nexus from last year and the Xoom officially have 4.0.3.
Whats up?
player911 said:
You know when you buy a nice shiny new Nexus, you'd expect to be leading the way in the Android version race...
But what the hell is Google doing with the Galaxy Nexus? Handsets are still at 4.0.1 and 4.0.2... but the Nexus from last year and the Xoom officially have 4.0.3.
Whats up?
Click to expand...
Click to collapse
That is what the source is for
There are already other threads on this.
The Nexus S OTA isn't even pushed to everyone. It's on hold right now.
The Xoom's ICS push is only for the WiFi version and only for specific people who signed up for it.
Who says that the GN will even get an OTA 4.0.3 update? They may even wait for 4.0.4 or whatever at this point. Who knows. But theres clearly a reason why they're not releasing it. They're not finished and just holding onto it for no reason...
If you really want it that bad you can install a custom ROM based on 4.0.3, or compile it yourself from source and flash it. Or, just wait for the OTA and chill!
BlackDino said:
That is what the source is for
Click to expand...
Click to collapse
^this right there^
Xoom ICS has gone out to the general pop.
I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Yea 4.0.3 may be more geared with older devices to bring them up to speed... but obviously it isn't hurting the Nexus's unofficially running the 4.0.3 AOSP roms, so why not just throw it down to us? If the Nexus is the developer phone for Google, then 4.0.3 was developed on a new Nexus. Then why don't we have it yet?
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?
player911 said:
I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Yea 4.0.3 may be more geared with older devices to bring them up to speed... but obviously it isn't hurting the Nexus's unofficially running the 4.0.3 AOSP roms, so why not just throw it down to us? If the Nexus is the developer phone for Google, then 4.0.3 was developed on a new Nexus. Then why don't we have it yet?
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?
Click to expand...
Click to collapse
Totally.My.Thoughts.
One thing I'm curious about: Why on Earth was OTA for SNS halted?! My SNS with 4.0.3 was fine, IMO
If you are going to root and put a rom on your phone why do you honestly care? There are so many threads on this already. No PHONE is being pushed 4.0.3 right now anyways.
Sent from my Galaxy Nexus using xda premium
holy hell guys the OTA for the nexus s was halted because they found some bugs during rollout, so they stopped. and they stopped galaxy nexus because of that as well. when they fix the bugs, they will continue the roll out. do you guys think google is doing this on purpose, they want to NOT give our the update to all as some master plan. or the more likely answer, they are fixing serious bugs.
RogerPodacter said:
holy hell guys the OTA for the nexus s was halted because they found some bugs during rollout, so they stopped. and they stopped galaxy nexus because of that as well. when they fix the bugs, they will continue the roll out. do you guys think google is doing this on purpose, they want to NOT give our the update to all as some master plan. or the more likely answer, they are fixing serious bugs.
Click to expand...
Click to collapse
The thread should end on this note
Sent from my Galaxy Nexus using xda premium
Do you know how to read version numbers? 4.0.3 Small release. If it were something like 4.1, ok, but a small release like this...chill out seriously.
player911 said:
I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Click to expand...
Click to collapse
It is out officially.
Build.
It.
Your.
Self.
The difference between a Nexus and every other Android phone is that you can take the LATEST publicly available source code and build a 100% fully functioning ROM with it. No matter how you slice it, you're not going to be able to build a 100% functioning Stock Android build for any other phones. They are hacked together. They are frankenbuilds. Yes other phones have 4.0.3 releases, but none of them are 100% functional. Not sure if you noticed, but for those phones you'll see a list of "what works" and "what doesnt work". For the Nexus phones, you can just build directly from Google's source and it will just work.
See: Nexus S vs Galaxy S. Although the Nexus S and the Galaxy S are identical in almost every way, the Nexus S has had ICS for months now. And you can build 4.0.3 for the Nexus S and it will Just Work.
The Galaxy S ICS releases otoh are FILLED with "known issues" - feel free to check yourself.
Just because it's not an OTA doesn't mean it's not available. You want a pure AOSP build that will be identical to an OTA that Google would push? Just build it yourself.
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?
Click to expand...
Click to collapse
They updated the Nexus S 4G a few times before they ever rolled out updates to the mainline Nexus S. There's really no rhyme or reason to when they roll out OTAs. If you care so much about having the latest official build though, again, build it yourself from their source code. What else do you think they do? The OTA for 4.0.3 will/would be built from the same identical 1's and 0's, bits, and bytes, that is already available quite openly in the AOSP tree. It's been available for months.
i was on 4.0.1 standard with no OTA updates. doesnt matter because the nexus is made to be customised, and be a developer edition device.
i was happy to flash 4.0.3 and a custom kernel. if you arent, then i think that buying a nexus was not the wisest of decisions.
I think people just want a quality official update direct from Google. Not knocking anything the developers do, but they aren't official builds. I'd rather have something I know Google wants out there running on my phone. For all we know, there are issues with 4.0.3 which is why it hasn't been actually placed on the Nexus S and Galaxy Nexus. Yet, you are so eager to say put it on yourself.
Sent from my Galaxy Nexus using XDA App
I would rather wait a little linger for a more stable build.
Sent from my Galaxy Nexus using Tapatalk
player911 said:
I'm on XDA multiple times a day and never seen an actual thread on this. Yea we have kangs and AOSP but who doesn't. I bought a Nexus to get Android updates as they come out... I'm running 4.0.3 and it isn't a huge deal that it isn't out officially, but why is it rolling out to everyone else BUT US?
Yea 4.0.3 may be more geared with older devices to bring them up to speed... but obviously it isn't hurting the Nexus's unofficially running the 4.0.3 AOSP roms, so why not just throw it down to us? If the Nexus is the developer phone for Google, then 4.0.3 was developed on a new Nexus. Then why don't we have it yet?
Something just seems strang IMO. Having a Nexus One and following the Nexus S, I haven't seen them update an older device BEFORE the current line. Isn't it a little weird that last years model is running a newer version then we are? Some Nexus's are running on 4.0.1. Whats that about?
Click to expand...
Click to collapse
Could be because of 4g??
Sent from my Galaxy Nexus using Tapatalk
jsntrenkler said:
I would rather wait a little linger for a more stable build.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I've been using Androids since the Eris came out. Seriously, 99% of the time the ROMs/kernels put out by the devs here and on other sites are more stable than the official OTAs by the companies.
And I've been using Android since the G1, minus a small timeout on WP7, and custom ROMs always came with quirks left and right, that in their entirety always managed to piss me off in some way. If they don't do stupid **** in the kernel (I especially like the enabling of Linux kernel features just because they sound nice), they mess around with the userland, trying to improve things into breaking.
Tom Servo said:
And I've been using Android since the G1, minus a small timeout on WP7, and custom ROMs always came with quirks left and right, that in their entirety always managed to piss me off in some way. If they don't do stupid **** in the kernel (I especially like the enabling of Linux kernel features just because they sound nice), they mess around with the userland, trying to improve things into breaking.
Click to expand...
Click to collapse
Google tells you how and what to build a completely untouched version of their code. If that bugs ya, and is not official enough for ya, then you are missing the point of this device. The device is officially supported by AOSP for yakju and mysid. If the idea of a source built rom bugs you just because its not on a Google sanctioned buildbox, then thats a shame.
I understand what you are saying about customized builds, but its easy to make a completely stock Google approved experience. Download source, setup vendor, and then make. Then you can use fastboot to flash. No need for clockwork, no need for root. If there is a demand for this, I would be happy to make both maguro and toro builds. I won't even root them and they will be odexed.
Once i get some time i plan on compiling myself a fully stock ics rom. Cause i can and that is the point of this stupid thing.

Cyanogenmod Security changes

http://www.cyanogenmod.com/blog/security-and-you
An interesting change, I'd say...
Care to give those of us to lazy to read this, the readers digest version?
Sent from my SPH-D710 using xda premium
mauricehall said:
Care to give those of us to lazy to read this, the readers digest version?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
CM9 will come with root access turned off (from the rom) by default. There is a new option so that you can turn root on be it for
Disabled,
Enabled for ADB only
Enabled for Apps only
Enabled for both.
That's all this really is.
Root is taken out of the builds for security purposes. You can enable root through adb.
Sent from my SPH-D710 using XDA
CharlyDigital said:
Root is taken out of the builds for security purposes. You can enable root through adb.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
You CAN enable ADB root using ADB which almost seems like a security flaw ADB root access is off by default as well.
But from what I have read ADB will not be required to set this. It just has to be changed by the user from the development options.
I have been wondering about this for a looooooong time. When we root our devices we are voluntarily opening up the biggest hole possible. I'm glad to see it addressed in such a practical manner.
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
kthejoker20 said:
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
Click to expand...
Click to collapse
....maybe it's just the devices you've owned?
Ask someone with an OG droid, or someone with an Evo, or a Hero, or a GSM Samsung Anything....Hell, CM7 is fantastic on my Nook Color....Cm9 is too, though--I don't remember--I think It's a kang....
The only issue I've had has been with CDMA Samsung handsets...
EDIT: I guess what I mean to say is, there is so much to support that unless you have one of the heavily supported (or easily supported) devices then the fact that it boots up and works at all should be impressive enough.....On all the above mentioned devices I had a nearly flawless experience far preferable to stock....and even with the CM7 kangs (though I haven't tried the CM9s yet). I'm not so sure we'll ever get official support at this rate, though I'm not convinced that's a death sentence. Bubby's Cm7 was working nearly flawlessly for me, aside from a scant few mildly irritating bugs....
kthejoker20 said:
Cyanogen sucks now.
They sucked ever after CM6, they just can't get anything out anymore.
They just can get anything developed anymore.
Very disappointing. Thier roms were awesome, but i think he lost his touch.
I honestly can't figure out why they have so much invested, website, hosting and all, and just can't put out a functioning rom anymore.
They are just kanged left and right now to get roms developed, since they never get around to doing anything.
AOKP is the new Cyan. They rock.
Click to expand...
Click to collapse
I saw nightlies left and right on my OG Evo and though the E4GT may not get official CM7 support, We'll surely get offical CM9.
They couldn't get much done for a while because they were using older servers that couldn't keep up. Now they have nightlies going on the Galaxy Nexus, Nexus S, Xoom, Asus Transformer, Asus Transformer Prime, and the HP Touchpad.
I'm sure we'll get nightlies soon enough and you'll be seeing official functioning ROM's everywhere.
We already have functional CM9.
What is AOKP built on anyway?
Ophois said:
http://www.cyanogenmod.com/blog/security-and-you
An interesting change, I'd say...
Click to expand...
Click to collapse
I think they're trying to go mainstream, maybe OEMs will start putting CM on their phones instead of their own skins. It would be a huge selling point.
phatmanxxl said:
maybe OEMs will start putting CM on their phones instead of their own skins. It would be a huge selling point.
Click to expand...
Click to collapse
Problem is the root is still easily accessible. You would see them providing rooting methods for their own software before you saw that. The carriers would also want nothing to do with it. The manufacturer still has the concern of warranty while the carriers have the concern of tethering etc. Carriers likely would never reject an entire manufacturers line, they will always have to cave to some things they do not like.
Though selling unlocked devices with CM much as PC manufacturers will sell hardware with alternative operating systems isn't outrageous. As for the concern of warranty and software caused damage. Routers for example have set a precedent in the support of custom firmware while maintaining warranty. There is plenty of unbricking support in routers. Though providing accessible jtag interfaces in devices that would be sold both retail and unlocked would probably be interesting. Thats just a need in a worst case scenario though not required.
They do seem to be moving in that direction for whatever intent or purpose.

[Q] Why A Nexus? Advantages of an OPEN DEVICE??

Hi guys, I have been on this forums for quite a while even though I don't own a Nexus myself. I have been browsing through the development section every day and looking at all the ROMs etc..
I know that everything is open on the Nexus, all the sources, drivers, etc. I know that the advantages of having a Nexus is stock experience, with faster updates directly from Google. But what is the advantage of having an open phone as a user? I don't find much difference between the ROMs for Galaxy S II and the ROMs for the Galaxy Nexus. In fact the Siyah kernel, i think, has many many more features than the most popular kernel on this forums, the Franco kernel.
I am not trying to spark up anything over here. I just want to know what is the benefit of having such an open phone?
Difference between being in a wheelchair in a jail cell, even a jail cell with a window and open field sunny day with your legs running however fast you can. Its like that.
let it be.
@rbiter said:
Difference between being in a wheelchair in a jail cell, even a jail cell with a window and open field sunny day with your legs running however fast you can. Its like that.
let it be.
Click to expand...
Click to collapse
I would think that, but I can't see that translating to development. I mean, I must be blind to not be able to see the differences, but I really can't. I don't see any major improvements in the ROMs on the Galaxy Nexus
darkgoon3r96 said:
I know that the advantages of having a Nexus is stock experience, with faster updates directly from Google.
Click to expand...
Click to collapse
You answered your own question.
I already had 2 not Nexus Samsung phones and I will never make this mistake again. The lack of updates, the crappy skin that tries to look as the iPhone, etc.
In my experience, the builds from Google are much more stable, fast and reliable. And nothing in TouchWiz add anything that matters to me. To me Android is Nexus, I dont think I will build anything that is not Nexus again (but I really hope that HTC build the next one, I love the build quality of their phones).
martonikaj said:
You answered your own question.
Click to expand...
Click to collapse
Haha, that wasn't my question. I am not asking why the Nexus is a better device. I am asking how does opening up the sources and drivers improve on the development...
darkgoon3r96 said:
I would think that, but I can't see that translating to development. I mean, I must be blind to not be able to see the differences, but I really can't. I don't see any major improvements in the ROMs on the Galaxy Nexus
Click to expand...
Click to collapse
Sorry man, but in my opinion the stock ICS on the GNexus is miles ahead of any build from the SII.
martonikaj said:
You answered your own question.
Click to expand...
Click to collapse
The difference is some stuff on aosp
Roms still don't work on galaxy s2 but everything works on aosp roms on nexus because it's open and drivers and everything is available...
bottom line aokp cm9 etc will give u a better user experience on nexus fewer bugs
Sent from my Galaxy Nexus using Tapatalk 2
darkgoon3r96 said:
Haha, that wasn't my question. I am not asking why the Nexus is a better device. I am asking how does opening up the sources and drivers improve on the development...
Click to expand...
Click to collapse
Because your Galaxy Nexus comes with stock ICS out of the box. Sorry, but a custom ROM will never be as smooth and nice as the native out of the box OS.
juliano_q said:
Sorry man, but in my opinion the stock ICS on the GNexus is miles ahead of any build from the SII.
Click to expand...
Click to collapse
I still don't get why you guys think the Stock is so much better than AOKP? I mean, isn't that very similar to stock?
OK, let me see if I can answer it. I'm not a developer, so take it with a grain of salt.
The phone I had before this was the Samsung Captivate. I bought it August 2010. At the time, it was one of the more advanced phones on the market. However, within about an hour of using it, I realized that the AT&T bloatware was a problem. Though the device had a lot of memory available, the app drawer was harder to navigate because of 15 different AT&T apps on the phone, most of which charged a monthly fee to do what Google's equivalent apps did for free. So, I had to root it.
Things were fine for a couple weeks, but then I noticed that there were several apps that I couldn't download because everyone was on Froyo and I was stuck on Eclair. There was no word when either samsung or AT&T was going to provide me with an update, so I had to take matters into my own hands and get a ROM from someone else. I'm not saying the devs didn't do a good job, but they were hamstrung by both AT&T and Sammy who were not giving them the tools they needed to do the job right the first time.
I should also point out that a lot of these problems were caused by AT&T's insistence that they have their own version of the Galaxy S that was different from everyone else's. Thankfully, all the carriers learned from that mistake.
Over the course of a year and 8 months, I tried at least a dozen different ROMs on my phone to either try to keep up with the changes in the market, or just to keep it from freezing. Even stock Gingerbread had problems, likely because it was rushed out. I finally found a stable build in a ROM that used ICS (ironically, ported from the GNex). So that meant, if not for the great work of Team ICSSGS, my Captivate would NEVER have been a stable phone. All those commercials about being a smartphone beta tester seemed to be designed with the Captivate in mind.
The point of all this: When it came time for me to get a new phone, I was considering waiting for the GSIII, but then Google offered the GNex off contract for $400, a not unreasonable price for the hardware at all, but what I was really paying for was getting off the treadmill. Now granted, at this point I've only had the phone for about a week, but it performs every function I need it to, and AT&T has no say in it. Samsung only had a say in the hardware. And that's how it should be, and honestly why I think Apple had such a marketing edge for such a long time. Apple told AT&T exactly where they can shove their customizations, and now we have Google doing the same, but not publicizing it enough.
TL;DR: Google experience and faster updates. But those are more valuable than you think.
darkgoon3r96 said:
I still don't get why you guys think the Stock is so much better than AOKP? I mean, isn't that very similar to stock?
Click to expand...
Click to collapse
You just answered yourself... great roms/builds like aokp would not be possible without the Android Open Source Project. Even after saying that the quality on aosp devices running aokp like the gnex and ns are miles ahead of say the sensation or something along those lines due to the very face the the nexus phones have open source readily available.
Sent from my Maguro Yakju
The open let's you literally change ans re-code any part of the device you want. A touch wiz phone cannot do this cause the code is closed.
Custom roms on other devices are not the same though you may think they are. Most of the time something doesn't work cause it relies on a closed touch wiz framework function that has to be reverse engineered or hacked, or usually never works at all..
You need the kernel source code to really make any legit custom rom, and often have to wait months foe it to be released.
With an open device, you literally can implement anything your imagination can cone up with. No bugs or work a rounds.
In my opinion, there are two major differences:
1. On a Nexus device, you are guaranteed a large developer community. The SGSII may have a large developer community, but that's because it's pretty much of the most popular phones. If you buy something like the Samsung Galaxy Infuse (which several of my friends have) then you won't have nearly as big a developer community as the one for the Galaxy Nexus.
2. It's much much easier to root/customize/flash a Nexus device than any other device. All you need is "fastboot oem unlock" and the phone opens up for you. No need for bootloader downgrading/rooting exploits/HTCDev/manufacturer restrictions. This phone is designed to be a developer device. Also, when you screw up a Nexus, it is much easier to solve problems. Phone not booting? Use CWM. Recovery borked? Fastboot. Fastboot not working? ODIN flash. Lots of fail-safes.
Thanks a lot guys for taking the time just to help me out
I got my gnex last wednesday. No regrets at all, it's an amazing phone. My next phone will definitely be another nexus.
Advantage of having a Nexus?
It is like Burger King, you can have it your own way.

No Bluetooth Low Energy for the Galaxy Nexus

Those of you have been waiting for the Galaxy Nexus to gain support for Bluetooth Low Energy - to enable syncing with devices like the Fitbit Flex or Polar heart monitor - can stop. While BLE support will arrive in the next drop of Android, it will - according to one of the folks on the Android team - apparently not be making its way to the Nexus. See the comment here:
https://plus.google.com/116110604589325140832/posts/VsF1BcaFY1g
Looks like the best bet, then, is either custom ROMs or upgrading to a Nexus 4 or later.
Great... Another nail in the coffin against the galaxy nexus, time to start looking for a suitable replacement.
Sent from my Galaxy Nexus using xda premium
This question is fairly general as I'm considering the remaining life of my device. Does anyone have an idea, once API level 18 is released, is it possible or probable that we will get BLE ported over in a ROM? Should I hold out hope for my Nexus or move on? BLE is something I've been looking forward to for a while.
Lol, that's just ****ing weak.
fireknuckles said:
This question is fairly general as I'm considering the remaining life of my device. Does anyone have an idea, once API level 18 is released, is it possible or probable that we will get BLE ported over in a ROM? Should I hold out hope for my Nexus or move on? BLE is something I've been looking forward to for a while.
Click to expand...
Click to collapse
I don't think it's that simple, it will require some work to port it over, I remember that a google employee mentioned in the keynote that BLE requires a new stack. Correct me if i'm wrong, i'm kinda sleepy when i watched the keynote..
Yeah, which will come with next Android release. They just don't want to bother with the drivers for GN, which is bull****.
Sent from my Galaxy Nexus using Tapatalk 2
And we're still missing camera and GPS binaries.
Sent from my Nexus
bk201doesntexist said:
And we're still missing camera and GPS binaries.
Sent from my Nexus
Click to expand...
Click to collapse
Missing where?
Sent from my Galaxy Nexus using Tapatalk 2
Nexus Prime's hardware has become old now...dual core TI A9 and the BT3 ,with the TI gone there would be no proper binaries
N4 or Next nexus would be better upgrade option :good: !
madd0g said:
Missing where?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Official AOSP license
https://developers.google.com/android/nexus/drivers
Sent from my Nexus
No one cares, since they get them from the stock build.
So, now that Android 4.3 is out, what are the chances of getting BLE ported from another device with the same BT chip?
CommanderROR said:
So, now that Android 4.3 is out, what are the chances of getting BLE ported from another device with the same BT chip?
Click to expand...
Click to collapse
I hope so. It's disappointing that Google is already starting to abandon what was their flagship phone just a year ago.
madd0g said:
No one cares, since they get them from the stock build.
Click to expand...
Click to collapse
If someone were to track down the people who are providing ROMs with the all binaries included, even the ones that are not licensed to us by Google and manufacturers, there would be no 100% complete ROMs.
CommanderROR said:
So, now that Android 4.3 is out, what are the chances of getting BLE ported from another device with the same BT chip?
Click to expand...
Click to collapse
So no 100% confirmation yet of people who have gotten the update today?
Gbcue said:
So no 100% confirmation yet of people who have gotten the update today?
Click to expand...
Click to collapse
I already got 4.3 on my GNex, I can confirm that nothing changed in the Bluetooth settings screen. But I don't know if you can see BLE support in the interface somewhere or is it only under the hood?
http://www.androidauthority.com/galaxy-nexus-passes-bluetooth-android-4-3-224336/
Ashutos1997 said:
http://www.androidauthority.com/galaxy-nexus-passes-bluetooth-android-4-3-224336/
Click to expand...
Click to collapse
I'm unsure if you're saying it will get it or won't.
They just recertified BT 3.0 for it. If you go to https://www.bluetooth.org/tpg/listings.cfm and top in GT-I9250 in the search box you'll notice that it says it as for 3.0 not 4.0.
If you put in the model LG-E960 (nexus 4) and search you'll notice that it was for 4.0.
so will gnex support BLE ?
It doesn't have it, they would certify for 4.0 if it would. Only way (unofficial at least) would be to work with with similar binaries from a 4.0 certified device, if it's possible.
It sucks ass, but I guess it was more of a business decision then a engineering one. Personally I don't see much point in having a Nexus anyway, so this decision kinda sealed that I'll look around for the next phone.

Categories

Resources