yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] miketoasty:
You are free to use data as you wish, as it is pre defined in your agreement you make with the carrier when you use their network. Verizon has tethering in their contract as a paid service. I understand it may be different where you live but here in the states that's just how it is.

The tethering is usable once you enable a tethering plan to your account so why would they remove it?

Yes there is a free market out there but there are also contracts we sign so we can use these phones, and like I said it may be different around here than it is out there.

Enjoy your phone and we will continue to live in our idiotic bliss.

---------- Post added at 04:09 PM ---------- Previous post was at 04:08 PM ----------

Read above post, and they stripped nothing, just added a message (If you don't pay for the service) that you need to pay for it before you use it.
[Samsung Galaxy Nexus] adrynalyne:
If you don't have the technical knowledge, then don't speak of what you do not know.

They stripped nothing. They have a provisioning apk in place for legit users. Its easily bypassed and we leave it out of aosp.
[Samsung Galaxy Nexus] thereddog:
u mad

......
[Samsung Galaxy Nexus] rubiconjp:
I'd return it asap.. who'd ever want to be the laughing stock of the internet!?
[Samsung Galaxy Nexus] PathologyX:
Dear God! People on the internet will 'lol' and 'rofl' at me?!?!?! I'm returning it ASAP!
[Samsung Galaxy Nexus] miketoasty:
I already did, picked me up a brand new iPhone 4! Now everyone will love me!
[Samsung Galaxy Nexus] mutelight:
This is absolutely, in no way, shape or form limited to this phone, let alone Verizon. ;)

Many handsets and carriers in the US have provisioning functions across numerous Android handsets and iPhones.

This, exactly.
[Samsung Galaxy Nexus] k20igor:
I can't say much about rooting, falshing, hacking, etc. Mine is all stock and locked and i LOVE this phone. But i hear nothing but great things about it if you do end up rooting and flashing roms and all so either way i say KEEP IT!!!! you wont be dissapointed.
[Samsung Galaxy Nexus] knyghtryda:
A few important questions to ask yourself... do you want to pay $300 for a phone or $700? Do you want HSPA+/3g data or LTE data? Does the service in your area suck for either? This will determine if you want a CDMA/LTE gnex or GSM gnex, not whether or not Google has the phone on their officially supported list. CDMA sucks when the lawyers get involved, but where I live Verizon has the best service hands down, so you gotta pick what's important to you.
[Samsung Galaxy Nexus] PathologyX:
When it comes to service, the obvious answer for me is CDMA/LTE/Verizon.

Really it wasn't a matter of GSM GNex vs LTE GNex. It was a LTE GNex or another LTE phone that devs might start paying more attention too over the LTE GNex.
[Samsung Galaxy Nexus] player911:
They already have GSM/LTE kitchens started so before long a dev can make 1 rom for both phones. Ideally I'd like to see a general rom with separate LTE/GSM counterparts... kinda like rom manager flashes gapps after CM, except a 3rd option for model. Streamline it.

But dev support won't go anywhere. As soon as a GSM rom dumps or new AOSP, the Verizon will get it. Plus Google will be pushing updates just as fast as the GSM. Its only the AOSP source stuff that's stopping because it contains non-open source material.

You still won't find that level of support on any other phone. You also probably won't be upgrading past ICS with any other phone, where your getting another good bump with the next Android next year.

LTE EX Galaxy Nexus - CM9 AOKP

Asus Transformer - Revolver
[Samsung Galaxy Nexus] martonikaj:
You honestly think there will be another LTE phone on Verizon that gets more development than a Nexus?

Sure it may not be perfectly supported by Google or whatever, but its the closest damn thing Verizon customers are gonna get to it. Its so easy to unlock/root/etc that you can always count on a vibrant modding community.
[Samsung Galaxy Nexus] knyghtryda:
+1

There will be better phones hardware-wise (I personally think the rezound had far better hardware than a gnex) but software support will always be nexus first then everything else. When the eventual CM10 comes around you'll be sure to have the first builds right behind the next-Gen nexus.
[Samsung Galaxy Nexus] afma_afma:
what is this cm10 ur taking about?

