Develop Bugs

EVO HW003 Nova Random Reboot

My girlfriend's HW003 Nova EVO is in a state of random reboot. I have run out of ideas.
It is not OS dependent, meaning I have gone through 3 different ROMS including stock rooted.
There are 6 log files below. They are logcat files right before the phone kills the connection.
Knowing that the ROM is not the cause, I am down to Radio, WIMAX, GPS, WIFI, or CPU/MoBo.
I executed the gpsclrx command and it had no effect on the random reboots.
Is anyone else having the same issue? Have you exchanged your phone at a Sprint location? What have you done?
http://www.andrewdefilippis.com/uploads/Documents/Restart_1.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_2.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_3.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_4.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_5.txt
http://www.andrewdefilippis.com/uploads/Documents/Restart_6.txt
Sent from my HTC EVO via XDA App

003 / Nova
I have some random reboots as well, thought it was related to temp but after a while that seems to not be the case. Happens on every ROM and seems to happen 9/10 times when browsing. Stock Browser / Dolphin HD. Reason I thought it was a temp thing was I started noticing a light spot on the screen, evidently above the processor, and so I figured something had to be happening with it all.
Have been meaning to start calling around about it and see if it's something Sprint can replace or not. Am more than prepared to pay the deductible, but I haven't really made steps to get to the bottom of it.
It's strange because when I think I realize what is doing it, it ends up not really seeming to be the case. It all started happening when I had a bad wipe / flash (clockwork) and it started happening then. Lost my RSA Certs (not a huge thing, obviously something I'll need to address at some point but currently using CM6 so I'm not really "missing it." But that's when it all started happening. So I guess in that regard, the WiMax shouldn't necessarily be an issue ... or so I would think. Happens when on WiFi and off, happens whether GPS has even been turned on at any point or not so I figured it had to be some CPU issue but not necessarily due to heat.
Know this probably doesn't help, but I thought I'd post.

have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?

Exchange the phone?
Sent from my PC36100 using XDA App

Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC

just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.

conqu1stador said:
Right, naturally that'd be the next step.
Have tried nearly all ROMs without app restoring or even downloading, including not restoring system data.
sent from my SUPASONIC
Click to expand...
Click to collapse
If you have setcpu installed, I need you to go to the info tab, scroll down and tell me what value is next to memtotal. It should be 425000.
Let me know what yours is.
Sent from my HTC EVO via XDA App

omegasun18 said:
have you tried seeing if it reboots with out apps installed? not sure if she uses setcpu or other similar type apps that could cause issues. I used to get random reboots too especially when i would run certain apps while i was over clocked.
and this may be a stupid question if so sorry but you are wiping between roms and you are NOT restoring system settings from a back up after you do correct?
Click to expand...
Click to collapse
This issue is ROM/APP independent. There is no connection to 3rd party software or os.
Sent from my HTC EVO via XDA App

No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC

lgevo said:
just curious what recovery are you using? Maybe u should try to wipe with a different recovery and flash a new rom.
Click to expand...
Click to collapse
Gah, just saw this sorry for double post. Issues all starred after bad flash after bad wipe with clockwork. Using amon now, 1.7. Have yet to update to 1.8.
sent from my SUPASONIC

conqu1stador said:
No setcpu, and I've never used it. :embarrassedface:
Have never used a log cat but I could always try and see what happens...?
sent from my SUPASONIC
Click to expand...
Click to collapse
The reason why I was asking you to check the info tab for the memtotal value, is because on my phone, currently I am not having a problem and the value is 425000kB , but on my girlfriend's phone, it registers only 424840kB.
Sent from my HTC EVO via XDA App

Alright, will look for the one on these boards.
Hate to even go here, but I really never used a logcat before; but my phone just rebooted and I went immediately into the logcat and just like when I launched it at first there is just a wealth of information. I see it says ;
D/alogcat ( 521): stopping ...
D/alogcat ( 521): resumed
Might sound dumb, but am I to assume that's the point the log stopped and began again, due to the reboot? Would think it is .... on to that setcpu I guess.
edit: seeing that stopping and resuming in multiple spaces, guess that's not it. =/

setCPU - memtotal; 424828 kB

conqu1stador said:
setCPU - memtotal; 424828 kB
Click to expand...
Click to collapse
Alright. I need more people with HW003 Nova EVOs to check the same, and say if they are having reboots. This could be corrupted or bad memory.
Sent from my HTC EVO via XDA App

i have hw 02 but my memtotal is 424832... does that matter?

????
i have hw 02 but my memtotal is 424832... does that matter?

