yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] filipeangelo:
Hey guys I got a I727 but I live in Brazil.

I am having a lot of issues with the connectivity here.

I tried a lot of combos ( roms / kernels / radios / SIM cards) and it still acting randomly. Sometimes it works for days and it makes me believe that I got it fixed, sometimes for hours on even less than that. I've trying almost everything.

I know we can use radios from t989 and blaze's and note but all I got here in the forum was from Canadian or American devices.

So my next attempt is to try to port a radio optimized for my country from a device that is similar to the i727.

Does anyone have an idea of how to port radios? I want to use one optimized to use my country's frequencies.

Thanks in advance guys.

And please take easy on me, I m just a newbie
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mahanddeem:
No one ever tweaked radio to date but Sammy!!! sad but true lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] filipeangelo:
Sorry, but whos Sammy, and also if none tweaked a radio how do we are able to use blazers and t989 and notes? PS: ( Iknow t989 are twin of ours i727, but i believe the modem hardware is a bit different since they dont have LTE) .
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mahanddeem:
Sammy = Samsung.... Its a common nickname

Some SR users USE blaze or T989 radios as is (so they can use their phones on T mobile) ... Those are never tweaked radios and nobody can
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tjsooley:
I use bell I757m skyrocket HD
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] filipeangelo:
How did you know that this modem was compatible with your device? Just try and error?

Is it possible to brick my device if I give a try in other devices modems?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mahanddeem:
Never mess up with things like radio...you might easily end up bricking your phone or messing the IMEI number which is at least a pain in the ass to fix...you can just use (flash) things that are commonly known to work with your skyrocket (learn here)..And talking about t989 radio in a skyrocket , never think it works right..expect ton of problems in connectivity.. But at least you can run t mobile on SR (even though very buggy) !
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tjsooley:
Looked up the radio chipset and found it to be the same
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] filipeangelo:
The chipset isn't the mainboard "brain"? If I do an analogy with PC, main boards controls everything and a modem is just a PCI card controlled by the motherboard. If so, that does not mean that my radio is actually the same but that the brain is. Maybe the way that the modem communicate with the motherboard is standard?

If so I will look up to some Sam modem for a phone from here that got the Qualcomm MSM8260 Snapdragon chipset, and then I will try to flash it.

Im aware that Sony got some models here, but I not as much crazy to flash their modems
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tjsooley:
The modem/radio chipset not soc chipset
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] filipeangelo:
Where do I find this info?For the i727 and other devices.

Thx
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] filipeangelo:
Im aware of the risks of bricking it. If it bricks it doesnt matter to me, thats already a useless device, since I cant receive calls or send message properly and Im not a fan of cell games.

I have flashed radios/roms/kernels/boots thousand of times for the SR and many other devices.

About the Q&A dont worry i wont post nothing like that.

I am just looking for info from ppl that had the same idea that i did ( flash other devices radios) to minimize my bricking risk. Again I dont care abou brick it!!!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tjsooley:
You did nothing wrong. The other guy was just rude, and I have already reported him for the rude and hurtful post.

---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------

Alot of searching on google and this forum. I would not recommend anyone to try what i did. I also have ~15 years experience as a IT Professional with computers, linux, Security & Mobile devices. It was also in part a educated guess. The imei issues the other guy was talking about can happen if your not carefull and I also had to see if the cwm files had ril or not (They dont). Others are testing this modem/radio so Just wate.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] filipeangelo:
Thx for your kind answer man. I guess i got no lucky to find technical info regard the modems chipset here.

Ill have to dig deeper on google.

Thx anyway
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] plwalsh88:
You do realize that every single thing done on this entire website incurs a risk of bricking, right? It's his own responsibility to know that, not your responsibility to shove it up his butt. He's trying to figure something out to make his device better for him, which it sounds like he knows the risks of, and which is also the whole point of this website. If you have no useful advice to offer, don't talk.
[Galaxy S II Q&A, Help & Troubleshooting] eddy4823:
I slept last night with 40 % battery and woke up to see 0 %. I was shocked. Please help. Is there something wrong with battery or some app is the reason of the problem ? Any help appreciated.
[Galaxy S II Q&A, Help & Troubleshooting] saywhatt:
Did you charge your phone?