edit..never mind I figured..cyanogen mod 10
[Samsung Galaxy Nexus] Smokeey:
So wait...you say the GSM version will get updates before the LTE...SO THEN WHY ARE WE .0.2 versions AHEAD? Yeah. Shut up. The VZW Galaxy Nexus is the best Android phone out right now. Developer support isn't going anywhere, its a nexus phone and will be fully capable for the next 2 years AT LEAST. Regarding the "bloatware"......really? Two apps, one of which most will use (My Verizon) because it helps you manage your account and check data. Please...GTFO our XDA.
[Samsung Galaxy Nexus] martonikaj:
Lol you realize 4.0.4 isn't even an official OTA, right?

By your logic, the Nexus S is superior to the Galaxy Nexus because it has a newer version.

Settle down, seriously. Why so defensive?
[Samsung Galaxy Nexus] gnarlyc:
If anyone wants to actually read something about this from Google, here you go...

https://groups.google.com/group/android-platform/browse_thread/thread/10c8db7b1c893e1e?pli=1

This is kind of a summary from the end of the first post for those who don't want to read the thread.:

"Now, here's how things are likely to look in the future for those CDMA devices:

- Most likely, the relevant source files will continue being in the Android source tree.

- Quite likely, it will be possible to actually compile that code.

- We plan to continue to distribute factory images for Galaxy Nexus and proprietary binaries for all relevant devices, where we can.

- There won't be any testing done on AOSP builds for those CDMA devices, so they'll probably bit-rot.

- CDMA devices won't be targeted by improvements in the way AOSP builds can be installed or distributed. "

JBQ