I think this may be a HARDWARE issue...
Hello xda folks,
Long time reader, first time posting...
I'll try and condense this down, everytime I try to post something xda says I'm not logged in, so I'm keeping it short out of re-writing frustration.
I'm HW003, I lack setcpu, so I can't really check my memtotal, but I believe that in short the flash mem/nand memory may be getting damaged or corrupted by flashaholics like myself. I'm curious to see in any non-root users have experienced the completely random reboots like some of us here.
Let me be clear about one thing, I'm describing random rebooting, not consistent bootloops, at least they weren't at first.
Initially, I thought this problem was a byproduct of OC'ing, or overheating the unit, but I have flashed every combination of rom, kernel, OC/stock, hboot ver, etc, virtually anything I have some control over, and the phone still reboots. Ive even rolled back to stock unrooted, and tried bone stock 2.2 but the phone keeps throwing a fit.
Everything on this phone hardware wise screams "I was manufactured on the cheap, and put out to stores on the quick", so it stands to reason there is some kind of failure taking place.
I'm no expert, but I've flashed this thing A LOT. Probably around 100 times.
It also seems to be getting worse, as it often sticks in bootloops now, not just random reboots. Causing me to have to flash it on an even more arbitrary basis!
Next step for me, is rolling back to stock 2.2{Again}, and sending this bad boy back to where it came from, and wait for my POS replacement and its new set of shenanigans. I will root the new one once, pick one rom, and flash it once...
It will be difficult, but I will be attending Flashaholics Anonymous.
We can do this together.
Anyone have a more logical answer?

WiFi goes to sleep when phone is locked

So after the screen goes off, the wifi automatically goes to sleep hence making those apps which can send toast/tile notifications like Flory and various twitter apps practically useless. Any work around?

Keep it plugged in.

Um...you just realized that? It puts wifi on standby (basically turns it off) when it goes to sleep, unless you are charging, in which case, the wifi remains connected. Data, on the other hand, does not have this problem, and will persist, despite the phone going to sleep/lockscreen.

I would also like a workaround for this... I don't own a data plan, and I'm pretty much always near some wifi connection...
thanks!

There is no work around. It is a 'feature' by design so that you won't ended up with a battery drained phone. Your only hope is complain loudly to Microsoft.

foxbat121 said:
There is no work around. It is a 'feature' by design so that you won't ended up with a battery drained phone. Your only hope is complain loudly to Microsoft.
Click to expand...
Click to collapse
As usual with WP7, MS is taking "don't give a choice to the user" approach... I hope this and other small things get fixed sooner or later... like the stupid camera shutter sound!

kapanak said:
Um...you just realized that? It puts wifi on standby (basically turns it off) when it goes to sleep, unless you are charging, in which case, the wifi remains connected. Data, on the other hand, does not have this problem, and will persist, despite the phone going to sleep/lockscreen.
Click to expand...
Click to collapse
Well if you're connected to WiFi but its in sleep mode, data doesnt just turn on. It will for some things, but I found out that for some games that have push notifications, they just dont happen in that situation. The 3g stays sleeping with the WiFi. I only get emails in this situation.
banvetor said:
As usual with WP7, MS is taking "don't give a choice to the user" approach... I hope this and other small things get fixed sooner or later... like the stupid camera shutter sound!
Click to expand...
Click to collapse
I thought the shutter sound was become of some law saying you have to have it on. Weird thing though, that law ain't in the US...I read that sht on cracked where they were talking about countries saying you have to leave the shutter sound on and that's to prevent people from getting away with sticking their phone under a girls skirt and taking a picture. Normally I'd be like "man, cracked is just making stuff up again" but I've been following that site for 3 years and read everything and can tell the joke articles from the legit ones.

And they probably dont have that many options because they dont want to see a lot of people complaining about battery life. Because if you google anything android related, you'll get a bunch of battery life threads and complaint. so they are just defaulting settings that offer the best battery life and they are getting rid of the option to change those settings. that way nobody can post a bunch of threads complaining about battery life and by that not happening, when you search anything windows mobile related you'll see more threads about its features than bad battery life.
And yes, if WiFi never slept, it would be using more power than the disconnected 3G option it defaults to.

having wifi turn off automatically completely defeats the purpose of background notifications for apps like twitter/facebook or any other IM since there wont be any wifi connection for them to use if the phone is in sleep mode. Not everyone has unlimited cellular data. This is just really stupid.

ammarmalik said:
having wifi turn off automatically completely defeats the purpose of background notifications for apps like twitter/facebook or any other IM since there wont be any wifi connection for them to use if the phone is in sleep mode. Not everyone has unlimited cellular data. This is just really stupid.
Click to expand...
Click to collapse
If those background notification use that much of data, they are not designed properly. For comparison, my son's Focus is on 200mb/month data plan and he never exceeds the data limit.
Sent from my SAMSUNG-SGH-I897 using XDA App

maybe they should have an option to change it - but it should default to the current settings as only a handfull of people won't have a data plan.

