Database Develop

FRF91 update is buggy

After updating to FRF91, I notice two things.
1) My phone froze at least 3 times since the update when I tried to make a phone call. I had to remove the battery and restart it.
2) My calls are now less clear even with my blue-tooth. When I call someone, they and I will hear static. Sometimes the static is really bad. (no, I am not holding it the wrong way )
Anyone have similar issues?
My Nexus One is NOT rooted.
stock 2.1 to FRF50(manual install)->FRF83(manual install)->FRF91(OTA install)

No issues here. Clean install.

I would agree it seems buggy to me also; it could be the manual update path of updating, but im def getting some wonkyness.
When im on edge at my house, it always seems like WIFI is on demand and not connected (This differs from what my phone used to do and i also have wifi to never sleep); so when i try to access something intially i get a network error then the Wifi connects; then i connect even though im on edge which used to connect albeit slow.
A slight jerkiness when I longpress to remove widgets; don't remember that one previously.
Very erratic battery life; seems to be due to network switching from 3g to edge to wifi; can't really confirm that though; not real rogue apps on my device that are running, but who knows.
Car dock has been giving some force close issues from time to time which didn't really occur previously.

FRF83 more stable
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.

Falen said:
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Click to expand...
Click to collapse
let me know how that works out; I may do the same. Maybe go back and ota update.

I applied the full FRF85B when I did mine, and wiped cache / format user data from the boot loader. That cleared up issues.

gmail stopped working properly for me.

I have had some issues with my phone freezing up too but my trackball would still flash when i got alerts. I think it might be related to trackball alert because now that I have uninstalled it i haven't gotten any freezes.

I did the factory reset and I no longer have any problems. I am still waiting to see if my dialing still freezes randomly though.
Sent from my Nexus One using XDA App

I'm still on frf83 and found that flashing the frf91 gapps has somewhat reduced the freezes/reboots.

My XDA app freezes for a couple of seconds before it responds. Is this app up to date for frf91?
Sent from my Nexus One using XDA App

1. Going into Gmail it takes forever to display emails (usually shows the "loading icon" for 10-20 seconds) as if it is only then connecting to the server and downloading new/old emails.
2. Caller ID still does not keep settings when rebooting.
3. Task Managers don't actually seem to kill tasks anymore. Have tried multiple with settings to auto-kill 10 minutes after the screen goes off ... 5 hours later the programs are still running. Obviously just KILLS battery life.

nexusdue said:
Obviously just KILLS battery life.
Click to expand...
Click to collapse
Yeah, obviously, you're using auto-kill, it probably tries over and over and over when they don't actually close.
Stop using auto-kill. Even if it worked you will get less battery life by killing tasks. Read up about it. Only reason to EVER kill something is if it isn't acting nicely and has a bug that keeps using CPU or keeps the phone awake.

Factory Reset works almost all the time
If you got problems after update you should allways wipe (factory reset)

[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] Unusable phone, phone freezes and launcher restarts constantly