So, the reality is somewhere between the two extremes I'm reading from folks. It's not the end of the world, but it's not all roses either. When I read that I see "Most likely, Quite likely, We plan, probably, and won't". Maybe I'm being pessimistic, but I'm rarely like that.
[Samsung Galaxy Nexus] :
You should head over to rootzwiki. The CMDA and GSM forums are completely separated so you dont have to wade through all the GSM bs.
[Samsung Galaxy Nexus] Rem3Dy:
Did lightning strike your tin foil hat?
[Samsung Galaxy Nexus] PathologyX:
This was the kind of answer I was looking for originally lol.
[Samsung Galaxy Nexus] miketoasty:
I think you are being a little pessimistic here. Basically as long as source keeps getting released (Why wouldn't it be?) we can take official source then throw our blobs into it to get it to work with our CDMA Gnexuii. At some point the dev's may have to throw some hackery into the blobs to get them to work correctly but our devices should easily last for the next two years.

There are many legal reasons why Google can't put the blobs in themselves so they are basically saying wait for your carrier to release an OTA or root your phone.
[Samsung Galaxy Nexus] Gahh Its Lee:
Didn't read every page just throwing in my two cents. I love this phone. I love Verizon. In my opinion Verizon is consistently the best carrier this phone is ridiculously fast. You can change everything you could on any other phone if not a bit more. You'll love it once you get into it man
[Samsung Galaxy Nexus] miketoasty:
In the end, this is also how I feel. Verizon is by far the best carrier in my area (Suburb of Pittsburgh), I get 4G almost everywhere I go (Most importantly home and work). The network is super fast and their customer support isn't that bad. Couldn't be happier with my decision even if I have to wait an extra to week to get an update compared to having a GSM phone and having crappy service everywhere and a easily hacked radio.
[Samsung Galaxy Nexus] PathologyX:
I'm already "into it" as far as phone hacking goes. My DX (my last phone) was flashed daily lol (addict). That wasn't an issue. I just haven't been in the GNex scene before. I knew devs were excited for its release, but my upgrade wasn't until August this year (took my dad's....we split the bill...cheaper for us to do it that way even though we dont live together lol), so I didn't look into it much. Circumstances made it to where I had to get a new phone...so I bought this one because it was something I had heard good things about back when it was released. I got it and brought it home and starting reading on things and saw a few comments about the CDMA version and grew concerned. You guys steered me in the right direction though. Upon further research, this phone isn't going anywhere in a long time despite the whole CDMA thing (not a huge deal IMO).

The phone is lightning fast, all of my apps work great with ICS, and I get great service with stock 4.0.2 radios (albeit occasional screeching when video chatting via Skype/ooVoo/Tango)....plus there are already about the same, if not more, ROMs and hacks for the GNex than there were at the end of the DX's life....so that's saying something about how hackable/much dev support there is for it.

I'm not going anywhere. I'm sold. Thanks for the insight all.
[Samsung Galaxy Nexus] :
Lmao. Currently a newer version of Android is available for CDMA and NOT GSM, right? And 2 Verizon apps are bloatware? One of them is to check minutes and they can both be easily disabled. I'm sure experiences differ by region, but where I live VZW is the only network with good service and the GSM networks are ****.
[Samsung Galaxy Nexus] martonikaj:
Not right. There's a leaked build of 4.0.4 for the CDMA version, which happens because there are network employees involved that like to leak things. That doesn't mean the CDMA is on "a newer version of Android".

Until there are

official

4.0.4 OTAs popping up around the country for the CDMA version, it's still on 4.0.2 just like the GSM model. You can go buy a stock CDMA model from Verizon and smash the "check update" button all you want and it'll still be on 4.0.2, that's how you measure what version its on.
[Samsung Galaxy Nexus] lowandbehold:
Can't we all just get along? This is a community! GSM, CDMA..whatever...it is still a Nexus.

Now, with that being said, if I had a Verizon Nexus I would be concerned. I would not be concerned about the Galaxy Nexus. It is still going to get it's updates, and it is still going to be the most developed phone on Verizon, by far with quality devs. What I would be worried about though is the future Nexus devices being available on Verizon. Google might decide it's just not worth the trouble, and if that happens, we all lose. With the ROM's and Kernels so interchangable, us GSM guys will be losing out on alot of great dev's.
[Samsung Galaxy Nexus] TwilightSparkle:
If there was a "**** you" button, you'd deserve it.
[Samsung Galaxy Nexus] Stadsport:
Sure is sensationalist FUD in here.
[Samsung Galaxy Nexus] vdub804:
Never thought I'd see a thread like this, it's hilarious both phones are the same only different radio technologies both will have the last est version of android before any other device (officially) any rom that's built for the gsm version can be ported to the cdma version and vice versa we are all in the same boat only different networks. It's crazy how this thread turned into a my stick is bigger than yours debate when we're all using the same phone :)
[Samsung Galaxy Nexus] roymontante77:
Couldn't agree with you more haha.. I absolutely love everything about this phone if it is the laughing stock of the internet, everyone I know must not ever get on the internet because right now my phone has gotten envy from just about everyone I know!
[Samsung Galaxy Nexus] s2d4:
sometimes ppl forgot that its their phone, who cares what other ppl think as long as YOU like it.
[Android Software/Hacking General [Developers Only]] amraving:
I was wondering, is it possible to set maximum frequencies for specific apps or does the kernel only allow for global settings?

I was thinking this because the video player I use can play video well at 500 ish MHz but I want the browser to have 998 so its fast and responsive.

Any thoughts?

sent from my desire running seb's aio rom
[Off-topic] io53:
I watched red dwarf again and noticed this :D

http://www.youtube.com/watch?v=r46ujrKBUIk&feature=related
[Off-topic] io53:
Every body need good aaandrooids..

http://www.youtube.com/watch?v=WXmKCVRzv-0
[Verizon Droid Incredible 2] HypostaticOnion:
I found this theme for go contacts, and I'm hoping to get a full theme based on this as well.

I'm specifically looking for something that matches how this dialer looks. I'd love to see this sort of theme done.

View attachment 894752
[Verizon Droid Incredible 2] ubuntunerd:
I'm a fan of tron what u on right now(rom)
[Verizon Droid Incredible 2] HypostaticOnion:
I was on mikrunny when I posted. Now I'm on ics, but I'm trying to think of a good ROM to do it on.

And now I'm back on mikrunny. Maybe you could add it to your troj icon theme for MIUI. That one looked good, but it was mostly icons. Maybe find some images similar to that.

Or even virtuous unity or something. Trying to think of something that would be good to add the theme to.
[Verizon Droid Incredible 2] ubuntunerd:
i have some tron images that got that color for sure, i could make an icon pack also of that color if you really want 1 i even have a live tron wallpaper that looks just like that
[Verizon Droid Incredible 2] HypostaticOnion:
I know you have the icon pack, i'm kinda wanting a more complete package.
[Verizon Droid Incredible 2] smadonna1986:
Virtuous rom is great
[Verizon Droid Incredible 2] Un1c0de:
That would be sweet in a miui theme :-)

Nevermind. Jaw saw your post with the miui theme :-) Checking it out.
[Verizon Droid Incredible 2] ubuntunerd:
miui is the easiest to theme in my opinion i think that would be the best rom to do it on
[Verizon Droid Incredible 2] HypostaticOnion:
Well, that could potentially be the thing that brings me back to it for a while.
[Verizon Droid Incredible 2] zaidyou999:
best theme