ms79723 said:
I thought the shutter sound was become of some law saying you have to have it on. Weird thing though, that law ain't in the US...I read that sht on cracked where they were talking about countries saying you have to leave the shutter sound on and that's to prevent people from getting away with sticking their phone under a girls skirt and taking a picture. Normally I'd be like "man, cracked is just making stuff up again" but I've been following that site for 3 years and read everything and can tell the joke articles from the legit ones.
Click to expand...
Click to collapse
Wow, that's just weird. How come so many compact digital cameras can have the shutter sound removed then? It doesn't really make sense... anyway, I saw in the Reg Tricks topic a way to turn it off, will probably do after I get the NoDo (in a year maybe? hehehe)
Back to topic: sure the default should be the same as it is now, but give me the option to change it, and when I select it, give me a big warning telling me that this will destroy my battery life. Then I know what to expect (ok, I would already know, but many people wouldn't...)

banvetor said:
Wow, that's just weird. How come so many compact digital cameras can have the shutter sound removed then? It doesn't really make sense... anyway, I saw in the Reg Tricks topic a way to turn it off, will probably do after I get the NoDo (in a year maybe? hehehe)
Back to topic: sure the default should be the same as it is now, but give me the option to change it, and when I select it, give me a big warning telling me that this will destroy my battery life. Then I know what to expect (ok, I would already know, but many people wouldn't...)
Click to expand...
Click to collapse
Found the article. Had to go back and look for it because after my last post I thought I made it up but I was right haha. And it seems to say just cellphones. I imagine it would be really hard trying to stick a camera under someone's skirt...so they just leave the option to remove that sound there...iunno

banvetor said:
Wow, that's just weird. How come so many compact digital cameras can have the shutter sound removed then? It doesn't really make sense... anyway, I saw in the Reg Tricks topic a way to turn it off, will probably do after I get the NoDo (in a year maybe? hehehe)
Click to expand...
Click to collapse
what's weird is that my HD7 doesn't make the shutter sound when i turn the volume all the way down to 0
also, topic related, my ipod touch stays connected to wifi 24/7 sleep or no sleep... i think that feature came with iOS 4 though??

Your iPod Thouch doesn't have any other means to go online. Your phone does.

ms79723 said:
And they probably dont have that many options because they dont want to see a lot of people complaining about battery life. Because if you google anything android related, you'll get a bunch of battery life threads and complaint. so they are just defaulting settings that offer the best battery life and they are getting rid of the option to change those settings. that way nobody can post a bunch of threads complaining about battery life and by that not happening, when you search anything windows mobile related you'll see more threads about its features than bad battery life.
And yes, if WiFi never slept, it would be using more power than the disconnected 3G option it defaults to.
Click to expand...
Click to collapse
Yep, cause changing the default search in IE from Google to Bing, where it should be, will certainly degrade my battery life.
The options are there because Microsoft have no clue what they're doing.
I'm willing to bet most of the people who worked on Windows Mobile are gone and these people working on WP7 are utterly clueless.
They're certainly disconnected form their customer base... completely...

N8ter said:
Yep, cause changing the default search in IE from Google to Bing, where it should be, will certainly degrade my battery life.
The options are there because Microsoft have no clue what they're doing.
I'm willing to bet most of the people who worked on Windows Mobile are gone and these people working on WP7 are utterly clueless.
They're certainly disconnected form their customer base... completely...
Click to expand...
Click to collapse
you mean the customer base that was running away from winmo in droves and led to a less than 3% marketshare???
Sent from my HTC HD7 using Board Express

Hello all,
Does anybody know if this problem has a solution with the NoDo update (presumably, NoDo comes with "wifi improvements")? I tried WP7 for a while and this was the failure that made me switch back to Android (I work in lots of basements; no GSM signal, but Wifi aplenty).
Thanks!

linj said:
Does anybody know if this problem has a solution with the NoDo update
Click to expand...
Click to collapse
It's not a problem - it's a "feature". Features don't get fixed.

radeon_x said:
It's not a problem - it's a "feature". Features don't get fixed.
Click to expand...
Click to collapse
Fantastic... Normally, though, that's true for "bugs," not "problems."
Well, I was unable to find any information one way or the other; this seems a lesser priority for many users. If anybody in the thread has updated, please let us know!

[Q] Will no data connection for days wreak havoc for the Epic?

I went to Mexico for a week recently and turned off the data connection on my phone to avoid data fees. I planned to use my phone for GPS and maps since I didn't have Mexico map data for my Garmin. Everything worked fine for about 5 days and then suddenly I started getting FCs on everything and the phone became unusable and eventually required a complete rebuild. I rebuilt using the new EC05 and then loaded Syndicate ROM 1.1.0 and have had no problems since. When I had this issue I was using EB13 with Syndicate ROM 1.0.1 flashed on top of it.
I have no idea what caused this but it was a major pain not having a phone until I returned. Some idea I had were that some application that like to check for piracy couldn't connect to the market and after a few days went haywire. I also think it may have been the ROM but I was using it fine for a couple weeks prior to the trip.
Any ideas on what went wrong for me?

How were you using the navigation system without data? Unless you have a program that already includes all the maps stored on the phone you were probably still using data.
And, no, I don't believe shutting off the data caused your force close issues.

You stated you were using SRF 1.0.1, and as that rom has journaling disabled, it is very likely that an improper shutdown/reboot or a problem with an app may have caused data corruption, which will cause all those FC's.

socos25 said:
How were you using the navigation system without data? Unless you have a program that already includes all the maps stored on the phone you were probably still using data.
And, no, I don't believe shutting off the data caused your force close issues.
Click to expand...
Click to collapse
I was using Gaia GPS which allows you to store maps on the phone and I downloaded maps for the entire area before leaving. That part actually worked very well while it was working.

Dude like the mexican water never let your phone drink mexican data.... you'll only get force closes and will need to do a ##786# and enter msl code and reformat your phone to like new condition.
Also you use ext4 which only lasts for a few days. You need to reset your phone. Only use ext4r with jourling on or stop using custom roms as they all have issues like ext4 bug. I using stock and not one issue. Can't say that with custom roms.
Sent from my SPH-D700 using XDA Premium App

Koadic said:
You stated you were using SRF 1.0.1, and as that rom has journaling disabled, it is very likely that an improper shutdown/reboot or a problem with an app may have caused data corruption, which will cause all those FC's.
Click to expand...
Click to collapse
Interesting insight. I'm supposing journaling was disabled to increase performance/disk space usage? Before this happened I turned my phone off and on to conserve battery life, then finally when turning it back on it went berserk and after that it was toast until I could Odin it. I didn't notice a bad shutdown and I never had to remove the battery or anything unusual to restart the phone. If this happens again is there a way to get the logs off the phone for some analysis? I use CatLog to find issues now but that assumes the phone is mostly operational. If I have a bad application that is causing this I'd like to contact the author or remove it. I've since discovered CWM backup/restore and I hope that will help me if it happens again. FYI, I'm a little new to Android and I'm sure that shows in my reply but I've been using Linux for 13 years now and am a software developer. This is my first Android phone.

epicblows said:
Dude like the mexican water never let your phone drink mexican data.... you'll only get force closes and will need to do a ##786# and enter msl code and reformat your phone to like new condition.
Also you use ext4 which only lasts for a few days. You need to reset your phone. Only use ext4r with jourling on or stop using custom roms as they all have issues like ext4 bug. I using stock and not one issue. Can't say that with custom roms.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
"Also you use ext4 which only lasts for a few days."
Is that for real? I could see a catastrophic shutdown corrupting the filesystem but your response makes it sound like it could fail at any time with no cause. That is very consistent with what I experienced though.
I like the Syndicate ROM and would like to continue using it so I'll look at turning the journaling on like you mentioned. But in the end I came from Windows Mobile to Android for stability in my phone. Using custom ROMs and tweaking my phone might seem dumb considering stability is my highest priority but it's in my nature to take things apart and tinker with them. In the end I will revert to stock ROM if that is the only long term stability I can find.

I really don't know what epicblows is talking about. Journaling, like the name implies, creates a journal of the changes you make before actually executing the action. Say for example, you are playing a game straight through and get to level 6, then suddenly you drop your phone and the battery pops out. With journaling on, you can likely restart your phone and get back to level 6. No journaling, you will likely be right back to level 1. Journaling slightly slows the system because it has to write information to the journal before it executes the command. I have not heard anything about a bug inherent to ext4. There are plenty of stable roms here such as Bonsai, Shinigami and UrbanLegend. I have used those myself and had great stability. They are really stripped down roms with most of the mods done under the hood to improve stability and performance. I have used other roms but prefer these for their barebone approach.

epicblows said:
Also you use ext4 which only lasts for a few days.
Click to expand...
Click to collapse
I call BS.
I ran EXT2 for MONTHS with no issues on both my Moments, and have run EXT4 on my Epic since it was first released.
I have done battery pulls several times, and for the most part, have not run into any issues I could trace back to EXT4.
If your EXT4 build is not lasting more than a couple days, YOU must be doing something wrong to cause the issues, IMO, not EXT4 itself.

I also like the stripped down nature of the ROMs found here. I don't particularly care for NASCAR, I have my own channels for accessing football information, and so on. After using Syndicate ROM I would only reluctantly go back to stock as a last resort. Based on my problem do you think the CWM backup/restore would fix that problem that I described? If I can fix my phone on the road that would be good enough disaster recovery for me.

DCRocks said:
I call BS.
I ran EXT2 for MONTHS with no issues on both my Moments, and have run EXT4 on my Epic since it was first released.
I have done battery pulls several times, and for the most part, have not run into any issues I could trace back to EXT4.
If your EXT4 build is not lasting more than a couple days, YOU must be doing something wrong to cause the issues, IMO, not EXT4 itself.
Click to expand...
Click to collapse
I agree about the nature of software errors. As a junior developer 15 years ago I would always find problems with the compiler I was using, or the OS, etc. After some time I came to realize that my problems were always related to some oversight/misunderstanding on my part. Since Gingerbread is set to use ext4 I was having a hard time accepting that it is fundamentally flawed, but then again I'm new to the Android world, and ext4 is new for Android. It is good to know there are people using ext4 for months with no problems.

If it ever happens again I would recomend just applying your clockwork /data backup. This will usually fix your force closes and other problems from data corruption due to improper shutdown. That's the bad part of running with journaling disabled. It is quick to restore a nandroid backup though and will save you the hassel of a full reformat.
Sent from my SPH-D700 using XDA App

DCRocks said:
I call BS.
I ran EXT2 for MONTHS with no issues on both my Moments, and have run EXT4 on my Epic since it was first released.
I have done battery pulls several times, and for the most part, have not run into any issues I could trace back to EXT4.
If your EXT4 build is not lasting more than a couple days, YOU must be doing something wrong to cause the issues, IMO, not EXT4 itself.
Click to expand...
Click to collapse
Well bs it is not. Ext4 is flawed with out journling on. I would say it is worth any performance hit to not lose your mind about force close. I use stock and not a single issue
Sent from my SPH-D700 using XDA Premium App

In approximately 30 seconds, a spammer will post "fifth post" below me.

k0nane said:
In approximately 30 seconds, a spammer will post "fifth post" below me.
Click to expand...
Click to collapse
Mandro1d said:
fifth post
Click to expand...
Click to collapse
I'll be here all week, folks.

brian0wens said:
...Since Gingerbread is set to use ext4 I was having a hard time accepting that it is fundamentally flawed, but then again I'm new to the Android world, and ext4 is new for Android. It is good to know there are people using ext4 for months with no problems.
Click to expand...
Click to collapse
Ext4 itself isn't really the problem, it is the fact that journaling was disabled added to the fact that there was obviously some event that caused the data corruption (whatever that may have been). While ACS is looking into getting their newest version with journaling enabled working, you can always effectively reenable journaling on their non-journaling rom by doing a full backup in clockwork, and then do a full restore, which should provide an additional safeguard to help keep something like that from happening again.

I tried over 20 ROMs in 2 weeks to solve a Serious Problem with Screen

I have a serious problem.
I have HTC Evo 4G, My screen is getting dim (NOT BLANK), I cant see screen in bright sun, It's really dark.
But this happen only Sense based ROMs, but this doesn't happen with Cyanogen or MIUI.
I have tried many sense-based ROMS ( Infected, Runny, MikG, ICS,...etc).
With every Rom, I flashed it many times, sometimes with wipe everything. I though it's hardware problem why this doesn't happen with ASOP ROM. (I don't like Cyanogen, or MIUI... LOL), Also, I tried every setting related to brightness But the problem still.
I've read every thread, article about similar problem, but useless.
For additional info about my problem: after starting up my phone, Every thing is OK, but after screen off for first time the screen getting so dark.
(Only one workaround I found, Just set "Screen always on") I'm going to kill my Evo.
Please Help me, I'm getting Crazy.

Forgive my week English.
I'm not going anyway, I'll stay here, Refresh this page every 5 Seconds, till i get a solution.
Please help me.

menu-settings-display-turn off automatic brightness and turn brightness all the way up....?

Thank you for your replay.
Sorry I forget to tell you I tried this, I set brightness so high, but nothing happen.

beezy69 said:
menu-settings-display-turn off automatic brightness and turn brightness all the way up....?
Click to expand...
Click to collapse
Sorry I forget to tell you I tried this, I set brightness so high(100%), but nothing happen.

Please help me, I still waiting for replay

What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue. I replied to your other thread as well and copied the response here as well in case you didn't check the other thread, for future reference one post is enough and double posting will more than likely end up getting your flamed and trolled pretty hard

-EViL-KoNCEPTz- said:
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue. I replied to your other thread as well and copied the response here as well in case you didn't check the other thread, for future reference one post is enough and double posting will more than likely end up getting your flamed and trolled pretty hard
Click to expand...
Click to collapse
sorry for double post, I thought the other place is better, and I really suffer from this proble.
It's Ok, the other post is enough.
http://forum.xda-developers.com/showthread.php?p=21324350#post21324350

Yea always remember to only post once and in the proper section or some ppl will flame you up and troll your thread ;-)

Battery and stability issues with new ICS

I've updated from a rooted stock GB ROM to the ICS update. I'm surprised this is the update Sprint/Samsung released for the phone. The GB ROM was stable and clean, this one seems to have some issues... primarily:
1) Battery life is 6-7 hours LESS - at least.
One thing I've noticed here is that "Android OS" is using about half of the battery. Previously (and confirmed with my buddy with his GSIII), this only used about 4% or 5% . I suspect this is a culprit.
I've attached some screenshots showing this.
Almost no use of the phone all day, I was at work - some light texting later in the day. So little that SMS or GoSMS don't even appear on the chart.
2) Swype keyboard issues.
Yes, you can clear your app cache for swype and get it to work. However, you apparently can't get copy/paste/select word/select all to work.
When you click on text and click the little handle that appears, only a small box appears above, which is where the menu should be for copy/paste/select word/select all should be. At least I think that's the options - from memory, since I don't have them any more. :crying:
I've attached a screenshot showing this.
[EDIT: This is a usage issue - I consider this more difficult than before, and quirky in that it doesn't always work, but generally if you press and hold text, it'll open an edit panel where the notification bar is. Sometimes double-clicking works.]
3) Signal issues.
Again using the Battery screen - I'm seeing some very odd patterns both with carrier data signal and wifi. Previously, carrier signal was an uninterrupted line, of varying shades of green that corresopnded to signal strength. Now, when I look at this line, there's some very good sized breaks in it. That's a sharp contrast to how it used to be.
I know that searching for signal can use battery - maybe an issue with the radio? modem?
Same for wifi - I used to have a setting for "wifi off when screen off". Now it's gone, or changed - I see a "wifi on while sleep" that is checked. Despite this setting remaining constant, I see periods where that seems to be happening (later), but also a long period where wifi is active despite the screen off.
I've attached a screenshot showing this. See the "mobile network signal" line in the plot.
4) General, observed quirkiness.
Screen not being as responsive. When I press the power button on my phone now, it takes 2 or 4 seconds for the screen to activate. Touching the screen sometimes results in a very laggy response... enough time to poke the screen a second time. Skippy/unsmooth screen transitions in some cases. I've had GoSMS vanish on me a couple times and I had to relaunch it. Other apps become unresponsive and I've had to hit the home button repeatedly - sometimes 10-15 seconds before the phone comes back to the home screen and out of that app.
The screen captures were taken throughout the day - the times appear on them.
I've also attached two BetterBatteryStats dump files - one of them I had all options checked, the other just the defaults. They were taken about the same time, and about the same time I took the 8 hour screen cap.
If it matters, I'm using Go Launcher EX, it's still my stock launcher. I'm noticing not many people on ICS using it - are there known problems?
This is frustrating to me - I use this phone for work, I came off an AOKP ROM to get back on a stock ROM, for two things:
1) stock stability and battery life.
2) the Exchange account options for sync scheduling (on peak/off peak schedules for sync) that only seem to be in the stock ROM.
[EDIT: I performed a full factory wipe several days ago, and reinstalled all apps via market, and still are experiencing these exact symptoms. No improvement. May restore my nandroid from before the wipe just to gain back a few things I inadvertently lost as this didn't resolve anything.]
Accordingly, I'd like to see this ROM working. Any thoughts on these?
Anyone else observing these symptoms, relative to the stock GB rom?

5) GPS changes/bugs
I've also noticed some GPS changes / bugs that I'm not liking.
The GB GPS sucked, now this one seems worse:
Driving tonight, I had to reboot my phone to stop my eternal wait for "searching for GPS" in the car. No different than I've occasionally had to do with the GB rom.
However, then when I made a couple wrong turns or deviations from the route, it got stuck on "recalculating". Eternally.
I know I was in an area with good data, because I exited the Navigation app, relaunched it and picked the last destination and it calculated the new route instantly. It didn't successfully recalculate once... three times I had to restart the navigation app.
Also - the old navigation app used to tell you "...in a quarter mile, exit on..." and "...in 100 feet, turn onto..."
This new navigation app does no such thing. It just says "turn right on _____ street". Which is useless if there's no street sign (hence several of my "recalculating" incidents).

