Database Develop

[Q] Stock 2.3.3 issues [other than battery problems]

Note: I just blogged about it and planning on posting on few Googler's twitter to see if we can get some attention to fix these issues, if they already haven't started looking in to these! If you are interested, please visit "Is the latest Gingerbread (Android 2.3.3) OTA update for Nexus One buggy? "and share your experience with Android 2.3.3 on your NexusOne's the Android team can get a bigger picture of these issues! More the merrier!
By now, I have reset to factory default couple of times but still after about 50hrs of usage my Nexus One starts acting freaky! Performance slows down, launching apps gives me black screen, lock screen freezes until I receive a call and not answer it and finally forcing me to reboot the phone.
Is anyone else aware of these issues or experiencing these issues?

I've had a few, repeated issues since upgrading to Gingerbread:
The stock messaging application will sometimes crash after sending a text message. The message gets sent, but the program closes out and returns me to the home screen. When I try to get back into the app, it animates like it is opening, animates like its closing and then gives me an error message about it not responding. I have found the only way to get rid of this is to reboot the phone.
Occasionally, all of the items - icons, widgets, etc - will disappear from the home screen. All I can see is my background image (just a plain JPEG, nothing animated) and cant get anything else to happen. I've tried to give it a few minutes (coming from Windows Mobile, I've learned to be patient) but it never came back. As expected, only a full reboot of the phone fixed the problem.
I've been having strange WiFi and data connection problems. Sometimes when connecting to WiFi it takes several minutes to establish a working connection; however most times it is pretty instant. The data connection will sometimes completely drop out and not come back on its own - even in areas with known good signal (I'm on AT&T, insert jokes here). Again, the best solution I've found is a full reboot.
I have heard some reports from friends that they have experienced issues with Exchange support after the upgrade, but I haven't seen it personally. Other than those above issues (which are very annoying) Gingerbread is has been OK. As I like to tell everyone, I'm sure glad my phone makes a cool TV of animation but can't seem to want to send text messages... Thanks Google?

monkeyboy0076 said:
I've had a few, repeated issues since upgrading to Gingerbread:
The stock messaging application will sometimes crash after sending a text message. The message gets sent, but the program closes out and returns me to the home screen. When I try to get back into the app, it animates like it is opening, animates like its closing and then gives me an error message about it not responding. I have found the only way to get rid of this is to reboot the phone.
Occasionally, all of the items - icons, widgets, etc - will disappear from the home screen. All I can see is my background image (just a plain JPEG, nothing animated) and cant get anything else to happen. I've tried to give it a few minutes (coming from Windows Mobile, I've learned to be patient) but it never came back. As expected, only a full reboot of the phone fixed the problem.
I've been having strange WiFi and data connection problems. Sometimes when connecting to WiFi it takes several minutes to establish a working connection; however most times it is pretty instant. The data connection will sometimes completely drop out and not come back on its own - even in areas with known good signal (I'm on AT&T, insert jokes here). Again, the best solution I've found is a full reboot.
I have heard some reports from friends that they have experienced issues with Exchange support after the upgrade, but I haven't seen it personally. Other than those above issues (which are very annoying) Gingerbread is has been OK. As I like to tell everyone, I'm sure glad my phone makes a cool TV of animation but can't seem to want to send text messages... Thanks Google?
Click to expand...
Click to collapse
You are right, I've been having those home screen issues as well, though my wifi connectivity seems to be fine so far.
Sent from my Nexus One
http://mindmirror007.blogspot.com/p/home.html

I can confirm Gingerbread on my N1 facing similar problem. Riddled with bugs such as battery drain, Wifi, Exchange Server, Date format on Notification Bar, Awake forever, just to name a few.
REverted back to 2.2.2 More stable amid less 'cheeky' in term of UI.

Also had force close issues with launcher and other programs getting a black screen after about 2 days without a reboot. Got tired of it and went back to Froyo

I've had trackball notification issues. First it stopped working entirely. After a restore it now only blinks notifications if the screen is off. Once the screen is turned on (even if the phone isn't unlocked) it stops. If the screen is on when the notification is recieved nothing happens.
I'm experiencing battery drain that i believe is associated with maps and location services (the alogcat shows it checking in all the time!).
I've had the launcher become unresponsive to touch. You can use the trackball to navigate, its slow, and once you're inside an app it works fine. Need to restart.
I've had the blank keyboard show up and need to restart.
I'm probably going to switch back to 2.2.2 tonight...