thanks
[Verizon Droid Incredible 2] knipp21:
I'm finally back on miui btw lol
[Galaxy S II General] dgndg:
I've seen a few questions on the forum asking how to root a 2.3.6 SGS2.

DooMLoRD's Easy Rooting Toolkit was a very easy way to root, without having to flash insecure kernels and all of that, and was great if the goal was just a rooted stock device. It was perfect for me, as all I wanted was AdFree, Titanium and OpenVPN on my device.

Unfortunately, the exploit the Easy Rooting Toolkit used seems to have been fixed in the SGS2 2.3.6 firmware and the toolkit doesn't work any more (see, for example, here).

Before I upgraded from 2.3.4 I prepared myself to mess around with ODIN to get root back after upgrading.

Imagine my delight after upgrading (via OTA), that I still had root without doing anything at all!

So it looks as if upgrading a rooted 2.3.4 stock firmware to 2.3.6 results in a rooted stock 2.3.6 firmware (for I9100XWLA4, at least).

Which means that the easiest way to get to a rooted stock 2.3.6 SGS2 is to root it using DooMLoRD's toolkit before upgrading.

Sorry if this is obvious and, if not, hope someone finds it useful.

Rgds,

dgndg
[Galaxy S II General] kmaximax:
not everyone can update or have the option to update OTA!

whats so hard about using ODIN to update then flash CF-ROOT?! :)
[Galaxy S II General] Mittaa:
Hi

Nice to hear - I'm on 2.3.5 Nordic and expect an 2.3.6 update before ICS arrives :)

But also a bit strange that you keept ROOT!

Other attempts using zergRush Exploit on 2.3.6 have failed as far as I know.

Could it have to do with the fact that you updated through OTA and not KIES?
[Galaxy S II General] Entropy512:
OTAs just replace things that changed - KIES does what is effectively a full Odin flash.
[HTC ChaCha] Dr_Deathscythe:
This worked for me

See Ya
[HTC ChaCha] miguel11691:
What is this for... This aint the full software... Is this the update
[HTC ChaCha] Dr_Deathscythe:
No pal you must complete the register in HTC dev and follow the instructions. I only put the RUU who worked for me. Maybe is the correct for HTC Status
[Epic 4G Apps] Trident:
I used PhoneWeaver on all my WindowsPhone devices and it was awesome. I use it on my EVO4G and it works great. I tried it on my 2nd EPIC and got the same results as the first one- horrible battery life. I went through my extended battery in about half the time.

Does anyone else have this experience? I really like the app on every other device I've tried it on. I know it's not Android because of the EVO. I know it's not the ROM, because I've tried it on stock & various rooted.

Does anyone have any tips that might make it more keep-able?
[Epic 4G Apps] earldom:
You have to make sure you're not using GPS for your locations. It eats up the battery. Use the other option of cell network (can't think of the exact wording).
[Epic 4G Apps] beemerTPPC:
Verify if PhW appears in the battery usage app list. It shouldn't.

Also activate PhoneWeaver log mode, leave it run for a day and take a look to the log to see if tere are any recurring events that shoulden't be.

As Earldom says, using alert location method and having GPS always on will make the OS to use the GPS for the location system. Ensure you have GPS off or change to Intelligent polling or AP+Cell in location method.

Finally, ensure you have the latest 2.2.8 version installed.
[Sony Tablet S] pcoulson:
Hi,

Has anyone noticed that root breaks the automatic popup of the gallery app when putting the tablet into the cradle?
[Sony Tablet S] Vinny1967:
I still get the option of clock or gallery and both work fine.
[Sony Tablet S] pcoulson:
Yep - sorry - sorted it. Had to clear the Gallery cache and re-do the Cradle Settings under Applications. It was no longer firing, but looks fine again now.