Bump - anyone experiencing these bugs? I haven't seen them reported - any of them.
Looking for something to try to resolve one, or all of them.
Any suggestions are appreciated, thanks.

geolemon said:
Bump - anyone experiencing these bugs? I haven't seen them reported - any of them.
Looking for something to try to resolve one, or all of them.
Any suggestions are appreciated, thanks.
Click to expand...
Click to collapse
I have had HORRIBLE battery life since the upgrade. It is worse than half of what I was getting prior to ICS
My GPS is working like a bauce though, finds my locations within seconds.
My boss got the upgrade last night and has Go Launcher and their suite of products on his device and he can't send texts now

I feel accomplished if I've stumped all of XDA... :silly:
I did discover a workaround for the copy/paste/select issue - long pressing in ICS opens a menu at the top of the screen for that.
However, still stumped on
1) 6-7 hour battery life reduction
3) signal issues
4) Quirkiness/freezing/sputtering responses
5) GPS issues - both signal and new app
Anyone else but me experiencing any others besides #1?

geoleomon - I would suggest grabbing XDA's version of Better Battery Stats, and monitoring your battery life that way rather then using the Android version.
But yes, I have experienced some of the battery issues, just no where near to that extent (maybe 4 -6 hours less).

GH0 said:
geoleomon - I would suggest grabbing XDA's version of Better Battery Stats, and monitoring your battery life that way rather then using the Android version.
But yes, I have experienced some of the battery issues, just no where near to that extent (maybe 4 -6 hours less).
Click to expand...
Click to collapse
Where do I get that one? (I paid for the full version of the Android market version)
What's different about it?