Let it charge up to 100%, as charging to full battery will "reset" it (somehow), i find it hard to explain

Anyway, it is not a serious matter:)
[Galaxy S II Q&A, Help & Troubleshooting] eddy4823:
you sure that it's not a serious matter ? coz I am worried.
[Galaxy S II Q&A, Help & Troubleshooting] stormtroopercs:
Its fine :) its the fuel gauge acting up.. it won't affect the phone in any way :)
[Galaxy S II Q&A, Help & Troubleshooting] eddy4823:
but the fuel gauge isn't wrong. my phone had 0 % battery when I woke up. I charged it to 40 % before sleeping.
[Verizon Samsung Galaxy S III] jtadak:
I had root custom cwm recovery had JB ROM installed and flashed solid ice 2.0 and booted up. Once in tried installing ROM toolbox and couldn't get root access. I still have custom recovery and super user but I have no root access. I did searches and followed all instructions but couldn't find anything on my current situation. I've never flashed a ROM and lost root. I'm on sprint but have my girlfriends s3 rooted on Verizon. Any help would be greatly appreciated.
[Verizon Samsung Galaxy S III] tu3218:
When I lost root on my galaxy nexus, I just restored a nandroid backup and I was back in business. That should work assuming you have a previous backup.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Try opening SuperUser and updating your binaries.
[Verizon Samsung Galaxy S III] jtadak:
Thanks but I have no option in super user to update binary.
[Verizon Samsung Galaxy S III] jtadak:
I did not nandroid.
[Verizon Samsung Galaxy S III] kintwofan:
In super user store to the left. You should see some green and possibly Red writing. Touch there and you now have the iron to update binaries.

Sent from my white sgs3 running Eclipse 2.1
[Verizon Samsung Galaxy S III] droidstyle:
yes you do...open super user, slide your screen to the left, under the info tab look down and tap update binary...so easy a

