Develop Bugs

OTA update issues/bugs

after searching the forums, i'm kind of surprised that nobody has brought to the attention any bugs that were caused after the OTA update. here's my problem:
after purchasing the htc evo and applying the OTA update, i have been having a few issues with the phone:
1 - home screen notification bar does not work. unable to slide the notification bar down with the phone is upright. it does, however, work in landscape mode. the only way to open the notification bar is to tap the menu button and select notifications.
2 - when opening the camera or camcorder and tapping the arrow on the left side of the screen in landscape mode to change the camera settings i notice extreme lag. i haven't found a way around this yet either.
i did try a hard reset with both of the issues but no luck.
i did notice that these issues did not exists before applying the OTA update. i contacted sprint and they played dumb and told me to take it back to the sprint store where i purchased the phone and have them look at it. they seem to believe that it is also an OTA update bug. being that i have 30 days to return the phone(they are currently out of stock)i told them that i would wait until the 2.2 froyo update on june 23rd and see if that fixes the issue. however i have done a lot of searching on the internet and only came across a few other forums(none in xda-developers) where people were describing the same issues that i am having, and after everyone has contacted htc as well(including myself) we have not yet gotten any response from them. i will post any news i hear from them as soon as i do.
also there is an issue i believe everyone to be having even after the OTA update which is that apps begin to run in the background even after force closing them and killing the process using any task manager. if anyone has any current fixes please post them and help us all out. i do believe the first 2 issues that i described are pretty wide spread, but i'm assuming that they are new to the android OS and really aren't aware of how to use the notification bar or know how it works. thanks everyone

I gotta say... I held off on the OTA update - threatened to walk out of the store without buying - the Shack guy relented and let me have the phone without the OTA update.
After researching it - but without experiencing the SD card issues... I was drunk and did the OTA update (and PRL update).
Since then - I swear the 3G signal has sucked. It was IDEAL and rock solid in the same geographic area before.
Before OTA update... regularly getting 1200kbps down and 1000 kbps up 3G
After - 800kbps ish down and 800kbps ish up...
The embarasing thing - is that an iphone 3gs guy is sitting next to me pulling down 1400kbps to my 800...
Having to power up 4G to blast him away with 4000kbps sucked...
Is it paranoid of me to think that Sprint would want me to use 4G instead and would intentionally throttle/limit 3G to get me to stay 4G which might be cheaper for them?
recap:
After OTA and PRL update
-about a 40% drop in 3G speeds
-have had a few 3G dropouts that I didn't seem to have for the first few days before OTA and PRL update.
Is it just me or anyone else?
Sorry- but no lags on camera options.
I do seem to see more progrs running in background... which pisses me off since they are ones I will NEVER use.

willfck4beer said:
I gotta say... I held off on the OTA update - threatened to walk out of the store without buying - the Shack guy relented and let me have the phone without the OTA update.
Click to expand...
Click to collapse
Lol, the guy at BB hit update and it started to download and i just said nope, and reached over and hit cancel lol. He just stood there for a second then continued with activating the phone.