geolemon said:
Where do I get that one? (I paid for the full version of the Android market version)
What's different about it?
Click to expand...
Click to collapse
Nothing, except this one is free.
http://forum.xda-developers.com/showthread.php?t=1179809

Hmm.. Weird I've had the ota installed for a day now and my Android os is averaging 10-15% at the most
Sent from my SPH-D710 using Tapatalk 2

GH0 said:
Nothing, except this one is free.
http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
I've previously posted my results from the paid full version of the app... see the original post, two text files attached.
(one complete, one over-complete)
Anything out of the ordinary in there? What should I look for?
thanks-

Another piece of the puzzle:
I was using the camera, and it crashed - an error I didn't capture but something like "media server crashed - camera must restart". Happened twice before the camera actually started OK. Perhaps significantly, I had the phone docked when I fired up the camera - desk dock.
Also, noticing that listening to music in my desk dock at work, several times now the song has just stopped playing a few seconds in, and the media player closes. I restart the music player, and everything is OK. Sometimes that happens 2 or 3 times before the player works again, and then sometimes it'll happen an hour or so later even after it does start working again.
Could this be related?

try this then report back I have none of these issues you speak of but I am generally in a good signal area. Your signal looks awful, defiantly will cause battery drain.
http://forum.xda-developers.com/showthread.php?t=1721229