caveman can do it!
[Verizon Samsung Galaxy S III] jtadak:
Haha, not on this version :( Just says it's out of date. I think there's some kind of a flashable zip to update right now.
[Verizon Samsung Galaxy S III] kintwofan:
Forgot I had this

http://db.tt/ff2iOUgx

Sent from my white sgs3 running Eclipse 2.1
[Verizon Samsung Galaxy S III] jtadak:
She had to leave and took her phone! I'll try as soon as I see her again. Thanks bud.
[Verizon Samsung Galaxy S III] jtadak:
It worked. GTG thanks again guys.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Just for clarity for future users who stumble on this thread, which method worked: updating your binaries or installing whatever is in the dropbox link?
[Verizon Samsung Galaxy S III] jtadak:
Yes it was the flashable zip that kintwofan was so cool as to post. That's what enabled me to update binaries on the version I'm on. Great idea, that's why I wanted reply with the success but I should have clarified :D
[Verizon Samsung Galaxy S III] SlimSnoopOS:
No, thank you. This may help someone in the future.
[T-Mobile Samsung Galaxy S II SGH-T989] klau1:
I'm looking for accessories such as extended battery and battery cover and case for the Koodo Samsung Galaxy SII T989D.

However all accessories available online are listed for T989 instead of the T989D.

GSMARENA reports that the dimensions are different.

http://www.gsmarena.com/compare.php3?idPhone1=4468&idPhone2=4129

In fact, according to gsmarena, all the SII variants have different sizes.

Has anyone found any accessories such as battery and battery covers, and case that work for the other S2s that also work for the T989D?

Some say the phones are actually identical and that the accessories are interchangeable.

If so, which ones?
[T-Mobile Samsung Galaxy S II SGH-T989] jainanshal:
Hey sadly there wasn't any reply... I am in the same boat, was looking for a cover for T989D but couldn't find any. Did you try any of the accessories of T989 on this one?
[T-Mobile Samsung Galaxy S II SGH-T989] klau1:
This extended battery w/ battery cover for the T989D works

http://www.batterybuyer.com/battery-galaxy-hercules-sght989-galaxy-extended-with-back-cover-p-7290.html

But I'm still looking for a TPU case that fits on top of the battery cover that comes with the product above.

Be aware, the following does not fit:

www.ebay.ca/itm/180991057271?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
[Galaxy Note II Q&A, Help & Troubleshooting] sayajoris:
The screen on my G Note 2 N7100 dims whenever I open the stock email app. Initially, when I set up the very first email account the brightness was normal but after it finishes and goes to Inbox it went darker. I've tried tweaking the display setting but have not been successful and it wouldn't be productive to manually toggle the brightness whenever I am using the email app. When I leave the email app on to home screen or any other app the display brightness returned to normal.

Is anyone experiencing similar issues? Any thoughts to fix this?
[Galaxy Note II Q&A, Help & Troubleshooting] D3_:
Is it the "auto adjust screen tone" setting?
[Galaxy Note II Q&A, Help & Troubleshooting] harshull:
i am facing the same issue. tried lot of things but no success....seems this is the way this app looks...disappointment
[Galaxy Note II Q&A, Help & Troubleshooting] amf:
Try disabling "Power Saving" mode.
[Galaxy Note II Q&A, Help & Troubleshooting] sayajoris:
Power Saving Mode

Hey @amf, you're right...sort of. It's the Power Saving mode that's messing with the screen dim but as I pointed out this issue only occur with the stock email app. Every other apps I tried were fine with Power Saving mode on. With that said, I found that you don't have to completely turn off Power Saving, just uncheck Background Color and leave the rest checked. This is strange because I thought that Background Color is supposed to dim for bright background to reduce power consumption but the email app's background is black.

Anyway, thanks everyone for replying! :good:
[Galaxy Note II Q&A, Help & Troubleshooting] manjeev:
Hi,

The darker the background, the less battery it consumes. It seems to make sense when you turn on Power save mode.

Cheers!!
[Galaxy S III Q&A, Help & Troubleshooting] nvleafs:
Is there any way I can get this feature on my Galaxy Nexus? I tried looking through the apks in system.img but had no luck in finding it (if it even is there).
[Galaxy S III Q&A, Help & Troubleshooting] themate1987:
Wrong forum. Ask in galaxy nexus Q&A
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] handman29:
I recently changed roms from aokp to cm10 while changing roms to cm10 I lost all signal no connection..I restored my nandroid backup...no luck...flash stock rom via oden...no wcdma only gsm with edge connection...any ideas what happend ? Help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
Have you by chance checked ro see if your imei is still intact.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] handman29:
I didnt check my imei...I should of...I just reset flash counter and stocked it. Got a replacement thru tmo..how would you fix an iemi issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
peoplearmy has a whole thread stickied in the dev section with tools to restore corrupted imei.
[Verizon Samsung Galaxy S III] ergon:
Got another S3 on the way. What's the latest and easiest method to get this done?
[Verizon Samsung Galaxy S III] Nopi45:
Download the EZ Unlock app on the market.
[Verizon Samsung Galaxy S III] droidstyle:
the guide linked in my sig ;)
[Verizon Samsung Galaxy S III] thirsty1258:
Thx need this also
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
so this has been a terrible issue with samsung since the galaxy s 1 days... im sick and tired of slow updates.. whats your thoughts on this ? will it change your mind on what phone to get next?

http://www.androidauthority.com/u-s-galaxy-s3-jelly-bean-update-released-coming-months-123557/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jbizz:
IMO, It really doesn't matter! I have used JB and ICS on my phone, and other than Google Now, I don't see the need to update to JB.

I look at it like this... the standard consumer is not rooted. The OEM and carrier have to smooth out bugs, and make the transition from ICS -> JB a seemless integration. This makes for a better customer experience.

