Related
Thought I'd share this with you guys. I recommend sending out a similar email so that they know that there are serious concerns about the phone. I did it online at the Contact Us page on the Samsung website.
Here's what I wrote:
Hello,
I recently purchased a Samsung Captivate. Overall, I am quite pleased with the device. However, there are a few things that irritate me about it that I was hoping you could comment on:
1.) There is a serious lag issue. Do a quick google search and you'll find that this is a universal problem with the phone.
2.) The GPS does not work. Also a universal issue.
3.) No 2.2 Froyo.
4.) No last.fm scrobbling support for the default music player (which I love by the way!)
5.) Drivers for Windows 7 x64 do not work well. After a lot of trial and error, I finally got it. Again, a universal issue.
A lot of people complain about the TouchWiz UI, but I personally enjoy it, as long as the lag issue is taken care of. Also I'm pleased with the phone call quality, and almost all other aspects of the phone.
I appreciate your time, and hope to hear from you soon.
Thank you,
[thecoolestcow]
Here is the response:
Dear [thecoolestcow],
Thank you for your inquiry.
Regarding the GPS on the phone, Samsung Mobile is aware that under certain conditions, the GPS on our U.S. Galaxy S devices may not be meeting performance expectations. We are diligently evaluating the situation and will provide an update as soon as possible.
We advise you to use assisted GPS powered by your service provider.
We still don't have any update regarding the release of the Android 2.2 for the Captivate and the drivers that will be compatible with Windows 7 64bit.
We will forward your report of this behavior along to the appropriate parties for additional review and consideration.
We are unable to speculate when/if this software revision might be available due to the fact that this might lead to inaccurate information and confusion.
Should this become available, it will be posted on our website in the Samsung Download Center.
Please feel free to check back with us periodically for updates.
Should you desire additional assistance resolving this, we invite you to call Samsung Customer Support by phone at our toll free number 1-888-987-4357 between the hours 7:00 a.m. to 9:00 p.m. Monday through Friday, and 9:00 a.m. to 6:00 p.m. Saturday, Central Standard Time.
Thank you for choosing Samsung.
Sincerely,
Technical Support
thecoolestcow said:
Thought I'd share this with you guys. I recommend sending out a similar email so that they know that there are serious concerns about the phone. I did it online at the Contact Us page on the Samsung website.
Here's what I wrote:
Hello,
I recently purchased a Samsung Captivate. Overall, I am quite pleased with the device. However, there are a few things that irritate me about it that I was hoping you could comment on:
1.) There is a serious lag issue. Do a quick google search and you'll find that this is a universal problem with the phone.
2.) The GPS does not work. Also a universal issue.
3.) No 2.2 Froyo.
4.) No last.fm scrobbling support for the default music player (which I love by the way!)
5.) Drivers for Windows 7 x64 do not work well. After a lot of trial and error, I finally got it. Again, a universal issue.
A lot of people complain about the TouchWiz UI, but I personally enjoy it, as long as the lag issue is taken care of. Also I'm pleased with the phone call quality, and almost all other aspects of the phone.
I appreciate your time, and hope to hear from you soon.
Thank you,
[thecoolestcow]
Here is the response:
Dear [thecoolestcow],
Thank you for your inquiry.
Regarding the GPS on the phone, Samsung Mobile is aware that under certain conditions, the GPS on our U.S. Galaxy S devices may not be meeting performance expectations. We are diligently evaluating the situation and will provide an update as soon as possible.
We advise you to use assisted GPS powered by your service provider.
We still don't have any update regarding the release of the Android 2.2 for the Captivate and the drivers that will be compatible with Windows 7 64bit.
We will forward your report of this behavior along to the appropriate parties for additional review and consideration.
We are unable to speculate when/if this software revision might be available due to the fact that this might lead to inaccurate information and confusion.
Should this become available, it will be posted on our website in the Samsung Download Center.
Please feel free to check back with us periodically for updates.
Should you desire additional assistance resolving this, we invite you to call Samsung Customer Support by phone at our toll free number 1-888-987-4357 between the hours 7:00 a.m. to 9:00 p.m. Monday through Friday, and 9:00 a.m. to 6:00 p.m. Saturday, Central Standard Time.
Thank you for choosing Samsung.
Sincerely,
Technical Support
Click to expand...
Click to collapse
man I just dont see this lag yall are talking about... Had the phone since day 1, no lag fix and its fast as my n1 on 2.2. about.. Wierd...
Also GPS does work, just not reliably all the time, some works fine, others not, others sometimes.. So saying it dont work is exadurating. I just dont want people that dont have one think that the GPS dont work. It does and I use it everyday without issue. No fixes or anything, mine and some others works...
2.2 froyo will be here soon. Hold your horses on and it will be here next month I will bet...
I didn't see the lag either for a while, but I see it in most of the Samsung native apps, like Messaging and the screen unlock.
GPS also used to work amazingly. It just stopped completely now for me.
It's good though that they acknowledged in the email that they were going to release a fix for it.
thecoolestcow said:
I didn't see the lag either for a while, but I see it in most of the Samsung native apps, like Messaging and the screen unlock.
GPS also used to work amazingly. It just stopped completely now for me.
It's good though that they acknowledged in the email that they were going to release a fix for it.
Click to expand...
Click to collapse
Yea, Well Im certain it will be fixed. The samsung epic 4g is rumored to have a working GPS (more testing needs done for me to believe it for sure) and if we have the same hardware gps wise as the Epic 4g we should definatly see a fix...
Nice, Engadget confirms.
engadget.com/2010/08/18/samsung-says-gps-is-tested-and-validated-on-epic-4g-our-testi/
There is most certainly lag. Like you guys, it wasn't a big deal until I saw the lag fix.
Long story short, I've been running the lag fix about a week, then borked my phone with another tweak and had to revert back to stock. HOLY COW was that thing slow... I never really knew any different until I had seen greener pastures
I will say I don't think the DEFAULT lag is worse than any other phone on the market. But it is capable of much, much faster.
Also you forgot to include the complaint that MMS doesn't work on EDGE, only 3G.
TexUs said:
There is most certainly lag. Like you guys, it wasn't a big deal until I saw the lag fix.
Long story short, I've been running the lag fix about a week, then borked my phone with another tweak and had to revert back to stock. HOLY COW was that thing slow... I never really knew any different until I had seen greener pastures
I will say I don't think the DEFAULT lag is worse than any other phone on the market. But it is capable of much, much faster.
Click to expand...
Click to collapse
Which lag fix did you use? I saw several. I haven't rooted my device yet because I'm a little girl. I'm trying to gather as much info as possible first.
thecoolestcow said:
Which lag fix did you use? I saw several. I haven't rooted my device yet because I'm a little girl. I'm trying to gather as much info as possible first.
Click to expand...
Click to collapse
Well I did all my tweaks manually the first time. However when I borked and started over I used this: http://forum.xda-developers.com/showthread.php?t=751934
That will do all necessary tweaks at once. Just download the update.zip file to the root of your INTERNAL card, reboot into recovery mode (ask if you don't know how... easiest way is to use ADB), and select "reinstall packages" and you're done.
Just check the post I linked to, but it'll remove all the ATT crapware, remove the loud startup sounds, install root, block ads, etc.
After it's ran you then can go into the app it adds and run the lag fix... After you run that script it needs a reboot... And then you've got a lag fixed phone that runs twice as fast. ROM Manager, for instance, takes like a whole freaking minute it seems to open un-lag-fixed. Lag-fixed it takes several seconds max.
TexUs said:
Well I did all my tweaks manually the first time. However when I borked and started over I used this: forum.xda-developers.com/showthread.php?t=751934
That will do all necessary tweaks at once. Just download the update.zip file to the root of your INTERNAL card, reboot into recovery mode (ask if you don't know how... easiest way is to use ADB), and select "reinstall packages" and you're done.
Just check the post I linked to, but it'll remove all the ATT crapware, remove the loud startup sounds, install root, block ads, etc.
After it's ran you then can go into the app it adds and run the lag fix.
Click to expand...
Click to collapse
Holy crap, how did I miss that one? Excellent, thank you. I will likely be doing that in the near future!
Sent from my SAMSUNG-SGH-I897 using XDA App
thecoolestcow said:
Holy crap, how did I miss that one? Excellent, thank you. I will likely be doing that in the near future!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
NP.
I'm happy with 2.1 right now... I mean the Captivate at 2.1 runs faster than anything else on the market, including the N1 2.2......
So I can live with 2.1 until Samsung releases 2.2
Once you see how much faster it is with the lag fix, you'll start to wonder how much faster 2.2 will be. The Captivate will be untouchable.
There is definitely significant lag on the stock firmware - most notably for me with the marketplace but s also for some other apps when they are loading data. I haven't applied any fixes yet as I'm waiting for a decent firmware update before I do too much with my phone.
JH2/3 are looking like good bets, but I would suspect that an official firmware is right around the corner given the few changes between JH2 and JH3.
Sent from my SAMSUNG-SGH-I897 using XDA App
Why wait? It takes 5 minutes to vastly improve the usability of your phone.
And worst comes to worst, you use the Odin3 one-click to restore it to stock. Seems pretty awesome. I'll probably be "super-rooting" tonight!
Also to note you should only be doing that super-rooting from stock to start with... It's the most reliable method anyway. You can try it from what you've got but- if there's issues you just need to do it from stock.
Hm. And there's no way to back up my apps/data right?
thecoolestcow said:
Hm. And there's no way to back up my apps/data right?
Click to expand...
Click to collapse
Yes, download ROM Manager but you need to be rooted first I think... So you can root your phone only (same process but it just does rooting: http://forum.xda-developers.com/showthread.php?t=725555), download/install ROM Manager (http://forum.xda-developers.com/showthread.php?t=734163). Then when you reboot into the ROM Manager recovery screen there's nandroid backup utility that'll back up everything.
If you like selective backups of stuff you can also use Titanium Backup (also requires root).
smashpunks said:
man I just dont see this lag yall are talking about... Had the phone since day 1, no lag fix and its fast as my n1 on 2.2. about.. Wierd...
Also GPS does work, just not reliably all the time, some works fine, others not, others sometimes.. So saying it dont work is exadurating. I just dont want people that dont have one think that the GPS dont work. It does and I use it everyday without issue. No fixes or anything, mine and some others works...
2.2 froyo will be here soon. Hold your horses on and it will be here next month I will bet...
Click to expand...
Click to collapse
GPS does NOT work. It barely functions, so it does not work. Anybody that says it does is just trying fool themselves into thinking they didnt make a mistake. GPS absolutely does not work. Its been documented by numerous sources and tens of thousands (or more) vibrant and captivate users here in the US. For Christ's sake, even Samsung has admitted that it doesnt work. They've used incorrect drivers from Broadcom, so it can't possibly work.
Samsung may release Froyo to the carriers toward the end of next month, but it'll be quite a while before AT&T releases it to us. They have to go through and add all their crapware and remove any functionality that's in the stock rom that they can charge money for (this really pisses me off I REALLY, want that wifi hotspot functionality!!!) and they have to cripple the kernel and radio so there'll be no HSUPA.
derek4484 said:
GPS does NOT work. It barely functions, so it does not work. Anybody that says it does is just trying fool themselves into thinking they didnt make a mistake. GPS absolutely does not work. Its been documented by numerous sources and tens of thousands (or more) vibrant and captivate users here in the US. For Christ's sake, even Samsung has admitted that it doesnt work. They've used incorrect drivers from Broadcom, so it can't possibly work.
Samsung may release Froyo to the carriers toward the end of next month, but it'll be quite a while before AT&T releases it to us. They have to go through and add all their crapware and remove any functionality that's in the stock rom that they can charge money for (this really pisses me off I REALLY, want that wifi hotspot functionality!!!) and they have to cripple the kernel and radio so there'll be no HSUPA.
Click to expand...
Click to collapse
We're about a month after release and have Vanilla Android 2.1 ROMs, so chill out. Have some patience, I'm sure we'll see them for 2.2 as well.
derek4484 said:
GPS does NOT work. It barely functions, so it does not work. Anybody that says it does is just trying fool themselves into thinking they didnt make a mistake. GPS absolutely does not work. Its been documented by numerous sources and tens of thousands (or more) vibrant and captivate users here in the US. For Christ's sake, even Samsung has admitted that it doesnt work. They've used incorrect drivers from Broadcom, so it can't possibly work.
Samsung may release Froyo to the carriers toward the end of next month, but it'll be quite a while before AT&T releases it to us. They have to go through and add all their crapware and remove any functionality that's in the stock rom that they can charge money for (this really pisses me off I REALLY, want that wifi hotspot functionality!!!) and they have to cripple the kernel and radio so there'll be no HSUPA.
Click to expand...
Click to collapse
Mine works and so do others in those thousands of people threads. If you would like I can copy n paste them for ya...
Its directed me to many places perfectly so it works, its just unreliable and not the best, hence needs to be optimized ...
now post a link where samsung admitted using incorrect drivers? I've never saw that...
I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...
pezx44 said:
I know the issue of people's Captivates turning off by themselves has been discussed a lot and if there is a solution that is already provided, I apologize for cluttering up the forum a little more. If not, I have something that works for me and was wondering if it might be helpful for troubleshooting what the issue is/how to fix it.
For myself, it seems to be an issue when the battery is near full more than any other time. If I just unplug the phone in the morning and come back to it later it will be off. However, I often go running in the mornings. When I do, I like to listen to music and I use Grooveshark to do it. Just opening Grooveshark does not seem to fix the issue, but if music is playing (even if there is no volume) my phone does not turn itself off. I haven't played around to see if the same is true for just playing music through the regular music player, but I was wondering if perhaps accessing audio playback somehow keeps the phone alive.
Again, if there is already a known solution I'm sorry for cluttering things. Maybe I just had to search around some more...
Click to expand...
Click to collapse
My guess is you guys have tried to overclock and your phone really didn't like it and caused some minor damage. I have heard reports from stock 2.1, 2.2 and Cognition, most of them I have talked to have tried overclocking at some point. If you haven't, maybe just faulty hardware out of the box, if you can flash stock and it still happens, take it back and exchange it.
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.
I only had overclocking on my phone once in a sre build and tested it once and found it worthless to me so i disabled it.
Anyways i have never had an issue with shut downs prior to flashing ji6. Now when i leave my phone plugged in over night, on, i wake up in the morning to find it off. This has happened every day so i cant use my phone for an alarm at the moment. Otger than that ive had a few random shut downs during the day. I do want to know what the problem/solution is for the phone shutting off during the night though.
When i flashed over to ji6 i formatted sd odined jf6 then odined ji6. I did try to do tge master clear only to have it start then say FAIL! In a red box. Someone suggested i reinstall my drivers. I do plan on trying that but am getting so sick of flashing and redoing stuff i havent got aroubd to it.
Would a master clear do anything or make a difference you think since i formatted the sd?
Sent from my SAMSUNG-SGH-I897 using XDA App
designgears said:
Personally I won't be overclocking again, 200mhz is not working breaking a $500 phone. I find the lagfix isn't even needed on 2.2 stock.
Click to expand...
Click to collapse
Agree - the extra battery drain and heat buildup in the chip is not worth it... this device works pretty good with stock and/or new FS tweaks applied.
I do hope the OP gets his device recovered with Odin etc.... hopefully just a glitch that can be remedied back to stock....
I've Odin'd it back to stock but currently am running Cognition 2.2. This has been an issue from the getgo, however (maybe I should mention that I SIM unlocked it if that makes a difference). I couldn't return it because I live out of the country and didn't even receive the thing for about 40 days (gotta love Costa Rican customs). I agree that OC seems pretty pointless on this phone and I have avoided OC roms. I only thought it was interesting that running programs doesn't seem to prevent it, but for some reason playing music does seem to prevent the shutdown perhaps meaning that accessing a certain dll or something fixes the issue (I really have no idea why it works). I just thought that info might be helpful to people who understand the OS better than I if it is a consistent problem for people and if no solutions other than "return it" have been found.
Edit: Oh and DG, great work. You'd be one of those smarter than I guys I referenced...
i've never overclocked my phone and i've mostly run it without a lagfix and no matter what ROM i've used (i've been using cognition beta 1 since it came out) i've always had random shut-downs. For a while there on the stock rom it seemed to only happen when my wifi was on but now it doesn't matter. I don't have any special automation software running (task managers, tasker, ..etc). It's the single most maddening thing about this phone.
Same here... i have had my phone since launch... i had random shut downs since launch. I have had less problems now then before and i have flashed every rom that has come out including overclocking.
Sent from my SAMSUNG-SGH-I897 using XDA App
My wife's phone was never overclocked and it developed the random shut down problem about two weeks after she got it. After trying numerous things to fix the problem, some resulting in it working fine again for a few days and then starting random shut downs again, I came to the conclusion that it was definitely a defective hardware problem and had her return and exchange it. The new one is now set up exactly the same as her old one (rooted stock jf6 with the bloatware removed, side loading enabled, and market fixed) and has been running fine, with no shut downs for over two weeks.
I have been in the electronic repair business for over 25 years, and my conclusion is, the only fix is to return it and get it repaired or replaced. Nothing you can do is going to fix your defective hardware.
I had my phone for a month and it was flawless, updated to 2.2 beta and started getting random shutdowns. I replaced the phone and the new one doesn't shutdown at all on 2.2. The one I returned would shutdown at least 5-6 times per day. Again only after installing 2.2, on 2.1 it seems ok. Which could be a software issue, or just more strain on the hardware making the problem happen
Personally I think it's just bad hardware. Replace the phone.
I guess I'll have to see if there's any way of getting the hardware replaced but I don't think I'm going to be able to manage.
I just want to repeat, however, that I have tested this many many times and with numerous iterations of DG's roms as well as stock. I can guarantee a shut down soon after unplugging the phone in the morning, but I have never gotten it when I start playing music (specifically through Grooveshark - I have not tested it with the regular music player). I just think that even if it's a hardware problem, there appears to be a relationship which suggests that a software solution could prevent it (at least given my experience). I just thought it might be helpful information to people who might understand a possible relationship between the two and to see if anybody else can confirm or refute this behavior. If there is any way to trick the phone into thinking it is playing the music without actually playing it, the problem may go away for people who are experiencing it.
If anybody else can refute my observations or back them up, I would be interested to hear. Perhaps if enough people can confirm it, it may be worthwhile to investigate further. If people can refute it, I guess I'll just count myself "lucky" to have only a mildly faulty phone. Either way I'm happy with my phone. I just thought I might be able to help others out.
I actually convinced four coworkers to pick up Captivates here (our company policy is with at&t) and my boss' phone (completely stock) would randomly shut-down four or five times a day. I've been around the community since the G1 dev launch and my phone is definitely not stock but has never randomly shutdown.
I finally convinced him to return it and his new one came in today. With this many reports, it is not a user-induced problem.
+1 to everything im reading here. i tried a few software and hardware 'fixes' so to say and nothing fixed the issue for long term. sent in for a new captivate #3 yesterday. Im sorry its just got to be a hardware problem, its just to far widespread from what im seeing.
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol
Believe it or not, this has been working for me for a couple of days now
http://androidforums.com/captivate-...hone-shutting-off-randomly-5.html#post1572891
I called ATT and was told to call Samsung because I don't have an account. They did tell me, however, that they didn't know anything about a bad production run or anything like that or about many exchanges. Of course I take all of that with a grain of salt...
Out of curiosity, to the people that have had the shutdown issue: Did you SIM Unlock your phone? I have and I use a foreign SIM (just trying to see what is in common).
I understand that it seems to be a hardware-based issue, but there really does seem to be a correlation to software as well. If I'm told by Samsung that there was a bad production run, I'll go with it. But until then, I'm the meticulous sort and will continue testing.
I don't want to beat a dead horse though and I don't want to be one of those guys claiming some fanciful fix to something there is no fix for. I'm still doing some testing on my end. So far the music "fix" has worked for me (although I do not see it as a long term solution) and I just wanted to float it because it seems to work consistently (unfortunately you can't prove a negative). I understand, however, that others have claimed fixes that just plain don't work and so if I hear of anybody trying this and it not working for them I'll move along to focus on other possible correlations. Thanks for all the feedback so far!
Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.
ZoinksS2k said:
Why are people blaming hardware if it is exclusively a Froyo problem?
I've never OC'ed. Learned my lesson on the Evo 4g.
The power-off problem ONLY happens on Froyo builds
Issue happens with the ODIN-packaged 2.2 and all Cognition 2.2 releases
Inexplicably, I do not have the problem with my current Froyo build based on beta 4. Previous installs of Beta4 did have the problem, just not this one.
Odd behavior on a leaked build does not mean bad hardware. Once again, I NEVER have this problem on Eclair.
There is some combination of software and/or settings that causes this.
Click to expand...
Click to collapse
Blaming the 2.2 builds as the sole culprit is false. I have coworker who has two stock captivates. His had never had an issue, his wife is up to phone #2 and has had power issues on both.
Sent from my SAMSUNG-SGH-I897 using XDA App
It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.
pezx44 said:
It is definitely not exclusively Froyo. It has been happening to people (myself included) for a while.
I just got off the phone with Samsung (general customer support then level 2 technical support). I suggest that anybody else have the problem also call them to at least document the issue (888-987-4357 options 1-6-2-4). They said I can send it in for repairs (yeah right - like I can be away from my phone for that long!) but more importantly that they have not heard of this being a widespread problem but that probably just means that people aren't reporting it. I urge others to call in to at least let them have an idea of how widespread (or not) it is.
Click to expand...
Click to collapse
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process
bamonkey said:
I did want to point out one fear that is starting to cross my mind. i got my 1st one off craigslist which is hilarious because im still covered by warranty. HOWEVER. after the first exchange its then 90 days on a refurb *which begs me to wonder if samsung will still honor the 1 year warranty claim*..anyways.. im really really really hoping that i dont get one that seems to last a while and has this issue start up again....because that will be the last captivate for me...obviously lol
Click to expand...
Click to collapse
If you bought a new phone from AT&T, the warranty is 1 year. During this one year, you can have the warranty replacement (refurbs) as many time as you want and your warranty stays as the original (counted from the day you purchased your phone).
If you bought a refurb phone from AT&T, the warranty is 90 days.
bamonkey said:
Hmm im pretty sure i just got them yesterday HOWEVER they also sent me to their android support team *wha? really?* pretty much the same level of service but they made sure i was on the newest ota and had me try it for a day and said they would call back after 24 hours to check if the issue persisted.
Why did they tell you to send it in for repairs thou? this is going to be my 3rd and each time they send out the new one FIRST and i rma the bad one back in the box. only reason i havent been so when i have to go through this process
Click to expand...
Click to collapse
If I lived in the states I probably would have pushed for that myself. Unfortunately getting things shipped to/from me where I live costs money plus customs delays so I'm sort of resigned to the fact that I'm stuck with this handset for now. I was hoping I could just bust into an ATT store and get it exchanged but it doesn't look like that's an option. Calling Samsung was more to just document it with them. I'm glad you have had better luck.
3rd you say though? Has it been the same issue with each?
So basically, I bought my phone within the month the phone came out. I loved everything about it and I felt happy with my product.
Then later my phone starting powering off randomly and later I find out that my gps isn’t working. So I went to ATT and they replace my phone without a problem.
I finally get another captivate and the phone is working awesome, except for the GPS. Which really didn’t mind me anymore, because I always thought when froyo comes out everything will be working flawlessly. However I was terribly wrong.
When Froyo came out on February 24th 2011, I quickly updated my phone, little did I know it had a HUGE problem. It started powering off my phone again, I was a bit upset. I restored my phone to factory settings and still no luck. I then had no choice but to go back to ATT.
They told me many people are having the same issue. Froyo is the cause of the power off issue! I strongly suggest that nobody should update to froyo until its 100% fixed. They immediately gave me a new captivate, because you aren’t allowed to downgrade to 2.1.
I haven’t yet to test out the GPS, but hopefully its better then my other two. I’m also worried if my phone is even new because there’s this random Screen shot of the ATT store in my gallery. I kind of feel pretty bad going in there and asking for a new phone….. Anyways for those of you that having a working captivate, congrats.
p.s
samsung really fails somtimes.....
Same problem, I think, when 2.2 came out in Europe. It'll be fun to see if they get 2.2.1 out anytime soon.
The only way I've found to get reliable gps is to flash a custom rom.
cappysw10 said:
Same problem, I think, when 2.2 came out in Europe. It'll be fun to see if they get 2.2.1 out anytime soon.
Click to expand...
Click to collapse
Oh, wow, yeah it would be cool if they get 2.2.1 out fast.
bigbooty said:
The only way I've found to get reliable gps is to flash a custom rom.
Click to expand...
Click to collapse
I already did that, still did not help.
I returned my cap on Sunday for random reboot. Got another one and it got 0 satellites. I figured it was a fluke and went home to update to froyo. Still no lock. I called att to see about getting it replaced. After the phone call from hell (they wanted to troubleshoot data, even though i kept telling them that i had no data issues it was gps) I finally got to warranties. Phone arrives today. I am hoping this one works. I so am tired that they will not say it is a hardware issue. I love the fact that this thing is as hackable as it is. Holding out for the nexus s or galaxy s2.
In the midst of talking/venting at the tier2 rep, he did mention there were data issues with froyo. Wonder how long the fix will be. After seeing the samsung froyo getting pulled back so much for the other galaxy phones, I kinda don't blame the us carriers taking so long to get the stuff out. Then again that is a whole other argument.
Hi,
Sorry I've been away for a few weeks. I used to follow these threads like a hawk but I just got too busy with a huge dev project that ate my life like they can sometimes do... I read through threads about rooting 1.85 and unlocking...But I'm just confused. Sorry if this is redundant but...
I'm currently on 1.74 (if I'm reading that right, 1.73.502.1 710RD ... oddly enough I tried to update but it didn't let me... assuming that annoying message I kept declining for days was the 1.85 update).
Now I could go to check for updates again but I'm not. I figured I better ask around and see what the best course of action is.
I rooted a while ago when it was first available. So I have root.
So that's where I'm at. Now, my question is what's the best course of action?
Am I not able to update OTA to 1.85? Because I already rooted?
If I can check for updates and get the update, will it remove my root?
The last post in the 1.85 root thread says that they may have fixed their servers to avoid rooting 1.85??
Can I just now unlock my phone and flash ROMs? and not worry about carrier updates?
Is there anything I'm missing with the 1.85 update? That I couldn't get elsewhere?
I may or may not flash a ROM. I just don't want to be prevented from doing so if I want. HTC's Sense is not crashing like it used to, so I have no major need to flash a ROM yet... Improved performance would be the only reason. Maybe some development reasons as well.
Opinions?
Thanks much. I appreciate the help.
crap this isnt under general is it...
tom_m said:
crap this isnt under general is it...
Click to expand...
Click to collapse
Haha no it's not. Also, it should be under Q&A.
You can go ahead and unlock and flash a custom rom. There's no need to get the OTA (which would most likely make you go through the rooting process again). Since your'e already rooted pre-1.85 you can flash a rom and guarantee that you'll retain your root status.
:laugh: Suffer the wrath of trolls.
Nah, I would download the 1.85 firmware update RUU [ran from your computer to install instead of OTA] and root [SOON] or root / unlock bootloader / install custom recovery then flash a new rom. First idea for a rom would be CleanROM. If all you want is root status, I would start there because It gives you basically a clean slate with bloatware removed and some minor tweaks I believe. Otherwise you could use CM9 or one of the few other roms that you may like. Personally I get the best performance out of KingCobra's rom. So idk :b
Gotta add my two sense for unlock and flashing Sick Sense. Very smooth.
Sent from my HTC One X using Tapatalk 2
Thanks guys, sorry again for misplacing this post.
I think I might browse the ROMs then. I didn't realize there were already so many options. I thought the 1.85 update may improve my issues with the signal being lost...I have to turn on airplane mode and off again to reconnect to their network despite the 4G (and sometimes LTE) icons showing up the whole time...But I'm just thinking I'm unfortunate in that my apartment has poor signal. Though my wife's iPhone works just fine...Oh well.
Thanks again. Time to check out some ROMs. I definitely don't want to grab some update and get locked out of it all.
my vote goes to scott standard clean rom! it has eqs, and a couple other little tweaks, that way u can add whatever u want!
tom_m said:
Thanks guys, sorry again for misplacing this post.
I think I might browse the ROMs then. I didn't realize there were already so many options. I thought the 1.85 update may improve my issues with the signal being lost...I have to turn on airplane mode and off again to reconnect to their network despite the 4G (and sometimes LTE) icons showing up the whole time...But I'm just thinking I'm unfortunate in that my apartment has poor signal. Though my wife's iPhone works just fine...Oh well.
Thanks again. Time to check out some ROMs. I definitely don't want to grab some update and get locked out of it all.
Click to expand...
Click to collapse
I have had the same issues with data and have had my phone swapped twice because of it and the 1.85 update nor any of the other radios has made any difference so I would just unlock the bootloader, flash a custom recovery and then rom of choice.
tom_m said:
Thanks guys, sorry again for misplacing this post.
I think I might browse the ROMs then. I didn't realize there were already so many options. I thought the 1.85 update may improve my issues with the signal being lost...I have to turn on airplane mode and off again to reconnect to their network despite the 4G (and sometimes LTE) icons showing up the whole time...But I'm just thinking I'm unfortunate in that my apartment has poor signal. Though my wife's iPhone works just fine...Oh well.
Thanks again. Time to check out some ROMs. I definitely don't want to grab some update and get locked out of it all.
Click to expand...
Click to collapse
There is a new radio that should fix that stuff. Lemme find it. Here ya go. the latest ATT at the bottom. ATT 2.09 (0.17a.32.09.24_2_10.91.32.19L http://forum.xda-developers.com/showthread.php?t=1694012
This should help wifi and mobile data. I also replaced a phone because of the mobile data issues. New phone did it also. Once i installed 1.88 ruu it was all fixed. You dont have to install the ruu now. Just pick your favorite custom rom and then flash this radio. The radio from 1.88 fixes it also but its from an asia ruu,. This new ATT radio is promising, i'd go with that.. Thank Designgears for that leak
Clean rom is good. Sick Sense as well as King Cobra. I'm rockin the new king cobra 1.2 and its pretty amazing. Any of these roms will be much much much better than stock. Tons of great mods, Speed and stability is great with all of them. You will think your CPU speed doubled..No lies! Install Titanium Backup (purchase it) and back up all of your apps. If you get the paid version, you can restore them all to your new rom 1 touch. The free version you have to do each app 1 at a time.
Edit. Of course you are rooted. But did you unlock the BL through HTC Dev also? If you mentioned it i must have missed it. If not you need to do that first.
nugzo said:
There is a new radio that should fix that stuff. Lemme find it. Here ya go. the latest ATT at the bottom. ATT 2.09 (0.17a.32.09.24_2_10.91.32.19L http://forum.xda-developers.com/showthread.php?t=1694012
This should help wifi and mobile data. I also replaced a phone because of the mobile data issues. New phone did it also. Once i installed 1.88 ruu it was all fixed. You dont have to install the ruu now. Just pick your favorite custom rom and then flash this radio. The radio from 1.88 fixes it also but its from an asia ruu,. This new ATT radio is promising, i'd go with that.. Thank Designgears for that leak
Clean rom is good. Sick Sense as well as King Cobra. I'm rockin the new king cobra 1.2 and its pretty amazing. Any of these roms will be much much much better than stock. Tons of great mods, Speed and stability is great with all of them. You will think your CPU speed doubled..No lies! Install Titanium Backup (purchase it) and back up all of your apps. If you get the paid version, you can restore them all to your new rom 1 touch. The free version you have to do each app 1 at a time.
Edit. Of course you are rooted. But did you unlock the BL through HTC Dev also? If you mentioned it i must have missed it. If not you need to do that first.
Click to expand...
Click to collapse
I still have data issues even with the leaked radios.
Tiffany84 said:
I still have data issues even with the leaked radios.
Click to expand...
Click to collapse
What kind of issues? :crying: the same as before? they completely went away for me.:fingers-crossed: Have you seen anybody else still having issues with 1.88 or newer? Maybe you actually have bad hardware..coincidences happen.. I'd swap again if the new radios are working for most others. You paid to much for that phone for it to be poopoo.
nugzo said:
What kind of issues? :crying: the same as before? they completely went away for me.:fingers-crossed: Have you seen anybody else still having issues with 1.88 or newer? Maybe you actually have bad hardware..coincidences happen.. I'd swap again if the new radios are working for most others. You paid to much for that phone for it to be poopoo.
Click to expand...
Click to collapse
Well, I've swapped it 3 times now. The first one I do not remember having that problem. Not saying it didn't but I can't remember. I returned it due to random reboots. Other than that the 1st one was flawless. Ever since then the phones I've received and have swapped have an issue where if I got into work where I have a hard time getting a signal the phone doesn't automatically re-connect when I go outside and have great signal. Even though it shows I have 4g and full bars if you look in the settings menu at mobile network it says turning on instead of connected and the only way to be able to make or receive phone calls or text messages is either toggle airplane mode or reboot the phone. Problem now is I'm past my thirty days so it would probably have to be done threw the warranty and not an in store swap.
Wow, I'm sorta surprised there's not a USCC-specific thread anywhere yet...unless I just missed it, like I could well have.
Oh well, just thought it'd be nice to have a thread here at XDA, especially since it's so hard to find much of anything about USCC-branded phones in general anyway.
As far as my experience so far, I can't report any real issues beyond the usual so-so signal strength that I've experienced on every US Cellular phone me or my wife have owned ever since moving to my current location in town (yet it was fine at our old house just a few blocks over!). In the six years or so I've had USC, I've never found their phones being notably loaded down in bloatware, and nor is this one, so that's nice I guess. I was hoping I'd find some unlikely, overlooked USCC-specific perk like an unlocked bootloader on their models, but I don't see that happenin'... siiigh.
As for the phone itself independent of US Cellular, eh, I'm no power user, I'm probably not the dude who should make too many hardware-based critiques because the thing's more than powerful enough to ably do anything I'll ever need a phone to do. I will say I briefly owned an S6 Edge (briefly being because it was stolen) and I can't say the S7 seems like a huge upgrade to me, not one worth full retail anyway, but obviously it's a damn nice phone anyhow. (...But I went from my stolen fancy S6E down to an old, cheap Motorola Razr M (aka Electrify M) for a little over a year before getting my S7E and I was, for the most part, totally satisfied with the Motorola's performance despite the huge discrepancy in horsepower, so what the hell do I know?)
So yeah, bring on your USCC-specific guides, thoughts, questions, complaints, opinions, etc etc!
So I'll kick things off with a bit of root discussion/issues...
I rooted my phone maybe a week or so after getting it back in July, taking the chance against my better instincts that the instructions found over in this Verizon thread would work out for USCC phones too. Much to my surprise, not only did it work, I experienced almost none of the many problems that the Verizon users kept encountering in the early weeks of that thread. Why that is, though, I still have no clue. I guess VZW's software is somehow different from USCC's in such a way that we simply weren't affected by whatever kept causing the boot loops, extreme battery-drainage and heat issues for those phones. (Mostly...)
I don't want to steal the work of thread-starter psouza4 or anyone else in that existing Verizon thread so I don't want to try and rewrite every full detail but for any future USCC S7/Edge owners who might wind up here, I guess I'll do a real basic rundown of exactly how I did mine (and also I'll do it so that maybe someone more versed in Android-tinkering than me can tell me where I may have gone wrong on certain steps). The files I used in my root/fix/debloat process are the ones listed in Bold below and all can be found on that thread - I'd link 'em directly here but I don't know how kosher that is - and what isn't there should be in the Play Store.
So, after disabling "Secure Startup" under Settings-->Lock Screen & Security (and ensuring I had the correct drivers and ADB working and such), I...
1). Flashed the Samsung_G935x_QC_Rooted_BOOT.TAR image using the Odin3_v3.12_PrinceComsy.zip variant. The Verizon thread reports that some AT&T users had recommended the Comsy version because they found it prevented boot issues that they were experiencing when flashing with the other "plain" version of Odin that was linked. As for me, I only used the PrinceComsy version because the plain version simply doesn't run on my computer for some reason. I have no idea what the difference is between the two versions, so I've got no idea if the Comsy version may be the better way to go for USCC users as well (or if it even makes a lick of difference for anyone really), but it works.
2). After successful flash and reboot, I installed SuperSU-v.2.76-S7QC.zip via the included root.bat file and waited for another reboot to finish. I can't recall if SuperSU prompted me to download a newer version of the "su" binary upon opening the now-installed SuperSu app (as the original thread indicated it might) or not, but I didn't and neither should you apparently. As of the original post in the other thread on 7/15/2016, the "2.76-S7QC" build was the most recent version for S7 models . Since that's been over a month ago, can anyone verify if the current 2.78 version of SuperSU works with S7s (and/or USCC phones), or if there's a 2.78"-S7QC" version specifically? (I'm guessing no and no, but I lost track of the Verizon thread a while back and haven't seen any specific reference to 2.78 working or not working...)
3). From there, I downloaded FlashFire (v051, I believe) and flashed the suggested S7_or_S7Edge_Fixes_Debloater_V15.zip file, which aims to, y'know, fix some stuff and debloat the thing. I didn't manually adjust any of the "fixes" applied by the patch, and many of the apps and services killed by the "debloater" part of the script don't even come on USCC-branded versions of the phone. The instructions in the thread go on to say that some users reported problems with a handful of the fixes - Lag issues, Wifi passwords refusing to save, "Unauthorized Actions" pop-ups, and problems with VoLTE icons (the last of which isn't relevant to USC really anyway). While it seemed like the majority of VZW/ATT/other-carrier users in the thread were experiencing at least one of these issues, I didn't. There was some lag, for sure, but sporadically, and the remaining steps mostly knocked it out and I didn't need to do anything extra.
4). Next I installed a couple, but not all (initially) of the programs/settings suggested in the separate . Amplify Premium 3.3.7 and L Speed 3.1.9.7 (though I updated to the current 3.1.9.8 Beta shortly thereafter with no ill effects). Now I thought I followed the thread's suggestions pretty much exactly for these two, but when I looked just now to verify, I found that I hadn't made quite a few of the recommended changes in Amplify after all. (Probably because many of them give warnings when adjusting that the other entries hadn't, and I figured I'd play it safe). Anyway, I went ahead just now and finished everything up so that it does follow that thread's suggestions - I'll report back on it if they seem to make a notable difference. Maybe worth noting here that not all of the recommended changes are valid on US Cellular phones, so no need to worry if you can't find a few of them. As for L-Speed, I did indeed have all of the thread's recommended settings for it set, except for one, "Storage IO Tweaks: Partition Remount - Enabled." Not sure why this wasn't set, guess I just didn't see it the first time. Anyway, I've enabled it now, and since it seems to be there for "giving more permissions to the SD card," it was probably irrelevant to me anyhow since I don't currently use one.
Now, the guide suggests installing Xposed when you do all of this, along with three more apps - Greenify, ForceDoze, and LeanDroid. I decided to hold off on all the above for a while when I did it, but I'd say it's plenty safe to do it all in one go if you choose to. By the time I got around to applying the L-Speed and Amplify settings and rebooting, I had been up and rooted for at least a couple hours altogether, enough to notice that I wasn't seeing the immediate disasters a lot of other posters were finding. The most common problem seemed to be bootloops and random resets, which I hadn't encountered (and still never have really, beyond a couple of unexplained reboots once or twice that had no noticeable effects other than mild annoyance). There were also a lot of complaints about some rather extreme-sounding overheating, terribly reduced battery life, and serious lag problems - these all appeared in some degree, but seemingly nowhere nearly as bad as what people were reporting from their VZW/etc-branded phones in the thread. Plus, after making the L-Speed/Amplify changes, the battery seemed to be holding up a bit better, the phone wasn't running as warm as it had been pre-tweaking, and the lag I had experienced had calmed down from "pretty minor but definitely kinda annoying" to mostly gone. I wondered why I was missing out or getting much milder versions of all the problems mentioned by others, but by that point in the thread people were beginning to suspect Xposed was the cause. Some reported their phones working well up until installing Xposed, after which they'd begin getting bootloops or other problems. Not wanting any of that headache, I decided to just wait it out a few days and see how it held up before risking the install.
The guide also suggests at this point to turn off Wifi Scanning, Bluetooth, Location and Location History. I left the Location stuff alone, but this all seems pretty optional. It's also suggested to turn off the AOD Clock, which I left alone at the time but later disabled (and am now having issues with, but more on that later). I don't think there's any need to do the recommended disabling of all animations in Developer Options either, at least for our phones. I've left those settings at their defaults and speed's been fine.
So, since I basically took a break at this point when I was actually doing all this the first time, I'll take a break here too before getting into the next stuff I did regarding debloating and how my now-rooted-but-not-yet-real-tweaked USCC phone would turn out to actually run over the next few days...
I'm looking for a firmware which has european languages any idea?
Any new news on root and roms for our phones?
HavING trouble unlocking bootloader and flashing custom rom.
Is this possible yet? I've achieved root, But failed to flash twrp or cm. Any help would be appreciated!
lugnut2099 said:
So I'll kick things off with a bit of root discussion/issues...
I rooted my phone maybe a week or so after getting it back in July, taking the chance against my better instincts that the instructions found over in this Verizon thread would work out for USCC phones too. Much to my surprise, not only did it work, I experienced almost none of the many problems that the Verizon users kept encountering in the early weeks of that thread. Why that is, though, I still have no clue. I guess VZW's software is somehow different from USCC's in such a way that we simply weren't affected by whatever kept causing the boot loops, extreme battery-drainage and heat issues for those phones. (Mostly...)
I don't want to steal the work of thread-starter psouza4 or anyone else in that existing Verizon thread so I don't want to try and rewrite every full detail but for any future USCC S7/Edge owners who might wind up here, I guess I'll do a real basic rundown of exactly how I did mine (and also I'll do it so that maybe someone more versed in Android-tinkering than me can tell me where I may have gone wrong on certain steps). The files I used in my root/fix/debloat process are the ones listed in Bold below and all can be found on that thread - I'd link 'em directly here but I don't know how kosher that is - and what isn't there should be in the Play Store.
So, after disabling "Secure Startup" under Settings-->Lock Screen & Security (and ensuring I had the correct drivers and ADB working and such), I...
1). Flashed the Samsung_G935x_QC_Rooted_BOOT.TAR image using the Odin3_v3.12_PrinceComsy.zip variant. The Verizon thread reports that some AT&T users had recommended the Comsy version because they found it prevented boot issues that they were experiencing when flashing with the other "plain" version of Odin that was linked. As for me, I only used the PrinceComsy version because the plain version simply doesn't run on my computer for some reason. I have no idea what the difference is between the two versions, so I've got no idea if the Comsy version may be the better way to go for USCC users as well (or if it even makes a lick of difference for anyone really), but it works.
2). After successful flash and reboot, I installed SuperSU-v.2.76-S7QC.zip via the included root.bat file and waited for another reboot to finish. I can't recall if SuperSU prompted me to download a newer version of the "su" binary upon opening the now-installed SuperSu app (as the original thread indicated it might) or not, but I didn't and neither should you apparently. As of the original post in the other thread on 7/15/2016, the "2.76-S7QC" build was the most recent version for S7 models . Since that's been over a month ago, can anyone verify if the current 2.78 version of SuperSU works with S7s (and/or USCC phones), or if there's a 2.78"-S7QC" version specifically? (I'm guessing no and no, but I lost track of the Verizon thread a while back and haven't seen any specific reference to 2.78 working or not working...)
3). From there, I downloaded FlashFire (v051, I believe) and flashed the suggested S7_or_S7Edge_Fixes_Debloater_V15.zip file, which aims to, y'know, fix some stuff and debloat the thing. I didn't manually adjust any of the "fixes" applied by the patch, and many of the apps and services killed by the "debloater" part of the script don't even come on USCC-branded versions of the phone. The instructions in the thread go on to say that some users reported problems with a handful of the fixes - Lag issues, Wifi passwords refusing to save, "Unauthorized Actions" pop-ups, and problems with VoLTE icons (the last of which isn't relevant to USC really anyway). While it seemed like the majority of VZW/ATT/other-carrier users in the thread were experiencing at least one of these issues, I didn't. There was some lag, for sure, but sporadically, and the remaining steps mostly knocked it out and I didn't need to do anything extra.
4). Next I installed a couple, but not all (initially) of the programs/settings suggested in the separate . Amplify Premium 3.3.7 and L Speed 3.1.9.7 (though I updated to the current 3.1.9.8 Beta shortly thereafter with no ill effects). Now I thought I followed the thread's suggestions pretty much exactly for these two, but when I looked just now to verify, I found that I hadn't made quite a few of the recommended changes in Amplify after all. (Probably because many of them give warnings when adjusting that the other entries hadn't, and I figured I'd play it safe). Anyway, I went ahead just now and finished everything up so that it does follow that thread's suggestions - I'll report back on it if they seem to make a notable difference. Maybe worth noting here that not all of the recommended changes are valid on US Cellular phones, so no need to worry if you can't find a few of them. As for L-Speed, I did indeed have all of the thread's recommended settings for it set, except for one, "Storage IO Tweaks: Partition Remount - Enabled." Not sure why this wasn't set, guess I just didn't see it the first time. Anyway, I've enabled it now, and since it seems to be there for "giving more permissions to the SD card," it was probably irrelevant to me anyhow since I don't currently use one.
Now, the guide suggests installing Xposed when you do all of this, along with three more apps - Greenify, ForceDoze, and LeanDroid. I decided to hold off on all the above for a while when I did it, but I'd say it's plenty safe to do it all in one go if you choose to. By the time I got around to applying the L-Speed and Amplify settings and rebooting, I had been up and rooted for at least a couple hours altogether, enough to notice that I wasn't seeing the immediate disasters a lot of other posters were finding. The most common problem seemed to be bootloops and random resets, which I hadn't encountered (and still never have really, beyond a couple of unexplained reboots once or twice that had no noticeable effects other than mild annoyance). There were also a lot of complaints about some rather extreme-sounding overheating, terribly reduced battery life, and serious lag problems - these all appeared in some degree, but seemingly nowhere nearly as bad as what people were reporting from their VZW/etc-branded phones in the thread. Plus, after making the L-Speed/Amplify changes, the battery seemed to be holding up a bit better, the phone wasn't running as warm as it had been pre-tweaking, and the lag I had experienced had calmed down from "pretty minor but definitely kinda annoying" to mostly gone. I wondered why I was missing out or getting much milder versions of all the problems mentioned by others, but by that point in the thread people were beginning to suspect Xposed was the cause. Some reported their phones working well up until installing Xposed, after which they'd begin getting bootloops or other problems. Not wanting any of that headache, I decided to just wait it out a few days and see how it held up before risking the install.
The guide also suggests at this point to turn off Wifi Scanning, Bluetooth, Location and Location History. I left the Location stuff alone, but this all seems pretty optional. It's also suggested to turn off the AOD Clock, which I left alone at the time but later disabled (and am now having issues with, but more on that later). I don't think there's any need to do the recommended disabling of all animations in Developer Options either, at least for our phones. I've left those settings at their defaults and speed's been fine.
So, since I basically took a break at this point when I was actually doing all this the first time, I'll take a break here too before getting into the next stuff I did regarding debloating and how my now-rooted-but-not-yet-real-tweaked USCC phone would turn out to actually run over the next few days...
Click to expand...
Click to collapse
Any updates on how this is running on USCC devices.
It's running beautifully for me. I haven't went through the entire guide for the improvements with the extra apps, but root and xposed are perfect. I am using the ForcedDoze app and it does help, without causing any issues.
Sent from my SM-G935R4 using Tapatalk
barndawg76 said:
It's running beautifully for me. I haven't went through the entire guide for the improvements with the extra apps, but root and xposed are perfect. I am using the ForcedDoze app and it does help, without causing any issues.
Sent from my SM-G935R4 using Tapatalk
Click to expand...
Click to collapse
Hello? I'm new to USC. Want to get one off ebay. Seller says AT&T works on it. Does it mean phone is sim unlocked? Considering USC is CDMA?
I'm not sure about that. Check with the USC guys over at teamuscellular.com It should be possible, but I don't want to steer you wrong.
Sent from my SM-G935R4 using Tapatalk
Yikes, sorry for never finishing that initial post, everyone. Nonetheless, most of it would be outdated by now anyway, and though it ran well-enough for a while after some more tweaks that I never got around to describing here, it was still never a fully satisfying experience just due to the inherent jankiness of the Engboot root. (And it gradually ended abruptly in a softbrick). I haven't kept up with developments on S7 root at all really, though I thought I saw something in regards to a new root method a while back - anybody know on that?
Anyway, here's what I found works much better, though still Engboot-based - the Stang5liter custom ROM found here - https://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
All of the frequently found issues with Engboot root - heat, lag, battery life, etc. - were pretty much immediately greatly improved when I installed it. "Improved," not "gone" - they do still exist to a degree which some may find unacceptable, but if you don't expect 100% perfection, you shouldn't have any problem with it. The issue I notice most on this ROM is lag, but this tends to happen mostly only when attempting to do a lot of tasks quickly, opposed to just here and there all the time randomly the way it often seemed before I switched to the Stang ROM. Oh, and for whatever reason, it kinda frequently runs crappy while charging, but that's really a minor annoyance. The biggest plus of all, however, is that you don't need to waste hours tinkering with arcane settings like before to create minor improvements in performance - all the tweaks are integrated into the ROM, so you pretty much just install it and forget about it. Overall besides the lag I've been basically problem-free with it, especially in regards to heat, which I always had varying issues with on "plain" Engboot root. It's worth noting too that I'm still using the v1 version of stang5litre - v2 is current and was released a while back, I just never upgraded out of sheer laziness and the "good enough for me" status of v1. I will probably try to upgrade finally this week sometime, so if I do I'll note any improvements/problems here.
The caveat that you may have noticed here is that Stang5litre is a Verizon ROM intended for the SM-935V. The good news is that it runs just fine on our SM-935R4 without any adjustments - I don't think I even had to tinker with the APN. Your phone may exhibit some Verizony characteristics - your phone will identify itself as a Verizon phone, for one - but you should be good. If you want to root, this is the best way to go that I've found, plus it's quick and easy.
(Oh and hey, has USCC pushed Nougat yet?)
No, no nougat. No root for nougat anyway, so no real rush to see it.
Sent from my SM-G935R4 using Tapatalk
Any idea of when nougat will be released for this phone? I'm using one and live in Malaysia. Haven't receive nougat. Really want to have it. Dont really care about rooting, etc
A US Cellular version? In Malaysia? You are in the wrong thread my friend.
Sent from my SM-G935R4 using Tapatalk
Just wanted to let you guys know this works on our variant of the S7 Edge.
https://forum.xda-developers.com/showthread.php?t=3552824
I flashed with Flash Fire and mounted system as read/write without any issues and it definitely makes a big difference in sound output.
Try at your own risk!!, but is working on my rooted US Cellular S7 Edge running PK1 firmware. Gonna try the dual speaker sound mod next and will update here if it works.
The dual speaker mod also worked for me, link below. I am using windows 7 professional 64-bit.
https://forum.xda-developers.com/showthread.php?t=3494412
Here is something else I found that works on the the edge panel to control your music. I only tested with Spotify, as that is the music player I always use.
https://forum.xda-developers.com/showthread.php?t=3365528
Sentm my SM-G935R4 using Tapatalk
Sent from my SM-G935R4 using Tapatalk
huszonnegy said:
I'm looking for a firmware which has european languages any idea?
Click to expand...
Click to collapse
Hi, did you find a solution?
Anyone taken the Nougat update yet? Just wondering how its running for you, if so.
Sent from my SM-G935R4 using Tapatalk
My wife set the update to install tonight,I have yet update ,liking my rooted mm, will update on how she likes it in a few days.
Sent from my Nexus 6 using Tapatalk
Yeah, I'm kinda hiding out for a more stable Nougat root, but I don't thunk we'll see one.
Sent from my SM-G935R4 using Tapatalk
The wife took the update and is really liking her battery usage. Said it is lasting way longer before needing charged(no definitive proof here. just what she said). She is trying to get use to the ui changes. So i decided to go ahead and update mine as the last week or so it has been lagging more than normal and eating battery. So i downloaded our firmware from updato.com and flashed with odin 3.12.3 and used the home.csc so not to lose any apps and data(had everything backed up with titanium in case of issues). All went well and was running fine so i decided might as well root and see how that goes. Rooted using this thread https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502 and i used the alternative root.bat listed in the op(post #688) i also did the suggested cache wipe and leave the phone for 5-10min, i waited at least 10 watching a youtube video. Have been running all day with no noticeable lag and decided to download Antutu and do a test,pulled a 132374. I know that benchmarks dont mean dudu but to me it verified it is running as fast and smooth as it seems. So far i have no complaints and have not found anything not working properly.
Just an update, the update and root on nougat apparently broke the fingerprint sensor. Only had 1 app I use that on so no biggy for me.
Sent from my SM-G935R4 using Tapatalk