riggs170 said:
try this then report back I have none of these issues you speak of but I am generally in a good signal area. Your signal looks awful, defiantly will cause battery drain.
http://forum.xda-developers.com/showthread.php?t=1721229
Click to expand...
Click to collapse
I used the "nodata" version of that kernel to install CWM after rooting.
This will wipe my phone, which I'm looking to avoid doing if possible, if that's not the "nodata" version I already have.
Can you clarify on what you are advising?
Interesting though - a coworker suggested possibly if I wipe my phone it might clean things up.
I have just cleared my Dalvik cache, however I believe I did this before. I'm doing this now noting that as per my prior post, I'm seeing a few things force close, or else stop suddenly (like music player) without closing.
Also using CWM to "fix permissions" (not quite sure what this means).
We'll see what my results are after this.
I'd like to get this stock ROM working well if at all possible - if for no other reason than the Exchange peak/off peak email sync settings that don't seem to exist in other ICS ROMs.

I wish a mod would sticky a battery life complaint thread and close all others. Every other thread is an ics battery life complaint.
Sent from my SPH-D710 using Tapatalk 2

geolemon said:
I used the "nodata" version of that kernel to install CWM after rooting.
This will wipe my phone, which I'm looking to avoid doing if possible, if that's not the "nodata" version I already have.
Can you clarify on what you are advising?
Interesting though - a coworker suggested possibly if I wipe my phone it might clean things up.
I have just cleared my Dalvik cache, however I believe I did this before. I'm doing this now noting that as per my prior post, I'm seeing a few things force close, or else stop suddenly (like music player) without closing.
Also using CWM to "fix permissions" (not quite sure what this means).
We'll see what my results are after this.
I'd like to get this stock ROM working well if at all possible - if for no other reason than the Exchange peak/off peak email sync settings that don't seem to exist in other ICS ROMs.
Click to expand...
Click to collapse
using nodata is you're problem, all of the issues you've described could be caused by using nodata, this is why it is advised in almost every roms dev thread to do a full wipe, not no data... you may be able to get away with it without any serious bugs upgrading the same rom one revision but not going from gb to ics. you need to do a full wipe and fresh flash, legacy gb app framework is causing these issues, not ics
kingsway8605 said:
I wish a mod would sticky a battery life complaint thread and close all others. Every other thread is an ics battery life complaint.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
SERIOUSLY! i dont get why people come to xda to whine about the OTA, XDA is the place you come not to run stock... And half the threads that arnt about battery life/"bugs" where the poster provides only basic anecdotal "evidence" and no technical data whatsoever on FF18 are gripes about sprint and sprint related issues... have people never heard of the sprintusers forum, THATS where those complaints belong, not here

