Database Users

Gingerbread issues

Anyone experiencing any? Sometimes if i dont restart my phone for 2days my phone gets weird.
1. when someone calls screen stays black till i slide it when i think the sliders at.
2. same with messaging black screen till i just randomly press on the screen and it opens.
Also same when i do my slidepattern lock i have to guess where the dots are.
Then phone gets sluggish to go back home screen
Anyone else experiencing this?
I am not rooted. Also i installed the update manually.

very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.

by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?

yes, very random things happen after a few days on stock gb - i have to reboot and/or kill the launcher every so often. find gb battery life sucks too.

Damnit i might have to reset and stick to 2.2 till this fixes its annoying. You say this is also present in cayenmod(sp?) 7.0?

sotorious said:
by call wonk bug do you mean where someone calls and the screen is just black, and if you slightly move the slider to answer the phone the screen comes off of black?
Click to expand...
Click to collapse
well not exactly, but similar. the "call wonk" bug has been plaguing AOSP versions of gingerbread for months now, and nobody can fix it. until this thread, the "wonk" problem is only present on AOSP version, NOT the OTA version of gingerbread from google. some people dont experience it, like me, and some do. it varies as to what exactly happens with the wonk, so i cant give a good description. but i'm not sure your problem is necessarily the same issue. seems similar, but possibly something different.

I've been having the same issues lately. It's very similar to the Gingerbread keyboard bug where the popups stop showing when you press the keys or hold a key to get the menu of other characters. It's actually still there, and you can try to guess where the character you want is and hope to get it... but it doesn't display. This can be fixed by killing the Android Keyboard process.
I'm seeing similar things in other places on my phone. Today, after not having rebooting for quite a while, the unlock slider wouldn't slide. Swiping my finger across where it should slide still unlocked the phone, but nothing animated to show this.
I went to change my News & Weather widget refresh interval the other day and the screen went dim (like it does in behind a select list popup), but nothing showed... however, the popup was there... and by guessing the location on the screen I was able to hit the refresh interval I wanted (after several attempts).
I've noticed the same in a few other locations that I can't remember right off. Basically, something is supposed to show on the screen, but doesn't... yet the phone still reacts properly as if it were there. Just like the keyboard bug.
It could be some kind of screen refresh bug... in my case (completely stock... updated manually to 2.3) it's definitely not any kind of call wonk as experienced in AOSP builds (unless this is the root cause of those wonks, but I somehow doubt that).
Thankfully, I haven't had any battery life issues with Gingerbread. Maybe even a little better battery life (or maybe just placebo effect).

^^^ ditto that entire post.
At first noticed it with the incoming call screen, and then the keyboard.
Easy to fix, but is a huge annoyance. Often can't see who is calling and end up answering blindly which is BS.
I'm now starting to see it in apps all over the place. Tower Raiders 2, Market, Messenger, and probably more I'm forgetting. Having to reset every couple days is becoming almost a necessary inconvenience.
Battery has been perfect, contrary to many. I did see a noticeable drop in Quadrant score switching to GB, but overall feel of performance has probably been better. Swype for some reason stopped working, similar to what happens after you update, but nothing has updated since? Regardless I'm sure an reinstall will fix.
Nothing but stock for me btw.

RogerPodacter said:
very weird, does this mean you have the call wonk bug on stock GB rom? maybe some others can reply and confirm. but cm7 users have a similar call bug that isnt known to be present on the stock ROM.
Click to expand...
Click to collapse
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.

