yashsingh1/xdaforums huggingface dataset:
[myTouch 4G General] DJ Scooby Doo:
I just saw this now, Simple Mobile is an MNVO of T-Mobile, so basically where T-Mobile gets service, you'll get service. They work off of T-Mobile's towers. Although, they do have some sort of cap, I switched my parents off of that and put them on Straight Talk. I wish I could pay that $90 for the "truly" unlimited everything plan, lmao.
[Nexus 7 General] arcisbre:
Go to Settings -> Language & input -> Voice Search -> Download offline speech recognition -> All -> Choose the language.

After downloading, go back a page and select Language -> English -> Choose the English dialect/accent you want. And you're ready to go!

Hope it helps anyone wanting to change this.
[Droid 2 General] xXdarkkittyXx:
So I know that the OTA update 2.3.4 (621) made flashing sbfs impossible due to it leading to a bricked phone, but if you use the new root method and successfully root the D2, does it fix this and make it possible to flash sbfs? For those who don't know, this is the new root method.

http://xdaforums.com/showthread.php?t=1773391

I don't think I can post links yet so just copy paste that into your search bar, or a higher ranked user post the link.
[Droid 2 General] supergear:
You can still flash sbfs you just can't downgrade thanks to the new bootloader
[Droid 2 General] sd_shadow:
you are stuck with 621, and can only flash 621 sbf
[Droid 2 General] supergear:
If there is ever another update (highly doubt there ever will be) he/she could sbf that one too
[Droid 2 General] sd_shadow:
i was trying to stick with what's avalible

a new update is about as likely as unlocking bootloader
[Nook Touch General] speedman2202:
hello guys

i think many times why not to change nst screen with lcd touch one and we can have almost a good Ipad ...... is that may get works??? and if it works , what a suitable screens that fit nst , and how about working on install , buy screen ....etc

i just share my thoughts to try use nst as best as we can :P

thx
[Nook Touch General] J_Palito:
Buy a LCD screen equiped tablet instead.
[Nook Touch General] Speedmatze:
IMHO the screen is the best part on the nook. With its extremely low power consumption it's perfect for reading and i would want anything else for a reader (exept maybe a next generation color-e-ink screen).

There are affordable multimedia tablets with Android out there for those interested in photos, videos and games. But because of the screen their battery live sucks!
[Nook Touch General] bobstro:
Here are the NOOK Simple Touch strong points:

The daylight readable screen. Most color devices, at least the affordable ones, are nearly unusable in direct sunlight, and have a LOT of glare outdoors.

It's feather light, and completely usable for extended periods with one hand. The NST weights less than 1/2 the NOOK Color.

It fits in a pocket. You might fit a NC/NT or an iPad in your pocket, but you'll get some stares.

It has impressive battery life. Color devices suck the battery down quickly, even on devices with much larger (4,000 mAH) batteries than the NST (1,530 mAH). If a NOOK Color/Tablet is good for about 8 hours, a NST would be good for less than 1/3 of that. Not very impressive at all.

If you wanted an iPad, this is probably not the device for you. If you want a cheap color device, there are dozens of cheap Chinese tablets that work well enough. Some are actually as cheap as, if not cheaper than a new NST. If you want any or all of these features, there's nothing like the NST.

The NST is never going to be an iPad, nor does it need to be. It's not the device for hipsters at the coffee shop fighting over outlets. It's the device for people that want outstanding readability and impressive battery life in a lightweight, pocketable device.
[Nook Touch General] speedman2202:
the main objective from my thread is try use all device abilities like when we do root for it we can access to many things we cant do if we use it's current OS , that all i talk about ..... but also in case any nst screen dead ... what the other solution for it .... so i suggest this idea at this thread

and for ur info i am with u in all what u say and i am not against or disagree ... just want to improve/edit nst properties to become better

