First, a bit of background. My wife won't let me root her Epic, mostly because she's had to return it 3 times for hardware failures and it's annoying to have to wipe the phone each time.
I told her to hold off on downloading the OTA update to Gingerbread, to make sure there aren't any crippling bugs that show themselves after the masses get a hold of it.
Is there any reason that she should stay away from the OTA update?
None go ahead and update
Sent from my Nexus S 4G using xda premium
I'm not rooted, updated to GB, but I'm getting random reboots and freeze ups (had to pull battery each time). Other than that it's good to go. Battery lasts longer, but WI-FI range decreased.
If she won't let you root it and put on a GOOD ROM then the next best thing is the OTA so go ahead. It is easier to root on froyo and then flash a GB ROM though. I know a few "stockies" and they love it. No issues with their phones at all.
Before I rooted, EI22 was fast and stable. But I was getting problems keeping the GPS connected and WIFI was not as stable as in froyo. The only other problem I noticed is not being able to change the volume while the phone is next to my ear. Rooting and installing ACS ICS solved most of these
Don't wipe you're phone after the
Update, it will break wifi.
Sent from my Epic 4G using Tapatalk
Ha-ha. My wife is the same with her epic.
Upgrade to gingerbread. It's much better even in stock form.
Sent from my SPH-D700 using XDA App
I'm on stock GB, lets see ..
1. weak GPS (i've never had gps issues before)
2. keyboard lag on physical keyboard
3. screen likes to come on during calls and then my cheek hangs up on people (lots of fun)
4. screen loses responsiveness randomly
at this point i'm ready to drop kick the phone out a 5 story window. so my personal recommendation is if you aren't going to use a rom, stick with froyo. also word just came out that there is a already a new 2.3.6 version of GB coming for the epic. Hopefully this update will fix some of these issues.
wife did OTA upgrade to gingerbread without my approval.
My wife has the original Epic and did the OTA upgrade herself, but has been complaining that battery life is far worst. It's been about 2 weeks maybe.
So I did a factory reset and so far so good. However, it's only been a few hours since I wiped it so only time will tell. I'm told wifi is buggy now from reading other posts, and will report back on that aspect.
If the battery life still suck, I'm going to be forced to root this damn thing and flash it with a battery saving rom.
Any suggestions? I'm new to the OG Epic when it comes to modding.... I'm on a rooted EpicTouch via Starburst.
going to start looking for a stable rom.....
thanks!
Thanks everyone. I kinda figured that there would be some common issues with gingerbread that they'll need to release a maintenance update for in a couple weeks.
I've been running CleanGB on mine and it's been awesome.
oh yeah i forgot to mention weak wifi. i can be 10 feet from the router and get 1 bar on wifi.
I used the flash update for GB that was posted here a while back and I can't say I've noticed any considerable improvements or diminution in quality apart from the GPS which appears worse than before. Battery life may be a bit better than it was under Froyo but there's no real incentive to upgrade from Froyo as far as I can tell.
A friend who installed via the OTA has been dealing with very poor battery life ever since - he says that Android System usage is up over 64% and is awake time is considerably longer than the time is screen is on for whatever reason. He told me he normally leaves GPS on all the time but the usage shows very minimal resources going to GPS. also, he never turns on WiFi and he's in a very strong signal area.
Wifi is fine here. Solid connection from a story away. If. I'm in the same room I get full bars and 65mbps link.
Also zero reboots on two household epics since the update.
But dude, you've got to put on a kernel to fix the keyboard. My wife thought I was a god when I did that for her on froyo, there was no question it had to be done again in gb. She sends hundreds of texts a week (over 2k texts in a month not uncommon) and the keyfix saves what must add up to hours a month in retyping.
Running swupdate or odin takes 5 minutes, tops 10...
Sent from my SPH-D700 using XDA App
I just got the message that I could install Gingerbread, but then it failed. Not sure why but Clockwork broke it.
So my question is, does GB fix the bluetooth problem involving wiimotes?
If she won't let you root it, then go ahead an OTA, if she has issues *let's hope so* then you'll be able to root and fix her issues.
Sent from my SPH-D700 using XDA App
I have the same issue. My wife has an Epic and she doesn't want me to change from stock. We just did the OTA GB update about a month ago and it broke a WHOLE bunch of stuff.
1) Random mic feedback/squealing.
2) 3G turns off unexpectedly, so when 4G isn't available we get no data service.
3) Gmail contact sync broke, getting google.apps. error message.
About to throw this thing off the roof. Maybe I'll convince her to let me go to Cyanogen 7.
I think most had all these issues because ota updates imo are a horrible and unreliable way to update. Especially updating over existing data from a previous build of android. Yea it sucks starting over, but... when you do it wipes everything clean and I rarely hear of people have those issues when it's done that way. I had issues myself at one point. Did a fresh odin install, formatted data, updated, formatted data again, then reinstalled everything fresh and haven't had any issues since. Like no issues at all.
Sent from my SPH-D700 using Tapatalk
I updated from Stock EC05 (Froyo) to stock EI22 (GB) as soon as the google download was available. That should be the same as OTA. I was in a rush b/c I tought the stability of GPS and bluetooth was bad on Froyo. I was wrong. The GPS was completely unusable after the update--GPS apps usually froze within 5min (GPS Status & CardioTrainer) and required multiple reboots to fix. Just a mess.
I was planning to do a factory reset and a clean install, but then I stumbled across GPS_fix for EI22. So I flashed the GPS_fix and it was stable after that.
After investing the time with time making sure I understood the process and how to back up and restore everything that was important to me. It is pretty painless.
Initially I did not consider rooting b/c that would preclude software support by Sprint. Well the couple times I went to the store for that, I was not impressed. If I know zero, I they know less than zero. So that is worthless. So why suffer for $100/mo when I don't need to. And Sprint still gets $100/mo, a Win-Win.
CWM5/CleanGB 1.0
Root it and throw CleanGB 1.0 on it in the middle of the night after backing up everything so she doesn't know you did anything to it. After she says how nice the new "Update from Sprint" is, then tell her you rooted it.
Problem solved!
Sent from my SPH-D700 using Tapatalk
Related
How wide spread are these issues. I'm on my 3rd phone now and a side from an annoying dead pixel my phone still fades in and out while on voice calls to the point where I can't even catch a full conversation sometimes. Also drops calls.
The OTA did not help the problem one bit.
Is this something that will be/could be fine tuned? I've read the nexus never had a good radio compared to "other" phones.
As much as I like this g2 I can't have the poor voice quality issues.
Sent from my T-Mobile G2 using XDA App
For me, the radio got a tad better after the ota. I still get **** reception at home, but now it seems like it doesn't drop signal like before, but then again, I just installed the ota and rooted last night on the stock rom.
Sent from my T-Mobile G2 using XDA App
I got lucky the first time through, my hinge was pretty tight, i had 3.2 gb free space in my phone, and had one one minor antenna issue. Once a week or so I would drive somewhere and when I would look at my phone i would have an X and no bars. Only way to fix it was to restart, since it only happened once a week i didnt really bother with it. The OTA Fixed that problem so im just very lucky this phone around
ps: jk about the 3.2 gb, i got around 1.3 gb like everyone else
I am still seeing radio issues after the OTA. By switching it to airplane mode, then back to non-airplane mode (versus a rdeboot), the issue is temporarily resolved. Makes me think its a s/w issue with the radio. During the initial release I had to reboot to get a lock on GPS (a few times).
Hoping cell reception gets fixed in an upcoming OTA. Sucks having worst reception than my G1. Until then, wifi calling is saving the day at my house.
The only thing we can do is keep complaining and hope they listen.
-oldsk00lz
Sent from my T-Mobile G2 using XDA App
Sounds like it might not be a specific phone issue.
I really want to keep this phone but the radio is unacceptable! My wife's BB gets 3g throughout the house, and not only that she can talk on it without issues....
oldsk00lz said:
I am still seeing radio issues after the OTA. By switching it to airplane mode, then back to non-airplane mode (versus a rdeboot), the issue is temporarily resolved. Makes me think its a s/w issue with the radio. During the initial release I had to reboot to get a lock on GPS (a few times).
Hoping cell reception gets fixed in an upcoming OTA. Sucks having worst reception than my G1. Until then, wifi calling is saving the day at my house.
The only thing we can do is keep complaining and hope they listen.
-oldsk00lz
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Same with me for the most part. I just did the airplane mode trick, and it's the first time I've had to since the OTA. I have had the data drop plenty of times since the OTA, but after a few seconds it would come back again. The OTA was supposed to address this radio recovery problem, but clearly it didn't fix everything. I think I'm going to call customer service again and let them know.
On a side note I believe the issue I had today was with the XP tether driver. I think it's rather buggy as it tends to get stuck connected regardless if there is a phone tethered to the computer, and I have to restart! I still have had the data connection drop since OTA, but it usually fixes itself.
Hi,
ever since last week when I updated to 2.2.2, my battery life has been crap. In the half hour it takes me to get ready and drive into work, the battery goes down to 60%. with 2.2.1 it was like 98% so something is messed up.
Nothing else has changed, no new apps.
I did the froyo update manually so I sort of know the mechanics of the process but I'm just wondering if I need to go back to stock and then to froyo and then the updates or if I can just download the 2.2.1 image and update with it.
thanks,
I have the same problem :/
Obvious answer but have you tried a factory reset? I would take a stab at it before using more aggressive solutions.
Failing that you can flash a stock rom using the passimg.zip method and OTA back up but at some point you will be back on 2.2.1 and getting nagged to update to 2.2.2 again.*
*It could be that i'm using the European varient of the firmware but i've not had the best of luck flashing back to older versions (It's a long story). Suffice it to say, every method failed at some stage so i flashed a 2.2.2 stock/custom ROM instead.
I'm getting consistent 20hrs+ to 30% running CM7 nightly. Can understand wanting to keep it simply stock and CM7 is pre alpha but my battery performance is about double.
Sent from my Nexus One using XDA App
HTCinToronto said:
I'm getting consistent 20hrs+ to 30% running CM7 nightly. Can understand wanting to keep it simply stock and CM7 is pre alpha but my battery performance is about double.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Did I understand you correctly? You could only get 10 hours of your battery on stock rom?! And is there really a positive difference in CM7 battery performance? I know that some people (including me) had problems with that on CM6 so in my eyes CM is not the most battery efficient rom. Just curious..
About OP's battery problem. My N1 no different than before 2.2.2 update. Battery life seems the same. +1 for factory reset.
Cheers!
it could be time to root and go cutom
I had the same problem
And found out that it was google syncing (which i could not fix whatever i did). I wiped everything and started again.
This fixed it, however here are some tips to get good life on the nexus.
(This worked for me and saw my nexus 1 last 1.5 - 2 days before getting to 30%)
1: goto dial pad and do the *#*#info#*#* under phone set it from WCDMA to GSM perfered
2: Always use wifi where you can, wifi uses less battery than 3G, (this was a major saving in battery power for me) Set your wifi to always on (even when the screen is off). The 2 main places you spend most of your time is at home and work, set it up for those places and you will see your battery lasting a crap load
(my battery went from a drain of 7% a hour down to 2-3% by doing this).
I have a non-rooted stock NS on 2.3.3 and the phone was just sitting on my desk doing nothing when I felt it vibrate. I picked it up to check for a text or email, but the phone was instead rebooting.
Has this happened to anyone else on this build? I have had the phone reboot while in call before, but never just sitting there in standby.
This happens to me in 2.3.2. I will have the phone just sitting there and it will randomly just be rebooting. Its not frequently enough to bother me yet but it happens on and off.
Sent from my Nexus S using XDA Premium App
same here on 2.3.2.... thats why I wanted 2.3.3. Ill wait patiently for the nightlies to include it.
happened to me many many times on 2.3.2, but not 2.3.3. knock on wood
Happened to me...2 times already...never on 2.3.2...im rooted though
Sent from my Nexus S using XDA App
This happened to me like 2x a day with 2.3.2.
Hasnt happened once yet with 2.3.3.
I never got reboots in-call, though I did get them a couple times when I overloaded the phone's RAM.
Mine just rebooted in 2.3.3. I'm also getting "Can't connect to camera" anytime I use the Amazon barcode app which worked perfectly in 2.3.2.
Haven't tried the new update yet
Sent from my Nexus S using XDA App
I never had the in call rebooting, just overloading reboots on my nexus s. I have yet to have one since the update, but it has only been a little over 24 hours. Then again this has been happening to me since updating my nexus one be it stock, rooted, or CM6 FRF91 and FRG83D or any form of gingerbread I've used on it. The only thing I can say it it started in froyo for me.
Sent from my Nexus S using XDA App
on the new update havent had any issues.
I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App
MacGuy2006 said:
I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .
He's not rooted dude. Btw I get a reboot on every call. On cm nightly, no matter what I try/flash
Sent from my Nexus S using XDA Premium App
I just had reboot one time with 2.3.3 but I was running all processes 72 hours, without stopping and it suffered a lot !!!
deeren said:
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .
Click to expand...
Click to collapse
Nope.
It happens to 2 Nexus S, both stock, not even rooted. One barely has additional apps, too.
I think a lot of people don't notice the reboot, because it is silent, so if you are not looking at your phone exactly at the particular time it reboots, you wouldn't know it.
The inability to dial at times is much more annoying, IMO: you punch in a number, the phone tries to dial, then hangs up. At the same time, there are 3-4 signal bars. When it happens, it normally takes several tries to get it to work.
The crashing camera also doesn't happen every time, but it is definitely a new bug in 2.3.3.
Just had my first random reboot on 2.3.3 while phone was sat on my keyboard while at my PC.
Rooted detoxed Rom stock
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
This dim reboot screen thing used to happen quite a bit on my g2 in its early days, got it launch day. OTA fixed it.
Sent from my Nexus S using Tapatalk
fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
I am still hopeful, but I am losing some patience with Android.
The platform seems to be all about selling the newest hardware, but the user experience is definitely below that of the iPhone. I keep hoping that the next Android OS upgrade will close the gap, but....
The iPhone 5 will have 4" screen, with Apple's better screen aspect ratio. If it only did Flash....
Anyway, the Nexus S is really the best user experience Android has to offer, and it's overall fine. Except when it acts like WM6.
For some reason my EVO keeps restarting randomly on me, and all the time too.
I'm running CM7 7.0.3.1 and savaged zen 2.2.0, and I have an extended battery and I rum juicedefender.
Now I don't think its the battery because I've had it for month
Its most like savagedzen 2.2.0 but idk maybe its CM7 too.
I think this started after I started playing words with friends. Doesn't seem like a memory intense app and I never had this happen but lately its been rebooting randomly, like I'm download from the market. Internet, and even posting this thread!
Basically I'm thinking of switching to either virusrom or Mik, which is better?
Sent from my dope fly fresh EVO
my chick is having the same issue. hers just reboots at random after starting to use her pandora app about a week ago.
her evo is running:
Mod version: CyanogenMod-7.0.3.1-Supersonic
Kernel version: [email protected]#1
Ditto
I have same problem, and have tried various ROM's, most recently a complete wipe as per Mikroms instructions. Only pattern I can make out is it tends to start when the CPU is stretched a little, such as running Tango over 3G, or even Angry Birds for over ten minutes. Once it starts though, it reboots several times before it finally quits.
There was another thread on this, but no solutions, instead it turned into an argument over whether it is CM7 fault; not very constructive. I have tried different batteries and changed up CPU speeds, still to no benefit.
Like I said, if I don't tax the system I have no problems, and that so far has been my only solution, but a disappointing experience with my Evo.
My dad's kept rebooting too even after the gingerbread OTA. He is running a bone stock phone(not even rooted)
Wife is having the same issue on her stock EVO with the new OTA
same issue here, playing WWF,stupid zombies or surfing the web. on decks rom and on the gingerbread 2.3 stock.
Apparently, this is a common problem with the EVO. Mine started as soon as I accepted the recent OTA update. There is an XDA thread somewhere. Just do a Google search.
Same here & 2 of my other friends. I am on my 3 or 4 EVO (lost count) & everyone does it. This is only one I rooted as well. I noticed it does it less (once every few weeks to a month) with a custom non cm rom. Also restart your phone at least every couple of days (usually I did every day). It works out pretty well. What I tell my friends don't hesitate to tell sprint you have a issue so it gets documented. So you have proof to fall back on when you had enough. It's not like you pulling one over on them. They see if you have all these issues for so long why just now saying so. I have found that for some reason phone resets in middle of calls multiple times same day with certain Bluetooths. I drive truck for living so I on phone alot with customers/work/friends/family/etc. Always Bluetooth, and did up to 5 times a day. Then bought one top of line (jawbone icon &now Bose) and doesn't do it like that anymore. Hope this helps any of you. & again any issues you get tell sprint. Last time I got a new EVO in box, & they let me keep my old one. So gave it to my mother. Then had it replaced under her #.
Sent from my EVO using Tapatalk
Mine started out with a reboot
every so often. It finally got so bad it would reboot over and over until I pulled the battery for a few. Somewhere in the process, my GPS crapped out as well. It would work for a few minutes and then freeze. Not a good thing when you are not from Boston and trying to navigate 8am traffic to get somewhere.
I got a refurb as a replacement. It was in perfect shape and only had like 111 minutes of talk time. No telling why it was sent back but I've had no issues with it.
Mine is doing this too.. its annoying Ive restored backups and it just keeps rebooting, i dont know whats wrong. Im on avaFroyo 2.2
I don't remember where but there is a thread about this very topic. From what I read this was attributed to a corrupt data partition. My gf phone is starting to have this problem. Only fix I have read so far is to reroot phone and take it to sprint. I am waiting til they can root the ota. Then I will unroot her phone and get a new one.
Tim
Sent from my PC36100 using Tapatalk
Essentially I am just posting this to get my count up so that I can post in the development section.
I have been using the Droid 2 since October 2010. 9 months is the longest time I have ever kept the same model. Prior to that the longest was 1 to 3 months. Even though this phone doesn't work perfectly, the length of time I've been able to endure its use says a lot.
I had my device rooted within a few weeks of acquisition. When the GB leak came out, I had it instantly.
I am still kind of confused as to why I was too scared to install a custom rom. My first rom was Liberty GB .8 And naturally it was AMAZING and EASY. I love the liberty toolbox. My battery life was insane! So many configurations and options built in! I figured if one rom was this great, why not try more...I then tried the latest APEX rom. To me, that rom seemed a little slower than liberty, so I reverted to liberty immediately. Only one known bug presented itself, and that was the adjusting of volume with a bluetooth device, the call would end. After a few days of use, I decided to take the plunge to the almighty Cyanogenmod7...
The installation process was really easy. I already had the sbf files downloaded from switching to the newer rooted GB leak. After sbf'ing z4 root would not work, so I just used the easy one click pc method.
Installing nightly updates every morning probably isn't necessary but that's what I've been doing. I gotta say, I can't wait for a stable release of this rom. I think that this rom probably isn't for the average consumer, and to definitely experiment with something like Liberty first.
There are a few things that aren't quite up to par with this rom (which will be fixed with time I know). The camera app on this rom is actually not that bad. I have gotten used to it. But I can tell that when I have it set on 5MP, that the picture quality is not as good as the stock app. The flash is also not as bright, and I have seen a setting to tweak that, just need to get around to doing it.
With Liberty, I was honestly able to make it 36 hours without having to recharge my device, and was using it heavily (gps always on, bluetooth connected, navigating, phone calls, texting tons, etc). However, with cm7, even with sync off, bluetooth off, and brightness set to low, the battery seems to just fade away, even after re-calibrating it. And yes I am sure the fact that the battery percentage is in the notification bar, that being able to see each percent, might have a little to do with it. Even with the governor set at 600mhz, and profiles with setcpu, still crummy.
Anyway, I am thankful to no longer have problems with my keyboard backlight, and having the ability to use wireless tether, and netflix. (And I don't want to hear any negative remarks about it, because I constantly use wifi when I can, and I rarely reach 1GB of data use). My phone now runs FAST.
Alright, only 9 more posts like this to go.
So, overall, you would recommend Liberty above the others at this time?
If it came down to battery life as the biggest concern, by far, liberty. Its pretty darn fast too. But if you have an extended battery and are able to endure a few kinks for a short time, then try CM7.
Sent from my DROID2 using XDA App
Speaking of, I went back to Liberty! May go to 0.9 but the changes aren't that significant. It was nice to be able to cm7>LGB without sbf'ing!
Sent from my DROID2 using XDA App