[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
Probably the reason that thread hasn't been acknowledged is its a cluster of people with this 'issue', but claiming to be on OTA 2.3.3 and AOSP-based CM7..
My understanding of what is defined as the 'wonk' (which I experienced when my N1 was on CM7) is
15-20 seconds where the caller can't hear me, usually resulting in a hang up after about 10 seconds
call comes in but no slider to answer
That thread is describing a 2 second delay after the call connects, which I have NOT experienced on OTA GRI40 but would be manageable if I did. The 'wonk' as described above makes a cell phone unusable and I personally haven't seen a report of the 'wonk' on OTA GRI40. More importantly for myself, I have not experienced it in over a month of use..

Yea well the g2x is coming out next week or so and i mean it is on 2.2 which i guess i am fine with and if or when gingerbread comes to that hopefully all the wonks turn into woos!

I've had the keyboard issues randomly, and this week I had the issue where the screen is black when a call comes in. As someone before me mentioned, this is not the CM7 "wonk" and an issue with 2.3.3.

[email protected] said:
I'm afraid the call "wonk" bug is also on the stock Google ROM for "some" Nexus One users. See here:-
http:***//code.google.com/p/android/issues/detail?id=15297
(remove "***" as I cannot post links yet)
Personally I've never experienced it. There are lots of theories about this "wonk" and its cause.
Cyanogen has been battling to find an answer, even though he cannot replicate it himself.
One theory is that it comes about by not fully wiping the handset and SDcard before installing 2.3 for the first time and then not re-installing anything from a previous backup but rather doing a piecemeal restore on both phone and SDcard as if the handset were new.
I have to admit that, being an ex Nokia symbian user, this was the approach I adopted as not doing so on the symbian platform caused no end of problems.
Click to expand...
Click to collapse
the 2 second delay is not the "call wonk" people are experiencing on AOSP versions. the wonk is where the whole phone screen goes black for 30 seconds, and anything that uses the mic crashes or doesnt work. this 2 second delay when answering is an issue, but a different one, and commong to all 2.3.

If you're having the call delay problem, especially on a device that is not the Nexus One, please star the issue here:
http://code.google.com/p/android/issues/detail?id=16230
This is a known bug with Gingerbread, that Google recently declined, saying it was "device specific" (to the Nexus One).
However this problem is also being reportedly widely on the HTC Desire, as well as Samsung Galaxy devices. I have posted a new issue above and not attributed it to a specific device.
Please comment and star this issue. And please specificy especially if your device is not the Nexus One, so that Google gets this message that this is a widespread Gingerbread bug, which has nothing to do with the device.
Thanks.

The Google employee following up on the call delay issue, in the Google support forums, is asking people to fill out the following form, to gather information about how people are affected and on what devices.
http://goo.gl/10HJ1

I updated to GB right away, and I am just now annoyed enough to come post in the N1 threads.
Issue 1:When a call comes through the screen goes black. I will press the power button and the screen pops back up, displaying the caller info.
Issue 2: Sometimes (not all the time) when I close an app, any app, the home screen is blank with just the wallpaper picture showing. Again I press the power button to "sleep" the phone, press the power button again, slide to open and all of my short cuts and widgets are back to normal.
Issue 3: I also have the delay when answering. I have learned to play this off by bringing the phone up to my ear a little slower.
Issue 4: The trackball is extremely slow (unusable pretty much) in certain apps like Dolphin Browser HD, Yahoo! Mail, among others. This is mainly when I want to select text and use the Froyo trackball, click, drag, click method as opposed to the GB dragging of the little orange boxes...which I find the GB method more difficult anyway.
I will edit my post as more things come to mind.
My N1 is not rooted, btw.

Android 5.1.1 is here (according to website)

According to the Verizon website, LMY47X.N910VVRU2BOK3 or android 5.1.1 is finally here. I haven't recieved it yet but here it is on the site.
I apologize for my English, I am writing this whilst walking through the halls.
EDIT: So far, the phone runs smoothly and the battery life seems to be much better. I will edit as I use the device more.

If this is true this made my day lol

Yep, its true. I looked at verizons update page as well. Anxiously awaiting them to open the flood gates so we can update!

IIRC, they usually open up the OTA floodgates around noon-2PM EST on the day of the announcement. Or rather, there's usually a 12-14 hour delay after the post the announcement to when you are able to pull it manually. Though sometimes Kies beats everyone else to the punch. I am still shocked that this is rolling out. I hope it's a ROCK SOLID update because I have a feeling we won't see Marshmallow for the Note 4 for another 6-7 months (if at all).

The update is live. Im downloading right now

Nice!! Me too

Downloading it now.

Where?, when?, how? :crying:

I just checked, upgrade available, downloading now on my unlimited data getting f'd by Verizon

hey btw anyone who installs... first off, is recent apps not laggy anymore? my mom's note 5 is instant and that's on 5.1.1. also, did they change the dpi? her status bar icons are much smaller.. better for the big screen!
Sent from my Note 4

Installing now. Wonder if this update will be good enough to pull me away from my Droid Turbo 2?
QUOTE=jayochs;64755819]hey btw anyone who installs... first off, is recent apps not laggy anymore? my mom's note 5 is instant and that's on 5.1.1. also, did they change the dpi? her status bar icons are much smaller.. better for the big screen!
Sent from my Note 4[/QUOTE]
Note 5 has more ram, a better SoC and the 5.1.1 software was built from the ground up for it, not an update. I will let you know how it performs, I'm installing it now.
Edit: Still got that terrible red boot screen
Edit2: Everything seems to be running a touch smoother and responding a bit quicker. It seems to match my DT2 in a lot of actions now.
Edit3: Antutu score 52710 (3d:10178 UX:19595 CPU:18521 RAM:4416). No benchmarks on 5.0 My DT2 gets a 67998 (3D:24801 UX:24185 CPU:15592 RAM:3420)

Got it. Will download when at home

Ugh, that annoying "Wifi is connected" constant notification. Does anybody know how to get rid of it?

Oh and they didn't remove all references to AT&T. LOL

This update is so smooth already. Wow. I was incredibly fed up with how slow my phone has been lately. Hopefully this fluidity will last.

bbeelzebub said:
Ugh, that annoying "Wifi is connected" constant notification. Does anybody know how to get rid of it?
Click to expand...
Click to collapse
Try going to Settings, Wi-Fi, tap the three lines to the right of the 'on/off' switch, tap Advanced, and uncheck Wi-Fi Notifications. That should keep the notifications from popping up at the top of the screen.