Thats the business man... why release a sub par product and have thousands of support tickets for small minor issues.

From your sig, you're running JB already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bigjim1488:
Pretty depressing if you ask me. God if the new nexus phone wasn't being made by LG I'd probably be all over that thing at this point.

It will have 4.2 before we even get 4.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fortesquieu:
Telus' S3 will get JB before the end of November, so I'm thinking we should be very close by.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cmoore0965:
Full application of project butter in an official release of jb will be worth it. Only reason my nexus is still stock is that the only rom on the s3 that comes close to matching its fluidity, for me at least, is tasks aokp. It's night, and day. Slow rollouts of software are just one of those burdens of this era in development. Fortunately, the software is beginning to be more, and more worth it. Someday you'll lecture your grandkids on how we didn't have all this fancy "cognitive request firmware updates, and 5tb/second data speeds" lol

Pink pony Gs2 i777

Pure Google Gnex i9250

Pink stallion Gs3 i747

Stock tweaked Asus tf201
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HRodMusic:
i get what you mean man, but its seriously been 5 months, dont you think we could of had an updated by then? how long does it really take to release an update..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jbizz:
*shrugs* there was an update from 4.0.2 to 4.0.4

;)

I know what you're saying tho... I always look at devs like the CM team who have already put out updates way before the OEM and think... how come a billion dollar company is so slow?

I wish carriers would allow users to do soak tests and **** before release to send bug reports and stuff.

---------- Post added at 03:12 AM ---------- Previous post was at 03:11 AM ----------

Stupid app take out my cuss word! Hah!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] megagodx:
By the time we even get Android 4.1, Android 4.2 will already be out in the market.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
First, 4.2 will not be key lime pie.

Second, its not Samsungs fault, its the carriers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Getz2oo3:
And being the carriers fault - you have to wonder. Do they each only have like 2 people working on the Updates...or wtf. lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] icase81:
Because when there is a bug in CM, they can go *shrug*, we'll add it to the known issues list, like the bluetooth audio not working right. When there is a bug in a carrier supplied ROM, think of all the people that are going to want to call AT&T and be like 'Hey this isn't working, FIX IT!'. That costs money to pay the customer service people and it costs money from a PR point of view.

The carriers strive to make things as bug free as possible (which, is laughable considering some of the updates some carriers have pushed out, or even the state of a phone at release *cough*G2x*cough*). If they don't do super extensive testing on everything BEFORE the release, they're going to have to do the same testing AFTER the release, but after it costs them money in customer service and PR image.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ed20910:
It sucks that another manufacturer/carrier is delaying the update. Do we buy a phone on the promise/hope we will see the next update? I don't. "Why am I not getting update XX" seems to be a common complaint. I came from the Atrix 2. Motorola promissed ICS and an unlockable bootloader. The phone is now borderline if not already end of life with At&t and is just getting the ICS update and still a locked bootloader. I bought my GSIII with the thought "cool I will get JB" but didn't care when. With all of the leaks available, if you want JB, you can get it. Seeing some of the bugs in the leaks, do you really want that to be your update? If you got the update and had these bugs, thered posts of "how could they release this buggy version?" Don't get me wrong, I would like to see manufactures and carriers stand by their word, but I realize there are more important things to worry about than why my update is delayed or not getting it. If you want a phone that guarantees you'll see an update, get a ,cough cough, Iphone. Not all features may work but hey, you'll get your update. My one and a half cents and a THANKS to the hard working devs that bring us these leaks and roms (FOR FREE) to satisfy our need to update. YOU GUYS ROCK!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmacdonald19:
This phone is awesome straight out of the box. I'm just a flash junkie and I love new shiny stuff. I wonder if there's a support group for flash addicts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] viking2.0:
I dont understand why carriers have to tweak the software when samsung already does it. I dont think carriers change the software that much that it takes so long. Someone please enlighten me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deoxlar:
Lol