I wish I could explain better what I did, but I can't figure out what it might be.
I am running Captivate rooted, mostly stock 2.2 with a modded camera app, and sideloaded apps allowed (for the Amazon market). The behavior is this:
Phone takes about 5 minutes to boot, was previously booting in maybe 1-2 minutes before launcher comes up. Launcher loads and i have a slow but usable phone for 30 seconds then phone freezes, and maybe a few minutes later, launcher will restart. this whole time, i am getting double vibrate every few seconds, like something is freezing/crashing in the background (that's my best guess). I disabled all Widgets in both launchers and it does not hookup via USB once it freezes, but will charge.
This is happening with Samsung TWlauncher and with LauncherPro. Thinking this was a LauncherPro issue, I switched default launcher to TW, but same behavior occurred. I also uninstalled LauncherPro, but still no change in behavior for default launcher. I would like to try to get back to a usable phone, or if worse comes to worse, get my data off the phone before reinstalling either stock, CM7, etc. I do not have a phone recovery as I could never seem to get the clockwordmod recovery to install, so I only have reset user settings as an option from default recovery mode.
The only thing I can remember doing when this started was changing LauncherPro memory presets to see if it would stop restarting often, so I thought maybe LauncherPro was the issue, but it does not appear to be.
I reinstalled LP during a few hour period of usability, but then it occurred again and it took all day to have the right moment of unlocking my phone and getting to be able to uninstall LP before it froze again. If I wait too long to unlock, it is frozen until I restart or pull battery and try again at first bootup before the launcher goes crazy.
My main question is this:
Is there a way to determine which app is causing the problem, pull logs, etc. when the phone is off, and does not connect on USB (when it's frozen)?
If not, is there a way to pull data under same circumstances? (I'm guessing this is tied into the first answer)
If these all fail, I guess I will probably go to CM7 and try that out, but I have a hard time finding out what known issues there are as it still appears in unofficial status, since there's no downloads from the Cyanogenmod site.
Any help or advice is greatly appreciated. This has been a hard one to search for, so if anyone knows of other instances of situations like this, I would be glad to see what else was encountered. If I have this in the wrong forum, please forgive me.

[Q] Disable library sync?

Does anyone know how to disable the Nook library sync in the stock ROM?
It seems that every time I do something full screen, it stops and syncs with that grey box in the corner.

Update
Just an update.
If you open the library, hold down volume up and click Library, a button will appear. This will let you sync manually and it seems to delay automatic sync. It doesn't eliminate it though and it will pop up again, just later on.
If anyone knows more info on disabling it, please let me know.

That was one of the factors the led me to flash stock rom with CM10.1.
I believe someone tried to disable it but it kept coming back...
Combining this with performance and other issues with the already quite limited stock rom, I decided to rid of it permanently and go with CM10.1.

I was able to get rid of most of the BN malware as described in my thread: http://forum.xda-developers.com/showthread.php?t=2318487 but it took some doing. I tried CM 10.1 first but unfortunately for me, it kept complaining that "System UI has crashed" repeatedly when I launched it. My tablet now runs fine except the call-home messages that I see in "adb logcat".

Joe USer said:
Just an update.
If you open the library, hold down volume up and click Library, a button will appear. This will let you sync manually and it seems to delay automatic sync. It doesn't eliminate it though and it will pop up again, just later on.
If anyone knows more info on disabling it, please let me know.
Click to expand...
Click to collapse
I am using Nova Launcher, went into Library app, but wasn't able to get the button to show up.
Tried stock nook launcher, couldn't get anything to happen wheb pressing and holding vol Up and Library either...

You may not have this problem anymore and my response is quite late, but I only got my Nook hd+ few days ago. I too had this problem and I found out that freezing CloudService.apk solved the problem, but after freezing you can't click on anything in Library app.

My nook says sync is currently experiencing problems. It will be back shortly. That has said that for almost 3 weeks now. Is there anyway to fix it or get rid of it? I haven't been able to play my jigsaw puzzle game since this happened.

Keyboard Malfunctions

Okay, I've got several Samsung Keyboard issues, so bear with me as I explain as it may be a bit long.
First and foremost, my keyboard keeps crashing. At first, I assumed this was just a general issue that a reboot was necessary in order to fix. This is entirely not the case, as it even happens directly after a reboot at times. Also, they keyboard crashing happens in several different ways. This normally happens while using Kik messenger, but it does happen at times while using normal text messaging as well, so I'm assuming Kik isn't the problem.
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
I'm unsure what's going on. I am running a rooted system, so I'm guessing it may be some issue with the root combined with something I've installed, but I'm unsure what it could be. Keyboard was (and has been) working fine for months and months, and I haven't installed anything new since the day I rooted.
I'm rooted with Rooted Community Rom. I've not had any problems with this root since I've installed it, so I don't know what the Hell is going on. Any input would be wonderful, especially if someone could tell me what's causing this to happen, or if others have this issue.

BobScramit said:
1)Normal keyboard crash, where it gives an error and the phone tells me it has stopped working.
2)Keyboard entirely disappears, yet I can still type by touching the black area where the keyboard would normally be.
3)Keyboard doesn't disappear, but text entered doesn't appear inside the text box until after closing the keyboard.
4)Keyboard crashes normally, causing either (2) or (3) to happen.
Click to expand...
Click to collapse
I'm thinking 1) is due to Low Memory causing Force Close (due to many running apps) or the Keyboard App data somehow got corrupted and 2) and 3) are happening due to GPU not being able to draw the Keyboard and letters when called upon; can't entirely be sure unfortunately.
I can think of two solutions to try however:
Clear Data and Cache of Keyboard App
Go to Settings -> Apps -> ALL -> Keyboard
Select Clear data and Clear cache
Reboot or start a messaging app and start typing again
Try another Keyboard App
Many options available, try: AOSP Keyboard, Google Keyboard, Swype
Hope that helps!

Clearing it and letting it reload does fix all of the issues, but it just happens again shortly after. I don't have very many apps, and normally still have around 100MB RAM free at all times. I don't use social media or anything on the phone at all, and most everything else is just Google things, Kik messenger, and stuff pre-installed on the phone(Like the normal sms app, phone app, etc) Reboot, clearing memory, etc, all have the same result. Fixes the problem, only for it to happen again shortly afterward. Sometimes, in the case of the keyboard going blank, clearing memory doesn't fix the issue. It re-loads with a blank keypad. Doesn't happen very often, but it did once or twice today.
I've tried using Swype since it's already pre-installed, but it's not really the same size as the standard keypad and it's difficult to adjust to typing on it :\ I suppose I'll have to make due with using it for now, because that keypad doesn't seem to freeze or crash at all as I've used it (wasn't for very long, but the normal keypad tends to crash at least twice within the span of an hour if it's used regularly).
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol

BobScramit said:
It wouldn't even be a problem if it wasn't happening so damned often. I'm used to things crashing at random, because having a load of apps (before) caused it to make things crash sometimes. But this is definitely not a "sometimes" issue. It's a "Please God, make it stop" issue lol
Click to expand...
Click to collapse
I know how that feels. I remember experiencing those keyboard symptoms you mentioned in the past. Frankly, I couldn't leave the stock ROM fast enough.
You should try AOSP or Google Keyboard, the keys are bigger and appear less confusing than Swype.