will4958 said:
Try going to Settings, Wi-Fi, tap the three lines to the right of the 'on/off' switch, tap Advanced, and uncheck Wi-Fi Notifications. That should keep the notifications from popping up at the top of the screen.
Click to expand...
Click to collapse
That does not work. Mine was already unchecked

You can swipe it away. It won't come back till you reconnect to the Wifi.
Edit: Never mind, they changed it. You could swipe it away in 5.0.

I have never done a factory reset in the 1 year + I have owned this, don't feel like setting up everything again, I may go ahead and do this just to be safe.

At least on mine, the recent apps delay is pretty much gone and hitting it is instantaneous.. And knock on wood, the device is running pretty smooth..
from my note 4

Notifications unreliable... any ideas?

I'm running 4.4.4 on a Samsung Verizon S5 paired with a Moto 360 2nd Gen running 6.0.1.
My notifications seem to be very unreliable. The biggest pain is that I can't seem to find any pattern to what happening. Here's what might happen after any notification comes in:
Vibration on the watch, followed with NO notification showing on the watch display.
Vibration on the watch, followed by notification displayed as I would normally expect.
Vibration on the watch, followed by a displayed notification, but the display comes 4-6 seconds AFTER the vibration.
Vibration on the watch, followed by a display of the PREVIOUS notification, which then flips to the current notification after about 4-6 seconds.
As I said, it's really annoying because I just can't seem to pin down exactly what's causing the issue or any sort of pattern for when it works, when it sorta works, or when it fails totally. This happens with all notification types to varying degrees. GMail, Outlook, CloudMagic, Hangouts, SmartThings... to name the programs I regularly get notifications from.
The only non-standard thing I'm running on my watch would be WatchMaker Premium. I don't have any app launchers running on my watch.
I've tried uninstalling outlook (as someone in the Android Forums suggested). I've tried a factory reset on the watch. I've tried uninstalling, reinstalling Android Wear on the phone. I've tried re-syncing apps... Just not having any luck figure out what's going on.
Anyone else experience anything like this? Anyone have any suggestions/thoughts?

100% the same for me on my sw3. Sad that 1.4/6.0 doesn't fix it.
I've sent feedback via the app. There's also a couple threads about it on the official forum.

sirrelevant said:
100% the same for me on my sw3. Sad that 1.4/6.0 doesn't fix it.
I've sent feedback via the app. There's also a couple threads about it on the official forum.
Click to expand...
Click to collapse
I suppose it's comforting to know I'm not the only one experiencing this. What phone/os are you running?
I'm wondering if upgrading to a new version on my phone would help at all. An 'expert' in the official forum said it shouldn't make a difference, but at the same time it shouldn't be acting like it is, so I dunno.
Just really frustrating cause "glancable" notifications is one of the big pluses of a smartwatch and right now it just isn't working.

Another question: Which service are you using? I'm on Verizon. If you aren't that would eliminate service as an issue.
(Yes, I know that service shouldn't be an issue... but maybe whatever programs/radio/whatever Verizon pushes on the phone might somehow screw with things??)

FWIW, I flashed a new 5.0 rom last night. After lots of effort getting things back up and running (mostly), I'm getting proper notifications. Not sure why, but something in the process of flashing got things working again.

RedRamage said:
FWIW, I flashed a new 5.0 rom last night. After lots of effort getting things back up and running (mostly), I'm getting proper notifications. Not sure why, but something in the process of flashing got things working again.
Click to expand...
Click to collapse
Same issues with my Verizon S5 and 360. How did you downgrade the moto 360 from 6.0 to 5.0? I saw the forum about it but it wasn't clear.

help me understand

hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please

honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.

244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.

biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!

Is there a root app to disable it or not

biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate

Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug

Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.

thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing

biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.

Notification light (front camera light)

Guys, if I understand well, Samsung sad that they will fix issue with notification light with July patch. 2 days ago I receive that update but still notning. Does anyone of you konow the reasons for delay or any other info about this...I really dont wanna use Good lock, nice lock or any 3rd part. app, I just want default option for this like they sad we will be able to use soon (July patch shold fix it, bit it doesent)...
[emoji48][emoji48]
Sent from my SM-G975F using Tapatalk

Opus Dei said:
Guys, if I understand well, Samsung sad that they will fix issue with notification light with July patch. 2 days ago I receive that update but still notning. Does anyone of you konow the reasons for delay or any other info about this...I really dont wanna use Good lock, nice lock or any 3rd part. app, I just want default option for this like they sad we will be able to use soon (July patch shold fix it, bit it doesent)...
[emoji48][emoji48]
Click to expand...
Click to collapse
They've been saying they'll implement something since they released the phone. I'm not holding my breath for it anymore. So now, if it does happen it'll just be a nice surprise for me.