thx for sharing this info :)
[Nook Touch General] bobstro:
I am NOT a big-time Android developer. I just hack on my devices a bit. Forgive me if I get any of this wrong, My understanding is that the problem with doing wonderful things like porting CyanogenMod or other newer firmware to our wonderful NSTs is that the drivers for the screen hardware is not available. The basic Android OS source is available, but not the essential hardware drivers that would allow any port of a newer or different Android version to actually do anything. This is why, I believe, we have no great options like booting something different from uSD, or upgrading past Android 2.1 Eclair on these devices.

Therefore, I believe we're stuck with the Android 2.1 OS that B&N provides, and anything done is more-or-less just a hack of that. We can still do a lot, but we can't do everything.

I'd love to be wrong about this.
[Galaxy S II Themes and Apps] burninghouse:
i have seen a app called as ULTIMATE FAVS PRO on market....is there any other app similar to this app???
[Galaxy S II Themes and Apps] bobdoblo:
Try searching on google or 4shared!
[EVO 4G General] SLB9884:
So life shows up & I can't keep up with sprint's bill. I live in broward & miami dade county in south florida where our coverage is great.

However my bf is saying it will be difficult because of some eisn numbers? I dont kown what that is.. Is he right? Is it even worth it? Or should I sell it & start over?

My question is, I currently run Htc.evo 4g on sprint, will I still be able to use the same roms? Thanks you helping the first lady out! :o:p:p:D:D:D:D
[EVO 4G General] SLB9884:
Hmmmm mmmmm no answer on a saturday night? Hmmmm
[EVO 4G General] whoshotjr2006:
you could flash to say boost/cricket/elsewhere,

but

nobody here can help you do it. its against xda rules to talk about flashing a phone to another carrier. while technically "cloning" a phone for personal, and personal only use isnt illegal, its a huge legal grey area that is best left untouched here.

here is a guide provided by a brave soul, http://xdaforums.com/showthread.php?t=1182260 (not sure how the mods havnt caught it lol)

remember, any sort of flashing most definitely voids your warranty and can brick your phone. i would look through that thread and see if its something you could stomach, and if it isnt, just sell your phone and look for a cheaper carrier.

im on boost with my evo, but i cannot discuss how i accomplished it. if you check craigslist, usually there is a guy somewhere that can flash your phone for cheap. i use the same roms that someone on sprint would use, im actually running jmz's cm9 as a daily driver.

if your evo is in good condition, consider selling it on craigslist. in my area they go for 150$ used in good shape, and that could give you half the money to buy an evo design 4g on virgin, or an "upgraded" boost branded evo. boost unlimited (if available in your area) is 55$ a month with shrinkage every 6 months. i think virgin is somewhere in the area of 35$ a month for like 300 minutes, unlimited text and unlimited data.

sorry for the wall of text, hope that helps.
[EVO 4G General] SLB9884:
Thanks hun. And the whole time I'm typing I kept saying this is wrong...lol well then for me to stay on the safe side .... Let's just say I'm peaking around... Lol
[Samsung Galaxy Nexus] aooga:
Just wanted to share this with you guys...was on a irc and someone posted this screenshot...hope this is real. This is the vzw nexus with 4.1.2? Really weird but has a new build number too. Hopefully this is coming out soon...Verizon has put this phone to shame. (i have a custom rom, so i really dont care :) )
[Samsung Galaxy Nexus] aooga:
Another thing...the guy said he got this update from verizons servers...I have no clue how or if that was a lie or not.
[Samsung Galaxy Nexus] I Am Marino:
Would be interesting but if there was a 4.0.2 update, the GSM version would definitely see it first.
[Samsung Galaxy Nexus] Smokeey:
Does it matter?
[Samsung Galaxy Nexus] withbloodskies:
Looks legit?