cp320703 said:
using nodata is you're problem, all of the issues you've described could be caused by using nodata, this is why it is advised in almost every roms dev thread to do a full wipe, not no data... you may be able to get away with it without any serious bugs upgrading the same rom one revision but not going from gb to ics. you need to do a full wipe and fresh flash, legacy gb app framework is causing these issues, not ics
Click to expand...
Click to collapse
Thanks for this part - however...
The very advantage of going the OTA (or at least stock - I didn't OTA it) stock route is to not clear the phone.
Samsung/Sprint spent how many months developing this, to provide an update that's supposed to be clean for existing, non-technical, non-rooted, mom & pop users. I wanted to go this route simply as the "cleanest" option. And I've got lots set up on my phone and very little time around now - I'd prefer not to lose it if I can avoid it. As much as you try to back up, and remember, and all that, every time you wipe you forget something...
It's a little bit like being a Jeep owner, and saying "you know, everyone could get away with driving a Jeep".
Sure... they could... but they wouldn't all enjoy it, and it really wouldn't fit everyone's use case.
Usually, advise like this really just reflects a lack of vision: "I can't imagine anyone who uses their phone different than ME".
cp320703 said:
SERIOUSLY! i dont get why people come to xda to whine about the OTA, XDA is the place you come not to run stock... And half the threads that arnt about battery life/"bugs" where the poster provides only basic anecdotal "evidence" and no technical data whatsoever on FF18 are gripes about sprint and sprint related issues... have people never heard of the sprintusers forum, THATS where those complaints belong, not here
Click to expand...
Click to collapse
Does this look like whining, or seeking a solution? Hey, look - the original post!
geolemon said:
...This is frustrating to me - I use this phone for work, I came off an AOKP ROM to get back on a stock ROM, for two things:
1) stock stability and battery life.
2) the Exchange account options for sync scheduling (on peak/off peak schedules for sync) that only seem to be in the stock ROM.
Accordingly, I'd like to see this ROM working. Any thoughts on these?
Anyone else observing these symptoms, relative to the stock GB rom?
Click to expand...
Click to collapse
Again - seems more and more like you are a child, not only lacking maturity, but injecting your own prejudices rather than reading.
I'm seeking solutions.
And XDA is the place for options. Solutions are a subset of options.
Grow up.