Cheers.
[Sony Tablet S] Gasoze:
Mine is rooted and it works just fine
[Sony Tablet S] ps3taker:
Glad it's sorted. Checked my gallery just to be sure - seems ok.
[Sony Tablet S] grcd:
BOUNTY FOR UNLOCKED BOOTLOADER FOR SONY TABLET S

$103 PLEDGED!

Following the successful root of our devices, one would expect that more developer support should come to Sony Tablet S. Yet, having root is but one of the two 'holy grails' which will turn our devices into hot properties.

As such, I suggest we begin a second bounty, this time for the first person to successfully unlock the bootloader and provide a working proof of concept for its implementation*. Given that the ICS update will (likely) remove our root, we will still be back to square one unless someone can couple the first success with a working unlocked bootloader which will finally let us install recovery and hopefully install custom ROMs or customized official ROMs.

I hope we can get as many people aboard as possible, and at least some of the usual suspects from the root equivalent bounty topic.

*The Rules:

'Unlocking the bootloader' refers to: An exploit, method or application/software which unlocks the bootloader and allows us to install custom recoveries, kernels or ROMs.

To earn the bounty, you simply have to find the exploit which will allow the above first. You do

not

have to develop a recovery, or a kernel or a ROM, but you must provide with a working proof of concept, i.e. with a way which allows us to verify that the bootloader has been completely unlocked and that other developers can use this method to install recovery, kernel and ROMs.

Here's hoping there are some who will take this new challenge up with renewed vigour, now that root is here!

The pledgers:

1. grcd: $12

2. condi: $10

4. wintermute000: $10

5. kvssvarma: $10

6. ALF@be: $25

7. eldron: $16 [Pledged via PM]

8. xaviorffviii: $20

NOTE: THIS TOPIC ALSO CONTAINS AN ACTIVE TECHNICAL CONVERSATION REGARDING THE TOPIC. SEE HERE AND FOLLOW ENSUING CONVERSATIONS.
[Sony Tablet S] condi:
10$ from me :)
[Sony Tablet S] unclespoon:
$10 from me too
[Sony Tablet S] djrbliss:
Is there actually any evidence that the bootloader is locked? Keep in mind there's a difference between a locked bootloader and a bootloader that doesn't support flashing by default.

A truly locked bootloader (like HBOOT on HTC devices or Motorola's MBM bootloader) actually verifies a digital signature on the boot or recovery partition before booting it, so it's not possible to run custom ROMs without using workarounds like 2nd init.

On the other hand, some bootloaders don't allow you to *flash* images by default, but if you manage to get root and flash a new recovery or boot image, it will boot without complaint.

Unless someone has a reason to believe otherwise, it might be possible that the Sony Tablet S falls into the second category. Now that root has been achieved, it's possible to flash custom recovery images by writing to a block device using ADB.

It's definitely worth trying this out. Someone who knows what they're doing should create a full backup of the original recovery partition (using "dd" from a root shell) and flash a custom recovery image to the appropriate block device and see what happens when you try to boot into recovery mode. There's a chance it "just works".
[Sony Tablet S] grcd:
You are right about this. If you could provide a little bit more information I would be willing to try it out myself. Sometimes you have to treat everyone as a complete newbie. I have a degree in Computing -- although I have never professed it and I am now in an entirely different academic field (Sociology/Cultural Anthropology), and to be entirely frank, I am adept at following instructions but not trying things on my own which might brick my device ;)
[Sony Tablet S] djrbliss:
Well, the first step is easy: make a backup of the existing recovery partition.

Load up an ADB shell and type "su" to assume root privileges. Next, you can make an exact copy of the recovery image by using dd:

dd if=/dev/block/recovery of=/sdcard/recovery.img

This is assuming you have enough room on your SD card to fit the recovery image. At this point, it would be helpful if you could pull that off the phone ("adb pull /sdcard/recovery.img") and get it in the hands of someone who knows what they're doing.

The next step involves flashing a recovery image to the device. Basically just the reverse of the previous step:

dd if=/sdcard/new_recovery.img of=/dev/block/recovery

Where you've placed a new recovery image on the SD card as "new_recovery.img". Of course, this is the part where someone with experience needs to do some work. I doubt most custom recoveries are going to work right off the shelf. You'll have to get someone who's used to developing custom recoveries to get involved to port it to the Sony Tablet S.