Wonder what is going on behind the big red curtains.. :sly:
[Samsung Galaxy Nexus] Jubomime:
Radio is the same. Just thought I'd point that out.
[Samsung Galaxy Nexus] withbloodskies:
It wouldn't change though would it? Sorry I'm not this advanced in the phone world yet, so im not sure if they would update the radio or not.
[Samsung Galaxy Nexus] I Am Marino:
Radio wouldn't have to change at all, but there's been off and on rumors, or confirmed? new radios with the JB VZW update.

So if the screenshot is real, maybe he's testing the update, sans radio, therefore incomplete?
[Samsung Galaxy Nexus] wuby:
Its possible to change build number.

/potato
[Samsung Galaxy Nexus] Zeinzu:
As Toro and Toroplus are not completely AOSP I'm sure there would be some carrier branding of the build ID to match the baseband version like with Toroplus. Also, even if the radios haven't changed they usually update the radios and build number to match. I can go edit my build.prop to have some random build name and version 5.0, 6.0, 100.10.1, or whatever I want it to say.

Sent from my Stock AOSP Android 4.1.1 Galaxy Nexus
[Samsung Galaxy Nexus] Winesnob:
Probably a fake. The fact that toro has been moved into AOSP and the latest binaries are JRO03H, and the latest branch version is JRO03L, these build numbers should remain the same. Also, the build JRO93 is really not possible - there are not 93 days in quarter 3 of 2012 (and we're currently on day 57 of the quarter). Found a clear explanation of the build number here http://xdaforums.com/showthread.php?t=1655863

---------- Post added at 07:24 AM ---------- Previous post was at 06:35 AM ----------

Does this guy have a URL to back this up?
[Samsung Galaxy Nexus] Marcismo55:
Delete
[Samsung Galaxy Nexus] aooga:
URL as in link to the zip file or source code...both are no...that's why I said this might not be real. You guys think that guy was trolling? I don't know much about build numbers so maybe your right.
[Samsung Galaxy Nexus] Winesnob:
URL for the zip file (actual OTA package). However the kernel version looks legit, given the build date and signature keys. Recall that the 4.0.4 update had a kernel dated 2 weeks after the GSM version rolled. This guy may have a half truth, and possibly more info than we know.
[Samsung Galaxy Nexus] oldblue910:
Toro is fully supported in AOSP as of Jelly Bean. Licensing has been cleared up. Toroplus is not, and never will be, supported in AOSP.

---------- Post added at 01:49 PM ---------- Previous post was at 01:45 PM ----------

This is BS by the way. JRO93 is not possible. That day would be represented as JRP03. Nothing to see here, folks. Move along.
[Samsung Galaxy Nexus] I Am Marino:
What does keep Toroplus from being supported in AOSP, just curious, especially since the VZW version is supported.
[Samsung Galaxy Nexus] tgyberg:
I'm guessing it's this? Maybe he did it to impress the chicks?! :p
[Samsung Galaxy Nexus] Andro X:
I think Sprint has to provide drivers.
[Samsung Galaxy Nexus] oldblue910:
The fact that Toro gets updates from Google and Toroplus doesn't. Toroplus runs the mysidspr firmware, which is similar to all the GSM yakjuxx firmware. Updates come from Samsung, not Google. JBQ has stated that the Sprint Galaxy Nexus falls into that class of GN device and thus, it is not on Google's radar, thus no AOSP support. When JBQ weighs in on a topic, you can pretty much take it as gospel.

Sprint and Samsung could provide all the drivers in the world, but it does no good since there is no kernel source in AOSP. Developers can build ROMs for Toroplus fairly easily using the Toro (Verizon) AOSP kernel source, however, because the two devices are so similar.
[Samsung Galaxy Nexus] efrant:
When it comes to AOSP, yes. However, when it comes to other things, he has been known to make comments that lead to confusion. For example, he has made some comments in the past which seem to suggest that there may be hardware differences in devices shipped with yakju vs devices shipped with yakjuXX, which we know to be incorrect from empirical evidence.
[Samsung Galaxy Nexus] oldblue910:
Yes, I was strictly speaking about AOSP.
[Samsung Galaxy Nexus] Dragn4rce:
Verizon's Galaxy Nexus saw 4.0.2 first. So your wrong about that being a fact.

--------------------------------------------------

If I have helped you.... hit that sexy thanks button. ^_^
[Samsung Galaxy Nexus] aooga:
OK guys...I'll get this closed by a mod...thanks for the build date info...guess I can now tell if its fake or not! Verizon still being stupid...
[Samsung Galaxy Nexus] I Am Marino:
Oh, well, damn lol.
[Samsung Galaxy Nexus] bulvine420:
I'm on jb from day one with my gnex I just want new radios. Verizon has not dropped the ball on this phone name another phone with an unlocked boot loader and vanilla android at launch.
[Samsung Galaxy Nexus] DirgeExtinction:
Current? Lol,none. In Verizon's android history? Droid. :p

Btw, I think you mean "unlockable" not "unlocked". :)
[Samsung Galaxy Nexus] :
I think this is fake because the GSM nexus will probably get 4.1.2
[Samsung Galaxy Nexus] Winesnob:
Good reasoning. Good luck with that.
[Samsung Galaxy Nexus] jesusice:
What do you know that we don't know?