Wow! The issue seems to have touched a lot of NexusOne's. I just blogged about it and planning on posting on few Googler's twitter to see if we can get some attention to fix these issues, if they already haven't started looking in to these! If you are interested, please visit Is the latest Gingerbread (Android 2.3.3) OTA update for Nexus One buggy? and share your experience with Android 2.3.3 on your NexusOne's the Android team can get a bigger picture of these issues! More the merrier!

I have also been affected by the "black screen" problem after about 48 hours uptime. Returning to the home screen shows just the wallpaper and no icons. Pressing the "Home" button worked for a while to bring back the icons, but eventually most apps started showing some black screens and I had to reboot to fix the problem. I'm sticking with Gingerbread 2.3.3 for now, but it is disturbing after the multi-week uptimes I was getting under FroYo 2.2.2.

[Q] Trouble Calling on 9.5

Hi Guys,
I installed Darky's A few weeks ago and done a reinstall recently because I seem to be having a problem making calls and the screen lock.
When I make a call wether it be using the speaker or not the screen goes dark after about 20 seconds after the call is initiated then a few seconds later the screen lock kicks in and disconnects. I have reinstalled the rom and updated to the core 1.4 but no matter what I do it still does it.
Does anyone know of a fix for this? It seems to be just when making calls. In a call it's fine but making one it does it every time.
cheers

Well reflashed Darky's 9.5 set it all up, Set the screen timeout to 10 minutes which works for 10 minutes until I try make a call then it lasts about 10 seconds.

Installed v10 rc6 and the problem has gone

[Q] Phone kinda reboots with incoming call

I upgraded my Captivate to gingerbread/talon/continuum yesterday.
That went fine and everything was hunky dory.
Phone was working fine the whole day today, incoming/outgoing calls, data.
I came home and installed Skype and thats when all hell broke loose.
Now the phone part is dead (kinda!). I can make calls fine but if I get a incoming call, the call gets disconnected after 1 ring and I get a msg popup (like some error) but I cant really see what the message is.
I also noticed that it disconnects me from ATT network when a call comes in and then after a little bit it reconnects.
I also verified this by going to the About->Status screen and then making a call.
It normally says ATT but for a couple of secs after call drop it says 'Unknown'.
What did I do to screw it up and how can I fix it?
Thanks

Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK

mommehK said:
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
Click to expand...
Click to collapse
Sorry, I should have added that to my first post.
Yes, I did uninstall Skype and reboot the phone, just incase, but no difference.
Still the same.

Update:
After playing around with various things for a couple of hrs, I finally gave up and reflashed Continuum.
Everything started working again.
Applied my Ti backed up config and loaded Netflix. Same problem. Dialer died with an incoming call.
I reflashed Continuum again and everything started working as expected.
I then applied my Ti backup, still everything working.
I am in the process of updating all my apps and then lets see if everything is still working.
The only thing that is missing for now is the Netflix app.
I will keep everyone updated if its the Netflix app causing the issue or its the Skype.

activemind: Keep us posted if you find a cause. I am on a Samsung Vibrant (3g) via TMOB but have been having the same issue today with a completely different rom (simply honey). This is actually about the 6th thread I've found in the past two days having this same issue on Galaxy S phones.

I have had this problem before and what caused it was restoring system data with titanium. Make sure you are only restoring apps.
Sent from my GT-I9000 using XDA Premium App

Caller ID and Outgoing call issues

Hey everyone,
I'm having 2 separate issues that I don't think are related, but could be. I have an unlocked Droid 3 XT862 running on Rogers (in Canada) that has been upgraded to 5.6.890.
1) Since upgrading the OS, whenever I get a call from someone that is not in my address book, the caller ID always shows up as Pay Phone. I've tried a battery pull and checked all my call settings, but to no avail. I've considered reflashing back to the stock OS, but don't want to deal with the shoddy battery life.
2) Whenever I make a call (and this has happened since day 1), it goes to the call screen, then says call ended and goes to my home screen. About 2 seconds later, it goes back to the call screen, and makes the call as expected. So it will make the call, but with a ~3 second delay.
If anyone has any insight into these problems, I'd be happy to hear it!

As a followup for anyone that's on Rogers (in Canada), the call display issue was related to a feature called 'name display'. Apparently it's incompatible with the majority of android phones, so if you're having issues with call display, try disabling it.
Sent from my XT862 using XDA App

Second update, no improvement with the 'call ended issue'. Not a big deal, but still strange. Same deal with stock OS, Liberty rom, CM7, and CM9 alpha 1 and 2.
Sent from my XT862 using XDA App

[Q] phone calls cause sluggishness, freezing, and crashing of phone app

I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.

tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.

schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-

When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app

Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.

tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.

I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.