Related
Hello,
I'm new to these forums and android (with my new samsung vibrant)
I've only been using it for 2 weeks and I've only installed a few apps...safe and ones that shouldn't slow my phone down (juicedefender is the main one thats running mostly).
However, after the 1st 2 days or so, my phone started getting really laggy...I was hoping for froyo but it doesn't seem like its coming anytime soon...
What are my options at this point?
I've heard lagfix (idk which one to use) but I hear it could also cause problems?
ex: not being able to OTA update or update smoothly to an android update? or cause problems with apps?
Also, is it possible to UNDO the lag fix completely so that my phone were as if I never applied the lag fix or rooted it?
Thanks so much! I just want to get rid of this lag without having any issues arise regarding the phone / future updates!
Best bet I think, especially if your a newb like me, just go into the market and download ryanza oclf (one click lag fix). It sped my phone up noticeably, not even mentioning the outstanding quadrant scores I get now. Its a pretty simple process, just make sure you can enter recovery mode manually after rooting so you can apply packages/update.zip. And the app has the option to undo everything as well.
Sent from beyond galaxy s
Jhnboy said:
Hello,
I've only been using it for 2 weeks and I've only installed a few apps...safe and ones that shouldn't slow my phone down (juicedefender is the main one thats running mostly).
Click to expand...
Click to collapse
Uninstall Juice Defender, doesn't do anything, just keep Wifi off yourself when not in range.
What are my options at this point?
I've heard lagfix (idk which one to use) but I hear it could also cause problems?
ex: not being able to OTA update or update smoothly to an android update? or cause problems with apps?
Click to expand...
Click to collapse
I'd flash this. I've had good luck with the KingKlick Kernel version. Very fast.
Also, is it possible to UNDO the lag fix completely so that my phone were as if I never applied the lag fix or rooted it?
Click to expand...
Click to collapse
If an update if pushed over the air, it will be here waiting for you to flash it probably 48 hours or so before it is pushed. If not it will be here within the hour, and you can flash at your leisure. We have very good developers on the Vibrant. Eugene373, Sombionix, JustAnotherCrowd, KingKlick, WesGarner, Koush (who seems to be helping with CM6 on Vibrant).
Ok, I was thinking about maybe using that one click root app I found on the market but i need to know how safe is it? and is there a fully awesomely working version of Froyo out there or even gingerbread I can use and if so how do I install it?
And when the official froyo update comes out will my phone still be able to revive the over the air update?
Using the OCLF/Root was completely safe and easy, for me at least.
No issues at all doing it, it went very smooth with no issues at all.
Yes -- you can still receive OTA updates once you've rooted.
Ian
def no gingerbread out there for you to run
uhmmm i think if you arent even sure how to root, maybe you shouldnt get yourself into a beta rom.
98classic said:
uhmmm i think if you arent even sure how to root, maybe you shouldnt get yourself into a beta rom.
Click to expand...
Click to collapse
yEA, i KNOW YOU ARE PROB RIGHT BUT i REALLY WANT FROYO SO MUCH
ps- sorry for caps
Safe as in what? Secure wise or bricking your device? The Vibrant is easy to root but secure wise you need to be careful since your device will be "open" to any program getting root access.
I see people use the click app to root their phones. Check it out on YouTube that's where I found the info. Personally I am not going to root my cuz I don't want to deal with the headaches. Yes I have root one android phone before & was successful. I enjoy putting different roms but when I flash CM6 one his first updates on that then later on couldn't change the rom. The reason cuz I had a low memory I was told on the phone internally. So I am taking no chances with phone.
vamp6x6x6x said:
yEA, i KNOW YOU ARE PROB RIGHT BUT i REALLY WANT FROYO SO MUCH
ps- sorry for caps
Click to expand...
Click to collapse
Wait a sec fella. It doesn't work this way.
You cant type in all caps, then ps it "sorry for caps"
You should have stopped it when you saw it happening.
That would be like me raping you and then telling you i was sorry for it.
NoDataFound said:
Wait a sec fella. It doesn't work this way.
You cant type in all caps, then ps it "sorry for caps"
You should have stopped it when you saw it happening.
That would be like me raping you and then telling you i was sorry for it.
Click to expand...
Click to collapse
lol, well, all I have to say for myself is i didnt realize i was doing it til i was done
NoDataFound said:
Wait a sec fella. It doesn't work this way.
You cant type in all caps, then ps it "sorry for caps"
You should have stopped it when you saw it happening.
That would be like me raping you and then telling you i was sorry for it.
Click to expand...
Click to collapse
So are you admitting you like sausage lol
Sent from my SGH-T959 using XDA App
vamp6x6x6x said:
lol, well, all I have to say for myself is i didnt realize i was doing it til i was done
Click to expand...
Click to collapse
So you couldnt just delete what you typed and typed it correctly?
androidmonkey said:
So you couldnt just delete what you typed and typed it correctly?
Click to expand...
Click to collapse
Too much work. Easier to add ps.
I be posting this from my wicked awesome vibrant!
Before Rooting....
1) learn how to use the keyboard
2) find out what Froyo and the consequences of installing a beta are
3) No, if you install Froyo probably you won't be able to get the OTA update when available and, you may not be able to roll down if you want to.
I would stay out of it if i was you
not worthy to just root to flash the leaked Froyo... You only get the 'skin' of Froyo.. there is no JIT and GPS is not working
I would not root, because judging by you, you dont know much about android.
Few devices have froyo,
No devices have gingerbread.
If you think gingerbread, or even froyo is out then chances are you dont know how to use root features.
ps. I am not flaming, k?
Sent from my Samsung Vibrant using the xda-developers app.
SamVib said:
I would not root, because judging by you, you dont know much about android.
Few devices have froyo,
No devices have gingerbread.
If you think gingerbread, or even froyo is out then chances are you dont know how to use root features.
ps. I am not flaming, k?
Sent from my Samsung Vibrant using the xda-developers app.
Click to expand...
Click to collapse
I understand what your saying, and believe me I know a lot about android and actually a little bit about rooting but I am super paranoid about bricking my phone for two reasons:
I love my phone.
I had to pay full price for it.
What I don't understand that much is about different roms and whatnot. As for the Gingerbread thing I was kidding, but I was serious about the Froyo thing...but after reading this thread i have decided that if I do ever root with the one click root app it will only me to install simple things like lag fix, adfree, etc. Thank you for your help.
To do it again, I would not root mine. It has been less stable since I rooted it. Crashes to a black screen that says "user fault not kernel panic" and "upload mode". This is using a simple one-click root. So I advise against it.
What you'd find, should a problem occur, is that there is no going back. Folks recommend install this patch and that patch, and deeper down the rabbit hole (further away from stock) you go.
va
ughnsphotoart;8349227 said:
To do it again, I would not root mine. It has been less stable since I rooted it. Crashes to a black screen that says "user fault not kernel panic" and "upload mode". This is using a simple one-click root. So I advise against it.
What you'd find, should a problem occur, is that there is no going back. Folks recommend install this patch and that patch, and deeper down the rabbit hole (further away from stock) you go.
Click to expand...
Click to collapse
Or you can revert to a backup.
Sent from my SGH-T959 using XDA App
vaughnsphotoart said:
To do it again, I would not root mine. It has been less stable since I rooted it. Crashes to a black screen that says "user fault not kernel panic" and "upload mode". This is using a simple one-click root. So I advise against it.
What you'd find, should a problem occur, is that there is no going back. Folks recommend install this patch and that patch, and deeper down the rabbit hole (further away from stock) you go.
Click to expand...
Click to collapse
Simple unroot your phone
nomadrider123 said:
Simple unroot your phone
Click to expand...
Click to collapse
you know the one-click root that comes with the one-click lag fix? The unroot part didn't work.
This was my experience hacking on the g1 too... sometimes things worked, sometimes they didn't. When they don't, it's a lousy trip.
I just get sick of messing with it sometimes, and just want it to work.
Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
I dont know if one should/should not install custom roms on a work phone, as I don't have one. But I can tell you that if you do decide to root and install one of the custom roms, it's not that hard to unroot and go back to stock later on when you need to return the phone. There are several threads here that will guide you through the process too.
jenisiz said:
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
Click to expand...
Click to collapse
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
dsf767 said:
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
Click to expand...
Click to collapse
I hear you...but who's to say he won't ask for it out the blue someday?
Idk, at this point, the fascinate is practically impossible to brick. You also say you have experience rooting and customizing other phones, correct? I say go for it. The only reason I could see not to is due to security issues. Work passwords and etc.. I really don't know too much about all of that tho.
Sent from my SCH-I500 using XDA Premium App
I have a rooted android work phone. All you have to do is read what ppl are saying about the roms and FOLLOW DIRECTIONS and youll be fine.
dsf767 said:
Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Click to expand...
Click to collapse
Used my fascinating voodoo powers
I seriously discourage doing anything to it. It's not yours for one, and (no disrespect to the devs ofcourse, their work is amazing) there really isnt anything spectacular for this phone at the moment due to samsung's failure to provide any source code. To be more specific... our kernels suck.
And oh yea this shouldve been in the Q&A section so be ready for ashasaur to move this thread. (hes really good at doing that )
Depends on your comfort level, and of course, your corporate policies.
Sent from my SCH-I500 using XDA Premium App
I would say root your phone at the most. It's fairly easy to recover from just rooting, but flashing roms/kernels/modems is much more risky. At least with rooting, you could fairly easily freeze the bloat with TiBu and have a more functional phone. Thawing everything and un-rooting would have you a stock phone back fairly quickly, and you could also still receive OTA updates as well.
I say go for it if anything goes wrong all you have to do is odin back to stock it removes everything its as simple as plugging the phone in load the stock file and click start I've done this countless times
We pick our work cell phones specifically because of the potential customization we can do. I hate being stuck with some company's version of what they think will be useful to me in my job. I can Odin this phone back to stock/factory defaults in less than 5 minutes if need be, so customizing this phone and expanding its abilities, and recovering from those customizations quickly, were what attracted me to it.
Android is Android, whether it's Samsung's stock version or one of the dev's version of it. Your phone is still going to perform the same tasks you need it to for your job. As long as you are both competent with the technologies involved and confident in your ability to restore to stock, I don't see why you should hesitate from exploring the options that are out there, especially when Froyo source drops and we see an explosion of dev-created customizations/enhancements.
Really? If your asking for advice on whether to mess with a business owned phone, it makes me wonder are you the ceo's mail clerk?
SuperClean2.9.1vNitroDark
Personally for a work phone, I'd update it for better usage in my work.
Increasing battery life usage duration.
Less irritating buggy glitches.
Removing the idiotic TW/BING/VZW craps. (too many add-on hacks from google default causing reliability and dependability problems)
Adding Backup and Restore nandroid for possible failures and migrations.
I suggest DJ05 + SuperClean + Blaze v2.3.1R2.
Hey, I looked around but couldn't find a thread about this (so please dont kill me if I missed one).
I just did a 'check for update' on my AT&T SGS2, and it apparently found one. It immediately started downloading it, without letting me pause/stop it. I shut down the phone within a few seconds, restarted it, but it started to download it right away again. I tried to find the process and kill it (it's apparently called Device Management), but it completed the download before I could. It then asked me if I want to install the update or postpone it for a few hours. I chose the latter option, since I'm concerned if this update could cause me more problems or if it's actually worth installing.
I have the standard ROM, albeit with some modifications. It's rooted, has the CWM recovery installed, and a custom kernel to allow me to OC it.
Has anyone installed this new software update yet? Does it have anything worthwhile? Will it cause me to lose my root/kernel/CWM? If so, would it lock my device down and prevent me from re-rooting it, etc. again?
Assuming I don't want the update, there doesn't seem to be an 'undo' option. I imagine I can use Titanium to roll the DeviceManager app back to before I chose the update and make it forget I ever asked. I had assumed that when clicking 'check for update' that it would ASK me if I wanted it first. Guess not.
In any case, any suggestions/feedback would be appreciated. Thanks!
phonic said:
Hey, I looked around but couldn't find a thread about this (so please dont kill me if I missed one).
I just did a 'check for update' on my AT&T SGS2, and it apparently found one. It immediately started downloading it, without letting me pause/stop it. I shut down the phone within a few seconds, restarted it, but it started to download it right away again. I tried to find the process and kill it (it's apparently called Device Management), but it completed the download before I could. It then asked me if I want to install the update or postpone it for a few hours. I chose the latter option, since I'm concerned if this update could cause me more problems or if it's actually worth installing.
I have the standard ROM, albeit with some modifications. It's rooted, has the CWM recovery installed, and a custom kernel to allow me to OC it.
Has anyone installed this new software update yet? Does it have anything worthwhile? Will it cause me to lose my root/kernel/CWM? If so, would it lock my device down and prevent me from re-rooting it, etc. again?
Assuming I don't want the update, there doesn't seem to be an 'undo' option. I imagine I can use Titanium to roll the DeviceManager app back to before I chose the update and make it forget I ever asked. I had assumed that when clicking 'check for update' that it would ASK me if I wanted it first. Guess not.
In any case, any suggestions/feedback would be appreciated. Thanks!
Click to expand...
Click to collapse
This has already been covered, it's the 2.3.6 update. Don't do anything other than flash the file uploaded here to your device using Odin.
You really couldn't find anything on this?
If you've rooted your phone and removed any of the bloatware then letting the update continue will result in it not being able to complete. It will leave your phone as it is.
if you didnt want to install the update, why click on "check for update"?
Miami_Son said:
You really couldn't find anything on this?
If you've rooted your phone and removed any of the bloatware then letting the update continue will result in it not being able to complete. It will leave your phone as it is.
Click to expand...
Click to collapse
I checked the first few pages and didn't see anything about it. Later last night I found a couple threads that discussed the results in the update (ie: upgrading the OS to 2.3.6, which I didn't know was what this was for).
In any case, after the update downloaded and I postponed it, I wiped the DeviceManagement data (19ish MB), so I assume this will make it forget.
nyydynasty said:
if you didnt want to install the update, why click on "check for update"?
Click to expand...
Click to collapse
I didn't know if there was an update or what it was for. I had assumed that 'Check for Update' would do just (and only) that - check. Every other software program that had a similar feature would 'check', and if it found something, ask if you wanted to download/install it. Some would also tell you what the update was for or what it was updating. I assumed that would have been the case here.
Based on what I've found, it seems like the 2.3.6 update isn't really worth it, and has caused problems for others, so I'll hold off until ICS comes out.
I want mine to update to 2.3.6 but i can find anything i am on 2.3.4 and umnamed rom and i really want to put 2.4.6 then put the rom
x.Orville.x said:
I want mine to update to 2.3.6 but i can find anything i am on 2.3.4 and umnamed rom and i really want to put 2.4.6 then put the rom
Click to expand...
Click to collapse
What's the point of that? If you are running the latest UnNamed ROM then you are already on 2.3.6 there would be no point of updating to the official AT&T version.
phonic said:
Based on what I've found, it seems like the 2.3.6 update isn't really worth it, and has caused problems for others, so I'll hold off until ICS comes out.
Click to expand...
Click to collapse
its not a problem for everyone. Some people report issues and others dont.
PatriotXT92 said:
What's the point of that? If you are running the latest UnNamed ROM then you are already on 2.3.6 there would be no point of updating to the official AT&T version.
Click to expand...
Click to collapse
Some people in here just amaze the **** out of me.
jury still seems to be out on whether or not 2.3.6 is worth upgrading to. Many users complain of battery problems and other weird errors, in addition re-rooting complications.
My phone is working fine and with the exception of the 'lock screen bug' that I would love to have fixed, i don't see any reason to upgrade.
However I'd love to be convinced otherwise.
Deenybird said:
jury still seems to be out on whether or not 2.3.6 is worth upgrading to. Many users complain of battery problems and other weird errors, in addition re-rooting complications.
My phone is working fine and with the exception of the 'lock screen bug' that I would love to have fixed, i don't see any reason to upgrade.
However I'd love to be convinced otherwise.
Click to expand...
Click to collapse
Let the jury be absolved. 2.3.6, to make it clear, is very, very, very, very, bad, bad, bad, bad. Breaks HID bluetooth devices, has many issues, and is simply a stopgap between 2.3.4 and 4.0. Why they released such a **** version is beyond me.
Sent from my SAMSUNG-SGH-I777 using xda premium
Miami_Son said:
Some people in here just amaze the **** out of me.
Click to expand...
Click to collapse
+1 lmao
Sent from my SGH-I777 using xda premium
autonomous-inc said:
Why they released such a **** version is beyond me.
Click to expand...
Click to collapse
They lost to apple, and had to replace overscroll bounce.
RE: [RoM]UCLD3 Official ATT "Leak" !CLOSED!
I just wanted to say TY to the developers of this ROM, especially task. I got burned, but I knew what I was getting into. I'm within 30 days, plus have 1 yr warranty, plus insurance. I got my new phone and I'm happy.
Thanks again guys for trying to bring us something new and exciting.
Just a question: were all of the AT&T leaks affected by this, or just UCLD3?
The general consensus is that LD3 was the culprit, however it is possible that all leaks are affected.
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 were unaffected.
nbell13 said:
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 was unaffected.
Click to expand...
Click to collapse
And you know this how? Without facts, this statement is useless bro. One thing I do know is the bricking only happened to a few people. Far less then people who didn't have issues. Just like entropy said, without reproducing it would be hard to figure out. But either way. Leaks are just that. Leaks. They are pretty much worthless considering everything else we already have. So really, to figure out exactly the cause we would have to go through the process of brick, then replace/fix the device and so on.
task650 said:
And you know this how? Without facts, this statement is useless bro. One thing I do know is the bricking only happened to a few people. Far less then people who didn't have issues. Just like entropy said, without reproducing it would be hard to figure out. But either way. Leaks are just that. Leaks. They are pretty much worthless considering everything else we already have. So really, to figure out exactly the cause we would have to go through the process of brick, then replace/fix the device and so on.
Click to expand...
Click to collapse
I thought that's what you had said yourself in your thread (haven't read it in a while)
Task
I have flashed this rom many times and no issues with my phone. Although I have been lurking in these threads as a NOOB, it is apparent to me that you have to:
follow instructions in OP before flashing
Read all the of the thread before flashing
Make sure that you have the entire zip file downloaded before flashing...
Not sure what is the problem, but it is not anything with zip I down loaded.. I did both.The other files such as Shomans or AOKP as they are better than any stock rom...
Thank you for all that you do...
nbell13 said:
I thought that's what you had said yourself in your thread (haven't read it in a while)
Click to expand...
Click to collapse
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
task650 said:
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
Click to expand...
Click to collapse
Thanks for the hard work on it anyway Task. I read the OP. I read every post in the thread and then I read the OP again. I have flashed and reflashed it several times. Flashed several kernels and still running great.
The original OEM battery and earpiece failed within a day of each other so I am back to using my Atrix until I can get a warranty replacement on the i777.
Thanks again Task...it was fun while it lasted.
task650 said:
i think i may have said something about it, but just wasn't sure what was happening. there were too many "it could be this" and "it could be that" stuff being mentioned. but i did however make an attempt for 2 days trying to replicate the brick. i have no qualms about buying a new phone so i wasn't worried at all about bricking. i tried every way that anyone mentioned plus more but i still couldn't get it to brick. so i'm still iffy about the whole thing. i just said screw and took down the thread. considering A TON of people don't like to read OP's and follow directions i thought it would be the best thing to do.
Click to expand...
Click to collapse
Lol, I just bought the GNex from Google Play myself... Gonna need to switch back to T-Mobile in the fall when I move back to my hometown... AT&T has **** for signal there That, and I'm finally sick of touchwiz.
nbell13 said:
I'm finally sick of touchwiz.
Click to expand...
Click to collapse
Yeah that's why I use AOKP I can't stand touchwiz ics
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Lol. I installed nova to take care of that. Do want some of the other stuff so have to leave tw in some way but at least I don't have to look at it.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
nbell13 said:
The culprit was the CWM injected kernel in the version task posted. All other leaks and the one-click version of LD3 were unaffected.
Click to expand...
Click to collapse
No - even after the re-repack I believe a few more bricks happened.
Looks like the UCLD3 leak (and maybe all leaks) have the same bug that is in all of the Epic 4G Touch leaks and all Chinese Galaxy Note ICS leaks, along with the SHW-M250S/K/L official ICS releases and source code - it's a nasty one that can cause severe hardbricks if you wipe in recovery.
When I say "severe hardbrick" - I mean that the eMMC chip actually gets damaged to the point where not even JTAG recovery services like mobiletechvideos.com are able to recover the device.
It's looking like UCLD3 has the same issues that SiyahKernel 3.1rc6 had (which was rebased on SHW-M250L sources).
This is probably like some of the xbox360 and ps3 bricking updates -- an update changes something in the way the device operates. In those update -- spinning the media faster or turning on gpu acceleration of the UI, etc.. some devices can't take the change in the baseline for which they were certified and die.
Perhaps they changed voltages, media parameters, etc -- without source, we won't know for sure.
othermark said:
This is probably like some of the xbox360 and ps3 bricking updates -- an update changes something in the way the device operates. In those update -- spinning the media faster or turning on gpu acceleration of the UI, etc.. some devices can't take the change in the baseline for which they were certified and die.
Perhaps they changed voltages, media parameters, etc -- without source, we won't know for sure.
Click to expand...
Click to collapse
Sweet.... I want one of them Xbox with ICS
Yea this is one of those oddities. On mine I did do a wipe using the ld3 leaked kernel (trying to get ld3 installed) and although it wouldn't boot it also didn't hard brick. I ended up wiping using Odin and starting over.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Entropy512 said:
No - even after the re-repack I believe a few more bricks happened.
Looks like the UCLD3 leak (and maybe all leaks) have the same bug that is in all of the Epic 4G Touch leaks and all Chinese Galaxy Note ICS leaks, along with the SHW-M250S/K/L official ICS releases and source code - it's a nasty one that can cause severe hardbricks if you wipe in recovery.
When I say "severe hardbrick" - I mean that the eMMC chip actually gets damaged to the point where not even JTAG recovery services like mobiletechvideos.com are able to recover the device.
It's looking like UCLD3 has the same issues that SiyahKernel 3.1rc6 had (which was rebased on SHW-M250L sources).
Click to expand...
Click to collapse
Thank you for your insights, while I understand very little in the way of repacks and source code, I can grasp (beginning to) smart, safe flashing practices. When you share your thoughts on these subjects, the non-dev community is so much the better for it (though there will never be a silver bullet to the spreading of BS through the grapevine).
And it looks like I'm still the only one who wants Samsung stock roms.
raduque said:
And it looks like I'm still the only one who wants Samsung stock roms.
Click to expand...
Click to collapse
There are still plenty of great TW GB ROMs around. Unfortunately, people who want a stable, safe stock ICS ROM will have to wait until Samsung gives you one. Without the developers we wouldn't have ICS on our phone AT ALL, so complaining is without merit (unless you are complaining to Samsung).
raduque said:
And it looks like I'm still the only one who wants Samsung stock roms.
Click to expand...
Click to collapse
Naw I want a Samsung stock rom built for the ATT version also
Sent from my SGH-I777 using XDA Premium App