How do you know Toroplus will "never" be supported in AOSP? If the NS4G can be then it is possible. As far as the kernel, isn't it all the tuna kernel? GSM or CDMA? If not then wouldn't Google be required by GPL to release the Toroplus source?
[Samsung Galaxy Nexus] oldblue910:
Of course it's *possible*. It's also *possible* that the sun won't rise tomorrow. These are the facts:

The NS4G is supported in AOSP because it receives updates from Google (albeit after approval from Sprint). Google has absolutely nothing to do with the Sprint version of the Galaxy Nexus. Updates come from Samsung after approval from Sprint. Samsung compiles their own kernel for it. If you notice, the build signature on the kernel for toroplus is se.infra@SEI-29 and the build date is specified in KST (Korean Standard Time). Those are dead giveaways that it uses a Samsung kernel and not one provided by Google.

In AOSP, Google only supports devices that contain firmware that it provides OTAs for. Google provides updates for the NS4G, they do not provide updates for Toroplus. Hence until the day that Google would take over OTAs for Toroplus, you will never see Toroplus support in AOSP. I realize that this may not be what a lot of Toroplus owners on XDA want to hear, but regardless, facts are facts.

Toro and Maguro (and according to Google, only Maguro devices sold with a yakju or takju firmware) are supported in AOSP. See: http://source.android.com/source/building-devices.html, fourth paragraph.
[Samsung Galaxy Nexus] jesusice:
While your facts about the current state of affairs may be correct (or not) you cannot say that something that hasn't happened yet is a fact. The NS4G was initially not supported in AOSP and JBQ made the exact same post regarding its status and that there were no plans to support it. Now it's supported.

EDIT: Google does not have to provide the OTAs for it to be in AOSP. Xperia?
[Samsung Galaxy Nexus] efrant:
The actual quote from the site (with some parts snipped out) is:

Now, despite it being on Google's developer website, we obviously know that the part in bold is certainly not a fact, and just outright incorrect. I can build a ROM from source for my originally-sold-with-yakjuux maguro device just fine, with no difference than a device sold originally with yakju. This is what I was trying to get across: a lot of information that is posted (on Google's dev page and elsewhere) that is peripherally related to AOSP (like most thing relating to non-yakju/non-takju builds, and prob mysidpr builds) is just not true.
[Samsung Galaxy Nexus] oldblue910:
The NS4G has ALWAYS had kernel source code available in AOSP, even when it wasn't supported. You have always been able to build AOSP for the NS4G, you just couldn't build it with a working radio due to the issues of licensing CDMA blobs. That's why it wasn't supported. Same story goes for Toro, and for the exact same reasons. You could always build for Toro, even when it wasn't officially supported. You can even build for the Verizon Xoom (stingray) even though it isn't officially supported (same CDMA binary licensing problems).