I'm sure a huge population ate xda are
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dntesinfrno:
Its not the OS they are changing, it takes them this long to make their BS bloatware work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superm1:
Well and doing carrier certification. I think that's more of what ends up taking a long time than updating any carrier add-on software.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jbizz:
Sprint is receiving their OTA to JB starting today. So I'm sure we're not too far behind.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bizcanos:
this sucks but never a problem with custom roms and Samsung is the easiest to update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
I'm new to Android, so maybe that makes me naive. But, I'd like to bring up a few points:

1) How do you know JB for the AT&T GS3 is delayed until 2013? No one has given a release date. Heck, it might be 2014 or 2015. It's misleading to post a title like that.

2) "Coming months:" this ambiguity goes both ways. Sprint released their GS3 JB OTA update today.

3) AT&T is taking long to update their bloatware?! There are three stupid apps: AT&T Hotspots, AT&T Messages, and AT&T Navigator. AND AT&T's already released the Note 2, which comes with Jelly Bean. Thus,

these apps have already been updated to work with Jelly Bean!

The holdup on AT&T's part is something else...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kgbkny:
As you've mentioned in another thread, it could be something network related, but I highly doubt it. AT&T can implement a limited (read as: slow) OTA rollout, with Samsung concurrently rolling it out over Kies. Want the update OTA? Wait until your turn. Want the update quickly? Download it over Kies. I don't think this is a network issue.

I also don't think that AT&T is holding back the update in order to maximize sales of upcoming phones (or, in Note 2's case, current phones) that will come preloaded with Jellybean. The GS3 is slightly over 3 months old and is still very much a high end phone. In fact, it appears that it's still the hottest Android device on the market. Why not capitalize on the popularity and release Jellybean?

The more I think about the slow updates in the U.S., the more I become convinced of one thing, and it makes a ton of sense: the carriers just can't be bothered with updates and devote very little resources to "testing" them and pushing them out, and some manufacturers may feel the same way. When the original Galaxy S series was released, a Samsung executive went on record, stating that Froyo is a marketing gimmick (despite the fact that some accessories for the Galaxy S featured functionality that required 2.2) - take a look at this thread: http://xdaforums.com/showthread.php?t=845818.

Tech geeks like us are a very small, albeit vocal, minority of wireless customers. The average Joes and Janes have no idea what Android version is on their phones, nor do they know or care about updates. As such, the carriers and, to some extent, the OEMs choose not to allocate sufficient resources to provide speedy updates. Sprint is bleeding money from the iPhone deal, so it's in their best interest to be the only carrier in the U.S. whose S3 runs Jellybean, even if it's for only a few weeks.

Samsung and the U.S. carriers finally began releasing Froyo updates for the Galaxy S phones when there was an extremely public backlash from the customer base - remeber #NeverAgain? In fact, T-Mobile didn't even release it OTA, making it available only via Kies Mini. Perhaps the Jellybean delays will result in the same backlash? One thing seems certain, though - on the carriers' lists of priorities, OS updates aren't that high up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ikjadoon:
Oh, I wasn't thinking about network issues distributing the OTA, but network issues in using the devices (do you have to like update the device ID and authorize that through the network towers for use? Or something else complicated, lol?)

That's makes a lot of sense, though. And basically the exact community that complains about not getting an update is the same that will install a custom ROM. In an odd way, having custom ROMs probably dissuades AT&T from releasing updates.

But, this still begs the question of what exactly is taking so long. They already have the entire update from Samsung, their bloat apps are already updated: do they legitimately have one guy working on this as a side-project?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theraffman:
it's more atts fault than Samsung, the s3 has had leaks for months and other US carriers are getting it now.

Additionally, comparing a tw Ron release to a pure asop isn't really valid. Tw guys beyond pure so more testing would be necessary. I blame att for our delay with 4.1 not Samsung. Doesn't bug me though, the phone is bad ass either way, it's not the end of the world having to wait a little while... it's not like the phone is useless without jb.