I wasn't referencing you as whining at all, however this thread belongs in the Official OTA thread, not on its own, that's what the commenter prior to me and I were both refrencing- the constant new threads about the same 3 or 4 issues with the OTA when there is already a thread for it... that said you said you're seeking solutions, I offered you one that will work, I'm sorry that it displeases you, but doing a full wipe and a clean install will solve pretty much every issue you have, so backup your apps, and text messages if you want those as well, it takes less than 5 minutes in titanium backup and SMS backup, and do a clean flash or Odin (if flashing make sure you are on a safe kernel). That will fix your problems, its silly to keep asking for solutions when the best and most likely to be successful one has already been proffered.... or should you still for some reason not want to do this just unroot and take it to a sprint store, they'll do a factory reset, that'll fix all of the issues you're having. Save the time and effort and just do it yourself, no one is going to post any magic advice that'll make it all OK with nothing unchanged
Sent from my SPH-D710 using xda app-developers app

cp320703 said:
I wasn't referencing you as whining at all, however this thread belongs in the Official OTA thread, not on its own, that's what the commenter prior to me and I were both refrencing- the constant new threads about the same 3 or 4 issues with the OTA when there is already a thread for it... that said you said you're seeking solutions, I offered you one that will work, I'm sorry that it displeases you, but doing a full wipe and a clean install will solve pretty much every issue you have, so backup your apps, and text messages if you want those as well, it takes less than 5 minutes in titanium backup and SMS backup, and do a clean flash or Odin (if flashing make sure you are on a safe kernel). That will fix your problems, its silly to keep asking for solutions when the best and most likely to be successful one has already been proffered.... or should you still for some reason not want to do this just unroot and take it to a sprint store, they'll do a factory reset, that'll fix all of the issues you're having. Save the time and effort and just do it yourself, no one is going to post any magic advice that'll make it all OK with nothing unchanged
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I'll try it... just want to make that the last resort.
Wouldn't you consider it to be equivalent to just wiping/factory reset via CWM?

geolemon said:
I'll try it... just want to make that the last resort.
Wouldn't you consider it to be equivalent to just wiping/factory reset via CWM?
Click to expand...
Click to collapse
yup wiping in cwm will do it, again be sure you're on a safe recovery eg. agats or chris41's... things like the force closes of music player and the malfunctioning of swipe, camera, etc, are due to coming from gb without a full wipe... i do realize its a PITA if you wanted to keep it simple, but it is what it is you know... insofar as battery I've never had a problem running ff18 based roms such as blu kuban or goodness, I've never run bone stock myself but if you continue to have issues there are tweaks, such as kobridges and phakers scrips that'll help out a lot, in addition to disabling unnecessary syncs, etc... however after giving it a few days to settle I've not had any problem getting a full day of moderate use out of ff18 based roms...
just to add a little more, fixing permissions will help a little with force closes... if you are unfamiliar with the UNIX permission system you can find some good info here ( http://www.perlfect.com/articles/chmod.shtml ), however it would still probably be best to to a wipe as it most likely won't fix all the bugaboo's you have from keeping your gb /data partition... despite what the horrid touchwiz interface would have you believe ICS is a huge step forward from GB, and that old app data can and will cause problems... lastly sorry if i came off a bit gruff, as I'm sure you've picked up I'm somewhat tired of seeing threads about the OTA, however to your credit you did post tons of concise, detailed info and were open to suggestions, I've seen similar thread where the OP just posts something akin to "ICS data sux, wtfff????" and when recognized devs tell them what they need to do they start to argue, which makes no sense to me... I was most likely taking my frustration at those threads and their apposition to the purpose of XDA out on you, for that I apologize, good luck with it and should you need further help let me know, I'd be glad to assist or at least point you in the direction of information that may help

This thread seems to have gone off the rails a bit... All the answers you seek are in development op. It requires reading though... There are roms and explanations for every problem you listed. If you say no they're not... Then you have not taken the time to read... Simple as that... I am a developer here and no one taught me anything. I READ AND LEARNED IT. i have a family and a life and the whole bag... So there are no exscuses. I challenge you to take the time to read and learn and give back. Maybe YOU can find the answera to your questions and post the answers here so you can help someone else who will post this and that doesnt work (but does, they just didnt read and learn how to fix it). Because as soon as you post it someone else will have the same complaints and questions and will be to lazy to search...