Now that the licensing has been resolved for the NS4G and Toro devices, they devices now have official support.

There has yet to be a case where a device that had no kernel source in AOSP upon original release (in this case Toroplus) was suddenly added to AOSP at some point down the line. There's absolutely no reason to believe that Toroplus will be the first such device. Sure, I grant you that anything is possible, but it's certainly not likely.

Interesting, that's a pretty recent development. Missed that one. That's really interesting news. That will be the first time a non-GED has been added to AOSP...That's actually pretty cool IMO. Thing is though, it remains to be seen if a stable AOSP will be delivered on that hardware. It also appears that this will be a community-created project and won't have any code support from Google's development team like the GEDs do, though Sony has said they'll contribute "what source code we can". Take that at face value. I'll be following this with interest. Thanks for bringing that up!

You're absolutely right about the Maguro stuff. That's absurd and any developer knows that. I think they say that probably so they don't step on Samsung's toes, or so they don't get bombarded with questions about why there are no factory images for yakjuxx. But yes, your point is well taken. I also stated earlier that it's very easy to build ROMs that work on Toroplus because the Toro kernel works fine since the devices are so similar.
[Samsung Galaxy Nexus] efrant:
I think you're right: that is probably the case.
[Samsung Galaxy Nexus] Dragn4rce:
Wanna bet on that???

Verizon got 4.0.2 first. So Verizon will most likely get 4.1.2

--------------------------------------------------

If I have helped you.... hit that sexy thanks button. ^_^
[General Topics] _Variable:
Hello Everybody

So now....

Who in here's CURRENT PHONE has the lowest internal storage ever?

Lets start, My internal storage is 190MB
[General Topics] gagdude:
OptimusLove, I love how you always have worst phone contests.:p

Mytouch Q is screwed up so I've rolled back to my flipside which has 12mb of internal storage after I update all system apps. About 70 mb if I uninstall updates and clear cache. It actually has 512 mb but its partitioned so stupidly (thanks MOTO). On CM 7 it actually ends up with 110 mb and I can use link2sd, but you get the idea...

As soon as I fix my mytouch q ill be up at about 1GB of storage, total 2GB but partitioned so user data is approx. 1GB. Exact is 950mb
[General Topics] matte27:
in vodafone ideos (u8150) the internal memory is 256mb but the free (for porting of cm10) with facebook app and whatsapp is 56mb

with link2sd it's possibile move the app dawlink on the sd but not of the system app. with this procedure the free memory is 60mb
[Samsung Galaxy Nexus] dman3285:
Need a couple testers for AoCP CP-3 JB as we don't have this device, but we support many, and would love to add this device to our support. Thank you...

here are the test builds.. toro and toroplus coming later today...

Maguro: AoCP-Maguro-CP-3-Beta

Toro: AoCP-Toro-CP-3-Beta

Please leave feedback!
[Samsung Galaxy Nexus] pottyvick:
I could probably help
[Samsung Galaxy Nexus] Bfitz26:
+1 toro+ sprint

Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
[Samsung Galaxy Nexus] dman3285:
Uploading to server now.. will pm you guys the link.. thanks :)
[Samsung Galaxy Nexus] raymond4:
If you need toro plus user I'm available
[Samsung Galaxy Nexus] crixley:
any features that set it apart or just another aosp rom
[Samsung Galaxy Nexus] DarkJatrix:
I'll gladly test it
[Samsung Galaxy Nexus] dman3285:
You'll have to flash and find out...:D
[Samsung Galaxy Nexus] munchy_cool:
maguro link please

---------- Post added at 11:41 AM ---------- Previous post was at 11:39 AM ----------

PM sent for maguro link ..

Thanks
[Samsung Galaxy Nexus] Sleek69:
You're gonna need a lot to take me away from the 8/24 toro AOKP nightly. Impress me. :)
[Samsung Galaxy Nexus] DarkJatrix:
Can I have a link to test it
[Samsung Galaxy Nexus] dman3285:
1: this isn't a competition