pyr0path said:
after searching the forums, i'm kind of surprised that nobody has brought to the attention any bugs that were caused after the OTA update. here's my problem:
after purchasing the htc evo and applying the OTA update, i have been having a few issues with the phone:
1 - home screen notification bar does not work. unable to slide the notification bar down with the phone is upright. it does, however, work in landscape mode. the only way to open the notification bar is to tap the menu button and select notifications.
2 - when opening the camera or camcorder and tapping the arrow on the left side of the screen in landscape mode to change the camera settings i notice extreme lag. i haven't found a way around this yet either.
i did try a hard reset with both of the issues but no luck.
i did notice that these issues did not exists before applying the OTA update. i contacted sprint and they played dumb and told me to take it back to the sprint store where i purchased the phone and have them look at it. they seem to believe that it is also an OTA update bug. being that i have 30 days to return the phone(they are currently out of stock)i told them that i would wait until the 2.2 froyo update on june 23rd and see if that fixes the issue. however i have done a lot of searching on the internet and only came across a few other forums(none in xda-developers) where people were describing the same issues that i am having, and after everyone has contacted htc as well(including myself) we have not yet gotten any response from them. i will post any news i hear from them as soon as i do.
also there is an issue i believe everyone to be having even after the OTA update which is that apps begin to run in the background even after force closing them and killing the process using any task manager. if anyone has any current fixes please post them and help us all out. i do believe the first 2 issues that i described are pretty wide spread, but i'm assuming that they are new to the android OS and really aren't aware of how to use the notification bar or know how it works. thanks everyone
Click to expand...
Click to collapse
UPDATE:
after no response from htc and still waiting for the sprint store near my house to get a new batch of evos in stock, i decided to flash my phone with the original stock rom and radio RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253. shortly after a slight scare(downloading htc sync after installing the ruu in order to flash the stock rom, i began the flash process only to be notified that a the usb debugging driver was being installed and my computer needed to be rebooted to finish and i thought that i bricked my evo because of the messages saying 'do not interrupt' and the fact that that my phone was stuck on the boot screen until i rebooted it and booted right into the bootloader so i just ran the ruu installer again)
after flashing back to stock which the helpless employees at the sprint thought that the ota update was the issue as well as i did, i immediately checked to see if my notification bar was working. NO GOOD. i've tried the OTA update again and checked to see if the notification bar worked now. NO GOOD.
conclusion:
either one of 2 things have happened here;
1 - my htc evo is defective and has hardware issues(which weren't there before the initial OTA update) or;
2 - the OTA update has caused some sort of bug/glitch in the internal RAM which i am not too familiar with
i'm gonna start calling sprint stores first thing in the morning to see who has an evo in stock because i just because after being a dedicated android fan ever since the g1's release with t-mobile, i just can't live without my notification bar.
everyone feel free to comment if you have experienced this issue and i will keep everyone updated with what happens with the phone between now and tomorrow

Im having the exact issues the OP has. I too have the update installed. My friends task bar works, he did the OTA right in front of me and his task bar still works after. So seems to be. Select few.
When playings jewels and the phone is upright, the top row of jewels is untouchable, same reason why the task bar isnt working.
Still not a deal breaker, phone rocks regardless.

pyr0path said:
UPDATE:
after no response from htc and still waiting for the sprint store near my house to get a new batch of evos in stock, i decided to flash my phone with the original stock rom and radio RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253. shortly after a slight scare(downloading htc sync after installing the ruu in order to flash the stock rom, i began the flash process only to be notified that a the usb debugging driver was being installed and my computer needed to be rebooted to finish and i thought that i bricked my evo because of the messages saying 'do not interrupt' and the fact that that my phone was stuck on the boot screen until i rebooted it and booted right into the bootloader so i just ran the ruu installer again)
after flashing back to stock which the helpless employees at the sprint thought that the ota update was the issue as well as i did, i immediately checked to see if my notification bar was working. NO GOOD. i've tried the OTA update again and checked to see if the notification bar worked now. NO GOOD.
conclusion:
either one of 2 things have happened here;
1 - my htc evo is defective and has hardware issues(which weren't there before the initial OTA update) or;
2 - the OTA update has caused some sort of bug/glitch in the internal RAM which i am not too familiar with
i'm gonna start calling sprint stores first thing in the morning to see who has an evo in stock because i just because after being a dedicated android fan ever since the g1's release with t-mobile, i just can't live without my notification bar.
everyone feel free to comment if you have experienced this issue and i will keep everyone updated with what happens with the phone between now and tomorrow
Click to expand...
Click to collapse
I have a problem opening my camera and camcorder. Nether will open, I soft reset and still they will not open.

[Q] CM7 eventually just starts showing black screens instead of most things. Why?

This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.

Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001

Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.

bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.

dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.

I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.

I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol

Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App

I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.

[Q] Galaxy Nexus keeps crashing randomly

Hey guys, i need some advise here!
For weeks, i anxiously waited for the mailman to bring my my GNex and for a few days im very happy with it. Unfortunatly, the major plus of android, it never freezes, isnt true for my brand spanking new Gnex!
Seeming randomly, the phone freezes, refusing all input from the screen and the On/Off button. This happens about every 20 hrs.
Ususally i advise people with this problem to exchange their phone with a different one, but im afraid i wont get a stock 'yakju' build back in return, so want to try to fix (or at least determine) the problem first.
Can you guys give me some tips on how to get to the bottom of this?
Thanks in advance!
Info:
Model: Galaxy Nexus (GSM)
Android version: 4.0.1
Smalbandversion: I9250XXKK1
Kernel: [email protected] #1
Build: ITL41F (yakju)
And again, it's all stock

...
i had a lot of problems with the 4.0.1 fw, have you tried updating the phone to 4.0.2 it solves a lot of bugs!

I tried to update the phone through the system update menu in the settings, but it listed my phone as 'up to date'. I find this is odd, since i have a Nexus ánd the Google build
Is there a way of updating the phone without a lot of hassle?

I looked into it, in the Netherlands the 4.0.2 update should roll out in a few days. If it isn't, I'm going to flash it myself! Were your problems with 4.0.1 similar to mine e.g. crashes and freezes?
Sent from my Galaxy Nexus using XDA App

In my experience most of the time when that happened was caused by 3rd party apps that weren't ics optimized.
Sent from my Galaxy Nexus using XDA App

Well freezes and crashes maybe, but the whole phone unresponsive? Isn't there a try/catch somewhere which prevents this kind of 'dirty code' to crash the whole OS, anyway there should be.
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Sent from my Galaxy Nexus using XDA App

Same problem
Panatella said:
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Click to expand...
Click to collapse
That exact thing happened to me yesterday as well (running 4.0.1). I pulled down the notification bar, clicked on the email notification, and when the notifybar started collapsing again, the animation stopped, sound was caught in a loop, and two seconds later my phone rebootet with a clicking sound (I hope that it was just the speaker reacting strangely to the sudden signal loss...!)
The same day, the Nexus kind of crashed while I was streaming internet radio to my bluetooth speaker. The music kept on playing fine, but I wasn't able to turn on the screen. Even holding the vol+/- and power buttons only shut the phone down, but I couldn't restart before I removed the battery.
I really hope this is gonna be fixed with the 4.0.2 / 4.0.3 firmwares. This thing is crashing a little too often right now, for my taste

I'm getting the same problems as noted above. I've just picked up the nexus to move away from Apple's iPhones, but I'm left wondering I've made a serious mistake in doing so. An added problem is that the crash has also occurred when I've been recharging the battery while asleep- so the alarm I set did wake me.
Honestly, it's an unreliable product. I'm a customer, not a Samsung lab rat.

Got the same issue. 2 crashes in 4 days. Not a huge problem for me yet, but 4.0.3 better fix it.

Well most of my problems went away when i updated my phone. You should definitely try to update. Personalty I went straight for 4.0.3. The best ROM i've tested is definitely Android Open Kang Project :http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-13/
Everything just went so smooth and bugfree as far as i can tell. And i love the quick setting he put in notification bar.
You can see how to unlock your phone here using the gn toolkit :
http://forum.xda-developers.com/showthread.php?t=1392310

I had those kinds of crashes, too. My phone would crash maybe once every 3-4 hours on 4.0.1... doing anything. Whether it be idle, with no extra services (factory reset), or while composing messages. Anything would do it.
Anyway, I rooted the phone and I've been on Bigxie's ROM since V1 (AOSP 4.0.3) and the issue stopped, for the most part, except for an idle reboot every 18-28hrs. Suspecting it was kernel related, I swapped out the Apex kernel and threw on Franco's... since then, my phone can run for almost two days (of moderate usage) without a charge.

Any of you guys enabled 'force 2d hardware acceleration'? I don't know how relevant it is, but all my problems went away when I stopped to use this function.
Sent from my Galaxy Nexus using XDA App

Uv'ing too low can crashes also.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.

Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???

dhruvraj said:
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
Click to expand...
Click to collapse
U sure it's not a software u installed recently? For me changing back to the stock music player fixed the random crashing.
In general, I can say some apps are not stable at all.

I experience random crashes too, although they coincide with the sudden loss of signal, as described in these threads:
http://forum.xda-developers.com/showthread.php?t=1390816
http://forum.xda-developers.com/showthread.php?t=1387943
http://forum.xda-developers.com/showthread.php?p=20816554
I have started to make some logs to try to identify the cause of this problem. I use Log Collector for making a log and No Signal Alert to obtain a time stamp when the signal drops. What I see in the logs is that just before the signal drops I notice an entry in the log something like "process:com.lookout has died". Could this have something to do with the Lookout app I have installed or is it just coincidence that the app and a certain Android process have the same name?
By the way, does anybody know if there are websites or people who can analyze the logs I have created? Most of the content is mumbo jumbo to me and a knowledgeable person might be able to shed some more light on what happens inside the phone and what might trigger this problem.
I just upgraded to 4.0.2 on Thursday, but the problem persists.
Android version 4.0.2
Baseband Version: I9250XXKK6
Kernel Version: 3.0.8-gaaa2611
[email protected]#1
Build Number: ICL53F
ICS stock; non-rooted

Well i guess you tried already to remove the lookout app right?

My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.

b4cksl4sh said:
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
Click to expand...
Click to collapse
Are you sure it's the OS not some buggy/incompatible apps? I've had the phone since launch and it never froze even once. Stock 4.02 too.
And you should try out different OS. Then you will know what suits you.

2+ minute startup time

Saw a few posting for other android items but none for the GN so here it goes:
Ever since upgrading to JB, my phone takes 2+ minutes to startup. The actual time is 2 minutes 46 seconds displaying the google logo, then about 15 seconds at the multicolor X.
I had tinkered around with a JB release from Vicious a couple months before Verizon rolled their 'official' release out. At that time I also noticed an extremely long startup time, but didn't have it loaded on the phone that long so really not an issue.
But now this startup time is just insane. I made a few laps around the grocery store before the phone actually was ready to use again.
If anybody has an idea on this, please post. I can't imagine people would consider this acceptable so I'm hoping there is some resolution.
Thanks

I have a GSM Nexus and it takes a little less than 15 seconds on the "Google" screen and then another 30 seconds on the multicolored X. 4.1.2

ok so definitely not a common issue. any ideas?

Yup had the same problem after upgrading to JB on both Jelly Belly and AOKP. I would flash the JB bootloader hoping that would help but it didn't. On CM10 now and it boots right up, it's FAST.:good:

I've heard the CM10 referenced before, could you tell a bit about that in comparison to the base VZW version?

militarymedic23 said:
I've heard the CM10 referenced before, could you tell a bit about that in comparison to the base VZW version?
Click to expand...
Click to collapse
CM10 is based on AOSP, so right off the bat it is going to be very similar in terms of look and feel. And then you open the setting menu and find out how many customization options you have, and you see the built in theme engine, and realize how smooth and fluent everything is.

Seems to be random. Sometimes I have no startup delay, and other times the phone hangs at the Google screen for several minutes. No rhyme or reason, just happens. However since rebooting is not all that necessary on a regular basis, I stopped thinking about it. And my phone still works just fine.
Sent from my Xoom using xda premium

Jellybean does filesystem check and repair on boot, so if you did a dirty shutdown or something which caused filesystem errors, that would explain the the extra time taken to boot.

I decided to bump this up to CM10. although on the first try at backing up the phone it actually wiped the thing. Not quite sure what happened there.
I am opening another thread on a display problem with double clocks on the main screen.

As far as I can recall, I've shut the phone down through the software. Once in a great while I force power it off but nothing recently.
Anyway, we'll see how CM10 works.

[Q] Jelly Bean update caused problems! Need help!

So I have a Boost Mobile Samsung Galaxy S2 (Epic 4G Touch) and I recently found out there was an update from Ice Cream Sandwich to Jelly Bean. So I immediately rushed to my computer and updated the software. I absolutely love it! My girlfriend tried it out and she really liked it, so I plugged her phone in and did the update as well. Her phone is the T-Mobile Samsung Galaxy S2.
When we updated her phone (using the automated Samsung Kies update), she was not too happy with her version. She lost the "Active Applications" widget (and program it seems, we can't find it anywhere anymore; it's the one used to end programs and clear the RAM).
Instagram has a lot of problems. If she tries uploading a picture, when she's on the screen to add effects to the image and what not, she cannot see the bar at the top or bottom of the screen. We tried clearing the data, then uninstalling it and reinstalling it but that made no difference.
Also, when she tries to use the camera sometimes, something very similar happens and she cannot see the buttons on the top or bottom of the screen.
About half the time that she unlocks the phone, the screen just shows black, and you can't do anything. If you hold the power button down, it'll show the "Device options" box to restart or turn off the phone, even though the background is still showing black, so we know it's not freezing at all.
She's pretty mad that her phone is no longer working correctly cuz the update on my phone is awesome. We didn't run into any issues with the install procedure while updating her phone. I'm just trying to figure out what to do. I really don't want to wipe the phone clean and try hard rebooting it. And we really don't want to have to get it replaced.
Has anyone else had any issues with this? And do you have any ideas on what to do to fix it?

it sounds like she would be better off rooting the phone and installing the latest aokp rom which is 4.2.2
thats what i'm running right now on my t989 and its running smoother than stock