2: the collective strive for perfection, we don't claim to be better or worse than anyone else. Just different and original.

3: we only produce quality work.

If you want to try, you can if you like it that's cool. If not, stay with aokp. Its also a great ROM.:thumbup:
[Samsung Galaxy Nexus] Alex1123:
im in ill test a toroplus build and report bugs i find
[Samsung Galaxy Nexus] iSaint:
great attitude I'm willing to help anyway I can :)
[Samsung Galaxy Nexus] pottyvick:
Been running it for about an hour... Here is what i noticed.

1. Great boot Animation

2. No Gapps was included so i Flash 7/26

3. OTA FC's

4. Sound Seems really loud, but could just be me.

5. Torch toggle doesnt work (also missing some toggles like tethering)

6. Love the 4g icon

7. It comes with Faux kernel (have not flashed any other kernel, yet)

Will post more as i install more apps... Just wanted to give a quick insight.

8. Seems to be very AOKP-ish. As in its missing some things from cm10 (Show widget before pattern/pin unlock, tethering toggle, etc)

9. Can't edit launcher settings
[Samsung Galaxy Nexus] dman3285:
Its not aokp... anyway... look in ROM.zip and see if AoCP.apk is in there.. that would be the only reason OTA would FC
[Samsung Galaxy Nexus] dman3285:
Its based of aosp with some aokp-like features and cm hardware
[Samsung Galaxy Nexus] jomama123:
ill be happy to test this for you for CDMA
[Samsung Galaxy Nexus] pottyvick:
Didnt mean to imply it was aokp. I just meant it has some features of aokp. But to be fair i havent used an aokp rom on the galaxy nexus. Overall the rom seems fast and stable...
[Samsung Galaxy Nexus] qwer23:
I'm very willing to test the maguro ROM if you still need testers. It's always great to see new teams with new approaches working on the GNex :)
[Samsung Galaxy Nexus] crixley:
thanks given for that amazing gif
[Samsung Galaxy Nexus] kyokeun1234:
Sounds interesting... Any features that sets AOCP apart from other ROMs? I would love to try it :)
[Samsung Galaxy Nexus] DarkJatrix:
Still wanting to try it. :)
[Samsung Galaxy Nexus] qwer23:
Is this project already dead or do you only have sufficient testers? Would be nice if you could keep us updated about the progress being made.
[Samsung Galaxy Nexus] nibrwr:
I'd like to give it a shot
[Samsung Galaxy Nexus] dman3285:
Will be releasing maguro and toro builds today.. pretty sure the few bugs my testers reported are fixed. And working on adding toroplus to our device tree...:)
[Samsung Galaxy Nexus] justin94:
I'll test for toro
[Samsung Galaxy Nexus] Geo411m:
I'd be interested in testing as well. I have the Maguro variant Galaxy Nexus.
[Samsung Galaxy Nexus] dman3285:
Maguro test build in OP. Please leave feedback. Building toro and toroplus now. Will post those links in OP later today as its my Birthday today. Kinda busy..:)
[Samsung Galaxy Nexus] Geo411m:
Thanks, I give it a whirl when I get home later.
[Samsung Galaxy Nexus] robm1911:
Happy birthday bro!!! :thumbup:

Just happened to find this trollin around today.
[Samsung Galaxy Nexus] dman3285:
Toro Build up in OP for testing. And as always, feedback is much appreciated!
[Samsung Galaxy Nexus] dman3285:
Bump..:)
[Samsung Galaxy Nexus] strumcat:
Happy birthday, man, and thank you for the new ROM. :)
[Samsung Galaxy Nexus] nibrwr:
I'll test the Toro+ build as soon as it's ready
[Samsung Galaxy Nexus] PieR:
Github link?

Sent with a pigeon